Bonsoir,
Je recois ce mail a chaque fois qu un internaute valide un formulaire de contact sur un site en spip 1.9.1 utilisant le plugin “Formulaires” (Version : 0.2 | stable). En principe (jusqu avant la migration) le formulaire genere par le plugin, envoyait un mail a un admin a chaque validation par un internuate, hors depuis la migration, a la place de ce mail j ai ce mail de rapport d erreur ci dessous.
J avoue que je preferais avant quand meme…
que dois je faire ?
merci
triton
//
he message WAS NOT relayed to:
mail@domaine.fr:
554 5.6.3 Reject, id=69817-91 - BAD_HEADER: Non-encoded 8-bit data (char E9 hex): Subject: Vos Coordonn\351es\n
This nondelivery report was generated by the program amavisd-new at host
node2-1.ouvaton.local. Our internal reference code for your message is
69817-91/2hrpBCYfx9JP
INVALID HEADER: INVALID 8-BIT CHARACTERS IN HEADER
Non-encoded 8-bit data (char E9 hex): Subject: Vos Coordonn\351es\n
Return-Path: pointcentral@pointcentral.net
Message-ID: E1HbLH5-000EuI-07@node1-2.ouvaton.local
Subject: Vos Coordonnées
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.