On 2022-05-30 at 06:22:39 UTC-0400 (Mon, 30 May 2022 22:22:39 +1200)
DL Neil <SAlist@rangi.cloud>
is rumored to have said:
On 30/05/2022 03.06, Bill Cole wrote:
On 2022-05-28 at 19:25:46 UTC-0400 (Sun, 29 May 2022 11:25:46 +1200)
DL Neil <SAlist@Rangi.Cloud>
is rumored to have said:
No, he said it.
SpamAssassin x86_64 3.4.0 CentOS 6.el7 release
Postfix 2.10.1
unbound 1.6.6
Obsolete antiques all...
May be so, but some (would) like stability, aka trying to get it right
before making it better*
* being whatever settle on using to replace CentOS...
- but thank you for the warning/reminder!
Expanded defences to include dnswl.
Recommendation to install local dns caching server followed.
Once installed, large numbers of messages started to appear in
maillog.
The messages you included indicate that you've got spamd running with
debug enabled. The usual way to set debugging is in
/etc/sysconfig/spamassassin with the 'SPAMDOPTIONS' parameter. The
option to remove is '-D' and any list of message types that follow
it.
That was my first thought
NB word of caution to all who instantly-believe SO and similar advice:
reading the docs to understand what is being said, showed that -D and
-d
are quite different, and thus not a 'typo'!
I have no idea how you could have gotten the debug option enabled
without knowing it.
Nor I, but ...
Intended to only access the one white-list service. Have I
accidentally
released a hydra of services/checks?
I guess that's a matter of definition...
The spamd daemon is one service, listening either on a unix-domain
socket or a TCP port, usually port 783. The parent spamd process
handles
the listener and spawns a small number of child processes to which it
distributes individual messages for scanning.
SpamAssassin does a substantial number of DNS lookups to check the
domains used in email addresses and URLs in the message. The number
of
these is dependent on your local configuration, but there are many
enabled by default.
Is there a way to reduce all of these log-lines?
(many times longer than the actual email message itself)
Switch off debug logging, and the messages will stop.
I don't think it's on
It absolutely is. There's no other way to make spamd emit those
messages. It's not magic, it's code. The mystery is: what is turning it
on?
- having spent hours trying to find decent docs
which would tell me each of the different ways such might happen.
I did edit the /etc/sysconfig/spamassassin file.
What does it contain?
Herewith what systemctl
does with it (and showing that the environment variable holds no
value):
vps517507 /etc/mail/spamassassin: systemctl status spamassassin
● spamassassin.service - Spamassassin daemon
Loaded: loaded (/usr/lib/systemd/system/spamassassin.service;
enabled; vendor preset: disabled)
Active: active (running) since Mon 2022-05-30 00:01:55 UTC; 11s ago
Process: 4912 ExecStart=/usr/bin/spamd --pidfile /var/run/spamd.pid
$SPAMDOPTIONS (code=exited, status=0/SUCCESS)
Process: 4910 ExecStartPre=/sbin/portrelease spamd (code=exited,
status=0/SUCCESS)
Main PID: 4917 (/usr/bin/spamd )
CGroup: /system.slice/spamassassin.service
├─4917 /usr/bin/spamd --pidfile /var/run/spamd.pid -d
-m5
├─4919 spamd child
└─4920 spamd child
...
vps517507 /etc/mail/spamassassin: echo $SPAMDOPTIONS
All that 'echo' shows is what's in your current shell's environment. You
current shell almost certainly didn't load /etc/sysconfig/spamassassin
when launched.
What matters is what SPAMDOPTIONS was in the environment used by
systemctl when it launched spamd. Above, it appears to have been '-d
-m5' but that could possibly be a consequence of how systemctl trims
lines.
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire
