Andrea Resmini wrote: > List, > > I've setup a Courier MX relay server which should serve a couple of > customers. > > I had DNS records set up, and tried to send to a test domain for which > the primary MX (also Courier) was down. All mail got routed to the > secondary MX and queued. So far so good. > So I moved in to the next step: I brought up the primary MX, and found > that mail in the sec mx queue is processed, but not sent: all I get is > 'connection timed out' error messages. > I can ping and resolve the primary mx correctly from the sec mx, and > even connect directly on port 25 with ease: I checked the FAQ for mx > relay info and everything has been done precisely that way. > Any ideas about where the problem might lie or anything else I could > check?
Do you have a route set in esmtproutes for these emails? If so, what is it? If not, does "testmxlookup domain.com" from the secondary return the address of the primary? -- Bowie ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
