Hello,
25-dmarc.cf from corpus reads
># Requires the Mail::SpamAssassin::Plugin::DMARC plugin be loaded.
>
># Backwards compatible name (was renamed to DMARC in trunk before
4.0.0)
>ifplugin Mail::SpamAssassin::Plugin::Dmarc
The above statement evaluates to false which won't load the header
rul
* Bill Cole [03/04/2024 10:54] :
>
> If you are using something else to
> call Spamassassin, e.g. Amavis, MIMEDefang, etc., that other software
> controls the logging.
Ah, that must be it.
I'm using spamass-milter to allow postfix to call spamassassin and
Loren Wilton wrote on 4/04/24 9:26 pm:
Would it be worth adding some sort of test for this kind of thing
I started to look at where in SATest.pm it ought to go, and I found
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=5529
I think from the comments I left there 17 years ago that is is al
I haven't had a chance yet to read this thread carefully, but spamd when
run as root in tests will, at least in some cases, set itself to run as
user "nobody". If you do that in a subdirectory of your non-nobody user's
HOME, the usual permission configuration will not provide read access to
nob
