.cf file update procedures
When you folks are adding, deleting or updating spamassassin .cf files... After the changes are implemented and you have --lint do you folks shutdown your main SMTP process before you run something like /etc/init.d/spamassassin restart And then bring back up your smtp? Or do you just restart spamassassin and call it good? - rh -- Robert - Abba Communications Computer Internet Services (509) 624-7159 - www.abbacomm.net
.cf file update procedures
When you folks are adding, deleting or updating spamassassin .cf files... After the changes are implemented and you have --lint do you folks shutdown your main SMTP process before you run something like /etc/init.d/spamassassin restart And then bring back up your smtp? Or do you just restart spamassassin and call it good? - rh -- Robert - Abba Communications Computer Internet Services (509) 624-7159 - www.abbacomm.net
R: .cf file update procedures
When you folks are adding, deleting or updating spamassassin .cf files... After the changes are implemented and you have --lint do you folks shutdown your main SMTP process before you run something like /etc/init.d/spamassassin restart And then bring back up your smtp? Or do you just restart spamassassin and call it good? It depends from your MTA + SA setup. I use postfix + amavis + SA. Postfix is configured to pre- and post-queue messages around amavis. Postfix and amavis comm by inet/unix socks. SA is run embedded into amavis. As a result, this confs allow restarting amavis (cf.: SA) without loosing messages: the postfix pre-queue would store unchecked messages and then would resubmit them as soon as amavis starts again. I'm used to issue a 'postqueue -f' command just after amavis restart. giampaolo - rh -- Robert - Abba Communications Computer Internet Services (509) 624-7159 - www.abbacomm.net
RE: .cf file update procedures
It depends from your MTA + SA setup. I use postfix + amavis + SA. Postfix is configured to pre- and post-queue messages around amavis. Postfix and amavis comm by inet/unix socks. SA is run embedded into amavis. As a result, this confs allow restarting amavis (cf.: SA) without loosing messages: the postfix pre-queue would store unchecked messages and then would resubmit them as soon as amavis starts again. I'm used to issue a 'postqueue -f' command just after amavis restart. giampaolo Ok, so best common practice would be to shutdown the smtp daemon and associateds and then restart spamassassin and then bring up the smtp daemon and associateds Anyone using qmail? Correct? - rh
