Email Security.cloud

Hi,

I've recently migrated an existing MTA to a new VPS.  Evidently the previous user of my current IP address made it onto your blocklist, as my host cannot connect to your MX(es?):

Feb 19 07:56:53 bianca postfix/smtp[28721]: E7942FFA85: to=<redacted>, relay=none, delay=150, delays=0.13/0.03/150/0, dsn=4.4.1, status=deferred (connect to cluster14.us.messagelabs.com[216.82.241.197]:25: Connection timed out)
Feb 19 08:06:14 bianca postfix/smtp[28820]: E7942FFA85: to=<redacted>, relay=none, delay=712, delays=562/0.02/150/0, dsn=4.4.1, status=deferred (connect to cluster14.us.messagelabs.com[216.82.241.197]:25: Connection timed out)
Feb 19 08:21:14 bianca postfix/smtp[28913]: E7942FFA85: to=<redacted>, relay=none, delay=1611, delays=1461/0.03/150/0, dsn=4.4.1, status=deferred (connect to cluster14.us.messagelabs.com[216.82.241.197]:25: Connection timed out)
Feb 19 08:51:15 bianca postfix/smtp[29056]: E7942FFA85: to=<redacted>, relay=none, delay=3412, delays=3262/0.02/150/0, dsn=4.4.1, status=deferred (connect to cluster14.us.messagelabs.com[216.82.241.197]:25: Connection timed out)

Please can you un-blacklist my IP address, 46.43.14.54.  Happy to answer any questions.

Thanks for your prompt attention.

Hi James,

Probably better to contact the support team instead. Connect is a community-based forum, and while there are some Symantec employees trawling the forums at times, they won't do so all the time and this might get missed.

Check the link below for this:

https://support.symantec.com/en_US/email-security-cloud.html

Thanks!

Thanks Craig, I'll do that, appreciate your help.  Would certainly spare people's wasted effort if there were a clear and obvious place to go for this.

OK well, I think if it was going to get unblocked, it would have happened by now.

I faithfully followed the proscribed steps, and have given it 2 months, but my IP is still blocked.  All the MX records for the addressee in question resolve to cluster14 or cluster14a.messagelabs.com, 216.82.248.67.  I can ping and tracepath there successfully; 'tcpdump' shows the syn packets going out, and nothing coming back in response. 'nmap' shows port 25/tcp as "filtered". I'm forced to conclude my IP is still blocked.

What are you supposed to do if the official escalation method fails to unblock your IP?  I'm at a total impasse now, please can someone help out!

Hi James

I took a look at your IP and can see there was some significant throttling in place which was causing the issues you were seeing. As you mentioned its very likely that the previous owner of the IP had been compromised and relayed spammy content.

I've cleared the throttling now though so you should not see any further issues with this.

Regards

Ian Tiller

Tier 2 Senior Product Support Engineer

Brilliant, thanks very much Ian, successfully mailing again - appreciate your intervention.

Apr 24 13:56:56 bianca postfix/smtp[2067]: 758B4FF40C: to=<redacted>, relay=cluster14.us.messagelabs.com[216.82.241.197]:25, delay=2,
 delays=0.13/0.02/1.1/0.66, dsn=2.0.0, status=sent (250 ok 1524574616 qp 24822 server-9.tower-43.messagelabs.com!1524574615!84085446!1)

All the best,

James