On Sun, Jan 26, 2003 at 01:06:52PM -0500, Mike Burger wrote: > Losing mail? That's the point of tar'ing up /var/spool/mail.
I am not worried about losing old e-mail, I am worried about something not being straight in the new mail server and losing new e-mail, hence the suggestion of running the new server in the shadow for a time. > And the easiest addition to that is to stop the mail daemon on the old > system before tar'ing up the directory. One addition to my suggestion to run the new one in a test mode would be to stop all outbound mail on that server from actually going out, drop it all in a file if you can so you can see bad bounces and fix the problem. (Also would prevent legit bounces fomr happening twice.) What mailer you are using and so how to get it to do such things, I don't know. Maybe my double-delivery idea is a bad one, but I would try hard to do some sanity testing on the new server, after configuring it for your set up but before throwing the switch: sending mail to real users, to bogus users, to "vacation" users (if you offer anything like that), to any scripts or mailing lists that might get e-mail, etc. Do what you can to make sure the new server is working right before throwing the switch. Make the actual throwing of the switch as quick as possible. Don't worry about mistaken bounces as much as worrying about silent dropped mail. -kb, the Kent who has tried to do such a system switch, on a small scale. -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
