SupermanInNY
Verified User
- Joined
- Sep 28, 2004
- Messages
- 419
Hello all,
Something in gmail changed.
Until few days ago,. all my clients used
mail.theirdomain.com
for their SMTP and POP3 servernames which would resolve to the same IP (same A Record values).
Now,. looks like gmail tightened the restrictions, and seems like if you don't put the hostname (whatever replies in your telnet yourservername.com 25)
in your SMTP hostname of gmail, then you can't authenticate the email account.
Has anyone encoutered this issue?
It forced me to have an SSL (letsEncrypt) for the hostname:
While this by itself was a small hassle and not an issue, the big problem my clients are having is that they all must now change their
login info their gmail/outlook setups from : mail.theirdomain.com to server.myhostingservername.com (I like appending the word server as the hostname).
Is there any other option on how to resolve this issue that you know that would not require all clients to start changing their values?
Something in gmail changed.
Until few days ago,. all my clients used
mail.theirdomain.com
for their SMTP and POP3 servernames which would resolve to the same IP (same A Record values).
Now,. looks like gmail tightened the restrictions, and seems like if you don't put the hostname (whatever replies in your telnet yourservername.com 25)
in your SMTP hostname of gmail, then you can't authenticate the email account.
Has anyone encoutered this issue?
It forced me to have an SSL (letsEncrypt) for the hostname:
While this by itself was a small hassle and not an issue, the big problem my clients are having is that they all must now change their
login info their gmail/outlook setups from : mail.theirdomain.com to server.myhostingservername.com (I like appending the word server as the hostname).
Is there any other option on how to resolve this issue that you know that would not require all clients to start changing their values?