[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rt-devel
Subject:    Re: [Rt-devel] Bug: Forward + GnuPG sign = illegal MIME encoding
From:       Otmar Lendl <ol () bofh ! priv ! at>
Date:       2009-10-20 22:29:46
Message-ID: 4ADE39DA.7010905 () bofh ! priv ! at
[Download RAW message or body]

Hi,

Ruslan Zakirov wrote:
> Hello,
> 
> Thanks for looking further into RFCs. So I think we should do the following:
> 
> 1) in lib/RT/Crypt/GnuPG.pm don't set content transfer encoding on
> message/ parts.

Same applies to multipart/, see also 6.4 of rfc2045

----
   If an entity is
   of type "multipart" the Content-Transfer-Encoding is not permitted to
   have any value other than "7bit", "8bit" or "binary".  Even more
   severe restrictions apply to some subtypes of the "message" type
---

> 
> 2) set content transfer encoding of a forward subparts to base64 or
> quoted-printable unless it's 7bit. we should do this only if we're
> going to sign forwarded message.

Agreed, that's the proper solution.

/ol
-- 
-=-  Otmar Lendl  --  ol@bofh.priv.at  --  http://lendl.priv.at/  -=-
_______________________________________________
List info: http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
[prev in list] [next in list] [prev in thread] [next in thread]