Bon, en fait ça n’arrête pas depuis la migration :
[quote]The message WAS NOT relayed to:
<***@***.org>:
554 5.6.3 Reject, id=04688-04 - BAD_HEADER: Non-encoded 8-bit data (char E9 hex): Subject: Un nouveau message priv\351 vous a \351t…
This nondelivery report was generated by the program amavisd-new at host
node2-1.ouvaton.local. Our internal reference code for your message is
04688-04/8DSVzxw+UoVp
INVALID HEADER: INVALID 8-BIT CHARACTERS IN HEADER
Non-encoded 8-bit data (char E9 hex): Subject: Un nouveau message priv\351
vous a \351t\351 envoy\351.\n
Return-Path: <***@***.fr>
Message-ID: <1e2467a814f793c2b94f5c379e9c54b6@***.org>
X-Mailer: PHP
Subject: Un nouveau message privé vous a été envoyé.
WHAT IS AN INVALID CHARACTER IN MAIL HEADER?
The RFC 2822 standard specifies rules for forming internet messages.
It does not allow the use of characters with codes above 127 to be
used directly (non-encoded) in mail header.
If such characters (e.g. with diacritics) from ISO Latin or other
alphabets need to be included in a header, these characters need
to be properly encoded according to RFC 2047. Such encoding is often
done transparently by mail reader (MUA), but if automatic encoding is
not available (e.g. by some older MUA) it is a user’s responsibility
to avoid using such characters in mail header, or to encode them
manually. Typically the offending header fields in this category are
’Subject’, ‘Organization’, and comment fields in e-mail addresses
of ‘From’, ‘To’ or ‘Cc’ header fields.
Sometimes such invalid header fields are inserted automatically
by some MUA, MTA, content checker, or other mail handling service.
If this is the case, that service needs to be fixed or properly
configured. Typically the offending header fields in this category
are ‘Date’, ‘Received’, ‘X-Mailer’, ‘X-Priority’, ‘X-Scanned’, etc.
If you don’t know how to fix or avoid the problem, please report it
to your postmaster or system manager.[/quote]
Je n’avais jamais eu ces problèmes avant. Chaque fois qu’un de mes forums phpbb envoie un mail (par exemple pour l’annonce de l’arrivée de msg privés), j’ai cette erreur de header : avant les accents étaient acceptés, plus maintenant. Sur une des listes ouvaton, on m’a parle de cette fonction :
La fonction PHP mb_encode_mimeheader
(http://fr.php.net/mb_encode_mimeheader)
Mais je ne sais pas où la mettre pour régler le problème, si il peut être réglé avec cette fonction.
Des idées ?