Greg Earle writes:
Which means I'll have to change the Courier machine name to something else, like "myorg-mail.my.do.main" or something, and MX myorg to myorg-mail.But everything else mail-wise needs to stay the same - accept mail for myorg.my.do.main, and most importantly, continue to send out e-mail looking like it's coming from myorg and not myorg-mail, etc. What is the best way to accomplish this? Do I have to use Virtual Hosts with virtual users, and switch to "authuserdb" for authentication?
No. Nothing needs to be done except to change your DNS records; unless you don't have anything installed in the "me" or the "locals" configuration file, AND you're going to change the system hostname. In that case, you just need to explicitly override your local domain.
Courier looks first at "locals", then at "me" and only if neither of them are set, at the system hostname, in order to configure what it thinks is the local domain. After it accepts an incoming connection, mail addressed to a @localdomain is considered to be addressed to a local mailbox. Courier doesn't look at DNS for this, so if the server's actual IP address is now PTRed to something else, but an MX record still sends the mail to the server, nothing has changed, as far as the server is concerned, if nothing else has changed as well.
But if the system hostname has changed, and you don't have anything in "me" or "locals", meaning that Courier ends up defaulting to the system hostname for its only, local, configured domain, then you simply need to put the current hostname into the locals file.
pgp8Y3Ecly9PK.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
