Dan Hollis wrote: > I upgraded to 3.1.0, and now spamassasin is putting its headers > before all > others, even Received: lines... > > X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on > sasami.anime.net X-Spam-Status: No, score=0.0 required=5.0 tests=AWL > autolearn=disabled version=3.1.0 > X-Spam-Level: > Received: from ms-dienst.rz.rwth-aachen.de (ms-2.rz.RWTH-Aachen.DE > [134.130.3.131]) > > Is there any way to change it back to 3.0.4 behavior? There is nothing > mentioned in > http://svn.apache.org/repos/asf/spamassassin/branches/3.1/UPGRADE > or http://wiki.apache.org/spamassassin/UpgradeTo310
Short answer: the change was made to be nice to Yahoo!'s DomainKeys. See this excerpt from 3.1.0's Mail::SpamAssassin::PerMsgStatus... # Break the pristine header set up into two blocks; "pre" is the stuff that # we want to ensure comes before any SpamAssassin markup headers, like the # Return-Path header (see bug 3409). # # "post" is all the rest of the message headers, placed after the # SpamAssassin markup hdrs. Once one of those headers is seen, all further # headers go into that set; it's assumed that it's an old copy of the # header, or attempted spoofing, if it crops up halfway through the # headers. And bug 3409: http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3409 -- Matthew.van.Eerde (at) hbinc.com 805.964.4554 x902 Hispanic Business Inc./HireDiversity.com Software Engineer
