Deliver Email

I need a solution

Problems Delivering email

LOG: MAIN
  cwd=/usr/local/cpanel/whostmgr/docroot 4 args: exim -v -M 1iXvli-0006PP-3o
delivering 1iXvli-0006PP-3o
LOG: MAIN
  Sender identification U=interpar D=interpartesdemexico.com S=licitaciones@interpartesdemexico.com
Connecting to cluster9.us.messagelabs.com [67.219.247.54]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-13.tower-426.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.247.54]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.246.102]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-11.tower-386.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.246.102]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.251.54]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-22.tower-366.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.251.54]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.250.198]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-6.tower-346.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.250.198]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.250.102]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-2.tower-326.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.250.102]: Remote host closed connection in response to EHLO s1
Connecting to cluster9.us.messagelabs.com [67.219.246.198]:25 from 158.69.242.81 ... connected
  SMTP<< 220 server-22.tower-406.messagelabs.com ESMTP
  SMTP>> EHLO s1
  SMTP(close)>>
LOG: MAIN
  H=cluster9.us.messagelabs.com [67.219.246.198]: Remote host closed connection in response to EHLO s1
Connecting to cluster9a.us.messagelabs.com [3.222.201.247]:25 from 158.69.242.81 ... connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Fri, 22 Nov 2019 03:47:29 +0000
  SMTP>> EHLO s1
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-112-12-131.us-east-1.aws.symcld.net [100.112.12.131]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<licitaciones@interpartesdemexico.com> SIZE=105809
  SMTP>> RCPT TO:<humberto.villalobos@regalsprings.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
LOG: MAIN
  H=cluster9a.us.messagelabs.com [3.222.201.247]: SMTP error from remote mail server after RCPT TO:<humberto.villalobos@regalsprings.com>: 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster9a.us.messagelabs.com [34.237.164.170]:25 from 158.69.242.81 ... connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Fri, 22 Nov 2019 03:47:29 +0000
  SMTP>> EHLO s1
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-112-14-77.us-east-1.aws.symcld.net [100.112.14.77]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<licitaciones@interpartesdemexico.com> SIZE=105809
  SMTP>> RCPT TO:<humberto.villalobos@regalsprings.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
LOG: MAIN
  H=cluster9a.us.messagelabs.com [34.237.164.170]: SMTP error from remote mail server after RCPT TO:<humberto.villalobos@regalsprings.com>: 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster9a.us.messagelabs.com [52.73.243.182]:25 from 158.69.242.81 ... connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Fri, 22 Nov 2019 03:47:29 +0000
  SMTP>> EHLO s1
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-112-13-247.us-east-1.aws.symcld.net [100.112.13.247]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<licitaciones@interpartesdemexico.com> SIZE=105809
  SMTP>> RCPT TO:<humberto.villalobos@regalsprings.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
LOG: MAIN
  == humberto.villalobos@regalsprings.com R=dkim_lookuphost T=dkim_remote_smtp defer (-44) H=cluster9a.us.messagelabs.com [52.73.243.182]: SMTP error from remote mail server after RCPT TO:<humberto.villalobos@regalsprings.com>: 421 Service Temporarily Unavailable
0

Related:

421 Service Temporarily Unavailable

I do not need a solution (just sharing information)

Good day

My client always send message from  programacion.pampilla @ cargotransportperu.com to repsolpampilla @ repsol.com.

Today when cargotransportperu.com send mails to repsol.com receive an error message this message:

== repsolpampilla@repsol.com R=lookuphost T=remote_smtp defer (-44) H=cluster1a.eu.messagelabs.com [3.123.158.38]: SMTP error from remote mail server after RCPT TO:<repsolpampilla@repsol.com>: 421 Service Temporarily Unavailable

Thanks in advance for your help

Here full header:

LOG: MAIN
  cwd=/usr/local/cpanel/whostmgr/docroot 4 args: /usr/sbin/exim -v -M 1iK1A0-003783-Tu
delivering 1iK1A0-003783-Tu
LOG: MAIN
  Sender identification U=cargotra D=cargotransportperu.com S=programacion.pampilla@cargotransportperu.com
Connecting to cluster1.eu.messagelabs.com [85.158.142.97]:25 from 184.154.61.59 … connected
  SMTP<< 220 server-20.tower-222.messagelabs.com ESMTP
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-server-20.tower-222.messagelabs.com
         250-STARTTLS
         250-PIPELINING
         250 8BITMIME
  SMTP>> STARTTLS
  SMTP<< 220 ready for TLS
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-server-20.tower-222.messagelabs.com
         250-PIPELINING
         250 8BITMIME
  SMTP>> MAIL FROM:<programacion.pampilla@cargotransportperu.com>
  SMTP>> RCPT TO:<repsolpampilla@repsol.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 450-Requested action aborted [9] 222-20, please visit
         450-http://www.symanteccloud.com/troubleshooting for more
         450 details about this error message.
