https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7416
John Hardin <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #15 from John Hardin <[email protected]> --- (In reply to Dave Jones from comment #14) > (In reply to Merijn van den Kroonenberg from comment #10) > > Created attachment 5443 [details] > > added (exported) plugin method check_dkim_valid_envelopefrom(). It will > > check if the domain from the envelopefrom has a valid DKIM signature. > > > > Added a patch to add a check_dkim_valid_envelopefrom() function. tested only > > against a small testset of e-mail. patch against Mail-SpamAssassin-3.4.1 > > /Mail/SpamAssassin/Plugin/DKIM.pm > > @devs How do patches like this one normally get put into the SA testing > process? Anybody can create a local SA sandbox, apply the patch and test (and ideally create test cases for automated testing). Committing the changes to SVN so they are part of the standard SA release requires committer privileges, so a dev with such privileges needs to be convinced the patch is worthwhile. -- You are receiving this mail because: You are the assignee for the bug.
