Spamassassin 4.0.x Corpus - 25-dmarc.cf

2024-04-04 Thread Armin Tüting
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
rules etc. or exists an alias Dmarc == DMARC


Re: Syslog local3

2024-04-04 Thread Emmanuel Seyman
* 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 this
must be the result of spamass-milter's configuration. I'll look into
the documentation today.

> If you're running spamd, the facility is set with the "-s" option, as
> documented in the man page.

Indeed, but setting this had no effect.

Thenk you for the help, Bill.

Emmanuel


Re: Multiple test failures

2024-04-04 Thread Sidney Markowitz

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 already 
supposed to be handled. I'll look at the emails in this thread more 
carefully to see if perhaps we re-introduced the problem in some change 
we made since then.


 Sidney



Re: Multiple test failures

2024-04-04 Thread Loren Wilton
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 
nobody and the test will fail.


Would it be worth adding some sort of test for this kind of thing that could 
make a reasonably explicit "don't run install as root" or "incorrect 
directory permissions" or some such, to make it more obvious what is going 
wrong? I seem to remember at least one or two very similar postings here in 
the last year or so, so it is something that does happen and confuses 
people.