Noah Meyerhans wrote: > Believe it or not, it's a bug that you were running spamd in the first > place, as you had not enabled it. spamd is an optional feature of the > spamassassin package. Therefor, unlike most daemons shipped with Debian, > it is disabled by default and only enabled at the explicit request of > the admin. In the sysvinit days, that was accomplished with a setting in > /etc/default/spamassassin, but that mechanism has changed with systemd. > The systemd method was not working correctly until recently...
The spamassassin package, I think, did too much in one package. It included this optional behavior, requiring optional configuration, and therefore ended up in this situation of being different from typical Debian packages. It requires the user installing it to need to learn unique information about this package that makes it different from typical packages. If only it were possible to make things work in the way most of Debian works... That would reduce the workload of those installing the package. [ Of course I am saying that while looking shyly around the room. Because obviously it is possible. :-) ] > While I believe that the current behavior is the least buggy, honestly I > wonder if the final fix for this might be to introduce a new "spamd" > package, recommended by spamassassin, that just installs a unit file. > Would be a lot easier to reason about. If I install a daemon then I expect that daemon to be running. It always annoys me when I need to dig in and debug things and then find that the package for some reason requires manual intervention to make it perform its basic function. Grr... And when every package is different it consumes much needed brain cells. I have so few to spare. Having said that, I don't run the spamassassin deamon myself. I run spamassassin through my ~/.procmailrc file. Well... I don't run it on *my* mail. I do run it on mail systems I administer for others. Therefore I use it in both of the different modes. I am running it without the deamon some places and with the daemon other places. I would like it very much if there were one package for the regular spamassassin functionality and another package for the spamassassin daemon, which would be automatically enabled and running if installed, and I guess also keep the spamc package so that clients don't need to run the daemon locally but can connect to a remote server. I think that would be the most convenient. But change is always difficult and guarenteed to annoy someone. Bob
signature.asc
Description: PGP signature
