Message delivery has been delayed. Hotmail, yahoo etc reject

Discussions on webmail and the Professional version.
karmaahost
Posts: 4
Joined: Fri Feb 06, 2004 9:52 pm
Location: Bolingbrook

Message delivery has been delayed. Hotmail, yahoo etc reject

Post by karmaahost » Mon Jan 23, 2006 12:12 pm

Hello Folks,

We are having this issue that our mail going to big ISPs such as Hotmail, yahoo, paypal and ebay are being rejected. We checked our diagnostics report and have this report as follows:

http://www.karmaahost.com/mepro/012306.htm

This clearly states that SMTP Outbound status as being rejected by these ISPs. We have a hint that it might be due to the Reverse DNS not being set but want to confirm and know how to do that. We have not done this before and would to know how to do this.

We are using Windows 2003 advanced server and Mailenable Professional Version 1.5

Any suggestions, tips, concerns would be greatly appreciated.Please help. :)

Thanks
KarmaaHost

MailEnable
Site Admin
Posts: 4441
Joined: Tue Jun 25, 2002 3:03 am
Location: Melbourne, Victoria Australia

Post by MailEnable » Mon Jan 23, 2006 1:10 pm

You are not on any common blacklist... see: http://www.dnsstuff.com/tools/ip4r.ch?ip=69.44.153.71

You have a valid ptr for your forced outbound interface.. see:
http://www.dnsstuff.com/tools/ptr.ch?ip=69.44.153.71

The problem is most likely that one of your users has been sending spam through your system. You should check your logs to identify the source of the spam.

As well as reviewing the logs to ensure that you are not being abused, you should consider that any mail redirections containing spam are likely to present you as a source of spam.
Regards, Andrew

karmaahost
Posts: 4
Joined: Fri Feb 06, 2004 9:52 pm
Location: Bolingbrook

Post by karmaahost » Mon Jan 23, 2006 3:24 pm

We have changed our DNS address as the IP address of our servers have been switched to 64.34.197.201 from 69.44.153.71 That might be the issue. We have switched the DNS settings in SMTP properties wondering why it is still binding to the old one.

How do we fix this?

Thanks for the quick response.
KarmaaHost

MailEnable-Ben
Posts: 5858
Joined: Fri Jan 16, 2004 6:49 am
Location: Melbourne

Post by MailEnable-Ben » Tue Jan 24, 2006 5:53 am

Did you restart the SMTP service after the change? If so what do you mean the SMTP is binding to the old DNS server still?
Regards,

Product Services
MailEnable Pty Ltd

To keep track of all ME company updates and version releases you should subscribe to the MailEnable list at http://www.mailenable.com or the RSS feed http://www.mailenable.com/rss.

fdickey
Posts: 37
Joined: Thu May 27, 2004 5:57 pm
Location: Crossville, TN
Contact:

silent grey listing and delivery delays

Post by fdickey » Tue Jan 24, 2006 10:57 pm

I have been experiencing this issue since around the beginning of December with yahoo.com, hotmail.com sometimes with aol.com and always with mac.com. My customers have been putting me in the hot seat over this issue for the past few weeks. I've been banging my head over the issue...wondering if there is something wrong with mail enable...or maybe our mail server...or maybe our bandwidth...but our mail server is really not that busy....we've changed IP's and everything.

Finally....today...I finally find a posting on an obscure forum through google that sheds a lot of light on this issue. Silent Grey Listing.

You see...silent grey listing is where a receiving mail server does a redelivery attempt challenge to the sending mail server by deliberatly cutting the connection on the first attempt.

We had our first initial redelivery attempt set to 15 minutes. After pondering on these things, I realized that we have a similar filter that temporarily auto-bans IPs if a certain IP fails any of our spam filter rules more than three times in 10 minutes. It drops an IP into a temporary cache for 10 minutes and begins a counter on it.

I think this grey list filter does something similar...and I think it "forgets" the IP after X number of minutes...therefore...if the sending mail server doesn't attempt redelivery within that X number of minutes, it gets re-challenged yet again...and gets stuck into an infinite loop!

I've confirmed this behavior. I dropped our initial redelivery attempt down to 1 minute, sent an email to a test account I setup on mac.com and whoala...instant failure on first attempt....smooth sailing on second attempt within the 1 minute time frame.

Now if I could just figure out how to get mail enable to stop sending delivery delay notices to my users the second that a delivery attempt fails. The delayed time setting in the SMTP properties doesn't appear to be working for some reason. I have it set to not send a delivery delay notice until after 30 minutes...but it is still sending one instantly.
Fred Dickey, fdickey@thinkhope.com
Hope Ministries and Outreach, Inc.
http://www.thinkhope.com

MailEnable-Ben
Posts: 5858
Joined: Fri Jan 16, 2004 6:49 am
Location: Melbourne

Post by MailEnable-Ben » Wed Jan 25, 2006 5:40 am

Hi Fdickey you are correct in your findings I have been reporting such things in this forum for about a month now but I guess on some matters people have to find out for themselves, which is what I love about our forum and many of the people who post in it. Hard to find one for a mail server company that compares. :wink:

