7 messages in net.sourceforge.lists.courier-users[courier-users] Re: RFC2045rewrite bu...
FromSent OnAttachments
Folke AshbergJan 23, 2002 12:48 pm.diff
Sam VarshavchikJan 23, 2002 3:13 pm 
Folke AshbergJan 23, 2002 10:01 pm 
Sam VarshavchikJan 23, 2002 10:17 pm 
Folke AshbergJan 24, 2002 9:14 am 
Sam VarshavchikJan 24, 2002 2:46 pm.txt
Folke AshbergJan 24, 2002 3:36 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: RFC2045rewrite bug @ multipart/signedActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Jan 23, 2002 10:17:50 pm
List:net.sourceforge.lists.courier-users

Folke Ashberg writes:

On Mit, 24 Jan 2002, Sam Varshavchik wrote:

Folke Ashberg writes:

after a while i've found the cause: couriers MIME-rewrite.

The pgp-signed mail more than one signed boundry looks as follows: 1 multipart/signed 1.1 multipart/mixed 1.1.1 text/plain (mail text) 1.1.2 xxx/xxxx (attachment) 1.2 application/pgp-signature (all 1.1 stuff is signed)

Between the last boundry of 1.1 and the starting boundry of 1.2 there is a \n inserted when rewriting, and that's the problem.

The current version of Courier should be skipping multipart/signed MIME content altogether.

No! i refer to 0.37.2 and the function which has the comment

/* Slurp the untouchable portion of multipart/signed */

!!!

That code is correct. I see nothing wrong with it.

Hint: posting a claim that something isn't working correctly, without showing an example, followed by a patch whose meaning is not clear, is not going to fly.

If there's a problem, it must lie elsewhere. It's not here.

-- Sam