Jon Kvebaek wrote: > Quoting Matt Kettler <[EMAIL PROTECTED]>: > > >>Jon Kvebaek wrote: >> >>>Hi, >>>we get quite a few messages that have no Received: headers. These >> >>seem >> >>>to cause ALL_TRUSTED to fire (with a negative score of course), >> >>which >> >>>isn't exactly what I want. Any idea on how I should deal with this >>>correctly? >>> >> >>What version of SpamAssassin? I know this was a problem for some >>releases, but I >>believe it's fixed in 3.1.0 and 3.0.5. > > > We're currently on SpamAssassin version 3.0.4. I suppose an upgrade > might be called for.
For reference, here's the bug that was reported about this: http://issues.apache.org/SpamAssassin/show_bug.cgi?id=3949 Basically 3.0.5 has a back-port of the code from 3.1.0, which works a lot better than the stuff in 3.0.0-3.0.4. In 3.0.0-3.0.4 ALL_TRUSTED really works as a "no untrusted". Which has problems if there's errors parsing the Received: headers, or if there's no headers at all. In 3.0.5 and 3.1.0 you need: one or more trusted, no untrusted, and no unparseable.
