From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Content-type: text/plain
Date: Sat, 18 Oct 2003 01:37:04 +0200 [thread overview]
Message-ID: <m38ynj4esf.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <ilubrwntygk.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> Exactly what happens in Outlook when a part doesn't have a
> Content-Type header?
>
> Is there a suitable variable for these kind of workarounds? E.g.,
> (add-to-list 'mml-workarounds 'always-add-content-type). IMHO, it
> should be customizable regardless of what the default is.
Since people don't seem to be complaining much, I vote for pretending
that we don't know that there's any problem in this area.
Missing Content-type? What missing Content-type?
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2003-10-17 23:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-24 0:35 Lars Magne Ingebrigtsen
2003-06-24 2:54 ` Wes Hardaker
2003-06-24 13:08 ` Simon Josefsson
2003-10-17 23:37 ` Lars Magne Ingebrigtsen [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=m38ynj4esf.fsf@quimbies.gnus.org \
--to=larsi@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).