LOG: MAIN
  H=cluster1.eu.messagelabs.com [85.158.142.97]: SMTP error from remote mail server after RCPT TO:<repsolpampilla@repsol.com>: 450-Requested action aborted [9] 222-20, please visitn450-http://www.symanteccloud.com/troubleshooting for moren450 details about this error message.
  SMTP<< 503 RCPT first (#5.5.1)
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster1.eu.messagelabs.com [85.158.142.196]:25 from 184.154.61.59 … connected
  SMTP<< 220 server-13.tower-241.messagelabs.com ESMTP
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-server-13.tower-241.messagelabs.com
         250-STARTTLS
         250-PIPELINING
         250 8BITMIME
  SMTP>> STARTTLS
  SMTP<< 220 ready for TLS
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-server-13.tower-241.messagelabs.com
         250-PIPELINING
         250 8BITMIME
  SMTP>> MAIL FROM:<programacion.pampilla@cargotransportperu.com>
  SMTP>> RCPT TO:<repsolpampilla@repsol.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 450-Requested action aborted [9] 241-13, please visit
         450-http://www.symanteccloud.com/troubleshooting for more
         450 details about this error message.
LOG: MAIN
  H=cluster1.eu.messagelabs.com [85.158.142.196]: SMTP error from remote mail server after RCPT TO:<repsolpampilla@repsol.com>: 450-Requested action aborted [9] 241-13, please visitn450-http://www.symanteccloud.com/troubleshooting for moren450 details about this error message.
  SMTP<< 503 RCPT first (#5.5.1)
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster1a.eu.messagelabs.com [52.58.21.128]:25 from 184.154.61.59 … connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Mon, 14 Oct 2019 16:05:38 +0000
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-113-12-211.eu-central-1.aws.symcld.net [100.113.12.211]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<programacion.pampilla@cargotransportperu.com> SIZE=3602907
  SMTP>> RCPT TO:<repsolpampilla@repsol.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
LOG: MAIN
  H=cluster1a.eu.messagelabs.com [52.58.21.128]: SMTP error from remote mail server after RCPT TO:<repsolpampilla@repsol.com>: 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
Connecting to cluster1a.eu.messagelabs.com [3.123.158.38]:25 from 184.154.61.59 … connected
  SMTP<< 220 mail555.messagelabs.com ESMTP Mon, 14 Oct 2019 16:05:38 +0000
  SMTP>> EHLO cargotransportperu.com
  SMTP<< 250-mail555.messagelabs.com Hello ip-100-113-13-49.eu-central-1.aws.symcld.net [100.113.13.49]
         250-SIZE 52428800
         250-8BITMIME
         250-PIPELINING
         250-CHUNKING
         250-PRDR
         250 HELP
  SMTP>> MAIL FROM:<programacion.pampilla@cargotransportperu.com> SIZE=3602907
  SMTP>> RCPT TO:<repsolpampilla@repsol.com>
  SMTP>> DATA
  SMTP<< 250 OK
  SMTP<< 421 Service Temporarily Unavailable
  SMTP<< 503-All RCPT commands were rejected with this error:
         503-Service Temporarily Unavailable
         503 Valid RCPT command must precede DATA
  SMTP>> QUIT
  SMTP(close)>>
LOG: MAIN
  == repsolpampilla@repsol.com R=lookuphost T=remote_smtp defer (-44) H=cluster1a.eu.messagelabs.com [3.123.158.38]: SMTP error from remote mail server after RCPT TO:<repsolpampilla@repsol.com>: 421 Service Temporarily Unavailable
 

0

Related:

501 Connection rejected by policy [7.7] 40344, please visit www.messagelabs.com/support for more details about this error message

I need a solution

Getting below error message while send emails to clients hosted with Symantec messagelabs.com

Server Name = mail.scanllc.com

Server IP = 5.135.244.62

Please fix the issue. 

Thanks in advance.

Best Regards,

Zarshed

2019-09-04T11:11:53.083Z,SMTP Mail Send Connector,08D72FD2A7AC31D6,3,5.135.244.62:6782,67.219.246.195:25,<,”501 Connection rejected by policy [7.7] 40344, please visit www.messagelabs.com/support for more details about this error message.”,
2019-09-04T11:11:53.083Z,SMTP Mail Send Connector,08D72FD2A7AC31D6,4,5.135.244.62:6782,67.219.246.195:25,*,,”Dropping connection because server is not accepting mail. Server response :501 Connection rejected by policy [7.7] 40344, please visit www.messagelabs.com/support for more details about this error message.”
2019-09-04T11:11:53.083Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,0,,34.225.212.74:25,*,SendRoutingHeaders,Set Session Permissions
2019-09-04T11:11:53.083Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,1,,34.225.212.74:25,*,,attempting to connect
2019-09-04T11:11:53.083Z,SMTP Mail Send Connector,08D72FD2A7AC31D6,5,5.135.244.62:6782,67.219.246.195:25,>,QUIT,
2019-09-04T11:11:53.084Z,SMTP Mail Send Connector,08D72FD2A7AC31D6,6,5.135.244.62:6782,67.219.246.195:25,-,,Remote
2019-09-04T11:11:53.166Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,2,5.135.244.62:6787,34.225.212.74:25,+,,
2019-09-04T11:11:53.251Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,3,5.135.244.62:6787,34.225.212.74:25,<,”220 mail555.messagelabs.com ESMTP Wed, 04 Sep 2019 11:11:51 +0000″,
2019-09-04T11:11:53.251Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,4,5.135.244.62:6787,34.225.212.74:25,>,EHLO mail.scanllc.com,
2019-09-04T11:11:53.334Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,5,5.135.244.62:6787,34.225.212.74:25,<,250  mail555.messagelabs.com Hello ip-100-112-13-60.us-east-1.aws.symcld.net [100.112.13.60] SIZE 52428800 8BITMIME PIPELINING CHUNKING PRDR HELP,
2019-09-04T11:11:53.334Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,6,5.135.244.62:6787,34.225.212.74:25,*,,sending message with RecordId 47407849013301 and InternetMessageId <1AD7D2C0-CE67-4D7E-AAEA-84D526E40D8C@scanllc.com>
2019-09-04T11:11:53.334Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,7,5.135.244.62:6787,34.225.212.74:25,>,MAIL FROM:<solar@scanllc.com> SIZE=54912,
2019-09-04T11:11:53.334Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,8,5.135.244.62:6787,34.225.212.74:25,>,RCPT TO:<STEEVAN-R@marubeni.com>,
2019-09-04T11:11:53.417Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,9,5.135.244.62:6787,34.225.212.74:25,<,250 OK,
2019-09-04T11:11:53.417Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,10,5.135.244.62:6787,34.225.212.74:25,<,421 Service Temporarily Unavailable,
2019-09-04T11:11:53.418Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,11,5.135.244.62:6787,34.225.212.74:25,>,QUIT,
2019-09-04T11:11:53.500Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,12,5.135.244.62:6787,34.225.212.74:25,<,221 mail555.messagelabs.com closing connection,
2019-09-04T11:11:53.501Z,SMTP Mail Send Connector,08D72FD2A7AC31D7,13,5.135.244.62:6787,34.225.212.74:25,-,,Local

0

Related:

Avamar: Avamar Callhome is not working after migration to Office365

To setup an SMTP Relay on Office365

In Office365, click Admin, then click Exchange to arrive on the Exchange Admin Center

Click mail flow, and then connectors

User-added image


Use the “+” to start the wizard to create a new connector:

– From = your organisation’s email server

– To = Office 365

– Enter a name for SMTP Relay

– By verifying that the IP address of the sending server matches one of these IP addresses that belong to your organization sender’s IP address = all Avamar utility nodes that are configured on customer site (IP should match public IP address of location sending email).

And click save to create the connector.

Then you can test it by doing the telnet command:

telnet <smtp office365> 25

EHLO

MAIL FROM:avamar_user_configurated@xxxx.com

It return now:

250 2.1.0 Sender OK

Avamar callhome and dialhome is now working.

Related:

MessageLabs.com 421 Service Temporarily Unavailable, TLS negotiation failed with error IllegalMessage

I do not need a solution (just sharing information)

I have already indeed email a sample message to Symantec (investigation@review.symantec.com) for the NDR message delayed emails.

I poseted in hopes to maybe help with this issue and see if someone else has any ideas.

In the Send connector protocol logs, we see:

2019-01-09T16:42:03.318Z,Internet,08D1234567811DF6,0,,x.x.x.x:25,*,,attempting to connect
2019-01-09T16:42:03.334Z,Internet,08D6723456789DF6,1,x.x.x.x:32944,x.x.x.x:25,+,,
<,220 server-5.tower-347.messagelabs.com ESMTP,
>,EHLO Mail.xxxx.com,
<,250-server-5.tower-347.messagelabs.com,
<,250-STARTTLS,
<,250-PIPELINING,
<,250 8BITMIME,
>,STARTTLS,
<,220 ready for TLS,
*,,Sending certificate
*,”CN=mail.xxxx.com, O=””xxxx, Inc.””, L=xxxx, S=xxxx, C=US”,Certificate subject
*,”CN=DigiCert SHA2 Secure Server CA, O=DigiCert Inc, C=US”,Certificate issuer name
*,09024235443534F8234324,Certificate serial number
*,FDA0D53434343D933F32345123456789681DAAC3,Certificate thumbprint
*,mail.xxxx.com;autodiscover.xxxx.com;owa.xxxx.com;,Certificate alternate names
*,,TLS negotiation failed with error IllegalMessage
-,,Local

Then we Also See:

2019-01-09T19:35:50.765Z,Internet,08D67123445551F4,0,,x.x.x.x:25,*,,attempting to connect
2019-01-09T19:35:50.765Z,Internet,08D67123445551F4,1,x.x.x.x:48897,x.x.x.x:25,+,,
2019-01-09T19:35:51.093Z,Internet,08D67123445551F4,2,x.x.x.x:48897,x.x.x.x:25,<,”220 mail555.messagelabs.com ESMTP Wed, 09 Jan 2019 19:35:50 +0000″,
2019-01-09T19:35:51.093Z,Internet,08D67123445551F4,3,x.x.x.x:48897,x.x.x.x:25,>,EHLO mail.xxxx.com,
2019-01-09T19:35:51.140Z,Internet,08D67123445551F4,4,x.x.x.x:48897,x.x.x.x:25,<,250-mail555.messagelabs.com Hello ip-100-112-14-171.us-east-1.aws.symcld.net [100.112.14.171],
2019-01-09T19:35:51.140Z,Internet,08D67123445551F4,5,x.x.x.x:48897,x.x.x.x:25,<,250-SIZE 52428800,
2019-01-09T19:35:51.140Z,Internet,08D67123445551F4,6,x.x.x.x:48897,x.x.x.x:25,<,250-8BITMIME,
2019-01-09T19:35:51.140Z,Internet,08D67123445551F4,7,x.x.x.x:48897,x.x.x.x:25,<,250-PIPELINING,
2019-01-09T19:35:51.140Z,Internet,08D67123445551F4,8,x.x.x.x:48897,x.x.x.x:25,<,250-CHUNKING,
2019-01-09T19:35:51.140Z,Internet,08D67123445551F4,9,x.x.x.x:48897,x.x.x.x:25,<,250-PRDR,
2019-01-09T19:35:51.140Z,Internet,08D67123445551F4,10,x.x.x.x:48897,x.x.x.x:25,<,250 HELP,
2019-01-09T19:35:51.140Z,Internet,08D67123445551F4,11,x.x.x.x:48897,x.x.x.x:25,*,,sending message with RecordId 10261234567442 and InternetMessageId <1523344547606.84370@xxxx.com>
2019-01-09T19:35:51.140Z,Internet,08D67123445551F4,12,x.x.x.x:48897,x.x.x.x:25,>,MAIL FROM:<Paul.xxxx@xxxx.com> SIZE=34071,
2019-01-09T19:35:51.140Z,Internet,08D67123445551F4,13,x.x.x.x:48897,x.x.x.x:25,>,RCPT TO:<jschxxxx@xxxx.com>,
2019-01-09T19:35:51.186Z,Internet,08D67123445551F4,14,x.x.x.x:48897,x.x.x.x:25,<,250 OK,
2019-01-09T19:35:51.186Z,Internet,08D67123445551F4,15,x.x.x.x:48897,x.x.x.x:25,<,421 Service Temporarily Unavailable,

All Message Labs Servers we see with TLS Negoiation Problems:

server-6.tower-367.messagelabs.com

server-14.tower-387.messagelabs.com

server-35.tower-384.messagelabs.com

server-9.tower-347.messagelabs.com

server-13.tower-407.messagelabs.com

server-35.tower-404.messagelabs.com

server-3.tower-327.messagelabs.com

server-35.tower-344.messagelabs.com

server-8.tower-341.messagelabs.com

server-16.tower-381.messagelabs.com

server-3.tower-361.messagelabs.com

server-4.tower-246.messagelabs.com

MessageLabs with 421 Service Temporarily Unavailable:

mail555.messagelabs.com

0

Related:

email block

I need a solution

My client cannot send email to message lab addresses. We do not send bulk mail and are not listed on any blacklist including Symantec.

Returned emails have a header like this:

Subject: dmcsmtp.dansmanagement.com Mail delivery failed : returning message to sender

This message was created automatically by the SMTP relay on dmcsmtp.dansmanagement.com.

 

A message that you sent could not be delivered to all of its recipients.

The following address(es) failed:

  coloniallifesales.com

    SMTP error from remote mail server after RCPT TO:@coloniallifesales.com>:

    host cluster9.us.messagelabs.com [52.73.243.182]:

    421 Service Temporarily Unavailable: retry timeout exceeded

—— This is a copy of the message, including all the headers. ——

Return-path: <aaraujo@dansmanagement.com>

Received: from [200.0.0.54] (port=40176 helo=dmcsmtp.dansmanagement.com)

                by dmcsmtp.dansmanagement.com with esmtp (Exim 4.82_1-5b7a7c0-XX)

                (envelope-from <aaraujo@dansmanagement.com>)

                id 1gUZwM-00008V-2X

                for <message lab client>; Wed, 05 Dec 2018 11:22:22 -0500

Received: from dmc-Mail2010.dmcdomain.local ([fe80::9c64:df94:9c18:229c]) by  dmc-Mail2010.dmcdomain.local ([fe80::9c64:df94:9c18:229c%10]) with mapi id  14.03.0415.000; Wed, 5 Dec 2018 11:22:22 -0500

X-CTCH-RefID: str=0001.0A020205.5C07FB3E.00DD,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0

From: Abigail Araujo <aaraujo@dansmanagement.com>

To: <message lab client>

Subject: Test

Thread-Topic: Test

Thread-Index: AdSMtqTriyykCgvwQCKUl+Jmuj+kSQ==

Date: Wed, 5 Dec 2018 16:22:21 +0000

Message-ID: <3C7074C5333CC54287CD83E334D3105709CD65C7@dmc-Mail2010.dmcdomain.local>

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator:

x-originating-ip: [200.0.0.152]

Content-Type: multipart/related;

                boundary=”_004_3C7074C5333CC54287CD83E334D3105709CD65C7dmcMail2010dmcd_”;

                type=”multipart/alternative”

MIME-Version: 1.0

–_004_3C7074C5333CC54287CD83E334D3105709CD65C7dmcMail2010dmcd_

Content-Type: multipart/alternative;

                boundary=”_000_3C7074C5333CC54287CD83E334D3105709CD65C7dmcMail2010dmcd_”

–_000_3C7074C5333CC54287CD83E334D3105709CD65C7dmcMail2010dmcd_

Content-Type: text/plain; charset=”us-ascii”

Content-Transfer-Encoding: quoted-printable

Our email filter shows a smtp spool like this:

2018-12-09 15:01:18 cluster9.us.messagelabs.com [67.219.246.102]:25 Connection timed out
2018-12-09 15:03:25 cluster9.us.messagelabs.com [67.219.247.54]:25 Connection timed out
2018-12-09 15:05:33 cluster9.us.messagelabs.com [67.219.246.198]:25 Connection timed out
2018-12-09 15:07:40 cluster9.us.messagelabs.com [67.219.251.54]:25 Connection timed out
2018-12-09 15:09:47 cluster9.us.messagelabs.com [67.219.250.198]:25 Connection timed out
2018-12-09 15:09:47 SMTP error from remote mail server after RCPT TO:<postmaster@coloniallifesales.com>: host cluster9a.us.messagelabs.com [52.206.215.254]: 421 Service Temporarily Unavailable
2018-12-09 15:09:47 postmaster@coloniallifesales.com R=dnslookup T=remote_smtp defer (-44): SMTP error from remote mail server after RCPT TO:<postmaster@coloniallifesales.com>: host cluster9a.us.messagelabs.com [52.206.215.254]: 421 Service Temporarily Unavailable

This is my 2nd post and I have emailed the investigation email address twice. So far I have no replies

0

Related:

Email delays to customers via messagelabs

I need a solution

Hello,

 

We have multiple external parties who complain about delays in emails. The common factor seems to be messagelabs in the path between

See the headers below

 

Hop Delay From By With Time (UTC) Blacklist
1 * ANMLMBX1002.asp.local ANMLHT2001.asp.local mapi 6/7/2018 12:51:18 PM  
2 0 seconds ANMLHT2001.asp.local 10.254.233.2 keys.hierinloggen.nl   6/7/2018 12:51:18 PM
3 0 seconds keys.hierinloggen.nl 194.151.85.27 smtp.hierinloggen.nl ESMTP 6/7/2018 12:51:18 PM
4 5 hour smtp.hierinloggen.nl 194.151.85.22 server-20.tower-222.messagelabs.com DHE-RSA-AES256-SHA256 encrypted SMTP 6/7/2018 5:24:04 PM
5 0 seconds network     6/7/2018 5:24:04 PM  
6 1 Second using 85.158.142.97 server-5.bemta.az-a.eu-central-1.aws.symcld.net cipher DHE-RSA-AES256-GCM-SHA384 (256 bits)) 6/7/2018 5:24:05 PM
7 0 seconds mail6.bemta26.messagelabs.com 85.158.142.45 triton22.abnamro.nl ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384 6/7/2018 5:24:05 PM
8 0 seconds triton22.inet.nl.abnamro.com 10.121.46.226 aaamsr104.abnamro.com ESMTP 6/7/2018 5:24:05 PM
9 1 Second aaamsr104.abnamro.com 10.21.177.18 aaamsr003.abnamro.com ESMTP 6/7/2018 5:24:06 PM

 

Received: from aaamsr104.abnamro.com ([10.21.177.18])
          by aaamsr003.abnamro.com
          with ESMTP id 2018060719240649-1345099 ;
          Thu, 7 Jun 2018 19:24:06 +0200 
Received: from triton22.inet.nl.abnamro.com ([10.121.46.226])
          by aaamsr104.abnamro.com
          with ESMTP id 2018060719240554-533311 ;
          Thu, 7 Jun 2018 19:24:05 +0200 
X-AAB_From_Internet: TRUE
Received: from mail6.bemta26.messagelabs.com ([85.158.142.45])
  by triton22.abnamro.nl with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Jun 2018 17:24:05 +0000
Return-Path: <
Received: from [85.158.142.97] (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256 bits))
by server-5.bemta.az-a.eu-central-1.aws.symcld.net id 3F/05-20068-53A691B5; Thu, 07 Jun 2018 17:24:05 +0000
Subject: [External] RE: C1706019 Buy In Notifications Sweden
X-Brightmail-Tracker: H4sIAAAAAAAAA2WSb0gTYRzHfe5u2ylenHPq4yqiJRHpjU0l9IU
  S+kJ7E0WGpUSdeu4u5im7jaa+yJIyTWiY+S9MXWqipqBFgaY2RZlWVG+yyEg0NBeFkQpW2t1O
  zehePHx+v+/3+f5+Bw+OqjuUWpyxWxkLT5t1Sj/MVX0ymIo+H5puuFKsjFl70KaI+Tg3jx5Gk
  jveL2HHQJqC4zNy7ecU7NS1UVWeswqxf/J0qYpATQlSBvxwjBxRwO75Mkwq1GQvgCPuyyq5KB
  WLqXJFGcBxSKbC+tKzcr8RwGL3T7HviytJPXy82KmUWEPa4UvHvEIyoWQPgMuTaypJCCSNsGK
  1yxukISNh2wtO9kfCytZlIDFGhsEm5yNMYoI8Cgc6bnrz1eQJWN3QgkrsS6bAnkan1w/IYLgy
  3olIjJIh8N1sg5chqYHTryaUMgfBzzNrCpl18NfwICLvJv6YZ757Y1gAdNfOYg4QXLctq267r
  26bTzbxcPzh2w2OgI1935Uyh8PWJg+6yc+GZpD/+xSsdoxs9PfC2/cWgDysGcDyL7e2Qisrvq
  Kbpsrr06pGQLSD2AwLZ2KtOTRnpowGA2U0RlFGKtIQracLKFrP2KhMhrdaaFHV0xcEvZCfk2n
  O0vOMtQeIj8VH/B6D2tUsFwjFEV0QQZwJTVfvyMjNymdpgT1rsZkZwQV24bgOEqOsqAVYGBNj
  z+bM4ovblCHur9MQhZJMCHl0jsCZZGkcxOKub5XlKP7Ce7Y333CgaozP5RltCHFXukBKF1gbv
  xW3+YZfg93aQAKIC6r98xhLDmf9V18AITjQBRLhnJjiz/HWrakL4kKIuFAy6l3ISv+VtEUgqS
  OxpM81tv/+eSZsJrJmz4cBW3ZS74gm7lJ1wnGk4tTzwQSbxW/FSeGJy5N3jjw50KutSGn7UeI
  z6U951M7Z4UNxb9jw/uNCQtR01dLY6ZBCenWipYWJj0t9etEnzbEzY72AXR9yz4zHfzJMRtR4
  6nfsy+83zWp+L1415y3N6TCBpY0HUYtA/wE+qkkLvgMAAA==
