RE: Spamassassin header format issue
Hi Jason,
It must be something on your side. I use the same Spamassassin package from
bpo like you. Seeing the headers of your message it reads:
X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on mail.netinform.hu
X-Spam-Level:
X-Spam-Status: No, score=-1.2 required=5.0 tests=BAYES_00,HTML_10_20,
HTML_MESSAGE autolearn=no version=3.1.1
Inserting an empty line by a \n into the headers could cause messages to
read garbage, since an empty line separates the message headers from the
body. An extra empty line would push some header lines into the body.
Anyway it's interesting that the order of the quoted header lines are
different in this two installation of the same package.
Regards,
Andras Galos
> -----Original Message-----
> From: backports-users-bounces@lists.backports.org
> [mailto:backports-users-bounces@lists.backports.org] On
> Behalf Of Jason Martin
> Sent: Tuesday, June 06, 2006 4:23 PM
> To: backports-users@lists.backports.org
> Subject: Spamassassin header format issue
>
> Hello,
>
> I have a sarge server running spamassassin from
> backports.org. It recently was updated to 3.1.1, and since
> then all mail processed by spamassassin has had some of the
> X-Spam-Status and X-Spam-Checker-Version in the body of the
> message. I sent myself a test message to my gmail account and
> this is what the headers look like:
>
>
> X-Spam-Status: No, score=-102.6 required=6.0 tests=AWL,BAYES_00,
>
> USER_IN_WHITELIST autolearn=ham version=3.1.1
> X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on
>
>
> myserver.com <http://myserver.com>
>
> So it looks like there's an extra \n in there now. Is there
> anything I can do from my end, or is this a bug?
>
> Thanks!
> Jason
>
>
Reply to: