I had a situation where I'd migrated from Sendmail to Postfix, and I ended up reverting my configuration (Sendmail provides features that I couldn't get from Postfix, but that's not part of this bug, the important aspect is migrating from Postfix to Sendmail).<br />
<br />
The problem is that the package spamass-milter-postfix creates the directory /var/run/spamass-milter/postfix.<br />
<br />
The spamass-milter startup script uses the presence of this directory to determine where to put its .sock file (this can be overridden in /etc/sysconfig/spamass-milter, but I'd not done that). Despite my server no longer having a working postfix configuration, spamass-milter was still using this postfix directory to store the .sock file.<br />
<br />
Sendmail looks for a .sock file in /var/run/spamass-milter/ to determine if it should use that milter. Of course, it cannot find the file, it's in the postfix subdirectory, and as a result it cannot use Spamassassin support.<br />
<br />
Just having the the directory /var/run/spamass-milter/postfix present prevents Sendmail from using spamass-milter. Uninstalling the package spamass-milter.postfix does not remove that directory.<br />
<br />
Consequently, even though spamass-milter.postfix is uninstalled, Sendmail can no longer use the milter because it cannot find the .sock file. Note, that just having the spamass-milter.postfix installed will cause Sendmail to fail to use the milter.<br />
<br />
Potential solutions:<br />
<br />
1. Make spamass-milter always use the same directory for its .sock file whether it's using postfix or sendmail<br />
<br />
or<br />
<br />
2. Make sendmail look in this postfix subdirectory if it can't find the sock file in the normal place.<br />
<br />
using 'yum remove spamass-milter' should also remove the /var/run/spamass-milter/postfix directory, as it currently doesn't.
↧