X-Env-Sender: 
X-Msg-Ref: server-20.tower-222.messagelabs.com!1528392243!1575715!1
X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: 
  VHJ1c3RlZCBJUDogMTk0LjE1MS44NS4yMiA9PiA2MzY0OTI=n
X-StarScan-Received:
X-StarScan-Version: 9.9.15; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 20894 invoked from network); 7 Jun 2018 17:24:04 -0000
Received: from smtp.hierinloggen.nl (HELO smtp.hierinloggen.nl) (194.151.85.22)
  by server-20.tower-222.messagelabs.com with DHE-RSA-AES256-SHA256 encrypted SMTP; 7 Jun 2018 17:24:04 -0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=euroccp.com; s=an_euroccp; c=relaxed/relaxed;
h=x-pgp-universal:from:to:cc:subject:thread-topic:thread-index:date:message-id:references:in-reply-to:accept-language:content-language:x-ms-has-attach:x-ms-tnef-correlator:x-originating-ip:content-type:mime-version;
bh=Y/ItkhdM4lnoyrhndFSRt0DWF4q3Y6SFrbqdN8934g8=;
b=dILMkhT8fRE7W8CK871PV8dPYsu1z4/3qrrbwb/3BDSYQK/ti9/FYdBiOWalm4nR+Ot99nPiq8y2RwMKFf8mWV07YbFzfM8KO4Wimn1Es6zmAQnCTwTH8s+yNK0XXnYQnYP4WLmEzHO9ayMLHMeow8/gw20LtztifLtEtrDMbWugyPrWcTBHbOafcjsh9jYBTTh1+hYwaIbiw6wL5w/JwDKuvhxlIM51pRJkLnNEjBRAxVvEo7kbwTv9kLtJ/e0DNnj/Zukf+pEAwBrzXaZdHYv6whO60H1zWXskSlxujfNSlmkS9ZOqcvBoPC1h5BEbTFscVq01u6l7nDx0JVh7fw==
Received: from keys.hierinloggen.nl (keys.applicationnet.nl [194.151.85.27])
by smtp.hierinloggen.nl  with ESMTP id w57CpIIE009199-w57CpIIF009199;
Thu, 7 Jun 2018 14:51:18 +0200
Received: from ANMLHT2001.asp.local ([10.254.233.2])
  by keys.hierinloggen.nl (PGP Universal service);
  Thu, 07 Jun 2018 14:51:18 +0200
