problems sending to certain domains all of a sudden

Discussions on webmail and the Professional version.
MailEnable-Ben
Posts: 5858
Joined: Fri Jan 16, 2004 6:49 am
Location: Melbourne

Post by MailEnable-Ben » Tue Dec 06, 2005 11:48 pm

Correct just the outbound IP will be checked against for a PTR record.

Here is one of my posts from another thread just FYI;

Hi, just a little update on the error 0 found in returned messages. This is a generic mail message returned by ME when the remote server inexplicitly terminates connection or rejects connection without notice.

Originally this was put into the message to explain the above and replace the earlier message with a code that could be better explained as opposed to the even more unclear message from earlier.

It would seem that this error is still confusing and does not handle the issue with an explanation that the problem is most likely not a problem with your MailEnable server but the remote, unless you are blacklisted or have no PTR yada yada......

We are in the process of changing this again and will simply try to write out the last line from the remote server and use the return codes if any to give maximum data on the disconnection. Yes we know, why didn’t we just do this in the first place well a case of minimum effort with maximum outcome but we now realize that more is needed
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.

bozak
Posts: 50
Joined: Fri Jun 20, 2003 9:36 pm

Post by bozak » Wed Dec 07, 2005 12:40 am

Thank you. I'll make sure I have a PTR for that IP, and the ourbound IP isn't on any blacklists.

thanks.

fellow ben (aka bozak)

dynaweb
Posts: 5
Joined: Wed Dec 07, 2005 3:01 am

Post by dynaweb » Wed Dec 07, 2005 4:22 am

From what I can tell, it all points to yahoo having connectivity issues lately.
Lots of timeouts in testing.

paarlberg
Posts: 1071
Joined: Tue Mar 02, 2004 7:33 pm
Location: Atlanta, GA, USA

Post by paarlberg » Wed Dec 07, 2005 9:50 am

I am also seeing the same issues. It started about the first of the month. I moved to a new hosting location and I have verified that there is a PTR record, we are not on a blacklist, and the issues are with several domains in South Africa and yahoo.com.

Is there a global melt down happening :?

Also this is happening on 3 servers in 3 locations on 3 different IP ranges (different IP range owners).

Our SPF records are strict to only allow mail from our servers and all ip ranges or servers are listed in there.

paarlberg
Posts: 1071
Joined: Tue Mar 02, 2004 7:33 pm
Location: Atlanta, GA, USA

Post by paarlberg » Wed Dec 07, 2005 10:16 am

I have also confirmed that it happens on versions prior to 1.7 Pro. I have another system that is an old version of Pro 1.18 that I have kept for testing and is actually running as a Standard version since the eval period is over..

It is also having the problem. It is on a 4th network in another country (US).

Could yahoo and some others be using some new requirement to prevent mail from being accepted? Or a possible bug in a mail server that is common to the problem domains?

paarlberg
Posts: 1071
Joined: Tue Mar 02, 2004 7:33 pm
Location: Atlanta, GA, USA

Post by paarlberg » Wed Dec 07, 2005 2:26 pm

After some digging, I have found that all of the servers seem to be running a greylisting service which is causing the mail to fail.

http://www.dnspark.com/support/faqs.php ... on=6&faq=1

mf_scott
Posts: 15
Joined: Mon Mar 15, 2004 7:41 pm

Post by mf_scott » Thu Dec 08, 2005 12:05 am

paarlberg wrote:After some digging, I have found that all of the servers seem to be running a greylisting service which is causing the mail to fail.

http://www.dnspark.com/support/faqs.php ... on=6&faq=1
Do you know if Yahoo! uses this service? I've checked their FAQs and help and see no reference to greylisting, but they seem to be the only domain we are having consistent delays sending to. All emails do seem to go through eventually however, which leads me to believe that it could very possibly be greylisting on their end.

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

Post by MailEnable-Ben » Thu Dec 08, 2005 12:30 am

