Re: Spamassassin spamming in log

[Bert Van de Poel]

If you are using systemd, you can "systemctl disable spamd". Otherwise 
you can indeed use the enabled=0. I would probably do both just in case ;)

On 2/06/2022 20:36, Timo Brandt wrote:

Maybe one of you has a hint for me how to disable the automatic 
startup of spamd?

Its been a long time ago that I setup a Debian from scratch :-(

It seems that spamd doesnt need to start at system boot so I will 
disable it.


Will this be done when I add ENABLED=0 into the file 
/etc/default/spamassassin  ?



Thanks,

Timo


Am 2022-06-02 20:27, schrieb Timo Brandt:

Hi all,


indeed - sorry.

I wasnt aware of that I do not need to run spamd beside amavis 🥴

Thanks for all your help.

Timo


Am 2022-06-02 20:18, schrieb Matija Nalis:

    On Thu, Jun 02, 2022 at 02:47:28PM +0200, Bert Van de Poel wrote:

        For the errors about nonexistent uses you will want to have a
        look at
        /etc/default/spamassassin I'm guessing.
        For the info messages: this has just got to do with your
        logging level. You
        will want to decrease it in local.cf or maybe also in the
        default file.


    Also, depending on your distro and init system,
    /etc/default/spamassassin
    might not be processed (e.g. on Debian systems, in many cases
    /etc/default/*
    entries are only read via /etc/init.d/* System-V-init scripts, and
    not used when using default systemd init system).

    You should use "ps auxwwwww" to determine with what exactly
    parameters it is being run, and then grep the system for those flags
    if different from ones in /etc/default/spamassassin (esp. when you
    change that file and restart, but changes are not applied)