Reolink updates Learn More
Meet Reolink at IFA 2024! Learn More
Reolink Q&A Learn More
Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.
Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).
This is an issue that is very frustrating. Some email servers require a login ID that is not the same as the email address, so for example your email address might be in the normal form (I can't quote an example as this board doesn't permit "links") but your login ID might be "user", or even something unrelated such as "loginID". However the Reolink built-in email client only supports the following fields:Sender Name (not functional as such, just displays as the name of the person sending the email)Sender Address (this is used in two ways, for the address from which the email has been sent AND as the login ID for the mail server)Password (the password for the mail server account)Recipient Address 1, 2 & 3 (great to have three addresses)To be compatible with all mail servers there needs to be another field, which is UserID, or LoginID, whatever name is chosen for it. This would be the ID which is sent to the email server when the email is sent if authentication is required (as it should be in most cases for security reasons and to avoid your server being used for spam). Without this you can ONLY send emails via servers which use the email address as the login ID, which is most definitely not all of the servers which people use.I can imagine that Reolink think it is simpler and maybe less confusing to not have this separate field, but the tradeoff is that the client just doesn't work with many servers, which is in my view not a good tradeoff!Quite apart from anything else, it is a definite security plus to have a different login ID than the email address, as many bad actors who try to gain access to your mailbox, or send spam, will default to trying to log in using your email address as the login ID. Having a different loginID makes it MUCH less likely that someone will be able to do either of these bad things, unless of course you succumb to a phishing attack. But you are much less susceptible to a simple trial and error attack by a bad actor. So having a different loginID is actually a really good thing, and I don't think that Reolink should prevent their users from using mail servers which are like this, as they do.
Welcome Back!
Hi there! Join the Commnunity to get all the latest news, tips and more!