X-PGP-Universal: processed;
by keys.hierinloggen.nl on Thu, 07 Jun 2018 14:51:18 +0200
Received: from ANMLMBX1002.asp.local ([fe80::b5e2:f47d:b5de:e585]) by
 ANMLHT2001.asp.local ([::1]) with mapi id 14.03.0352.000; Thu, 7 Jun 2018
 14:51:18 +0200
To: “‘b
Thread-Topic: 
Thread-Index: AQHT/kfmvaoRGRX8Lk2MwGGNCi1n8qRUqAVA
References: <OF859C8EFD.0D29E76E-ONC12582A5.00370301-C12582A5.0037F59F@abnamro.com>
In-Reply-To: <OF859C8EFD.0D29E76E-ONC12582A5.00370301-C12582A5.0037F59F@abnamro.com>
Accept-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.254.239.100]
MIME-Version: 1.0
From: “
X-Notes-Item: 859C8EFD:0D29E76E-C12582A5:00370301;
 type=4; name=$REF
X-Notes-Item: 2C60ED69:6234A33D-2E0C0B0B:6FE0CE1D;
 type=4; name=$INetOrig
X-Notes-Item: Thu, 7 Jun 2018 12:51:18 +0000;
 type=400; name=$Created
X-TNEFEvaluated: 1
X-Notes-Item: FD983B54:1AFD0F8D-C12582A5:005F9749;
 type=4; name=$Orig
