The reason why I want this might not be apparent so I'll explain a rather nasty situation I ran into yesterday.
A domain I administer run a hidden mail server (i.e. the final delivery is not at the primary MX) so it has an entry in esmtproutes on the primary MX to send the mail to the final server.
Yesterday some clown noticed that internal-mail.domain.com was an A record to the same IP as server.domain.com. He then decided to "optimise" this and changed internal-mail to a CNAME.
The effect of this was that courier discarded the route in esmtproutes and started mailing everything to itself (since it was the primary MX).
After a while the headers became so long that it started sending loop errors instead. The postmaster address was also in this domain so it then proceeded to mail those to himself.
Changing a mail server's entry to a CNAME was of course a stupid mistake, but these things have a nasty habit of happening anyway. So it would be nice if courier could detect that something is wrong and not destroy the mail.
Rgds Pierre
------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
