[dev] Fwd: IMP message header triggering spamassassin
Chuck Hagenbuch
chuck at horde.org
Thu May 12 10:35:58 PDT 2005
Quoting Kevin Myer <kevin_myer at iu13.org>:
> The problem with using the "for Horde" is that Horde isn't a
> recipient either.
> And since "for" is optional, and quite a bit of coding to do it right
> (once for each receipient, but not if its a BCC recipient), I'd just
> drop it altogether, unless your aim is to create a PHP MTA :)
>
> Attached is what I think brings the Received: header into RFC compliance. I
> fully agree that it belongs in a Horde generated message, just sans the "for"
> atom.
Sold. Committed to HEAD and FRAMEWORK_3 - thanks!
-chuck
--
"But she goes not abroad in search of monsters to destroy." - John
Quincy Adams
More information about the dev
mailing list