From: sigurd@12move.de (Karl Pflästerer)
Subject: Re: Ist multipart/mixed really correct?
Date: Sun, 24 Aug 2003 21:58:49 +0200 [thread overview]
Message-ID: <m3ptiux1zp.fsf@hamster.pflaesterer.de> (raw)
In-Reply-To: <m37k52ua12.fsf@defun.localdomain>
On 24 Aug 2003, Jesper Harder <- harder@myrealbox.com wrote:
> sigurd@12move.de (Karl Pflästerer) writes:
>> from a discussion in another newsgroup about the fact that Gnus under
>> special circumstances does create multipart postings we thought about
>> the correct value for the mime header.
>> Gnus declares the posting as multipart/mixed but according to rfc 2046
>> multipart/parallel seems to be the correct alternative. WDYT?
> Hard to say without knowing which special circumstances you're
> thinking about.
Sorry the reason was so obvious to me I didn't mention it: I you have a
posting with different charcter encodings which can't be unified you get
multipart/mixed.
KP
--
Mary had a little lambda,
Its syntax white as snow,
And every program Mary wrote,
She wrote in Lisp, you know.
next prev parent reply other threads:[~2003-08-24 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-24 18:09 Karl Pflästerer
2003-08-24 18:36 ` iMeowbot
2003-08-24 19:32 ` Jesper Harder
2003-08-24 19:58 ` Karl Pflästerer [this message]
2003-08-24 20:38 ` Jesper Harder
2003-08-24 21:51 ` Karl Pflästerer
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=m3ptiux1zp.fsf@hamster.pflaesterer.de \
--to=sigurd@12move.de \
/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).