> The problem happens the parsing of these messages results in a bogus mime > header based on the first line. In the above case the header name would be: > > "From [EMAIL PROTECTED] Tue Oct 15 11" > > ie. everything, including spaces, up to the first colon (which is, AFAICT, > correct according to RFC822).
That is incorrect according to rfc 2822 (section 2.2 says, "A field name MUST be composed of printable US-ASCII characters (i.e., characters that have values between 33 and 126, inclusive), except colon." - space is ascii value 32). Probably the "right" thing to do for that particular line is to ignore it, since it's purpose is to delineate the beginning of new messages stored in mbox format (which is not the case with dbmail). But the header parsing routines may need to be looked at still (eg. if a non-conformant "header" line like that was elsewhere in the headers). -- Jesse Norell [EMAIL PROTECTED]
