https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7269
--- Comment #8 from Andrew <[email protected]> --- (In reply to Kevin A. McGrail from comment #7) > (In reply to Andrew from comment #6) > Did you install DKIM? I believe that's needed for the pre-db design to > populate singnedby. yes, sure. and DKIM is looks like working in TxRep. The incoming mail is getting signedby fields whet I turn on this feature. BUT the outgoing white list scores are not recognised because outgoin mail can not have the DKIM signature of the remote address (the address that is added to the whitelist. it should be signed by the SENDER's server and its key.). the outgoing mail can only be signed by LOCAL (our domain) signature that is not related to the remote address. local dkim signature is useless for the spam checking and should not be assigned to the remote addr.. Actually in my configuration the DKIM signs the outgoing mail AFTER processing with SA. and it is okay. So the current logics for the DKIM isolation of the records and the auto whitelist outgoing mail is broken cause we can not sign outgoing mail with someone's key. That is why I proposed the algorythm where outgoing whitelist records should be processed separately ignoring the signedby field -- You are receiving this mail because: You are the assignee for the bug.
