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.

ruckus over 7 years ago

Thanks for the query. We had some work on the infrastructure last week. Do you know when the issue started?

- - - - - - - - - - - -

Communities Moderator, SOPHOS
Knowledge Base | @SophosSupport | Video tutorials
Remember to like a post. If a post (on a question thread) solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel
Slawski over 7 years ago in reply to ruckus

Unfortunately I have noticed this after moving my mail to my own infrastructure (two weeks ago). I didn't have control over this kind of stuff before.

You can PM me for log details.

Regards,
Slawek
Cancel
Vote Up 0 Vote Down

Cancel
ruckus over 7 years ago in reply to Slawski

Thanks. PM sent.

- - - - - - - - - - - -

Communities Moderator, SOPHOS
Knowledge Base | @SophosSupport | Video tutorials
Remember to like a post. If a post (on a question thread) solves your question use the 'This helped me' link.
Cancel
Vote Up 0 Vote Down

Cancel