Charles Gregory wrote:
On Fri, 18 Jun 2010, Randy Ramsdell wrote:
I have no problem going over there but I am not convinced that the
Amavis program is the problem. The header field is changed by
spamassassin. Doesn't the email simply get handed to Spamassasin by
Amavis where the headers are modified by spam report etc...?
The headers are missing.
Spamassassin records this fact, but is not responsible for it.
So find out what happens to your message BEFORE spamassassin is called.
Amavis is just a suggested starting place. And if it is to blame,
someone on their list will reocgnize your query as soon as you post it.
Suggestion: After each step of your mail processing, if you can, save
a copy of the mail to a log file. At least that way you get a quick
overview of *which* component removes those headers....
- C
Not exactly. Spamassassin sees the original messages including the
received headers, then it modifies those headers with its information. I
see these issues when running subsequent tests with spamassasin. So this
is why I am not convinced that spamassassin is not causing the problem.
Just clarifying the issue here. So it could be amavis, spamassassin or
postfix but I am leaning towards spamassassin at the moment.
From an earlier post in which I wrote: ( You see that the original
scan saw the headers, but after delivery they were gone. )
Example:
Original rules hit.
X-Spam-Status: No, score=-0.394 tagged_above=-9999
required=5tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001,
RCVD_IN_SORBS_WEB=0.619,URG_BIZ=1.585]
After running spamassassin -D
X-Spam-Status: No, score=4.2 required=5.0
tests=AWL,BAYES_80,HTML_MESSAGE,NO_RECEIVED,NO_RELAYS,TO_MALFORMED,URG_BIZ
autolearn=no version=3.2.5
