Matt, > > The only bad part is stopping and starting amavisd-new on a busy > > server. So maybe you could set it up, then save the stop and start for > > when you have other changes to make. > > We have two relays though :) Take one down and the other one is used. > > So I kill postfix first, and then work with amavis, then bring amavis back > up, and then postfix.
Don't stop postfix. And don't bother coordinating restart on two servers, just restart amavisd if/when needed and it will do. The messages that were being processes will be retried by Postfix in few minutes - but if you are impatient and amavisd was down for more than a few seconds, you may rush a MTA retry by: postfix flush Mark ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
