https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7269
Andrew <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Andrew <[email protected]> --- Well, regarding of how it should work, here is my vision of the algoryhtm that solving this issue: - For the first of all the records addded by outgoing whitelist feature should be stored separately in the db and not mixed to other records. - For example field "ip" in the case of outgoing white listing should have some personal value like "WHITEOUT" that identifies this records as outgoing whitelist record type. - The "signedby" field fot such records should be always blank and not depend on auto_whitelist_distinguish_signed value. - When analyzing new incoming messages and finding DB for the records we should check for the whiteout records first: try to find the records that hit the local user name (or overrided user name if set) and email fields (correspondent to currently analyzing message) AND field "ip" = WHITEOUT. such records should hit the saerch result not depending on "signedby" field and nevermind of dkim signature of the email being analyzed. The checking of the WHITEOUT records should be done separately from checking all other records (and of course when analyzing other records that are done now - such WHITEOUT records should be ignored to prevent double hits). - WHITEOUT records scores values can be changed when analyzing new incoming and ourgoing mail as done now with generic records. what do you think about it ? -- You are receiving this mail because: You are the assignee for the bug.