X-Notes-Item: Memo;
 name=Form
Message-ID: <E892BCE7DE1A4D4784638C0AFDF1B7A601160F68BA@ANMLMBX1002.asp.local>
Date: Thu, 7 Jun 2018 12:51:18 +0000
X-Notes-Item: starting jobs # AAAMSR003/HUB/ABNAMRO/NL # 06/07/2018 07:24:07 PM # Process
 M06 # 18.1.6.8044.n8/32,
Attachment Block EMEA#NT00000E6A(6000) # AAAMSR003/HUB/ABNAMRO/NL # 06/07/2018
 07:24:07 PM,
S/MIME Verify 2016#NT00000DDE(3995) # AAAMSR003/HUB/ABNAMRO/NL # 06/07/2018
 07:24:07 PM,
S/MIME Verify Gw 2016#NT00000DF2(3990) # AAAMSR003/HUB/ABNAMRO/NL # 06/07/2018
 07:24:07 PM,
S/MIME Verify Client 2016#NT00000DE6(3990) # AAAMSR003/HUB/ABNAMRO/NL # 06/07/2018
 07:24:07 PM,
Block Forwarded NonDelivery Notifications#NT00000C3A(3500) # AAAMSR003/HUB/ABNAMRO/NL
 # 06/07/2018 07:24:07 PM,
