Sven Juergensen (KielNET) wrote:
Hello Matt,
turns out that the script supplied by the
designers of the whole mess is, well,
suboptimal. I kicked it entirely and used
a single command line to run a per-recipient
checking.
Just for info: whenever spamc can't find
the $recipient or is lacking a '-u', it
falls back to the process owner. If there
are no userprefs defined for that recipient,
the $GLOBAL settings are applied.
That's mostly right, except spamassassin *NEVER* tries to find
$recipient. That's never been a feature of SA, and likely never will.
If both spamd and spamc ar lacking a -u, it uses the process owner
calling spamc. Period.
