From: NAGY Andras <nagya@inf.elte.hu>
Subject: mime encoding in 5.10.2
Date: Wed, 30 Jul 2003 00:08:06 +0200 [thread overview]
Message-ID: <87smopgf5l.fsf@goldfish.local> (raw)
Gnus 5.10.2 encodes a message with a plain us-ascii text part and an
attachment like this:
,----
| MIME-Version: 1.0
| Content-Type: multipart/mixed; boundary="=-=-="
|
| --=-=-=
|
| plain text
|
|
| --=-=-=
| Content-Type: application/octet-stream
| Content-Disposition: attachment; filename=printcap
|
| attachment
|
| --=-=-=--
`----
Note the missing content-type header for the text part. Is this
behavior standards compliant?
Andras
next reply other threads:[~2003-07-29 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 22:08 NAGY Andras [this message]
2003-07-30 5:06 ` Katsumi Yamaoka
2003-07-31 1:22 ` Simon Josefsson
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=87smopgf5l.fsf@goldfish.local \
--to=nagya@inf.elte.hu \
/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).