Re: Problem with Thunderbird and AmaViS on etch
On Wed, Mar 14, 2007 at 01:53:13PM +0100, Alessandro FAGLIA wrote:
> Dear users,
> I have a mailserver (i386) with etch and amavisd-new 2.4.2-6.1. The only
> locales I have generated is en_US ISO-8859-1. On the client side I have
> Thunderbird 1.5.0.9 with french localisation.
>
> Whenever a mail asks for a return receipt (accusé de réception) and
> Thunderbird sends it, amavis mark this as a message with BAD HEADER.
> This is what I read in the quarantined mail header:
> X-Amavis-Alert: BAD HEADER Non-encoded 8-bit data (char E9 hex): Subject:
> Accus\351 de r\351ception (...
>
> For the moment I solved the problem by setting D_PASS as default policy
> for banned messages, but I would like to understand why this happens. Is
> this a configuration problem of amavis or what else? I use Thunderbird
> also in other languages (italian, english) and I've never experienced
> such problem.
The problem comes from thunderbird which MUST send only ASCII characters
in headers!
only ascii code is allowed in headers, other characters have to be encoded
(can't find the rfc for characters encoding, but it is something like
"=iso-8859-1#E9" for <E9> character).
This encoding is the only to passthru following problem: Mime is defined
into headers, so it is not possible to interpret mime characters into
headers themselves.
[Following French part I'sciting the RFC 2822]
Le problème vient de Thunderbird, qui _doit_ encoder les caractères non
ASCII des headers selon un protocole, dont je n'arrive pas à remettre
la main dessus.
En effet, il n'est pas possible d'interprêter les en-têtes avant que
l'en-tête MIME ne soit défini : on se mordrait la queue.
Here is part of RFC 822:
[cite]
RFC 2822 Internet Message Format April 2001
to handle an arbitrarily large number of characters in a line
(certainly at least up to the 998 character limit) for the sake of
robustness.
2.2. Header Fields
Header fields are lines composed of a field name, followed
by a colon
(":"), followed by a field body, and terminated by CRLF.
A field
name MUST be composed of printable US-ASCII characters
(i.e.,
characters that have values between 33 and 126,
inclusive), except
colon. A field body may be composed of any
US-ASCII characters,
except for CR and LF. However, a field body
may contain CRLF when
used in header "folding" and "unfolding"
as described in section
2.2.3. All field bodies MUST conform
to the syntax described in
sections 3 and 4 of this standard.
[/cite]
Regards,
--
Thomas Harding
Reply to: