Pantek Library
Hosting Provided By
CybrHost
High Speed Hosting

Re: 8bit encoding in mail header by SpamAssassin

From: Lars Ippich <lars.ippich(at)speicherplatz4you.de>
Date: Fri Oct 12 2007 - 23:05:17 EDT


Mark,

>>>>> Oct 10 09:17:05 www amavis[2981]: (02981-06) BAD HEADER from
>>>>> : 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 using version 3.2.3 and that is as well
>> what it says in all mails I am getting from this host.

>
> Most likely these header fields were inserted by some remote mailer
> running SpamAssassin, over which you may not have any control.
> Amavisd would not see or check X-Spam-* header fields added by itself
> (or from SpamAssassin invoked from it).

There are two instances of SpamAssassin running: One on the sending mailserver which administrator claims to use v3.2.3 and one on my recieving mailserver on which I am running v3.0.3. The sending mailserver is adding the headers I mentioned above.

>> Amavisd, which I am running on my server, rejects these messages
>> because they are not obeying RFC 2822, which forbids 8bit encoding...

>
> 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.

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?

Thanks,
Lars Received on Fri Oct 12 23:02:19 2007

This archive was generated by hypermail 2.1.8 : Fri Jul 04 2008 - 15:00:31 EDT


Contact Us  Legal Notices  Order Services Online 
Pantek Home  Privacy Policy  IT news  Site Map  Pantek Library