Saturday, 27 October 2018

The response from the remote server was:553 Message filtered. Refer to the Troubleshooting page at http://www.symanteccloud.com/troubleshooting for more information.

Be the first to comment!

Past two days all the emails i send to a particular domains are getting bounced with an error. "The response from the remote server was:553 Message filtered. Refer to the Troubleshooting page at http://www.symanteccloud.com/troubleshooting for more information." The error indicates that my email was blocked as spam by Symantec anti-spam filter.Got to know from the Symantec Forums
Email bounce backs occur when an email is sent to an Email Security.cloud client, and a rule is triggered by the email recipient's configuration. As suggested by Symantec i tried  all the possible recommendations to resolve the issue but unfortunately these recommendations doesn't prove to be an issue in my case(Symantec Recommendation).

Upon reaching my Suite support I understand that my email message has bounced because a Google IP address has been blacklisted by Symantec Cloud filtering and As suggested by Suite i was asked to contact the recipients support to allow Gmail IP addresses to their Simple Mail Transfer Protocol (SMTP) gateway's whitelist.



It is really tough job to reach out all the customers to whitelist the google IP address to their Simple Mail Transfer Protocol (SMTP) gateway's. However I'm able to send emails without adding Hyperlinks to my Email Signature or in my body of the email. Seems like Symantec is filtering the Hyperlinks added to the Emails, As I don't have visibility of how the third party is treating  the links or how their filtering works.

If someone who is aware of this Symantec Cloud filtering on this regard can elaborate on how the hyperlinks can be modified or altered to successfully process the email it will be really helpful for me to resolve the issue.

Fahim Raza(Author)

Hi there! my name is Fahim Raza. I am a professional blogger. I like music(Linkin Park), playing games(football) and blogging...

No comments:

Post a comment