Anyway you are correct, exactly because of this issue and our diagnosis of it there have been some changes that ended up in our latest patches. The best thing to do will be to upgrade to 1.71 through our link
http://www.mailenable.com/mailenableprof.exe then use the latest SMTP patch that can be found at http://www.mailenable.com/hotfix/mesmtpc.zip
Alternatively you can wait for the new kit if you like which will be available in the next few days just in testing phase now, keep an eye out on the web site.

This will fix any minor issues with the SMTP delivery delays properties, and also an issue where a wrong entered recipient domain was entered the email was not immediately bounced but retried. I believe that this should help with any grey listing and silent grey listing matters.
Regards,

Product Services
MailEnable Pty Ltd

To keep track of all ME company updates and version releases you should subscribe to the MailEnable list at http://www.mailenable.com or the RSS feed http://www.mailenable.com/rss.

fdickey
Posts: 37
Joined: Thu May 27, 2004 5:57 pm
Location: Crossville, TN
Contact:

delivery notifications

Post by fdickey » Wed Jan 25, 2006 7:34 pm

I'm using the enterprise 1.1 version...is there a patch for it or is that the one your speaking of? Sorry...just realized which forum this thread was in...I got to this thread from the search function while in the eterprise forum and assumed I was in a thread there....guess it pays to read..lol

Also, I'm having a weird issue with delivery failure notices ending up in the bad mail folder that should be getting delivered to local inboxes. I've tested the mx record our mail server is seeing for the domains to make sure it finds itself. I can telnet to itself on port 25 by both the IP given by the mx record and the 127.0.0.1 local loop address.

It looks like this happens when one of our users sends out an email that is too large and the delivery attempt fails.

Here is what the debug log says in these scenarios (this was like a 15MB email...no wonder hotmail rejected...but sender is unaware of failure):

01/25/06 14:05:59 ME-E0011: [10F8D87873FF4FC09AD2F4A8FBDBED79.MAI] Failed to send socket data to remote server (error 10054).
01/25/06 14:05:59 ME-E0008: [10F8D87873FF4FC09AD2F4A8FBDBED79.MAI] Outbound, could not send the command to the server (error 10054).
01/25/06 14:05:59 ME-I0148: [10F8D87873FF4FC09AD2F4A8FBDBED79.MAI] DATE (DATA Termination) command failed.
01/25/06 14:05:59 ME-E0146: [10F8D87873FF4FC09AD2F4A8FBDBED79.MAI] DATA Command Failed.
01/25/06 14:05:59 ME-E0008: [10F8D87873FF4FC09AD2F4A8FBDBED79.MAI] Outbound, could not send the command to the server (error 10054).
01/25/06 14:05:59 ME-E0033: [10F8D87873FF4FC09AD2F4A8FBDBED79.MAI] DATA Transmission failed.
01/25/06 14:05:59 ME-E0060: [10F8D87873FF4FC09AD2F4A8FBDBED79.MAI] - System could not be delivered to its target domain (hotmail.com). Message returned to Sender.
01/25/06 14:06:00 ME-I0119: Domain [xxx.com] has used local loopback address [127.0.0.1] because it is hosted locally.
01/25/06 14:06:00 ME-I0026: [10F8D87873FF4FC09AD2F4A8FBDBED79.MAI] Sending message
01/25/06 14:06:00 ME-E0036: [10F8D87873FF4FC09AD2F4A8FBDBED79.MAI] MAIL FROM Command Failed.
01/25/06 14:06:00 ME-E0008: [10F8D87873FF4FC09AD2F4A8FBDBED79.MAI] Outbound, could not send the command to the server (error 10038).
01/25/06 14:06:00 ME-E0060: [10F8D87873FF4FC09AD2F4A8FBDBED79.MAI] - System could not be delivered to its target domain (xxx.com). Message returned to Sender.
01/25/06 14:06:00 ME-I0074: (Debug) [396] end of conversation
Fred Dickey, fdickey@thinkhope.com
Hope Ministries and Outreach, Inc.
http://www.thinkhope.com

fdickey
Posts: 37
Joined: Thu May 27, 2004 5:57 pm
Location: Crossville, TN
Contact:

delivery notifications

Post by fdickey » Fri Jan 27, 2006 8:31 pm

We just had another issue with mac.com delivery. I have now modified our delivery settings to thus:

initial reattempt: 1 minute
second atttempt: 4 minutes
third attempt: 5 minutes
subsequent attempts: 5 minutes
lifetime of email: 2 hours

We did have our lifetime set to 30 hours...but with all the issues that grey listing seems to be creating, I decided that if someone is down for maintenace for more than 2 hours we will just have to fail the delivery.

That's the cost for having to "slam" mail servers to take an email from us because of some redelivery challenge that seems to get us stuck into a loop.
Fred Dickey, fdickey@thinkhope.com
Hope Ministries and Outreach, Inc.
http://www.thinkhope.com

MailEnable-Ben
Posts: 5858
Joined: Fri Jan 16, 2004 6:49 am
Location: Melbourne

