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:

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:

#5.7.1 smtp; 550 5.7.1 Relaying denied> #SMTP#

I need a solution

Hi Folks 

I wonder if there is any Message Labs gurus out there taht can give me some advise:

We recently moved over to 365 email system and ever since any of our previous senders on message labs are getting bounce back messages with an error 

Your message wasn’t delivered due to a permission or security issue. It may have been rejected by a moderator, the address may only accept e-mail from certain senders, or another restriction may be preventing delivery.

The #< #5.7.1 smtp; 550 5.7.1 <>… Relaying denied> #SMTP#

any help would be apprecated 

 
0

Related:

SMTP AUTH Sender Login Map

I do not need a solution (just sharing information)

We have deployed SMG at Gateway in our branch office and we are using office365, i am planning to use SMPTH AUTH to allow users to login and directly send email through SMG, i have below concern which i am still not able to figure out:

How to restrict sending users from using any other “From address” other than his own email address,  i cannot find any option to enable this check, do i know to create custom content policy? 

My second query is related to inbound mails, we are getting spam from senders who are using different return-path address than from-address. Normally we dont receive any corporate mails with different MAIL-FROM/Return path. Do we need to create custom policy for this type of inbound mails?

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:

Emails from my email server to messagelabs times out

I need a solution

Hello,

Recently emails from my corporate email server to companies using your service started failing. In looking at the SMTP logs, i see our servers set up the connection, you send me your certificate, i send mine, then i start sending the message. I’m posting a portion of the logs after the cert exchange:

2018-03-23T16:35:21.315Z,xxxx,08D58F9040FA7A2A,27,x.x.x.x,216.82.251.230:25,<,250-PIPELINING,

2018-03-23T16:35:21.315Z,xxxx,08D58F9040FA7A2A,28,x.x.x.x,216.82.251.230:25,<,250 8BITMIME,

2018-03-23T16:35:21.315Z,xxxx,08D58F9040FA7A2A,29,x.x.x.x,216.82.251.230:25,*,,sending message with RecordId 231928234012 and InternetMessageId <65b0e54a982546729fc3218f2a7722b1@Exchange.bbtel.com>

2018-03-23T16:35:21.315Z,xxxx,08D58F9040FA7A2A,30,x.x.x.x,216.82.251.230:25,>,MAIL FROM:<xxxx@brandenburgtel.com>,

2018-03-23T16:35:21.315Z,xxxx,08D58F9040FA7A2A,31,x.x.x.x,216.82.251.230:25,>,RCPT TO:<xxxx@neca.org>,

2018-03-23T16:35:21.315Z,xxxx,08D58F9040FA7A2A,32,x.x.x.x,216.82.251.230:25,>,RCPT TO:<xxxx@neca.org>,

2018-03-23T16:35:22.456Z,xxxx,08D58F9040FA7A2A,33,x.x.x.x,216.82.251.230:25,<,250 2.0.0 MAIL FROM accepted,

2018-03-23T16:35:22.456Z,xxxx,08D58F9040FA7A2A,34,x.x.x.x,216.82.251.230:25,-,,Local

Any idea what could be going on?

0

Related: