View Single Post
  #6  
Old January 26th 07, 05:25 AM posted to microsoft.public.windows.inetexplorer.ie6_outlookexpress
Lisa Elliott
external usenet poster
 
Posts: 3
Default OE6 Mail Sending Format Recommendation

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

Ads