jobs ended # AAAMSR003/HUB/ABNAMRO/NL # 06/07/2018 07:24:07 PM;
 type=501; flags=0; name=$TkFlag50
X-Notes-Item: CN=AAAMSR003/OU=HUB/O=ABNAMRO/C=NL,
CN=NLAMSM181/OU=SRV/O=ABNAMRO/C=NL;
 type=501; flags=0; name=RouteServers
X-Notes-Item: =?UTF-8?B?MDctSnVuLTIwMTggMTk6MjQ6MDYgQ0VEVC8wNy1KdW4tMjAxOCAxOToyNDo=?=
 =?UTF-8?B?MDcgQ0VEVCwgMDctSnVuLTIwMTggMTk6MjQ6MDcgQ0VEVC8wNy1KdW4t?=
 =?UTF-8?B?MjAxOCAxOToyNDowOSBDRURU?=;
 type=401; flags=0; name=RouteTimes
X-Notes-Item: ;
 name=HasSafeStamp
X-Notes-Item: CN=AAAMSR003/OU=HUB/O=ABNAMRO/C=NL,
CN=NLAMSM181/OU=SRV/O=ABNAMRO/C=NL;
 type=501; flags=44; name=$UpdatedBy
X-Notes-Item: ;
 type=501; name=Categories
