On Fri, 23 Jun 2006 23:06:54 -0400, Chris wrote in message
> On Fri, 23 Jun 2006 18:02:04 +0200
> Arnt Karlsen wrote:
> > On Fri, 23 Jun 2006 09:04:18 -0400, Chris wrote in message
> > <20060623090418.3c8b7120@...>:
> > > On Fri, 23 Jun 2006 13:54:01 +0200
> > > Arnt Karlsen wrote:
> > > >
> > > > ..aye. Now, Flamebait, who _is_ using, and, _why_ use:
> > > > " Content-Type: multipart/mixed; boundary=
> > > > "===============1980762402==" ",
> > > > " Content-Transfer-Encoding: quoted-printable ",
> > > > " Content-Type: text/plain; charset="us-ascii"
> > > > MIME-Version: 1.0
> > > > Content-Transfer-Encoding: 7bit
> > > > Content-Disposition: inline ", etc? ;o)
> > >
> > > I have no idea what you're saying/asking.
> > .. ;o) The above snippet comes from your messages. I have only
> > seen these in Microsofts default setups of their mail clients, and
> > found your exchange with Andrew amusing, considering how he heeds
> > advice you don't heed, like http://www.expita.com/nomime.html
> > ..common wisdom is shy away
..my senselessly missing " from " here may have confused. ;o)
> > Microsoft classics like
> > " Content-Type: multipart/mixed " and
> > " Content-Transfer-Encoding: quoted-printable ".
> I'm sorry, but what you're saying makes no sense to me at all. The
> above is all a bunch of bog-standard MIME message and message part
> headers -- please see RFC 1341, which set the original standard for
> MIME-encoded email, and which Microsoft had exactly zero to do with.
> You're going to see "multipart/mixed", for instance, in the header
> of any MIME-encoded email with multiple, independantly typed parts.
> They'll come that way out of Thunderbird, Evolution, mutt, balsa,
> and sylpheed-claws (which I use); and it has nothing to do with
> Microsoft at all.
> If you're convinced you're onto something here, then feel free to file
> some sort of bug against the Debian packages that implement MIME
> handling (metamail, IIRC, but I'm not sure). But I can't imagine
> what the problem would be.
..I don't consider your compliance to rfc 1341 exposing Microsoft bugs,
a bug, just an inconvenience to our dear windroids using Microsoft mail
clients here, and the commonly accepted wisdom here is minimize any
such inconvenience, by using plain text messages only and avoiding
"fancy" stuff like "multipart/mixed" and "quoted-printable."
..in the long term however, I guess they will likely be better served by
suffering your mild pressure away from Microsoft software towards what
we use. Am I onto something here? ;o)
..med vennlig hilsen = with Kind Regards from Arnt... ;o)
...with a number of polar bear hunters in his ancestry...
Scenarios always come in sets of three:
best case, worst case, and just in case.