This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Community mailing fails to send proper HELO/EHLO.

I've just spotted on my mail server that all notifications from Sophos Community are rejected due to bad HELO/ELHO. The mail server introduces itself as xxxxxxxx.saas.telligent.com but that name does not exist in DNS so connection is rejected. I know that this kind of check is a little bit strict but it fends off many spammers.

BTW: xxxxx was used to hide the real tenant name.

Correct me if Sophos do not have anything in common with that mailing.



This thread was automatically locked due to age.