Message delivery has been delayed. Hotmail, yahoo etc reject
-
- Posts: 5858
- Joined: Fri Jan 16, 2004 6:49 am
- Location: Melbourne
Firstly I would make you first retry after 5 minutes anything less than this could be rejected with some greylistings waiting for 4 minutes before letting the retry through.
Your errors here are due to the remote server not with yourself, I know yahoo are doing something as I get the same problems when I telnet to the domain while testing.
Also I noticed you are failing on the DATA command you may like to look at this article;
http://www.mailenable.com/kb/viewarticl ... 020063.htm
Your errors here are due to the remote server not with yourself, I know yahoo are doing something as I get the same problems when I telnet to the domain while testing.
Also I noticed you are failing on the DATA command you may like to look at this article;
http://www.mailenable.com/kb/viewarticl ... 020063.htm
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.
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.
-
- Posts: 5858
- Joined: Fri Jan 16, 2004 6:49 am
- Location: Melbourne
Hi try the article now I have updated the link.
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.
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.
I am having the same problem, but in my case, I am getting it when sending to an Exchange 2003 server in the same location. So, my failure is not greylisting, and there is only one firewall between the MailEnable Enterprise server, and the Exchange server. I have confirmed that this is not an MTU problem, as noted in the article referenced above. Since I happen to manage the other server as well, I know that is does not have any connectivity issues, etc. And yet some mail gets delivered fine, and others just fail.
Here is the relevant log entries:
02/09/06 04:51:41 ME-E0011: [307D1EEDC9A8488A9F3FF7532C794414.MAI] Failed to send socket data to remote server (error 10054).
02/09/06 04:51:41 ME-E0008: [307D1EEDC9A8488A9F3FF7532C794414.MAI] Outbound, could not send the command to the server (error 10054).
02/09/06 04:51:41 ME-I0148: [307D1EEDC9A8488A9F3FF7532C794414.MAI] DATE (DATA Termination) command failed.
02/09/06 04:51:41 ME-E0146: [307D1EEDC9A8488A9F3FF7532C794414.MAI] DATA Command Failed.
02/09/06 04:51:41 ME-E0008: [307D1EEDC9A8488A9F3FF7532C794414.MAI] Outbound, could not send the command to the server (error 10054).
02/09/06 04:51:41 ME-E0033: [307D1EEDC9A8488A9F3FF7532C794414.MAI] DATA Transmission failed.
02/09/06 04:51:41 ME-E0060: [307D1EEDC9A8488A9F3FF7532C794414.MAI] - System could not be delivered to its target domain (britonhouse.com). Message returned to Sender.
Ben, do you have any thoughts as to why? The server with MailEnable also does DNS for the receiving domain, so it's not a DNS lookup issue either.
Here is the relevant log entries:
02/09/06 04:51:41 ME-E0011: [307D1EEDC9A8488A9F3FF7532C794414.MAI] Failed to send socket data to remote server (error 10054).
02/09/06 04:51:41 ME-E0008: [307D1EEDC9A8488A9F3FF7532C794414.MAI] Outbound, could not send the command to the server (error 10054).
02/09/06 04:51:41 ME-I0148: [307D1EEDC9A8488A9F3FF7532C794414.MAI] DATE (DATA Termination) command failed.
02/09/06 04:51:41 ME-E0146: [307D1EEDC9A8488A9F3FF7532C794414.MAI] DATA Command Failed.
02/09/06 04:51:41 ME-E0008: [307D1EEDC9A8488A9F3FF7532C794414.MAI] Outbound, could not send the command to the server (error 10054).
02/09/06 04:51:41 ME-E0033: [307D1EEDC9A8488A9F3FF7532C794414.MAI] DATA Transmission failed.
02/09/06 04:51:41 ME-E0060: [307D1EEDC9A8488A9F3FF7532C794414.MAI] - System could not be delivered to its target domain (britonhouse.com). Message returned to Sender.
Ben, do you have any thoughts as to why? The server with MailEnable also does DNS for the receiving domain, so it's not a DNS lookup issue either.
Glenn Hunt
Hunt Data Services Inc.
Hunt Data Services Inc.
-
- Posts: 192
- Joined: Tue Mar 22, 2005 1:18 pm
-
- Posts: 4
- Joined: Fri Feb 06, 2004 9:52 pm
- Location: Bolingbrook
Hi Ben,
As per your suggestions from your previous posting we upgraded our Mail enable Professional 1.72 and also applied the SMTP fix. Now we cannot even receive any email. This is turning into a real serious problem. We never had this problem before. Below is the link to our diagnostic report which we have posted at:
http://www.karmaahost.com/mepro/02112006.html
This was taken just couple minutes back using diagnostic report. We don't know what is the best way to configure settings in Mailenable Pro 1.72. When you say it is an upgrade and inspite of selecting "Preserving the existing configuration data" why do we have to manually all the settings all over again.
I think there is a serious bug in MailEnable Pro alltogether. We now cannot even receive any mail. Please somebody point into right direction or settings.
We are lost. We are ready to pay for this but we need a full proof solutions. WE WILL BE ABLE TO GIVE SERVER ACCESS IF SOMEBODY FROM MAILENABLE PRO WOULD BE WILLING TO HELP.
Hoping to get the solution fast as we are losing business.
As per your suggestions from your previous posting we upgraded our Mail enable Professional 1.72 and also applied the SMTP fix. Now we cannot even receive any email. This is turning into a real serious problem. We never had this problem before. Below is the link to our diagnostic report which we have posted at:
http://www.karmaahost.com/mepro/02112006.html
This was taken just couple minutes back using diagnostic report. We don't know what is the best way to configure settings in Mailenable Pro 1.72. When you say it is an upgrade and inspite of selecting "Preserving the existing configuration data" why do we have to manually all the settings all over again.
I think there is a serious bug in MailEnable Pro alltogether. We now cannot even receive any mail. Please somebody point into right direction or settings.
We are lost. We are ready to pay for this but we need a full proof solutions. WE WILL BE ABLE TO GIVE SERVER ACCESS IF SOMEBODY FROM MAILENABLE PRO WOULD BE WILLING TO HELP.
Hoping to get the solution fast as we are losing business.
Thanks
KarmaaHost
KarmaaHost
-
- Site Admin
- Posts: 4441
- Joined: Tue Jun 25, 2002 3:03 am
- Location: Melbourne, Victoria Australia
The best way to resolve issues like those you mention is via a support ticket. Some of the things you mention here have not been seen in any other installations. See http://www.mailenable.com/support
Specifically, if you are saying that your have upgraded (with the option to preserve settings) and they have been overwritten, then this is very serious (and something that has not been reported before).
In terms of not being able to receive mail at all, this also is very unusual.
Usually this means that your ISP has blocked your inbound SMTP port, your public DNS is invalid/pointing to the wrong server or that a firewall or some other service is preventing MailEnable form binding to port 25).
The only thing evident in your diagnostic report is that there seems to be a large quantity of Spam being sent out of your server (which is probably why other hosts are rejecting your mail/not accepting your connection).
Other than that, there is no obvious problem in the diagnostic report you provided - which means that the SMTP log file is the next point of call in determining why you are not receiving inbound mail.
Again, the support ticketing system is the most appropriate means of resolving specific issues because it is easier to review logs and obtain terminal service access if required.
Specifically, if you are saying that your have upgraded (with the option to preserve settings) and they have been overwritten, then this is very serious (and something that has not been reported before).
In terms of not being able to receive mail at all, this also is very unusual.
Usually this means that your ISP has blocked your inbound SMTP port, your public DNS is invalid/pointing to the wrong server or that a firewall or some other service is preventing MailEnable form binding to port 25).
The only thing evident in your diagnostic report is that there seems to be a large quantity of Spam being sent out of your server (which is probably why other hosts are rejecting your mail/not accepting your connection).
Other than that, there is no obvious problem in the diagnostic report you provided - which means that the SMTP log file is the next point of call in determining why you are not receiving inbound mail.
Again, the support ticketing system is the most appropriate means of resolving specific issues because it is easier to review logs and obtain terminal service access if required.
Regards, Andrew
-
- Posts: 5858
- Joined: Fri Jan 16, 2004 6:49 am
- Location: Melbourne
For anyone wondering it turned out that Karmaahost was running an IMAIL server on the same machine as MailEnable. This was preventing the binding of MailEnable to the necessary ports, obviously this issue has nothing to do with the Data errors we are seeing in the other posts.
In regards to the other data errors I suggest you submit a ticket through MailEnable support as they need to be assessed on a host by host basis to find out why the remote server/client is dropping your connection.
In regards to the other data errors I suggest you submit a ticket through MailEnable support as they need to be assessed on a host by host basis to find out why the remote server/client is dropping your connection.
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.
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.
-
- Posts: 4
- Joined: Fri Feb 06, 2004 9:52 pm
- Location: Bolingbrook
Hi Ben,
First of all we would like to thank Ben and his team to point us to fixing the IMail issue. We are now able to receive emails.
We are still testing with Hotmail and Yahoo account as well as other major ISPs. We are very excited about this major issue getting fixed as we have lost some clients due this issue.
We shall keep you guys posted on to the outcome. Ben, we would like to keep this ticket open just for bit longer till we are done testing. We should be done testing in next 48 hours.
Once again we appreciate all the inputs that you fine folks have given on this issue. We didn't know this was a bigger issue than we thought.
First of all we would like to thank Ben and his team to point us to fixing the IMail issue. We are now able to receive emails.
We are still testing with Hotmail and Yahoo account as well as other major ISPs. We are very excited about this major issue getting fixed as we have lost some clients due this issue.
We shall keep you guys posted on to the outcome. Ben, we would like to keep this ticket open just for bit longer till we are done testing. We should be done testing in next 48 hours.
Once again we appreciate all the inputs that you fine folks have given on this issue. We didn't know this was a bigger issue than we thought.
Thanks
KarmaaHost
KarmaaHost
-
- Posts: 5858
- Joined: Fri Jan 16, 2004 6:49 am
- Location: Melbourne
The retries that I set up on servers that seems to be pretty kosher to handle the latest grey listings and yahoo issues are;
First Retry - 5
Second Retry - 15
Third Retry - 25
Subsequent - 240
Failed Lifetime - 48
Don’t send delivery delays until - 30
First Retry - 5
Second Retry - 15
Third Retry - 25
Subsequent - 240
Failed Lifetime - 48
Don’t send delivery delays until - 30
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.
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.
-
- Posts: 11
- Joined: Wed Jul 27, 2005 7:55 pm
redirection to Hotmail emails being rejected
I upgraded to Enterprise version 1.23 last week. Since then any emails being redirected to Hotmail or popular ISP's are being rejected.
I've read the thread so far but am not sure what settings I need to check and how I change them.
Can anyone help please?
I've read the thread so far but am not sure what settings I need to check and how I change them.
Can anyone help please?
-
- Posts: 5858
- Joined: Fri Jan 16, 2004 6:49 am
- Location: Melbourne
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.
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.