Post by MailEnable-Ben » Mon Jan 30, 2006 3:26 am

It is possible you have another issue here looking at your debug logs can you show me the transaction in the activity log for the messages that are failing on the data command?
Regards,

Product Services
MailEnable Pty Ltd

To keep track of all ME company updates and version releases you should subscribe to the MailEnable list at http://www.mailenable.com or the RSS feed http://www.mailenable.com/rss.

mokuso
Posts: 3
Joined: Tue Jan 31, 2006 9:19 pm
Location: Montreal, Canada

Message delivery has been delayed

Post by mokuso » Tue Jan 31, 2006 9:33 pm

I just installed MailEnable Enterprise 1.1 over the weekend and I've been dealing with those "Message delivery has been delayed" messages since with people sending emails to @yahoo accounts.

I do not understand why I wasn't having those problems with the software I used before on the same computer, with the same IP and whitout a PTR record...

Regardless of this situation, I've created a valid PTR entry
(http://www.dnsstuff.com/tools/ptr.ch?ip=mail.mokuso.net)

and I'm still having this issue... Is there a delay for this to be functionnal ?

MailEnable-Ben
Posts: 5858
Joined: Fri Jan 16, 2004 6:49 am
Location: Melbourne

Post by MailEnable-Ben » Tue Jan 31, 2006 10:24 pm

We have put in a bit of extra logging and handling of such things in V1.72 which should be released by the end of today. The best delay settings I have found are;

First Retry - 5mins
Sec - 15mins
Third - 30

Dont send delivery delays until 30 mins

Try these settings after upgrading to version 1.2.
Last edited by MailEnable-Ben on Wed Feb 01, 2006 10:32 pm, edited 1 time in total.
Regards,

Product Services
MailEnable Pty Ltd

To keep track of all ME company updates and version releases you should subscribe to the MailEnable list at http://www.mailenable.com or the RSS feed http://www.mailenable.com/rss.

hardrocksr
Posts: 5
Joined: Wed Feb 01, 2006 4:41 pm

Post by hardrocksr » Wed Feb 01, 2006 9:22 pm

I think we may be having the same problem, or a problem simalar to this.

We are using mailenable pro 1.71 and are getting bouncebacks from aol. I did see 1 email that went through to aol, but can not get anymore.

when doing a sys diagnose we get the same oerror for messages going to aol "The socket connection to the remote host failed. The host was either not contactable or it rejected your connection."

we tried playing with the retry times but that seemed to have no effect.

I am pretty sure the email that went through also generated a mail delivery error.

What should I be looking into next to try and track this problem down?

MailEnable-Ben
Posts: 5858
Joined: Fri Jan 16, 2004 6:49 am
Location: Melbourne

Post by MailEnable-Ben » Wed Feb 01, 2006 10:34 pm

The 1.72 version is there now. Install it and set the delivery delay settings to my earlier post anything outside of this will probably mean you have a problem on the server or AOL has taken offence to you.
Regards,

Product Services
MailEnable Pty Ltd

To keep track of all ME company updates and version releases you should subscribe to the MailEnable list at http://www.mailenable.com or the RSS feed http://www.mailenable.com/rss.

plabry
Posts: 11
Joined: Fri Nov 18, 2005 8:10 pm

Post by plabry » Thu Feb 02, 2006 4:08 pm

I'm having a similar problem with yahoo and ME enterprise. I upgraded MESMTPC to the 1/25/2006 version and changed the retry timings to

1 min
4 min
5 min
5 min
2 hours

And I still have failures sending to Yahoo accounts. I did find our IP on a single black list but according to Yahoo, there would be a message regarding rejection due to blacklisting in the log if this was the case. My log entries look like this.

02/02/06 10:22:50 ME-E0038: [F089ED7D3F424CFC9FB9EE8E442701A1.MAI] Communications Error: Socket connection to mx2.mail.yahoo.com failed (error 10060). The host was either not contactable or it rejected your connection.
02/02/06 10:22:52 ME-E0038: [3880769F696F4D2E99E099D6E7D29E35.MAI] Communications Error: Socket connection to mx3.mail.yahoo.com failed (error 10060). The host was either not contactable or it rejected your connection.
02/02/06 10:22:52 ME-I0148: [5842FBC5D0DD4AA4ACD404F49B800D96.MAI] DATE (DATA Termination) command failed with temporary return code.
02/02/06 10:22:52 ME-E0033: [5842FBC5D0DD4AA4ACD404F49B800D96.MAI] DATA Transmission failed.
02/02/06 10:22:52 ME-E0059: [5842FBC5D0DD4AA4ACD404F49B800D96.MAI] Message Delivery Failure. Attempt (0): Domain (yahoo.com) returned temporary error for email. Message has been requeued.



I'm starting to wonder if perhaps Yahoo is having some difficulties with their mail servers. Some of the mail to Yahoo is getting through OK. I

ckvkkeek
Posts: 141
Joined: Tue Jun 28, 2005 1:23 am

Post by ckvkkeek » Thu Feb 02, 2006 8:45 pm

I am having these same issues with version 1.72 Pro.

Whats up?

Post Reply