My computer uses XP Pro sp2 with IE7 . I use POP 3 server for OE6 and use
norton system works 2006. I have read and searched for more information as
to what preferences I should select for sending/reading mail. I am still
confused without understanding the best setup for the maximum performance for
my system. I want to know what benefits there are for sending mail html vs
plain text and should it be different for my newsgroups. I currently have
HTML selected but have no clue as to what MIME is or which encode text I
should use (using none now) I have no idea what quotable printable is nor 64
bit are. The help manual too vague Thanks Lisa


--
Lisa

"Lisa Elliott" wrote in message
...
My computer uses XP Pro sp2 with IE7 . I use POP 3 server for OE6 and use
norton system works 2006. I have read and searched for more information
as
to what preferences I should select for sending/reading mail. I am still
confused without understanding the best setup for the maximum performance
for
my system. I want to know what benefits there are for sending mail html
vs
plain text and should it be different for my newsgroups. I currently
have
HTML selected but have no clue as to what MIME is or which encode text I
should use (using none now) I have no idea what quotable printable is nor
64
bit are. The help manual too vague Thanks Lisa


--
Lisa

Then leave the settings alone.

--
Frank Saunders, MS-MVP OE/WM
http://www.fjsmjs.com
Answer in newsgroup. Don't send mail.

For Mail, HTML is generally OK, but newsgroups generally prefer Plain
text and some newsgroups will refuse messages that use HTML.

HTML allows you to use various fonts, colored text, etc. Plain text
does not.

Most mail programs can read HTML.

HTML requires MIME format, and normally use quoted-printable encoding
for text.

For Plain text, you can use either MIME or Uuencode. MIME handles
attachment better, but for newsgroups, some prefer Uuencode. For plain
text if you use MIME, text encoding should be either None or
quoted-printable. Don't use Base64.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"Lisa Elliott" wrote in message
...
My computer uses XP Pro sp2 with IE7 . I use POP 3 server for OE6 and
use
norton system works 2006. I have read and searched for more
information as
to what preferences I should select for sending/reading mail. I am
still
confused without understanding the best setup for the maximum
performance for
my system. I want to know what benefits there are for sending mail
html vs
plain text and should it be different for my newsgroups. I currently
have
HTML selected but have no clue as to what MIME is or which encode
text I
should use (using none now) I have no idea what quotable printable is
nor 64
bit are. The help manual too vague Thanks Lisa


--
Lisa

Michael Santovec wrote:
[deleted]

For Plain text, you can use either MIME or Uuencode. MIME handles
attachment better, but for newsgroups, some prefer Uuencode. For plain
text if you use MIME, text encoding should be either None or
quoted-printable. Don't use Base64.

Adding to Michael's response:

Please do not use Uuencode unless you *know* it's needed (which is
almost never).

If you set it to Uuencode and you use any non-ASCII characters, OE will
send the characters as it, without the required "charset=..." header.

Because many people use MS-Windows with its (default) non (formal / de
jure) standard character sets, this problem will mostly go unnoticed
until it 'hits' someone whose mail/news program *does* conform to (de
jure) standards.

FYI, this is my 'recording' on the subject:

recording

Subject: Outlook Express, missing "charset=". (was:

[Subject: changed.]

[This is a recording:]

Dear Outlook Express user,

Your posting uses local language characters like u+umlaut, but
it does not contain the required MIME headers which specify the correct
character set (probably ISO-8859/1). You can fix this as follows:

Tools - Options... - Send - News Sending Format - Plain Text
Settings... You probably have "Message format" set to "Uuencode" (which
is some stupid OE default). If so, set it to "MIME", set "Encode text
using:" to "None" and do *not* set (i.e. no tic-mark) "Allow 8-bit
characters in headers".

You may want to set the "Mail Sending Format" the same.

If you reply after fixing this, then please add some local language
characters, so that I/we can see/check if everything is OK.

Best regards,

Frank Slootweg

[End of recording. 21SEP2005.]

/recording

Thanks for your help
--
Lisa


"Michael Santovec" wrote:

For Mail, HTML is generally OK, but newsgroups generally prefer Plain
text and some newsgroups will refuse messages that use HTML.

HTML allows you to use various fonts, colored text, etc. Plain text
does not.

Most mail programs can read HTML.

HTML requires MIME format, and normally use quoted-printable encoding
for text.

For Plain text, you can use either MIME or Uuencode. MIME handles
attachment better, but for newsgroups, some prefer Uuencode. For plain
text if you use MIME, text encoding should be either None or
quoted-printable. Don't use Base64.

--

Mike - http://pages.prodigy.net/michael_santovec/techhelp.htm


"Lisa Elliott" wrote in message
...
My computer uses XP Pro sp2 with IE7 . I use POP 3 server for OE6 and
use
norton system works 2006. I have read and searched for more
information as
to what preferences I should select for sending/reading mail. I am
still
confused without understanding the best setup for the maximum
performance for
my system. I want to know what benefits there are for sending mail
html vs
plain text and should it be different for my newsgroups. I currently
have
HTML selected but have no clue as to what MIME is or which encode
text I
should use (using none now) I have no idea what quotable printable is
nor 64
bit are. The help manual too vague Thanks Lisa


--
Lisa

All is great
--
Lisa


"Frank Slootweg" wrote:

Michael Santovec wrote:
[deleted]

For Plain text, you can use either MIME or Uuencode. MIME handles
attachment better, but for newsgroups, some prefer Uuencode. For plain
text if you use MIME, text encoding should be either None or
quoted-printable. Don't use Base64.

Adding to Michael's response:

Please do not use Uuencode unless you *know* it's needed (which is
almost never).

If you set it to Uuencode and you use any non-ASCII characters, OE will
send the characters as it, without the required "charset=..." header.

Because many people use MS-Windows with its (default) non (formal / de
jure) standard character sets, this problem will mostly go unnoticed
until it 'hits' someone whose mail/news program *does* conform to (de
jure) standards.

FYI, this is my 'recording' on the subject:

recording

Subject: Outlook Express, missing "charset=". (was:

[Subject: changed.]

[This is a recording:]

Dear Outlook Express user,

Your posting uses local language characters like u+umlaut, but
it does not contain the required MIME headers which specify the correct
character set (probably ISO-8859/1). You can fix this as follows:

Tools - Options... - Send - News Sending Format - Plain Text
Settings... You probably have "Message format" set to "Uuencode" (which
is some stupid OE default). If so, set it to "MIME", set "Encode text
using:" to "None" and do *not* set (i.e. no tic-mark) "Allow 8-bit
characters in headers".

You may want to set the "Mail Sending Format" the same.

If you reply after fixing this, then please add some local language
characters, so that I/we can see/check if everything is OK.

Best regards,

Frank Slootweg

[End of recording. 21SEP2005.]

/recording