This is not a spamassassin bug per-se, but rather a problem in the way we had packaged it for years.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=141323
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161785
It would be helpful if upstream could look at the excellent explanation in Bug #161785. I am hoping there is a better solution to this problem than the suggested shell script .pid solution suggested in that bug.

Wouldn't it be preferable to have a solution where spamd itself returns when it is finished stopping rather than relying on an asynchronous kill signal?

Warren Togami
[EMAIL PROTECTED]

Reply via email to