Hi. On Friday 25 April 2008, Sam Varshavchik wrote: > >> 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.
Okay, then this setup simply won't work. (without the workaround below.) > I neglected to mention that you just need to put an explicit entry in > esmtproutes that duplicates the primary MX record. Courier ignores this > check if the recipient domain has an explicit entry in esmtproutes. This is my current workaround, thanks. I don't know if i still consider this a bug. I think I do... :) regards, Bernd -- The hardness of the butter is proportional to the softness of the bread.
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------- 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
