atom feed21 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: To base64, or...
FromSent OnAttachments
Jerry AmundsonJun 25, 2003 1:55 pm 
Sam VarshavchikJun 25, 2003 3:09 pm 
Jerry AmundsonJun 26, 2003 9:04 pm 
Jerry AmundsonJun 26, 2003 9:25 pm 
Sam VarshavchikJun 27, 2003 7:42 am 
Sam VarshavchikJun 27, 2003 7:58 am 
Jerry AmundsonJun 27, 2003 8:38 am 
Sam VarshavchikJun 27, 2003 9:41 am 
Jerry AmundsonJun 27, 2003 2:55 pm 
Sam VarshavchikJun 27, 2003 6:35 pm 
Jason HaarJun 29, 2003 4:54 pm 
Jerry AmundsonJul 2, 2003 12:25 pm 
Sam VarshavchikJul 2, 2003 3:10 pm 
Jerry AmundsonJul 2, 2003 9:55 pm 
Sam VarshavchikJul 2, 2003 11:26 pm 
Jerry AmundsonJul 3, 2003 7:10 am 
Sam VarshavchikJul 3, 2003 8:37 am 
Jerry AmundsonJul 3, 2003 10:24 am 
Sam VarshavchikJul 3, 2003 6:07 pm 
Systems AdministratorJul 3, 2003 11:08 pm 
Jerry AmundsonJul 4, 2003 1:23 am 
Subject:Re: [courier-users] Re: To base64, or not to base64?
From:Jerry Amundson (jer@pbs.com)
Date:Jun 27, 2003 8:38:42 am
List:net.sourceforge.lists.courier-users

Sam Varshavchik wrote:

Jerry Amundson writes:

Regardless, the crap at least used to work. Perhaps one of several recent rfc2045 changes?

2003-03-01 Mr. Sam <mrs@courier-mta.com>

* webmail/autoresponse.c (read_headers): Use rfc2045_parse_partial() to properly size-up content without trailing newlines.

Irrelevant.

2003-01-30 Mr. Sam <mrs@courier-mta.com>

* rfc2045/rfc2045encode.c: clean up base64/qp encoding.

Only affects the encoding itself. Does not affect the decision whether to encode, and why.

Funny thing is the decision isn't corrupting the attachment. The modifications to the encoding are corrupting the attachment.

I'm rebuilding 0.40.1 so I can revert back to before the next batch of PDF's are sent out...

jerry