Bernd Wurst writes:
Hi.On Thursday 24 April 2008, Sam Varshavchik wrote:Define "primary MX". The MX record for the other machine must have a numerically lower priority (higher order priority) than the MX record for this machine.Well, I think I did this step correctly. To be precise, this is my setup: # dig -t mx suessmost.de [...] ;; ANSWER SECTION: suessmost.de. 3600 IN MX 5 d.ns.schokokeks.org. suessmost.de. 3600 IN MX 10 zucker.schokokeks.org. [...] zucker.schokokeks.org. 60 IN A 85.10.204.247 zucker.schokokeks.org. 3600 IN AAAA 2001:6f8:1060::1 d.ns.schokokeks.org. 3600 IN A 85.10.228.82 The entry of the priority 10 mx does not affect anything.In the above scenario, the courier daemon listenes to port 25 only on specified IP addresses:# netstat -nplt|grep ':25' tcp 0 0 78.46.69.2:25 0.0.0.0:* LISTEN 19945/couriertcpd tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 19945/couriertcpd
The couriertcpd configuration is not relevant. The esmtp client has no knowledge of how the tcpd daemon is configured.
But: 78.46.69.2 and 85.10.228.82 are configured on the same device:
There you go. Courier obtains a list of all locally-configured IP addresses. It sees 85.10.228.82, and sees that it's the highest priority MX, so it concludes that this domain should be configured as a local domain.
pgpQ3qXfc9UTL.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