I think I mentioned somewhere in this thread exactly that, in some circumstances it does look like there is a type of silent grey listing being performed on some mailboxes in regards to yahoo. It may also be linked to a throttling service that starts grey listing after an account has received too much mail or something like this. Although this is just all guess work as yahoo seem to be keeping tight lipped about alot of these problems.
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.

mf_scott
Posts: 15
Joined: Mon Mar 15, 2004 7:41 pm

Post by mf_scott » Thu Dec 08, 2005 1:26 am

Assuming that Yahoo! is doing some sort of greylisting, is there a way to prevent MailEnable from sending the first delay notice? This would allow one retry to occur and hopefully pass the greylisting filter without my customers receiving delay notices.

Also, is there any way to configure MailEnable so that it will notify the sender on a successful send of a previously delayed email? The delay notification says "MailEnable will keep trying to deliver this message and will notify you of any progress.", but if the message goes through on a subsequent retry it does not notify the sender.

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

Post by MailEnable-Ben » Thu Dec 08, 2005 1:36 am

The settings that you are looking for can be found in the ME Admin MMC->SMTP Properties->Delivery TAB.
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.

bozak
Posts: 50
Joined: Fri Jun 20, 2003 9:36 pm

tequila helps you know the truth.

Post by bozak » Thu Dec 08, 2005 3:06 am

MailEnable is bad ass.

Yahoo's mail servers are cheap whores.

yahoo addresses were failing from
http://dnsstuff.com as well ...

what do people expect when they get a free email address from a crappy marketing company.

ME FOREVER!




sorry ... the tequila made me do it.

baz_ni
Posts: 6
Joined: Wed Nov 30, 2005 3:12 pm

Post by baz_ni » Thu Dec 08, 2005 10:01 am

My problem wasn't just with Yahoo, it stopped sending to all external domains, only sending locally worked. I say "was" because for the last four days, everything has been running fine, and the only thing I done was delete about 20 odd emails that were in the the inbound folder, although not showing up in MMC inbound. All the emails had nothing in them..

Thanks anyway,

Baz..

Chrissicom
Posts: 10
Joined: Sun Feb 13, 2005 8:39 am

Post by Chrissicom » Thu Dec 08, 2005 9:12 pm

Sorry if I am a little late on this but I think one very important thing hasn't been mentioned here yet.
You should absolutely make sure that your DNS server has a PTR (Reverse DNS) entry for your mail servers address.

For example when your mail server is called

mail.domain.com

and has the ip

1.2.3.4

a reverse lookup to 1.2.3.4

should return mail.domain.com and not nothing

otherwise many strictly setup mail servers will block mails sent from you, because they assume temporarily setup spam servers which generally do not have any ptr record.
You can also improve acceptance of your outbound mail by adding an SPF and Sender ID txt record to your DNS. If you need help with this e-mail to webmaster@hydroconsult.net.

paarlberg
Posts: 1071
Joined: Tue Mar 02, 2004 7:33 pm
Location: Atlanta, GA, USA

Post by paarlberg » Fri Dec 09, 2005 8:41 am

I found a work around for some remote domains..

I set my 1st retry to 5 minutes and the mails went out. Some are still failing, I will restart the SMTP service to reset the failure count to 0 and see if that helps.

It appears that ME is not handling the greylisting request to resend in 300 seconds very well and then the remote server sees it as a new attempt..

Can the ME people confirm that it is properly handling the greylisting requests?

ccwong
Posts: 11
Joined: Thu Apr 03, 2003 2:00 am
Location: Hong Kong

Post by ccwong » Mon Dec 12, 2005 1:45 am

Same proble issue in HK Yahoo Server.

MailEnable: Message delivery has been delayed.

Message is waiting at "company.com" for delivery to mx1.mail.yahoo.com.

The message will be retried for another 30 hours.

Reason: Mail Server for yahoo.com.hk could not accept your email at this time. MailEnable will keep trying to deliver this message and will notify you of any progress.

Reason Code: SMTP Outbound - General Error
Error Number: 0

Post Reply