Hi. I got a strange problem today:
I have a server machine that has several additional IP-addresses, mostly for webserver-SSL-certificates. Now I tried to set up a second esmtp server on a different IP-address for some testing purposes. To get messages there, I set up a domain that has the second ip-address listed as primary MX (via intermediate Hostname, not IP as MX). What happens is that the primary courier-server says "configuration error: mail loops back to myself (MX problem)." when I send a message to that domain. It's not affected by SOURCE_ADDRESS in courierd config either. It's true, that the IP-address is on the same physical network device. But it's not true that port 25 on the other ip address points to courier. I would consider this a bug, what do you think. cu, Bernd
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
