Video Screencast Help
Give us your opinion and win with Symantec! Please help us by taking this survey to tell us about your experience with Symantec Connect, so that we can continue to grow and improve.  Take the survey.

Delivery failed 20 attempts

Created: 02 Oct 2013 | 4 comments

Hi

We have a customer Liberty Electronics who quite often has issues getting email through to a business using messagelabs. Their mail server name - mail.libertyelectronics.com; IP Address 66.71.204.139. Below is their latest failure; is the messagelabs spam filter blocking them?

-----Original Message-----
From: postmaster@libertyelectronics.com
[mailto:postmaster@libertyelectronics.com]
Sent: Tuesday, October 01, 2013 6:26 PM
To: erhoads@libertyelectronics.com
Subject: Undeliverable Mail

Delivery failed 20 attempts: pellis@aai.textron.com

Body of message generated response:




Original message follows.

Received: from DellRhoads [10.0.0.122] by libertyelectronics.com with ESMTP
  (SMTPD-11.5) id fe0c00004e67ba29; Tue, 1 Oct 2013 08:55:55 -0400
From: "Eric Rhoads" <erhoads@libertyelectronics.com>
To: "Patrick Ellis" <pellis@aai.textron.com>
References: <05fe01ce944d$b4364050$1ca2c0f0$@libertyelectronics.com>
<683C0BE4C62E5246B04DFE00A633386D21DE281A@TXAMASNWH026.ent.textron.com>
<026501ce985f$fc0871d0$f4195570$@libertyelectronics.com>
<683C0BE4C62E5246B04DFE00A633386D21DE660C@TXAMASNWH026.ent.textron.com>
<0a5601cea262$a3ed0f80$ebc72e80$@libertyelectronics.com>
<683C0BE4C62E5246B04DFE00A633386D21DEC448@TXAMASNWH026.ent.textron.com>
<110201cea9b2$3a26b090$ae7411b0$@libertyelectronics.com>
<683C0BE4C62E5246B04DFE00A633386D21E26351@TXAMASNWH026......ent.textron.com>
<045c01ceafcf$6e8ae310$4ba0a930$@libertyelectronics.com>
<683C0BE4C62E5246B04DFE00A633386D21E29E98@TXAMASNWH026.ent.textron.com>
<002c01ceafdb$b90ba5d0$2b22f170$@libertyelectronics.com>
<683C0BE4C62E5246B04DFE00A633386D21E29EDB@TXAMASNWH026.ent.textron.com>
<005501ceafde$78d09860$6a71c920$@libertyelectronics.com>
<683C0BE4C62E5246B04DFE00A633386D21E29F08@TXAMASNWH026.ent.textron.com>
<010d01ceb49f$949007f0$bdb017d0$@libertyelectronics.com>
<683C0BE4C62E5246B04DFE00A633386D2
	1E2C087@TXAMASNWH026.ent.textron.com>
In-Reply-To: 
Subject: FW: AAI PO 1130229 General Status
Date: Tue, 1 Oct 2013 08:55:57 -0400
Organization: Liberty Electroincs, Inc.
Message-ID: <0a3501cebea5$927add90$b77098b0$@libertyelectronics.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
 boundary=_Boundary_085555_40529168.00002718:00000000"
X-Mailer: Microsoft Outlook 14.0
Thread-Index:
AQIL0CQXzmdGP9NJZxklQxcWasc3wAIlvPjwAtPdwm8B+BoNrAGWOOwgAeEEQvgBfYl6kQHj
AQIL0CQXzmdGP9NJZxklQxcWasc3wAIlvPjwAtPdwm8B+NdIc
AVlAuukCO15u0QE/XhOiAlWxlCIBdWq4ngGaZrw4Ae2BcfoDWfTAnZh56LMwgAArN9CAAUF9YA=
Content-Language: en-us
Operating Systems:

Comments 4 CommentsJump to latest comment

Fiendslayer Paladin's picture

Hi there,

Are you able to provide the verbose logs from the sending mail server at Liberty? If you can paste a snapshot of the logs below - I should be able to advise what is causing the issue. It's likely that the sending IP is throttled by the MessageLabs/Symantec.cloud traffic shaping service - so if you are able to provide this then I will happily check for you to clarify if that's the case - although I appreciate if you do not wish to provide the IP in such a public forum.

As mentioned though if you can provide either the logs or the IP I should be able to clarify - but the logs would be preferable.

Kind regards,

- FP

crazygravy's picture

Dont have access to the logs the server is not in house here but @ Liberty - the IP is 66.71.204.139

Fiendslayer Paladin's picture

Hi Bob,

Having checked Liberty's IP it doesn't appear that Symantec.cloud are shaping the IP in anyway.

I have done some traces on the mails can indeed see that they all fail - the logs show a time out when connecting to Symantec.cloud as below:

SMTP Results - Tower 190, Server 4

2013-10-03 22:18:25.689109500  6014691:  *** session start ***
2013-10-03 22:18:25.689954500  6014691:  Remote IP: 66.71.204.139
2013-10-03 22:18:25.689972500  6014691:  Message reference: server-4.tower-190.messagelabs.com!1380838705!6014691!1
2013-10-03 22:18:25.689974500  6014691: 
2013-10-03 22:18:25.691961500  6014691:  < 220 server-4.tower-190.messagelabs.com ESMTP
2013-10-03 22:18:25.783194500  6014691:  > EHLO libertyelectronics.com
2013-10-03 22:18:25.783195500  6014691:  < 250-server-4.tower-190.messagelabs.com
2013-10-03 22:18:25.783196500  6014691:  250-STARTTLS
2013-10-03 22:18:25.783197500  6014691:  250-PIPELINING
2013-10-03 22:18:25.783197500  6014691:  250 8BITMIME
2013-10-03 22:18:25.876761500  6014691:  > MAIL FROM:<erhoads@libertyelectronics.com>
2013-10-03 22:18:25.879607500  6014691:  < 250 OK
2013-10-03 22:18:25.969561500  6014691:  > RCPT To:<brownpj@aai.textron.com>
2013-10-03 22:18:25.980892500  6014691:  - Using filter 'Brightmail' for recipient
2013-10-03 22:18:25.985781500  6014691:  < 250 OK
2013-10-03 22:18:26.076234500  6014691:  > RCPT To:<pellis@aai.textron.com>
2013-10-03 22:18:26.086491500  6014691:  - Using filter 'Brightmail' for recipient
2013-10-03 22:18:26.086498500  6014691:  < 250 OK
2013-10-03 22:18:26.176820500  6014691:  > DATA
2013-10-03 22:18:26.177297500  6014691:  < 354 go ahead
2013-10-03 22:22:26.271715500  6014691:  < 451 timeout (#4.4.2)
2013-10-03 22:22:27.986872500  6014691:  *** session end ***

As you can see from the above, our server issues the 354 go ahead command to the sending server, then we receive no response for 4 minutes and so the connection times out.

As such, you will need to get the sender to check their logs and clarify why the communication stops - it could be something firewall related so I would ask them to check both the mail server and the firewall for any issues.

Hope this helps.

Kind regards,

- FP