Reading encrypted multipart messages

Reading encrypted multipart messages

[Michael Piotrowski]

Hi,

I've posted this question before, but since I've never gotten a reply I
thought I'd ask again.  Here's the problem:

When someone forwards me a multipart message and encrypts it, I'm having
trouble getting at the forwarded message, especially its attachments.

For example, if the forwarded message consists of a text/plain part and
an attachment, or if it is a multipart/alternative message, Gnus only
displays the header of the forwarded message.  Using W M v shows the
text/plain part, but I have found no way [1] to access the attachment: K
b only shows the structure of the forwarding message, as does C-d.  In
the case of a multipart/alternative message, W M v shows all parts
(typically text/plain and text/html) but without QP decoding, etc.

Here's the structure `mm-dissect-buffer' reports for one of these
messages:

("multipart/encrypted"
 ("multipart/signed"
  ("multipart/mixed"
   (#<buffer " *mm*<7>"> ("text/plain" (charset . "iso-8859-1"))
	     quoted-printable nil nil nil nil nil)
   (#<buffer " *mm*<8>"> ("message/rfc822") nil nil ("inline") nil nil nil))
  (#<buffer " *mm*<9>"> ("text/plain" (charset . "utf-8"))
	    quoted-printable nil nil nil nil nil)
  (#<buffer " *mm*<10>"> ("text/plain" (name . "reviews_info.txt"))
	    quoted-printable nil ("attachment") nil nil nil)
  (#<buffer " *mm*<11>"> ("application/pgp-signature") nil nil nil nil nil nil)))

" *mm*<7>" is introductory text by the forwarder, this is displayed.
" *mm*<8>" is the header of the forwarded message, this is displayed.
" *mm*<9>" is the body of the forwarded message, this is *not*
           displayed.
" *mm*<10>" contains the attachment "reviews_info.txt" and the signature
            of the forwarder; both are *not* displayed.
" *mm*<11>" contains the PGP signature (not displayed, but this is ok).

Since I've never seen a similar question and have never gotten a
response, it seems that I'm in fact the only one who has this problem.
Maybe I have something incorrect in my .gnus; however, I have tried
removing all non-essential customization, without any effect.

I'd appreciate any hints on how to fix this issue.

Thanks and greetings


Footnotes: 
[1]  Except for saving the message, decrypting it, and opening it in
     Gnus using G f.

-- 
Michael Piotrowski, M.A.                               <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt> (ID 0x1614A044)

Re: Reading encrypted multipart messages

[Austin Frank]

On Mon, Jul 20 2009, Michael Piotrowski wrote:

> [...]
> 
> Since I've never seen a similar question and have never gotten a
> response, it seems that I'm in fact the only one who has this problem.
> Maybe I have something incorrect in my .gnus; however, I have tried
> removing all non-essential customization, without any effect.

Michael--

I've also noticed this problem, specifically on mails that I create by
forwarding a message that was signed using PGP/MIME.  If I can be of any
assistance in debugging this, please let me know.

Thanks,
/au

-- 
Austin Frank
http://aufrank.net
GPG Public Key (D7398C2F): http://aufrank.net/personal.asc

Re: Reading encrypted multipart messages

[Michael Piotrowski]

Frank,

On 2009-07-20, Austin Frank <austin.frank@gmail.com> wrote:

>> Since I've never seen a similar question and have never gotten a
>> response, it seems that I'm in fact the only one who has this problem.
>> Maybe I have something incorrect in my .gnus; however, I have tried
>> removing all non-essential customization, without any effect.
>
> I've also noticed this problem, specifically on mails that I create by
> forwarding a message that was signed using PGP/MIME.  If I can be of any
> assistance in debugging this, please let me know.

Thank you for confirming that there is a problem.

The output of `mm-dissect-buffer' shows that all parts are in fact
correctly decrypted and decoded; therefore it looks to me like the
problem is in the display of the decoded parts.  I'm not yet sure where
to go from here--I currently don't know which functions are involved
here and what it could be that inhibits the display of some parts.

Any hints would be appreciated!

Greetings

-- 
Michael Piotrowski, M.A.                               <mxp@dynalabs.de>
Public key at <http://www.dynalabs.de/mxp/pubkey.txt> (ID 0x1614A044)