After over a decade of running my old, frozen Courier configuration on a work host (call it "myorg.my.do.main"), with matching e-mail addresses of
u...@myorg.my.do.main The people in my organization want to roll out a new organizational Web server running on a different machine, and they want to be able to use http://myorg.my.do.main/ i.e. taking over the machine name and deploying it as a Virtual IP on another system, to be used solely for the Web server. 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? I've got existing Maildirs and a lot of time invested in my current setup - ideally I'd like to change as little as possible (since things get unstable very easily - for example just changing TLS_CIPHER_LIST in etc/imapd-ssl has prevented my one remaining customer that still uses Pine/Alpine from being able to read his e-mail). Thanks for any advice you can give me. - Greg ------------------------------------------------------------------------------ _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
