https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5185
--- Comment #22 from RW <[email protected]> 2012-02-13 16:55:00 UTC --- (In reply to comment #21) > The received header is not available in the mail stream at the time many > people > are running SA. Therefore, the synthesized header and the final header don't > match which generates two disparate msg_id's which is the problem we are > trying > to solve. I understand the problem I just think it's less objectionable than the solution. The problem doesn't hit everyone, you can work around it by turning off auto-learning, and I doubt it does all that much damage in the first place. > I'm very open to other ideas but just adding the received header back isn't > feasible as it will cause issues. Consider hashing in relays-external to make it harder to exploit. Perhaps you might need to remove some information from the first section if it's not stable between the temporary and permanent header. > However, the msgid is still generated including a substantial portion of the > body of the email. How can they generate a message ID for an email with > differing content as you propose? Just start with 1k of untokenizable text, perhaps hidden in mime or html. Since it's pristine_body I guess it could just be 1024 spaces. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
