Hello,
I'm an IT system integrator, I just upgrade one of my client from exchange 2003 to exchange 2016.
Now since the upgrade i can send email to every body except pleople using the messagelabs.com service.
I checked the IP reputation to confirm if anyting changed :
http://ipremoval.sms.symantec.com/lookup/
The IP address you submitted, 46.140.111.164, does not have a negative reputation and therefore cannot be submitted for investigation.
The IP address you submitted, 212.147.82.246, does not have a negative reputation and therefore cannot be submitted for investigation.
To request investigation of an IP address, enter that address in the IP Address field provided below. Confirm the security image text in the Image Text field and click Submit.
All emails send to people using messagelabs get delayed permanently, with no clear error message(see below) of why symantec is rejecting the message.
However for one of the recepients that i contacted they did something on they're symantec and then i was able to send email to them.
Can you tell me if I need to contact each symantec client (~20-50) to who i need to send email to manualy and ask each one them to do the change or is there a more efficient way of doing this on you side or if you can provide more details (error codes or guidelines) so that i can comply to your special requirements ?
Could you please check on this thank you in advanced.
2018-03-12T10:35:23.348Z,08D587F938D849DF,SMTP,waterman.co.uk,+,DnsConnectorDelivery 59547d17-6534-4d17-8836-45e376a6bdeb;QueueLength=TQ=1;RN=3;.
2018-03-12T10:35:23.849Z,08D587F938D849DF,SMTP,waterman.co.uk,>,"cluster3.eu.messagelabs.com[194.106.220.35, 85.158.139.3, 194.106.220.51, 85.158.136.35, 85.158.136.3, 85.158.142.192, 85.158.142.99], cluster3a.eu.messagelabs.com[85.158.139.103]"
2018-03-12T10:35:23.893Z,08D587F938D849DF,SMTP,waterman.co.uk,>,Established connection to 194.106.220.35
2018-03-12T10:35:24.670Z,08D587F938D849DF,SMTP,waterman.co.uk,-,Messages: 0 Bytes: 0 (Attempting next target)
2018-03-12T10:35:24.670Z,08D587F938D849E0,SMTP,waterman.co.uk,*,Session Failover; previous session id = 08D587F938D849DF; reason = ProtocolError
2018-03-12T10:35:24.670Z,08D587F938D849E0,SMTP,waterman.co.uk,+,DnsConnectorDelivery 59547d17-6534-4d17-8836-45e376a6bdeb;QueueLength=TQ=2;AN=1;RN=2;.
2018-03-12T10:35:24.716Z,08D587F938D849E0,SMTP,waterman.co.uk,>,Established connection to 85.158.139.3
2018-03-12T10:35:25.143Z,08D587F938D849E0,SMTP,waterman.co.uk,-,Messages: 0 Bytes: 0 (Attempting next target)
2018-03-12T10:35:25.143Z,08D587F938D849E1,SMTP,waterman.co.uk,*,Session Failover; previous session id = 08D587F938D849E0; reason = ProtocolError
2018-03-12T10:35:25.143Z,08D587F938D849E1,SMTP,waterman.co.uk,+,DnsConnectorDelivery 59547d17-6534-4d17-8836-45e376a6bdeb;QueueLength=TQ=2;AN=1;RN=2;.
2018-03-12T10:35:25.185Z,08D587F938D849E1,SMTP,waterman.co.uk,>,Established connection to 194.106.220.51
2018-03-12T10:35:25.721Z,08D587F938D849E1,SMTP,waterman.co.uk,-,Messages: 0 Bytes: 0 (Attempting next target)
2018-03-12T10:35:25.721Z,08D587F938D849E2,SMTP,waterman.co.uk,*,Session Failover; previous session id = 08D587F938D849E1; reason = ProtocolError
2018-03-12T10:35:25.722Z,08D587F938D849E2,SMTP,waterman.co.uk,+,DnsConnectorDelivery 59547d17-6534-4d17-8836-45e376a6bdeb;QueueLength=TQ=2;AN=1;RN=2;.
2018-03-12T10:35:25.746Z,08D587F938D849E2,SMTP,waterman.co.uk,>,Established connection to 85.158.136.35
2018-03-12T10:35:26.318Z,08D587F938D849E2,SMTP,waterman.co.uk,-,Messages: 0 Bytes: 0 (Attempting next target)
2018-03-12T10:35:26.318Z,08D587F938D849E3,SMTP,waterman.co.uk,*,Session Failover; previous session id = 08D587F938D849E2; reason = ProtocolError
2018-03-12T10:35:26.318Z,08D587F938D849E3,SMTP,waterman.co.uk,+,DnsConnectorDelivery 59547d17-6534-4d17-8836-45e376a6bdeb;QueueLength=TQ=2;AN=1;RN=2;.
2018-03-12T10:35:26.344Z,08D587F938D849E3,SMTP,waterman.co.uk,>,Established connection to 85.158.136.3
2018-03-12T10:35:26.874Z,08D587F938D849E3,SMTP,waterman.co.uk,-,Messages: 0 Bytes: 0 (Attempting next target)
2018-03-12T10:35:26.874Z,08D587F938D849E4,SMTP,waterman.co.uk,*,Session Failover; previous session id = 08D587F938D849E3; reason = ProtocolError
2018-03-12T10:35:26.874Z,08D587F938D849E4,SMTP,waterman.co.uk,+,DnsConnectorDelivery 59547d17-6534-4d17-8836-45e376a6bdeb;QueueLength=TQ=2;AN=1;RN=2;.
2018-03-12T10:35:26.917Z,08D587F938D849E4,SMTP,waterman.co.uk,>,Established connection to 85.158.142.192
2018-03-12T10:35:27.289Z,08D587F938D849E4,SMTP,waterman.co.uk,-,Messages: 0 Bytes: 0 (Attempting next target)
2018-03-12T10:35:27.289Z,08D587F938D849E5,SMTP,waterman.co.uk,*,Session Failover; previous session id = 08D587F938D849E4; reason = ProtocolError
2018-03-12T10:35:27.289Z,08D587F938D849E5,SMTP,waterman.co.uk,+,DnsConnectorDelivery 59547d17-6534-4d17-8836-45e376a6bdeb;QueueLength=TQ=2;AN=1;RN=2;.
2018-03-12T10:35:27.330Z,08D587F938D849E5,SMTP,waterman.co.uk,>,Established connection to 85.158.142.99
2018-03-12T10:35:27.790Z,08D587F938D849E5,SMTP,waterman.co.uk,-,Messages: 0 Bytes: 0 (Attempting next target)
2018-03-12T10:35:27.790Z,08D587F938D849E6,SMTP,waterman.co.uk,*,Session Failover; previous session id = 08D587F938D849E5; reason = ProtocolError
2018-03-12T10:35:27.790Z,08D587F938D849E6,SMTP,waterman.co.uk,+,DnsConnectorDelivery 59547d17-6534-4d17-8836-45e376a6bdeb;QueueLength=TQ=2;AN=1;RN=2;.
2018-03-12T10:35:27.817Z,08D587F938D849E6,SMTP,waterman.co.uk,>,Established connection to 85.158.139.103