[rollei_list] Re: "MIME encoding" (was: TEST)
- From: "Peter K." <peterk727@xxxxxxxxx>
- To: rollei_list@xxxxxxxxxxxxx
- Date: Tue, 26 Apr 2005 22:15:32 -0700
Oh-oh. Herr Lehrer is not going to like that f*&^%#g stuff.
On 4/26/05, Richard Knoppow <dickburk@xxxxxxxxxxxxx> wrote:
>=20
> ----- Original Message -----
> From: "Richard Knoppow" <dickburk@xxxxxxxxxxxxx>
> To: <rollei_list@xxxxxxxxxxxxx>
> Sent: Tuesday, April 26, 2005 5:49 PM
> Subject: [rollei_list] Re: "MIME encoding" (was: TEST)
>=20
> >
> > ----- Original Message -----=3D20
> > From: "Richard Knoppow" <dickburk@xxxxxxxxxxxxx>
> > To: <rollei_list@xxxxxxxxxxxxx>
> > Sent: Tuesday, April 26, 2005 5:46 PM
> > Subject: [rollei_list] Re: "MIME encoding" (was: TEST)
> >
> >
> >> Test for special characters. No coding being used.
> >>=3D20
> >> I will try some special characters here to see how they
> >> are=3D20
> >> reproduced: C =3DF9 =3DC7 =3DC2 =3DE3 =3DE9 =3DE8
> > Same but sending quoted printible C =3DF9 =3DC7 =3DC2 =3DE3 =3DE9
> > =3DE8
>=20
> So, this proves the odd charactes above are caused by the
> list machine converting Quoted-Printible to plain text. When
> the special characters are sent without coding of any sort
> they are reproduced properly as in my first test. The hash
> characters in earlier posts were caused by my turning on
> MIME and setting it for Base-64 as an option for _plain
> text_ in OE. I will not test attachments here because they
> should never be sent to the list. I have sent binary
> attachments via e-mail with these settings and they came
> through OK. Advise is to set your mail program so that it
> sends mail to the list in plain text with no MIME encoding
> at all if your mail program allows that.
>=20
> ---
> Richard Knoppow
> Los Angeles, CA, USA
> dickburk@xxxxxxxxxxxxx
>=20
>=20
--=20
Peter K
=D3=BF=D5=AC
Other related posts:
