[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Rewriting header incorrectly?

From: Steve
Subject: Re: Rewriting header incorrectly?
Date: Wed, 02 Dec 2009 07:06:39 +0000

On Tue, 2009-12-01 at 16:03 -0600, Daniel Norton wrote:
> On Tue, Dec 1, 2009 at 2:12 PM, Steve
> <address@hidden> wrote:
>         On Tue, 2009-12-01 at 14:10 -0600, Daniel Norton wrote:
>         > ...Who is writing this "Received" header line incorrectly?
>         > Is it not spamass-milter?
>         Is it *modifying* an existing header?
> Who knows?
>         > I guess I need to understand what's going on a
>         > little better and where the problem actually lies. 
>         And possibly the wording of the RFC you quote *modify* -v-
>         *create*
> RFC2821 doesn't indicate any distinction between modifying and
> creating a header. All I know is that:
> 1) When I don't use spamass-milter with spamd, and process it only
> using sendmail, all of the Received headers are compliant with
> RFC2821.
> 2) If I run spamassassin -Lt < mail.txt > out.txt, the output contains
> a spam report with an inserted message that has headers that are all
> compliant with RFC2821.
> 3) If I receive email using sendmail/spamasss-milter/spamd, I get a
> spam report with an attached email that contains a Received header
> line that is not compliant with RFC2821. Specifically, it is missing a
> required semi-colon before the time stamp.
> --
> Daniel
Can you tell me where in RFC2821 it says that there should be a
semi-colon before the time stamp? I've searched that document for the
word semi-colon (no hits) and colon (1 hit) but nothing to support that.
I'm curious where you are seeing that in 2821?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]