17 messages in net.sourceforge.lists.courier-users[courier-users] Re: last line being t...
FromSent OnAttachments
Jason R. MastalerFeb 20, 2003 3:43 pm 
Sam VarshavchikFeb 20, 2003 4:54 pm 
Jesse CablekFeb 24, 2003 10:51 am 
Sam VarshavchikFeb 24, 2003 2:47 pm 
Chris BerryFeb 24, 2003 3:08 pm 
Sam VarshavchikFeb 24, 2003 3:44 pm 
Chris BerryFeb 24, 2003 4:30 pm 
Jason TackaberryFeb 24, 2003 4:46 pm 
Kurt BiglerFeb 24, 2003 5:28 pm 
Sam VarshavchikFeb 24, 2003 5:33 pm 
Chris BerryFeb 24, 2003 7:02 pm 
Sam VarshavchikFeb 24, 2003 8:56 pm 
Chris BerryFeb 25, 2003 12:03 pm 
Jesse CablekFeb 25, 2003 1:16 pm 
Jesse CablekFeb 25, 2003 3:12 pm 
Sam VarshavchikFeb 25, 2003 8:11 pm 
Jesse CablekFeb 25, 2003 9:34 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: last line being truncatedActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Feb 24, 2003 5:33:46 pm
List:net.sourceforge.lists.courier-users

Chris Berry writes:

From: Sam Varshavchik <mrs@courier-mta.com>

Message files may be readonly.

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.