Hello, Jonathan. You wrote in <mid:[EMAIL PROTECTED]>
JA> Hi, JA> I think I can answer this one on my own, but it's a mix of RFC JA> things going on. The RFC for messages says that each line has to be JA> broken up with CRLF (\r\n). I received two emails the other day, JA> both were missing the \r, I thought it was a little odd, the message JA> had no subject, date, to, from, size, or content, but looking at the JA> headers displayed the full email. Exporting the emails, and running JA> a nice little linux command (od) over it, I saw that the lines were JA> ending in \n instead of \r\n. According to RFC822 it is not forbidden to have separately CR or LF (but is is forbidden in RFC2822). JA> I know the RFCs say that we should be using \r\n, but it'd be nice JA> if TB was nice enough to handle the bad mail servers that sent the JA> message out without the CR (\r). I think somebody said it nicely in JA> the past on here, "be lenient in what you receive, but strict in JA> what you send"... or something to those affects. ---------------- citation ------------------ A part of syntax is described in RFC 2822 as "old" (defined in RFC 822 or historically). The messages with old syntax must not be created, but must be processed if they have met. For example: separately staying CR or LF symbol NUL point inside a phrase empty phrase a line of continue contains only spaces and comments number of year contains 2 digits selecting timezone by name instead offset source routing must be ignored a line in quotes in the local part of address empty elements in the address list spaces before colon in the name of field phrases in the fields "In-Reply-To" and "References" ---------------- end of citation ------------------ -- Sincerely, Alexey. Using TB 1.63b11 on WinSrv2003 Enterprize (v5.2 b3790), spelling by ORFO2002 (CSAPI) mailto:[EMAIL PROTECTED] http://klirik.narod.ru ________________________________________________________ Current beta is 1.63b11 | "Using TBBETA" information: http://www.silverstones.com/thebat/TBUDLInfo.html
