Matthew, > Could anyone explain to me why amavisd-new seems to find headers ended with > <CRLF> as a BAD Header.
It doesn't. Perhaps you had a sequence CR CR LF in the SMTP protocol. > After reading RFC822 and RFC2821 I am a bit confused why amavisd-new will > not accept this as a good header. > According to RFC822 the header field needs to be terminated by <CRLF>. On the wire (SMTP protocol), lines end with CR LF. When mail is store to a Unix file, lines end with LF, i.e. CRLF line endings are converted to LF line endings. If you had a CR CR LF on the wire, this would end up as CR LF on a file, which it is illegal. > X-Amavis-Alert: BAD HEADER Improper use of control character (char 0D hex): > Reply-To: Matthew <[EMAIL PROTECTED]>\r\n > ... > When I replace \r\n with \n amavisd-new seems to find the header just fine. > So it seems to me that amavisd-new isn`t keeping up to the old RFC 822. > Is there a special reason why amavis should even consider this header bad? My guess is that whatever software inserted the Reply-To header field, did it incorrectly, leaving there one extra CR. Mark ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
