From: ShengHuo ZHU <zsh@cs.rochester.edu>
Subject: Re: Misplaced MIME headers
Date: 30 Nov 2000 23:55:29 -0500 [thread overview]
Message-ID: <2nlmu0agfy.fsf@tiger.jia.vnet> (raw)
In-Reply-To: <vxkvgt43i03.fsf@cinnamon.vanillaknot.com>
Karl Kleinpaste <karl@charcoal.com> writes:
> Using this evening's CVS, if I write a piece of mail containing this
> content...
>
> --------------------------------
> General test text.
>
> [#mml type=text/plain disposition=attachment]
> Attachment text containing "type=text/plain disposition=attachment".
> [#/mml]
> --------------------------------
You should use <#part> instead of <#mml>. If Gnus generates such a
text, it is a bug. The content of <#mml> is some text with a message
head. Since there is only one line in the part, Gnus treat it as
head.
ShengHuo
prev parent reply other threads:[~2000-12-01 4:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 4:03 Karl Kleinpaste
2000-12-01 4:55 ` 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=2nlmu0agfy.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).