From: Sam Varshavchik <[EMAIL PROTECTED]>In which case, couldn't you just adjust the parser to append whatever was in the buffer for that line when it hits the EOF marker? (I'm sure it's more complicated than I'm making it sound)
It is. So, when everything is working properly for well-formed mail content the last thing you want to do is screw around with it. The marginal benefit of improved handling of invalid input is outweighed by the potential of a major screwup.
Certainly true on a production system, couldn't it be supplied as an optional patch or something of that nature?
Potential changes to any part of MIME parsing logic must have a damn good reason for them.
No argument there, though I'm not sure I see what kind of evil things could happen by adding what's in the buffer when you see ^D instead of \n^D. Am I missing something obvious? Did anyone ever find out what client he was using to inject messages that was causing this problem, might be easier to attack the problem from that end anyways.
Chris Berry [EMAIL PROTECTED] Systems Administrator JM Associates
"Linux and I have a love/hate relationship. I hate its complexity until I figure out how something works, then I love its power."
_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE* http://join.msn.com/?page=features/virus
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
