Karsten Bräckelmann wrote:
> Since
> the localized German descriptions *do* use 8 bit chars, using these
> localized descriptions verbatim in headers *will* result in your
> problem. As hinted in my original, full question:
>
> Anyway, even when using the stock X-Spam-Report header with a Germa
On Sun, 2007-10-14 at 16:21 +1000, Lars Ippich wrote:
> > That does *not* look like the default X-Spam-Report header as inserted
> > when using report_safe 0. That looks like a custom added header. And a
> > broken one, frankly...
>
> You can see the header template at
> http://mod.privatepaste.c
Karsten,
> That does *not* look like the default X-Spam-Report header as inserted
> when using report_safe 0. That looks like a custom added header. And a
> broken one, frankly...
You can see the header template at
http://mod.privatepaste.com/16TExHyOgg as it is inserted into the
local.cf file.
On Sun, 2007-10-14 at 13:15 +1000, Lars Ippich wrote:
> > Hmm, while the descriptions in the X-Spam-Status header definitely
> > contained German Umlauts... I seem to remember seeing a list of Bayes
> > tokens in there, too?
> >
> > How does such a header look like again exactly? :)
>
> There yo
Karsten,
> Hmm, while the descriptions in the X-Spam-Status header definitely
> contained German Umlauts... I seem to remember seeing a list of Bayes
> tokens in there, too?
>
> How does such a header look like again exactly? :)
There you go:
> X-Spam-Report: SpamAssassin 3.2.3 on host vmail
>
On Sun, 2007-10-14 at 04:48 +0200, me wrote:
> I already deleted this thread (since it didn't seem all too interesting
> to me ;), but unless I am seriously mistaken and my memory plays foul
> trick on me: The quoted header in question is X-Spam-Report, and the
> German Umlauts appeared as part of
> > That is what I am here for, because the bad headers seem to be made by
> > SpamAssassin running on a system with German locale settings and
> > therefore causing trouble when encoding (or more precisely: not
> > encoding) umlauts. The administrator of that system claims he is using
> > the new
That is what I am here for, because the bad headers seem to be made by
SpamAssassin running on a system with German locale settings and
therefore causing trouble when encoding (or more precisely: not
encoding) umlauts. The administrator of that system claims he is using
the newest version and that
Michael Scheidell writes:
>
> > -Original Message-
> > From: Lars Ippich [mailto:[EMAIL PROTECTED]
> > Sent: Saturday, October 13, 2007 10:48 AM
> > To: Michael Scheidell
> > Cc: users@spamassassin.apache.org
> > Subject: Re: 8bit
> -Original Message-
> From: Lars Ippich [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 13, 2007 10:48 AM
> To: Michael Scheidell
> Cc: users@spamassassin.apache.org
> Subject: Re: 8bit encoding in mail header by SpamAssassin
>
>
> > Sounds like he
> Sounds like he created a custom X-Spam header and forgot that us
> arrogant americans invented the internet and don't have 8 bit characters
> in our alphabet. ;-)
I am not sure if X-Spam-Report could really be called a custom header:
> X-Spam-Report: SpamAssassin 3.2.3 on host vmail
> sca
> -Original Message-
> From: Lars Ippich [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 13, 2007 10:34 AM
> To: Michael Scheidell
> Cc: users@spamassassin.apache.org
> Subject: Re: 8bit encoding in mail header by SpamAssassin
> That is what I am here for, be
>> I do not specifically want to block these messages, I would
>> prefer a warning only policy. But I did not change any
>> amavisd settings beside the normal configuration stuff. So do
>> you know where these settings are done and where I can change them?
>>
> Look in ../etc/amavisd.conf* for $
> -Original Message-
> From: Lars Ippich [mailto:[EMAIL PROTECTED]
> Sent: Friday, October 12, 2007 11:05 PM
> To: Mark Martinec
> Cc: users@spamassassin.apache.org
> Subject: Re: 8bit encoding in mail header by SpamAssassin
> > This is not a default behaviour,
Mark,
> Oct 10 09:17:05 www amavis[2981]: (02981-06) BAD HEADER from
> <[EMAIL PROTECTED]>: Non-encoded 8-bit data (char FC hex) in message
> header
> 'X-Spam-Report'\n X-Spam-Report: ... Nachricht wurde nur
> \\374bervertrauensw...\n
>
>> The administrator claims to b
Mark Martinec wrote:
> This is not a default behaviour, normally such errors in header are only
> flagged/logged as a warning, but a message is delivered nevertheless.
> There is no particularly good reason to block such messages,
> but you can if you want to.
>
In countries like here, that wou
Lars,
> >>> Oct 10 09:17:05 www amavis[2981]: (02981-06) BAD HEADER from
> >>> <[EMAIL PROTECTED]>: Non-encoded 8-bit data (char FC hex) in message
> >>> header
> >>> 'X-Spam-Report'\n X-Spam-Report: ... Nachricht wurde nur
> >>> \\374bervertrauensw...\n
> The administrator claims to be u
Justin Mason wrote:
> Per Jessen writes:
>> Lars Ippich wrote:
>>
>>> I actually have problems with mails coming from a server where they
>>> already have been checked by SpamAssassin and have been added headers.
>>> Amavisd, which I am running on my server, rejects these messages
>>> because they
Per Jessen writes:
> Lars Ippich wrote:
>
> > I actually have problems with mails coming from a server where they
> > already have been checked by SpamAssassin and have been added headers.
> > Amavisd, which I am running on my server, rejects these messages
> > because they are not obeying RFC 28
Lars Ippich wrote:
> I actually have problems with mails coming from a server where they
> already have been checked by SpamAssassin and have been added headers.
> Amavisd, which I am running on my server, rejects these messages
> because they are not obeying RFC 2822, which forbids 8bit encoding
Hello list,
I actually have problems with mails coming from a server where they
already have been checked by SpamAssassin and have been added headers.
Amavisd, which I am running on my server, rejects these messages because
they are not obeying RFC 2822, which forbids 8bit encoding in mails:
Oct
21 matches
Mail list logo
