Amavis

Header malformado

Nos llega un mail de deste tipo cuando nos mandan por ejemplo un mail con un acento en el subject.

Received: from gacq.com ([unix socket])
	by geacequ (Cyrus v2.1.18-IPv6-Debian-2.1.18-1) with LMTP; Wed, 04 Jan 2006 20:13:39 -0300
X-Sieve: CMU Sieve 2.2
Received: from localhost (localhost.localdomain [127.0.0.1])
	by gacq.com (Postfix) with ESMTP id 0970D71DB5
	for <www-data@gacq.com>; Wed,  4 Jan 2006 20:13:39 -0300 (ART)
MIME-Version: 1.0
Subject: Undeliverable mail
Message-Id: <DSN22829-04@geacequ>
Content-Type: multipart/report; report-type=delivery-status;
 boundary="----------=_1136416419-22829-1"
From: amavisd-new <postmaster@geacequ>
To: <www-data@gacq.com>
Date: Wed,  4 Jan 2006 20:13:39 -0300 (ART)

INVALID CHARACTERS IN HEADER

Improper use of control character (char 0D hex) in message header 'Date'
  Date: Wed, 04 Jan 2006 20:13:38 -0300\r\n
                                       ^

This nondelivery report was generated by the amavisd-new program
at host geacequ. Our internal reference code for your message
is 22829-04.


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 (it also prohibits NUL and bare CR).

  If characters (e.g. with diacritics) from ISO Latin or other alphabets
  need to be included in the header, these characters need to be properly
  encoded according to RFC 2047. This encoding is often done transparently
  by mail reader (MUA), but if automatic encoding is not available (e.g.
  by some older MUA) it is the user's responsibility to avoid the use
  of 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 the 'From', 'To' and 'Cc'.

  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.

El problema es claro el cliente de correo no implenta bien el standar de codificacion y el amavis lo rebota. Como solucion se puede poner que no realice mas esta comprobacion con la siguiente linea en el /etc/amavis/amavisd.conf

@bypass_header_checks_acl = qw( . );