At 14:43 01/29/2004 Thursday, Margaret King wrote:
 >Sorry to dig up an old thread but we are thinking about using
 >the command mentioned below i.e.
 >
 >    quiet change * *@old.domain *@new.domain
 >
 >and I need a little more information.
 >
 >(1) Are there any 'gotchas'?  (What can I say?  People here
 >    are suspicious of anything that looks that simple.)

Why don't you try it on a test or list e.g.,

quiet change TEST-L *@old.domain *@new.domain

Of course some may have previously subscribed under their new domain so
changes for them won't work.

Don't forget to check to make sure that owners' addresses work from either.

 >(2) Will it work on 1.8d?

yes


Don't forget to check for any DNS "MX" RR anomalies or MUA gateways that
are confused.


 >Our old domain is pilot.msu.edu; our new one is simply
 >msu.edu - currently (since years ago) they are aliased
 >in aliases.names like so:  :nick.MSU.EDU :alias.PILOT.MSU.EDU
 >When we did that, they were the same system.  Now msu.edu is
 >actually a separate system that knows who is still on Pilot
 >and forwards as needed.  In a couple of months Pilot will go
 >away - meanwhile we want to route as much Pilot mail through
 >the new msu.edu system as possible, for better virus checking.
 >
 >Possibly I should also be asking if we should turn that
 >aliases.names record around now - i.e. is the right hand side
 >implied to be the "preferred" name somehow?