Email Security.cloud

 View Only
  • 1.  Delivery failed 20 attempts

    Posted Oct 02, 2013 11:18 AM

    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?




  • 2.  RE: Delivery failed 20 attempts

    Posted Oct 02, 2013 12:49 PM

    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



  • 3.  RE: Delivery failed 20 attempts

    Posted Oct 02, 2013 12:52 PM

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



  • 4.  RE: Delivery failed 20 attempts

    Posted Oct 03, 2013 08:17 AM

    Still no reply back?

     

    Bob



  • 5.  RE: Delivery failed 20 attempts

    Posted Oct 04, 2013 06:43 AM

    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