X-Notes-Item: ;
 type=401; name=$Revisions
X-Notes-Item: Thu, 7 Jun 2018 19:24:09 +0200;
 type=400; name=DeliveredDate
X-Notes-Item: Opmerkingen op designs FD770;
 flags=6; name=$Abstract
X-Notes-Item: 859C8EFD:0D29E76E-C12582A5:00370301, 859C8EFD:0D29E76E-C12582A5:00370301;
 type=4; name=$TUA
X-Notes-Item: 1;
 name=$NoteHasNativeMIME
X-MIMETrack: Itemize by SMTP Server on AAAMSR003/HUB/ABNAMRO/NL at 06/07/2018 07:24:06
 PM,
Serialize by NLNOTES.EXE on Nick Grashorn/NL/ABNAMRO/NL(Release 9.0.1FP6|April
 21, 2016) at 08-06-2018 09:40:01
Content-Type: multipart/related;
boundary=”_004_E892BCE7DE1A4D4784638C0AFDF1B7A601160F68BAANMLMBX1002as_”;
type=”multipart/alternative”
Content-Language: en-US
0

Related:

cluster{x}a.eu.messagelabs.com deferred mail from users at our domain

I need a solution

Hello.

I am hoping someone from Symantec support could look into this problem.

When sending mail from our domain (bfpe.com) to customers whose MX records point to both

cluster3a.eu.messagelabs.com

and

cluster8a.eu.messagelabs.com

mail is being deferred with the following message:

dsn=4.0.0, stat=Deferred: 421 esmtp: protocol deviation

The source IP for bfpe.com’s mail relay (smtp.bfpe.com) is 208.79.82.226.

I have checked the IPs reputation on mxtoolbox.com and directly at http://ipremoval.sms.symantec.com/lookup/ and there’s nothing to see there.

Mail to MX records at us.messagelabs.com (cluster{1,4}.us.messagelabs.com) are delivering normally, but I see instances where mail to cluster1a.us.messagelabs.com is also deferred with the same “protocol deviation” error.

It does seem that the cluster{N}a (where in is an integer like 1,2,3…) records are always the backup MX records for the domain. Is there some reason why when we initially queued the messages, the primary MX was unreachable and forced the switch to the backup? And now because the messages are queued for the “backup” and the “primary” is available we are being rejected (using a lower priority MX when the higher priority MX is available is a SPAMmer trick — hence the “protocol deviation”?)

Can anyone shed a little more light on why in particular cluster{N}a.eu.messagelabs.com and cluster{N}a.us.messagelabs.com MX destinations are deferring (for days now) mail from our users?

Thanks for your insights.

0

Related:

Messages to/from messagelabs not making it to destintation

I need a solution

Two issues relating to the same message labs user…

