From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: multipart part does not have valid content-type
Date: Mon, 30 Aug 2010 08:33:45 -0500 [thread overview]
Message-ID: <8762ysql6u.fsf@lifelogs.com> (raw)
In-Reply-To: <m3wrraz8g0.fsf@quimbies.gnus.org>
On Sun, 29 Aug 2010 00:19:43 +0200 Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
LMI> David Engster <deng@randomsample.de> writes:
>> I would vote for making this the default.
LMI> Since some things out there seem to not like having parts without
LMI> explicit Content-Type headers, that might be best. However:
>> I agree that it should be unnecessary; RFC 1521 does not "not
>> strictly" require it for text/plain, it simply does not require it
>> ("If no Content-Type is specified, this default is assumed.", with the
>> default being text/plain,us-ascii). I find it strange that debian-bugs
>> actually filters messages based on such very general notions.
LMI> It is really strange. Downright weird. I think debian-bugs should just
LMI> fix their filters.
Let's just be explicit about it. What's a few more bytes between friends?
Ted
next prev parent reply other threads:[~2010-08-30 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20100809231654.GZ31014@rzlab.ucr.edu>
2010-08-09 23:36 ` jidanni
2010-08-10 0:18 ` Katsumi Yamaoka
2010-08-10 5:59 ` David Engster
2010-08-28 22:19 ` Lars Magne Ingebrigtsen
2010-08-30 13:33 ` Ted Zlatanov [this message]
2010-08-30 17:01 ` Lars Magne Ingebrigtsen
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=8762ysql6u.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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).