delivery delay

Discussion regarding the Standard version.
Post Reply
ted
Posts: 19
Joined: Thu Jul 14, 2011 7:25 pm

delivery delay

Post by ted » Mon Nov 28, 2011 9:41 pm

It seems that I have a problem delivering mail to clients that are filtering their incoming mail at MessageLabs. No message will go directly out of my MailEnable server. It will send a "Message Delivery Delay" back to the sender and the message will sit in the outbound queue for 20 minutes or so. I went into nslookup and got the IPs for the MX records and tried to telnet to each of them directly from the ME server and only 2 of them allowed a connection, the others all gave "failed connection" responses immediately. All of the messages are eventually delivered to the recipient. I have looked on MXtoolbox and DNSstuff and the ME server does not seem to tbe Blacklisted, but do not know of a way to check this specifically at MessageLabs. Anyone else having problems similar to this? And is there a way to turn off the "message delay" messages or at least a setting so that the sender only gets them after several failed attempts? thanks.

MailEnable-Ian
Site Admin
Posts: 9166
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: delivery delay

Post by MailEnable-Ian » Mon Nov 28, 2011 11:10 pm

Hi,

Please review the following topic within the documentation for delivery delay notifications settings: http://www.mailenable.com/documentation ... ivery.html

For your problems sending to the remote server you will first need to inspect the SMTP activity and debug log files in respect to the date/time, sender/recipient addresses of the messages you are sending to see if there are any errors reported during the SMTP transaction. The following can assist you with the search (I.e: use the message tracking utility): http://www.mailenable.com/kb/viewarticl ... 020252.htm

Is there any error reported within the delivery delay message? Have you tried contacting the administrators of the remote mail server to see if they can provide more information as to why you are unable to send to their server?
Regards,

Ian Margarone
MailEnable Support

ted
Posts: 19
Joined: Thu Jul 14, 2011 7:25 pm

Re: delivery delay

Post by ted » Tue Nov 29, 2011 12:58 pm

Thanks for the screen shot, that is exactly what I was trying to find.

And, have not gotten any error messages in the delivery delay messages, only this:
Reason: Mail Server for DESTINATION.com could not be contacted at this time.
MailEnable will keep trying to deliver this message and will notify you of
any progress.

And if I telnet to the MessageLab servers from this ME server, only a couple of the servers will accept a connection. I contacted MessageLabs and they will not talk to me as I do not have an account with them.

From the MessageTrackingUtility, I can see that some of the messages took over 2 hours to leave the ME server, but have not found any errors yet. But I am still getting used to these log files. thanks.

ted
Posts: 19
Joined: Thu Jul 14, 2011 7:25 pm

Re: delivery delay

Post by ted » Tue Nov 29, 2011 8:08 pm

After digging through the SMTP debug logs, it seems to be saying the same thing as the activity log. Here are a couple of lines of an offending message.

11/29/11 10:16:05 ME-I0123: Domain [######.com] has MX list [cluster4.us.messagelabs.com,cluster4a.us.messagelabs.com]
11/29/11 10:16:05 ME-I0026: [32746D1C084F43ED856EB2E508275CF7.MAI] Sending message
11/29/11 10:16:05 ME-IXXXX: [SYSTEM] DNS resolved to the following record: IP Address=216.82.250.19, Family=2, Type=1, Protocol= 0
11/29/11 10:16:06 ME-I0074: [816] (Debug) End of conversation
11/29/11 10:16:06 ME-E0038: [32746D1C084F43ED856EB2E508275CF7.MAI] Communications Error: Socket connection to cluster4.us.messagelabs.com failed (error 10061). The host was either not contactable or it rejected your connection. Socket Family = 2; Host=216.82.250.19; Port=25
11/29/11 10:16:06 ME-I1350: [32746D1C084F43ED856EB2E508275CF7.MAI] Attempting to connect to MX 2 of 2 (cluster4a.us.messagelabs.com).
11/29/11 10:16:06 ME-IXXXX: [SYSTEM] DNS resolved to the following record: IP Address=85.158.139.103, Family=2, Type=1, Protocol=0
11/29/11 10:16:07 ME-E0038: [32746D1C084F43ED856EB2E508275CF7.MAI] Communications Error: Socket connection to cluster4a.us.messagelabs.com failed (error 10061). The host was either not contactable or it rejected your connection. Socket Family = 2; Host=85.158.139.103; Port=25
11/29/11 10:16:07 ME-E0059: [32746D1C084F43ED856EB2E508275CF7.MAI] Message Delivery Failure. Attempt (0): Could not find mail server for domain (######.com). The remote mail server could not be contacted at this time. Message has been requeued.

MailEnable-Ian
Site Admin
Posts: 9166
Joined: Mon Mar 22, 2004 4:44 am
Location: Melbourne, Victoria, Australia

Re: delivery delay

Post by MailEnable-Ian » Tue Nov 29, 2011 11:04 pm

Hi,

Are you able to send to other addresses I.e: ian@mailenable.com?
Regards,

Ian Margarone
MailEnable Support

ted
Posts: 19
Joined: Thu Jul 14, 2011 7:25 pm

Re: delivery delay

Post by ted » Wed Nov 30, 2011 12:56 pm

Yes. I can send to other domains. Domains using MessageLabs for filtering are the only ones that I have found to have this delay issue so far. But I tried another domain that uses MessageLabs' European servers and that one was delayed for over 12 hours and still has not been delivered. I have contacted the owner of the domain to see if I can get them to contact MessageLabs (Symantec) and at least get some info on why they are dropping/refusing the connections from this server. This will probably take some time as MessageLabs will not talk to me directly because I am not a customer. Thanks.

netmo
Posts: 31
Joined: Mon Jun 20, 2011 7:46 pm

Re: delivery delay

Post by netmo » Wed Apr 18, 2012 2:50 pm

Was there a follow-up as we are experiencing the same problem the last few weeks.

PackerIntl
Posts: 1
Joined: Sat Apr 28, 2012 12:42 am

Re: delivery delay

Post by PackerIntl » Sat Apr 28, 2012 12:50 am

Has anyone found a resolve to this issue?

You'll like to know (or not) that it is not just mailenable having this issue. In the past month, one of my clients has experienced he same thing with two separate email domains that are MessageLabs filtered. The event log just says that the connection was dropped by the MessageLabs server w/ no reason given. And it will do this over and over and over again until the message finally falls out of the queue with an NDR saying it couldn't be delivered.

This is on Small Business Server 2003 with all of the service packs and updates applied.

If you know the solution I would love to hear it.

Post Reply