[dev] Fwd: IMP message header triggering spamassassin

[Michael M Slusarz]

Quoting Kevin Myer <kevin_myer at iu13.org>:

> Perhaps I'm wrong but I see the current header as being sort of the 
> equivalent
> of a X-Forwarded-For: header for proxied HTTP requests, but in a mail
> context. But I would agree that the current behavior is wrong.

Nope.  This has been covered many, many times before on the list.  This 
header conforms with the standards - a received header is added for 
every transport along the way.  The PHP/HTTP server is acting as a mail 
relay from the local computer - why should it be treated *any* 
differently than any other mail transport hop?  Answer: it shouldn't.

Once again, to make the story short: spamassassin is broken. (news 
flash: spam analysis is buggy - 
http://news.yahoo.com/news?tmpl=story&u=/ap/20050503/ap_on_hi_te/emergency_spam_10 - so just because spamassassin doesn't like a header, that doesn't mean it is wrong.  no one as yet has blessed spamassassin as the final word on header analysis)  solution: if you dont't like the default way that IMP sends mail, change it 
locally.

michael

_______________________________________
Michael Slusarz [slusarz at curecanti.org]