On Thu, 23 Jan 2003, Adam Goryachev wrote: > Read carefully the section you quoted and you will see that the HEADERS of > the email should not contain any CR's. Headers are only terminated by NL's > > Of course, if I'm wrong, then someone will correct me, but I am pretty > confident that is the answer. Of course, you could test that in around 5 > minutes yourself anyway.
There's no place where I can find that HEADERS of email should not contain CR's... as line TERMINATORS!!! Of course if you say that CR or LF inside line (which by definition is a set of chars terminated by a CRLF sequence) then we agree. Sorry, but you're WRONG! Why? Read bellow, please! (ref: http://www.faqs.org/rfcs/rfc2822.html) Quoting RFC2822, section 2.1: " Messages are divided into lines of characters. A line is a series of characters that is delimited with the two characters carriage-return and line-feed; that is, the carriage return (CR) character (ASCII value 13) followed immediately by the line feed (LF) character (ASCII value 10). (The carriage-return/line-feed pair is usually written in this document as "CRLF".) A message consists of header fields (collectively called "the header of the message") followed, optionally, by a body. The header is a sequence of lines of characters with special syntax as defined in this standard. The body is simply a sequence of characters that follows the header and is separated from the header by an empty line (i.e., a line with nothing preceding the CRLF). " Quoting RFC2822, section 2.2: " 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. " Quoting RFC2045, section 2.10: " "Lines" are defined as sequences of octets separated by a CRLF sequences. This is consistent with both RFC 821 and RFC 822. "Lines" only refers to a unit of data in a message, which may or may not correspond to something that is actually displayed by a user agent. " You can also look at RFC2045, section "3. MIME Header Fields", to see formal definition of MIME headers. Best Regards, -- Paulo Matos ----------------------------------- ---------------------------------- |Sys & Net Admin | Serviço de Informática | |Faculdade de Ciências e Tecnologia | Tel: +351-21-2948596 | |Universidade Nova de Lisboa | Fax: +351-21-2948548 | |P-2829-516 Caparica | e-Mail: [EMAIL PROTECTED] | ----------------------------------- ---------------------------------- ------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
