5 messages in net.sourceforge.lists.courier-usersRE: [courier-users] Problem with Cour...
FromSent OnAttachments
Andrea ResminiMay 22, 2006 10:00 am 
Bowie BaileyMay 22, 2006 10:14 am 
Andrea ResminiMay 22, 2006 1:19 pm 
Bowie BaileyMay 22, 2006 1:48 pm 
Andrea ResminiMay 22, 2006 2:11 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:RE: [courier-users] Problem with Courier as a relay MXActions...
From:Bowie Bailey (Bowi@BUC.com)
Date:May 22, 2006 1:48:38 pm
List:net.sourceforge.lists.courier-users

Andrea Resmini wrote:

Do you have a route set in esmtproutes for these emails? If so, what is it?

No, I don't. I assume that's not a requirement unless you want to bypass DNS discovery, which in my case is not that useful since I have direct access to the domain records.

No, it's not required, but if it is there, it will override the DNS, which is why I asked.

If not, does "testmxlookup domain.com" from the secondary return the address of the primary?

Yes, it does. It returns both primary (first) and secondary, which is reported as 'local'.

That sounds normal. Is there anything in the maillog about these connections apart from the 'connection timed out' message?

Maybe you should try manually specifying a route in esmtproutes.

Try this first:

domain.com: primarymx.domain.com

and if that doesn't work, try it by IP:

domain.com: [xxx.xxx.xxx.xxx]

If either of these works, there is most likely a problem with the DNS records for either the mail server or the domain in question.

-- Bowie