From: Sam Varshavchik <[EMAIL PROTECTED]>Well, in that case the fix would have to be in the module that reads the files right? How are you currently detecting EOF, could this just be a fencepost problem?
No. Messages are parsed a line at a time. Hitting EOF prior to a newline terminates parsing without processing the partial last line. Part of processing involves updating the ending location of each MIME section, so when the client subsequently requests the one, and only, MIME section the server will not include the unparsed data.
Note that this only occurs when the original message is a non-multipart MIME message.
I think I'm getting in a little over my head, but here it goes.
So basically you're saying that if the file looks like this:
glad to hear from you bob\n hope things are going well with you^D
instead of this
glad to hear from you bob\n hope things are going well with you\n ^D
then they'll only see
glad to hear from you bob
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) By the way, you must be incredibly patient to listen to us all the time.
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."
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail
------------------------------------------------------- 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
