https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6155
--- Comment #88 from Mark Martinec <[email protected]> 2009-10-09 06:23:06 PDT --- > > The release notes could then say that one should lower the DKIM_ADSP_* > > scores on installations where it is known that mail is not reaching > > SpamAssassin in its pristine form (as received by the MTA). > > This case or old ham where the sender subsequently changed their DKIM policy > is only an issue for masscheck, not production scanning. True for the case of old ham where the sender subsequently changed their DKIM policy, or for the case of expired signatures - these are only an issue with masscheck. ...but not the case of wt-en6, where mail is transformed by its path through webmail. This is an issue both for masschecks, as well as for production runs. > Lowering the DKIM scores makes no sense then? If one knows that mail reaching SpamAssassin will be modified by his mail path, then one must disable rules targeting mail forgery and depending on a pristine mail, such as the DKIM_ADSP_DISCARD rule. Otherwise the rule would generate FP score points for legitimate mail from domains publishing ADSP (explicitly or through overrides). -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
