bad boundary choice in forwarded multipart/signed multipart/mixed

[Greg Troxel <gdt@work.lexort.com>]

[-- Attachment #2: Type: text/plain, Size: 1074 bytes --]


Using gnus from CVS about a month ago I forwarded one of my own signed
messages that itself contained a forwarded message, and a colleague
pointed out that the MIME boundary string had been reused.  That
particular example can't be sent to this list, but I managed to
reproduce the problem with test messages.

The inner test message had boundary =-=-= originally.  That got remapped
whent he message was forwarded, which I suppose is ok.  But it got
remaped to ===-=-= and that's the same value that was chosen for the
outer message's multipart/signed.

The below was generated with current CVS head epg and gnus git as of:

  commit 3aa91c009017b508c0f6298f7e8ee3a622bdccc2
  Author: Katsumi Yamaoka <yamaoka@jpl.org>
  Date:   Tue Apr 27 06:38:57 2010 +0000

      Don't load tm and apel XEmacs packages when compiling.


It looks like the key code is in mml.el in gnus, but I haven't
understood it yet.

Is perhaps the issue that the multipart/signed code is called without
the forwarded heder visible, and then the forwarded header is also
changed to the same value.


[-- Attachment #3: Type: message/rfc822, Size: 1745 bytes --]

[-- Attachment #3.1.1.1: Type: text/plain, Size: 49 bytes --]


forward of multipart/mixed as multipart/signed


[-- Attachment #3.1.1.2: Type: message/rfc822, Size: 88 bytes --]

[-- Attachment #3.1.2: Type: text/plain, Size: 31 bytes --]

Test multipart/mixed message.


[-- Attachment #3.1.3: foo.txt --]
[-- Type: text/plain, Size: 40 bytes --]

test attachment

--===-=-=--

--=-=-=--

[-- Attachment #3.1.4: Type: application/pgp-signature, Size: 194 bytes --]