From: Per Abrahamsen <abraham@dina.kvl.dk>
Subject: Re: Mail digest and MIME headers
Date: 07 Feb 2001 00:04:29 +0100 [thread overview]
Message-ID: <rjvgqnwgzm.fsf@ssv2.dina.kvl.dk> (raw)
In-Reply-To: <yl4ry74e5j.fsf@windlord.stanford.edu> (Russ Allbery's message of "06 Feb 2001 14:53:12 -0800")
Russ Allbery <rra@stanford.edu> writes:
> It's not strictly necessary, but it does say to other MUAs that you're
> guaranteeing that they can assume all of the standard defaults for the
> other MIME parameters, whereas if you leave off MIME-Version you're saying
> that the message may not comply with MIME and could be in an unknown
> character set.
Does this reasoning apply to nested messages, such as messages within
MIME digests?
For a top-level message, I agree it is a good tradeoff, because
unknown headers are hidden by most agents, even those that are not
MIME aware.
next prev parent reply other threads:[~2001-02-06 23:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 13:08 Per Abrahamsen
2001-02-06 14:09 ` ShengHuo ZHU
2001-02-06 22:41 ` Per Abrahamsen
2001-02-06 22:53 ` Russ Allbery
2001-02-06 23:04 ` Per Abrahamsen [this message]
2001-02-07 0:45 ` Russ Allbery
2001-02-06 23:09 ` ShengHuo ZHU
2001-02-06 23:16 ` Per Abrahamsen
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=rjvgqnwgzm.fsf@ssv2.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).