From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Forwarding message/rfc822 breaks subenclosures
Date: 01 Nov 2000 16:05:16 -0500 [thread overview]
Message-ID: <2nbsvz1jzn.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <vxkn1fjtntk.fsf@cinnamon.vanillaknot.com>
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
prev parent reply other threads:[~2000-11-01 21:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 20:55 Karl Kleinpaste
2000-11-01 21:05 ` ShengHuo ZHU [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2nbsvz1jzn.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).