https://issues.apache.org/SpamAssassin/show_bug.cgi?id=5976
--- Comment #8 from Sidney Markowitz <[EMAIL PROTECTED]> 2008-09-16 17:58:45 PST --- (reply to comment #6) Nick, those headers are enough to let me test, but it doesn't show the bug. If I run an email made with those headers through SpamAssassin 3.5 here it does not trigger the FORGED_MUA_OUTLOOK rule, nor would I expect it to. You didn't show any headers indicating that the email was scanned by SpamAssassin or what rules it hit if it was scanned. The problem appears to be on the receiving mail server in the first example that you used, when you posted the bug report. The Message-ID clearly was included by your PC, aussieserver, but the MISSING_MID hit indicates that SpamAssassin did not see any Message-ID header, and that's what led to the FORGED_MUA_OUTLOOK hit. If we can track down why the Message-ID header was not seen by SpamAssassin on the receiving server, then we can see if that was caused by a SpamAssassin bug or something else on the receiving server. If you get FORGED_MUA_OUTLOOK sending to different SpamAssassin installations, that's another issue. But I think we would still need to see a test case with the more complete header information (like the last one you posted) that also shows the FORGED_MUA_OUTLOOK rule being hit. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
