https://bz.apache.org/SpamAssassin/show_bug.cgi?id=8087
--- Comment #24 from Sidney Markowitz <sid...@sidney.com> --- (In reply to Benny Pedersen from comment #23) > maybe this https://metacpan.org/pod/Mail::DMARC::Result ? That's the object that is returned by the call the SpamAssassin plugin makes to $dmarc->valdate, just as described on the documentation page you linked to. The SpamAssassin plugin then uses the values in the object to decide whether or not rules have a hit, indicating whether the result was pass, reject, quarantine, none, or a missing policy. The result object is created completely in the Mail:DMARC::PurePerl code, not by anything that is in SpamAssassin itself. Thus any use of a whitelist file as specified in a mail-dmarc.ini file depends on the code in Mail:DMARC::PurePerl and the Mail::DMARC modules that it calls. I didn't see anything in the API that provides a way for the caller to influence that. And that's the limit of my expertise on it, the code inside Mail::DMARC is outside of my domain. But if you want to use the whitelist, find out where Mail:DMARC looks for the mail-dmarc.ini file and put your whitelist path in the whitelist option instead of the sample one that the sample mail-dmarc.ini has. -- You are receiving this mail because: You are the assignee for the bug.