1. We have a client who sends automated mail TO a message labs user, which never arrives, but if they manually send the same email, from the same email address it turns up.

The automated email ges a 250 sent from their mail server to a smtp relay service; this smtp relay service also gets a 250 sent from messagelabs, then the mail just vanishes (according to the intended recipient it never arrived).

Exchange > SpamTitan > SMTP Relay > MessageLabs

2. A different client is expecting email from the same user as #1, and I can see the email hit SpamTitan on our side and then it just fails to proceed… the log just reads..

Jun  4 00:46:19 sentry postfix/smtpd[XXXXX]: NOQUEUE: filter: RCPT from mail1.bemta12.messagelabs.com[216.82.251.1]: <mail1.bemta12.messagelabs.com[216.82.251.1]>: Client host triggers FILTER smtp-amavis:[127.0.0.1]:10021; from=<XXXXX@XXXXX> to=<XXXXX@XXXXX> proto=ESMTP helo=<mail1.bemta12.messagelabs.com>
Jun  4 00:46:19 sentry postgrey[576]: action=pass, reason=client whitelist, client_name=mail1.bemta12.messagelabs.com, client_address=216.82.251.1, sender=XXXXX@XXXX, recipient=XXXXX@XXXXX

Rather than the expected..

May 31 16:16:49 sentry postfix/smtpd[XXXXX]: NOQUEUE: filter: RCPT from mail1.bemta8.messagelabs.com[216.82.243.208]: <mail1.bemta8.messagelabs.com[216.82.243.208]>: Client host triggers FILTER smtp-amavis:[127.0.0.1]:10021; from=<XXXXX@XXXXX> to=<XXXXX@XXXXX> proto=ESMTP helo=<mail1.bemta8.messagelabs.com>
May 31 16:16:49 sentry postgrey[576]: action=pass, reason=client whitelist, client_name=mail1.bemta8.messagelabs.com, client_address=XXX.XXX.XXX.XXX, sender=XXXXX@XXXXX, recipient=XXXXX@XXXXX
May 31 16:17:44 sentry amavis[XXXXX]: (XXXXX) Passed CLEAN {RelayedInbound,Quarantined}, [216.82.243.208]:58830 [203.20.196.14] <XXXXX@XXXXX> -> <XXXXX@XXXXX>, quarantine: Q/clean-QQoKuYED7CJa, Queue-ID: 6B8FE4AD18A, Message-ID: <XXXXX@XXXXX>, mail_id: QQoKuYED7CJa, Hits: 2.345, size: 656110, queued_as: E05FA4AD1B0, Tests: [BAYES_00=-1.9,DKIM_SIGNED=0.1,DKIM_VALID=-0.1,DKIM_VALID_AU=-0.1,HTML_MESSAGE=0.001,IGNORE_BAYES_00=1.9,KAM_NW=2.75,PYZOR_CHECK=1.392,RCVD_IN_MSPIKE_H2=-1.697,SPF_HELO_PASS=-0.001], dkim_sd=messagelabs:XXXXX, 6324 ms
May 31 16:17:44 sentry amavis[XXXXX]: (XXXXX) Passed CLEAN, <XXXXX@XXXXX> -> <monica@XXXXX>, Hits: 2.345, tag=-999, tag2=5, kill=5, queued_as: E05FA4AD1B0, L/Y/0/0
May 31 16:17:46 sentry postfix/smtp[77470]: E05FA4AD1B0: to=<XXXXX@XXXXX>, relay=XXX.XXX.XXX.XXX[XXX.XXX.XXX.XXX]:25, delay=1.7, delays=0.04/0/0.14/1.5, dsn=2.6.0, status=sent (250 2.6.0 <XXXXX@XXXXX> [InternalId=XXXXX] Queued mail for delivery)

MessageLabs > SpamTitan > Exchange (not since May 31)

The MX records for the MessageLabs user are:

cluster5.us.messagelabs.com

cluster5a.us.messagelabs.com

Any ideas?

0

Related:

7022962: Mail relay not working with SLES11 postfix

This document (7022962) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 Service Pack 3 (SLES 11 SP3)

Situation

Customer has a SLES11 SP3 server and when they configure postfix to relay mail to another SMTP server, it fails to relay the mail message and shows an error in the /var/log/mail log file, the error is :

May 1 18:24:21 USA-US-X1015 postfix/smtpd[29037]: NOQUEUE: reject: RCPT from unknown[10.43.64.178]: 451 4.3.0 <john.smith@mycompany.com>: Temporary lookup failure; from=<john.smith@mycompany.com> to=<john.smith@mycompany.com> proto=ESMTP helo=<mycompany.com>

Resolution

It was discovered in the problem server “main.cf” file there as an invalid ip address range listed in the

“mynetworks” parameter. Of the 28 ip address ranges listed in this parameter, one was invalid, it was :
10.205.149/0/24
It should be :
10.205.149.0/24
Once this was corrected and postfix restarted, the problem went away.

Cause

Invalid ip address range in the postfix main.cf configuration file.

Additional Information

A clue to this solution was listed in the error one line above the error listed in the “Situation” section of this

technical document, it was :
postfix/smtpd[29037]: warning: bad net/mask pattern: “10.205.149/0/24”

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related: