Re: A lot of "invalid DKIM result" messages in my logs

On 17/11/2024 11:39, Damian wrote:
>> I am somewhat certain those two lines are related and that the 
>> "invalid DKIM result" is `invalid` verbatim.
>>
>> Mail::DKIM::Verifier creates a signature with a result `invalid` for 
>> ed25519, Amavis passes all signatures to SpamAssassin, 
>> Mail::SpamAssassin::Plugin::DMARC->_check_dmarc invokes 
>> Mail::DMARC::PurePerl->dkim with result => 'invalid', 
>> Mail::DMARC->dkim invokes 
>> Mail::DMARC::Report::Aggregate::Record::Auth_Results::DKIM->new with 
>> result => 'invalid', and the result-setter in that module croaks 
>> because `invalid` is not in the list of allowed values.
>
> Standalone SpamAssassin should not be affected, because without 
> Amavis-supplied signatures, SA triggers a different code path in 
> Mail::DMARC that has a fix for this issue [1].
>
> [1] https://github.com/msimerson/mail-dmarc/issues/21
So this is a bug in amavis and not spamassassin? Or is it in the 
DMARC.pm plugin? https://metacpan.org/pod/Mail::DMARC?