Forwarding message/rfc822 breaks subenclosures

Forwarding message/rfc822 breaks subenclosures

[Karl Kleinpaste]

Seen with this morning's CVS.

I received email containing a correctly-MIMEd text/plain with an
image/gif.  I forwarded this without modification to myself @ another
organization, that is, with no add'l text added: The message buffer
showed the #mml header as the 1st part of the content, so the entire
Content-Type was message/rfc822.  The received copy contained an extra
newline before the RFC headers began in the forwarded message,
resulting in there being no headers perceived in it.  (C-d on the
message correctly opened up a temporary nndoc subgroup, for which the
sender was "nobody" and there was no subject.  The actual RFC headers
were considered part of the body.)

Sending myself a fresh forwarded copy, then hand-editing out the extra
newline before letting Gnus see it, made it work as a properly
encapsulated message/rfc822.

Re: Forwarding message/rfc822 breaks subenclosures

[ShengHuo ZHU]

Karl Kleinpaste <karl+@cs.cmu.edu> writes:

> Seen with this morning's CVS.
> 
> I received email containing a correctly-MIMEd text/plain with an
> image/gif.  I forwarded this without modification to myself @ another
> organization, that is, with no add'l text added: The message buffer
> showed the #mml header as the 1st part of the content, so the entire
> Content-Type was message/rfc822.  The received copy contained an extra
> newline before the RFC headers began in the forwarded message,
> resulting in there being no headers perceived in it.  (C-d on the
> message correctly opened up a temporary nndoc subgroup, for which the
> sender was "nobody" and there was no subject.  The actual RFC headers
> were considered part of the body.)
> 
> Sending myself a fresh forwarded copy, then hand-editing out the extra
> newline before letting Gnus see it, made it work as a properly
> encapsulated message/rfc822.

The extra newline has been removed (0854 EST). 

ShengHuo