Outlook 2003 character encoding

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I did an upgrade from XP Pro to Vista Business. I'm still using Outlook
2003. Everything seemed fine...at first.

After a bit I received some bounced messages because the character encoding
is set to windows-1250 instead of US English. Sure enough, all my emails are
going out with this encoding. However, every place I can find to change that
setting shows US English.

It appears to be specific to Outlook. I installed Thunderbird and no
problem. I also uninstalled and reinstalled Outlook and Office in it's
entirety several times. I just can't find where this windows-1250 is coming
from.

Any ideas?
 
If you are only speaking english encoding makes no difference, most encoding
shows english characters unchanged (don't know about chinese and japanese).
UTF8 is a good choice. English is the same (as in all unicodes).

1250 is Central European. Vista supplies a default code page to ANSI (which
1250 is an ANSI codepage) applications (though OL is probably a Unicode
app). So check the default code page for ANSI Apps. Whoops - the
configuration dialog has gone from Vista. That makes it hard. Help wasn't
helpful, seems to return only items with nothing to do with search terms.

This guy is an MS programmer and expert on international features of
windows. When you look at the page I think you find it's not a simple
subject. He seems to answer questions from punters.
http://blogs.msdn.com/michkap

But I only speak english and I don't care about those who can't speak. I'm
an expert here on international features of the keyboard and how to get that
character into an app (I'm a reluctant expert). It is so complicated. I want
a simple windows that can talk english

Let germans speak german and english speak a derived german called english.

I'm surprised it bounced though - 1250 should be acceptable and if written
in english look identical.
 
There is no reason for messages to "bounce" just because of
using Windows-1250 encoding. Can you post one of these
bounce notices?

Gary VanderMolen
 
I don't have one handy. It bounced because the receiving server was set to
reject messages with that character set. It's becoming a little more common
because of all the 'international' spam. Most of my email is going through
okay. But there are a couple that have come back because they won't accept
that character set...an Earthlink address was one of them. I'll see if I can
get another bounce and will post it.
 
Here's a copy of some of the pertinent info from a reject:

The user does not accept email in non-Western (non-Latin) character sets.

--- Below this line is a copy of the message.
Received: (qmail 1590 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO pre-smtp04-02.prod.mesa1.secureserver.net)
([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by smtp14-02.prod.mesa1.secureserver.net (qmail-ldap-1.03) with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: (qmail 22255 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO secure.xxx.com) ([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by pre-smtp04-02.prod.mesa1.secureserver.net (qmail-ldap-1.03)
with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: from localhost (localhost [127.0.0.1])
by secure.xxx.com (Postfix) with ESMTP id 5CC1F5C06B
for <[email protected]>; Sun, 1 Apr 2007 12:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at xxx.com
Received: from secure.xxx.com ([127.0.0.1])
by localhost (secure.xxx.com [127.0.0.1]) (amavisd-new, port xxxxx)
with ESMTP id CB7zPfLybGTH for <[email protected]>;
Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
Received: from Partagas (adsl-xxx-xxx-xxx-xxx.dsl.lsan03.pacbell.net
[xxx.xxx.xxx.xxx
by secure.xxx.com (Postfix) with ESMTP id A53705C06A
for <[email protected]>; Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
From: "Don" <[email protected]>
To: "'xxx'" <[email protected]>
Subject: xxxxxxxxxxxx
Date: Sun, 1 Apr 2007 12:42:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
Thread-Index: Acd0leZOFQiAXPX4SiiIv9XdFIE5ZQ==
Message-Id: <[email protected]>

Hope this helps. Thanks for your ideas.

- Don
 
That rule (no non-Western character sets) might make it tough for
Eastern European or Asian folks to communicate in their native
language with relatives in the US.

Gary VanderMolen

Don said:
Here's a copy of some of the pertinent info from a reject:

The user does not accept email in non-Western (non-Latin) character sets.

--- Below this line is a copy of the message.
Received: (qmail 1590 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO pre-smtp04-02.prod.mesa1.secureserver.net)
([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by smtp14-02.prod.mesa1.secureserver.net (qmail-ldap-1.03) with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: (qmail 22255 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO secure.xxx.com) ([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by pre-smtp04-02.prod.mesa1.secureserver.net (qmail-ldap-1.03)
with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: from localhost (localhost [127.0.0.1])
by secure.xxx.com (Postfix) with ESMTP id 5CC1F5C06B
for <[email protected]>; Sun, 1 Apr 2007 12:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at xxx.com
Received: from secure.xxx.com ([127.0.0.1])
by localhost (secure.xxx.com [127.0.0.1]) (amavisd-new, port xxxxx)
with ESMTP id CB7zPfLybGTH for <[email protected]>;
Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
Received: from Partagas (adsl-xxx-xxx-xxx-xxx.dsl.lsan03.pacbell.net
[xxx.xxx.xxx.xxx
by secure.xxx.com (Postfix) with ESMTP id A53705C06A
for <[email protected]>; Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
From: "Don" <[email protected]>
To: "'xxx'" <[email protected]>
Subject: xxxxxxxxxxxx
Date: Sun, 1 Apr 2007 12:42:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
Thread-Index: Acd0leZOFQiAXPX4SiiIv9XdFIE5ZQ==
Message-Id: <[email protected]>

Hope this helps. Thanks for your ideas.

- Don

Gary VanderMolen said:
There is no reason for messages to "bounce" just because of
using Windows-1250 encoding. Can you post one of these
bounce notices?

Gary VanderMolen
Click to expand...
Click to expand...
 
Yup, I agree. It would make it difficult!

Generally I wouldn't care. Of course because of it I see my email is
encoded incorrectly and, although it shouldn't make a difference, it does. I
can't figure out how to fix it. I've checked all the places I can think of
and find for the character encoding for Outlook, Office and Windows in
general and they are all showing US English. I even when so far as to check
the Outlook values in the registry...as scary as that is. Still can't find
the problem.

Gary VanderMolen said:
That rule (no non-Western character sets) might make it tough for
Eastern European or Asian folks to communicate in their native
language with relatives in the US.

Gary VanderMolen

Don said:
Here's a copy of some of the pertinent info from a reject:

The user does not accept email in non-Western (non-Latin) character sets.

--- Below this line is a copy of the message.
Received: (qmail 1590 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO pre-smtp04-02.prod.mesa1.secureserver.net)
([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by smtp14-02.prod.mesa1.secureserver.net (qmail-ldap-1.03) with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: (qmail 22255 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO secure.xxx.com) ([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by pre-smtp04-02.prod.mesa1.secureserver.net (qmail-ldap-1.03)
with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: from localhost (localhost [127.0.0.1])
by secure.xxx.com (Postfix) with ESMTP id 5CC1F5C06B
for <[email protected]>; Sun, 1 Apr 2007 12:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at xxx.com
Received: from secure.xxx.com ([127.0.0.1])
by localhost (secure.xxx.com [127.0.0.1]) (amavisd-new, port xxxxx)
with ESMTP id CB7zPfLybGTH for <[email protected]>;
Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
Received: from Partagas (adsl-xxx-xxx-xxx-xxx.dsl.lsan03.pacbell.net
[xxx.xxx.xxx.xxx
by secure.xxx.com (Postfix) with ESMTP id A53705C06A
for <[email protected]>; Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
From: "Don" <[email protected]>
To: "'xxx'" <[email protected]>
Subject: xxxxxxxxxxxx
Date: Sun, 1 Apr 2007 12:42:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
Thread-Index: Acd0leZOFQiAXPX4SiiIv9XdFIE5ZQ==
Message-Id: <[email protected]>

Hope this helps. Thanks for your ideas.

- Don

Gary VanderMolen said:
There is no reason for messages to "bounce" just because of
using Windows-1250 encoding. Can you post one of these
bounce notices?

Gary VanderMolen

I did an upgrade from XP Pro to Vista Business. I'm still using Outlook
2003. Everything seemed fine...at first.

After a bit I received some bounced messages because the character encoding
is set to windows-1250 instead of US English. Sure enough, all my emails are
going out with this encoding. However, every place I can find to change that
setting shows US English.

It appears to be specific to Outlook. I installed Thunderbird and no
problem. I also uninstalled and reinstalled Outlook and Office in it's
entirety several times. I just can't find where this windows-1250 is coming
from.

Any ideas?
Click to expand...
Click to expand...
Click to expand...
 
Doesn't ur have an encoding menu/sub menu. It winmail / OE it is on the
format menu.
Don said:
Yup, I agree. It would make it difficult!

Generally I wouldn't care. Of course because of it I see my email is
encoded incorrectly and, although it shouldn't make a difference, it does.
I
can't figure out how to fix it. I've checked all the places I can think
of
and find for the character encoding for Outlook, Office and Windows in
general and they are all showing US English. I even when so far as to
check
the Outlook values in the registry...as scary as that is. Still can't
find
the problem.

Gary VanderMolen said:
That rule (no non-Western character sets) might make it tough for
Eastern European or Asian folks to communicate in their native
language with relatives in the US.

Gary VanderMolen

Don said:
Here's a copy of some of the pertinent info from a reject:

The user does not accept email in non-Western (non-Latin) character
sets.

--- Below this line is a copy of the message.
Received: (qmail 1590 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO pre-smtp04-02.prod.mesa1.secureserver.net)
([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by smtp14-02.prod.mesa1.secureserver.net (qmail-ldap-1.03)
with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: (qmail 22255 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO secure.xxx.com) ([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by pre-smtp04-02.prod.mesa1.secureserver.net (qmail-ldap-1.03)
with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: from localhost (localhost [127.0.0.1])
by secure.xxx.com (Postfix) with ESMTP id 5CC1F5C06B
for <[email protected]>; Sun, 1 Apr 2007 12:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at xxx.com
Received: from secure.xxx.com ([127.0.0.1])
by localhost (secure.xxx.com [127.0.0.1]) (amavisd-new, port xxxxx)
with ESMTP id CB7zPfLybGTH for <[email protected]>;
Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
Received: from Partagas (adsl-xxx-xxx-xxx-xxx.dsl.lsan03.pacbell.net
[xxx.xxx.xxx.xxx
by secure.xxx.com (Postfix) with ESMTP id A53705C06A
for <[email protected]>; Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
From: "Don" <[email protected]>
To: "'xxx'" <[email protected]>
Subject: xxxxxxxxxxxx
Date: Sun, 1 Apr 2007 12:42:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
Thread-Index: Acd0leZOFQiAXPX4SiiIv9XdFIE5ZQ==
Message-Id: <[email protected]>

Hope this helps. Thanks for your ideas.

- Don

:

There is no reason for messages to "bounce" just because of
using Windows-1250 encoding. Can you post one of these
bounce notices?

Gary VanderMolen

I did an upgrade from XP Pro to Vista Business. I'm still using
Outlook
2003. Everything seemed fine...at first.

After a bit I received some bounced messages because the character
encoding
is set to windows-1250 instead of US English. Sure enough, all my
emails are
going out with this encoding. However, every place I can find to
change that
setting shows US English.

It appears to be specific to Outlook. I installed Thunderbird and
no
problem. I also uninstalled and reinstalled Outlook and Office in
it's
entirety several times. I just can't find where this windows-1250
is coming
from.

Any ideas?
Click to expand...
Click to expand...
Click to expand...
 
You've probably already checked this, but, FWIW:

http://office.microsoft.com/en-us/outlook/HP052428821033.aspx
Change message encoding used to send messages in other languages

Hal
--
Hal Hostetler, CPBE -- (e-mail address removed)
Senior Engineer/MIS -- MS MVP-Print/Imaging -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Still Cadillacin' - www.badnewsbluesband.com

Don said:
Yup, I agree. It would make it difficult!

Generally I wouldn't care. Of course because of it I see my email is
encoded incorrectly and, although it shouldn't make a difference, it does. I
can't figure out how to fix it. I've checked all the places I can think of
and find for the character encoding for Outlook, Office and Windows in
general and they are all showing US English. I even when so far as to check
the Outlook values in the registry...as scary as that is. Still can't find
the problem.

Gary VanderMolen said:
That rule (no non-Western character sets) might make it tough for
Eastern European or Asian folks to communicate in their native
language with relatives in the US.

Gary VanderMolen

Here's a copy of some of the pertinent info from a reject:

The user does not accept email in non-Western (non-Latin) character sets.

--- Below this line is a copy of the message.
Received: (qmail 1590 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO pre-smtp04-02.prod.mesa1.secureserver.net)
([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by smtp14-02.prod.mesa1.secureserver.net (qmail-ldap-1.03) with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: (qmail 22255 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO secure.xxx.com) ([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by pre-smtp04-02.prod.mesa1.secureserver.net (qmail-ldap-1.03)
with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: from localhost (localhost [127.0.0.1])
by secure.xxx.com (Postfix) with ESMTP id 5CC1F5C06B
for <[email protected]>; Sun, 1 Apr 2007 12:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at xxx.com
Received: from secure.xxx.com ([127.0.0.1])
by localhost (secure.xxx.com [127.0.0.1]) (amavisd-new, port xxxxx)
with ESMTP id CB7zPfLybGTH for <[email protected]>;
Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
Received: from Partagas (adsl-xxx-xxx-xxx-xxx.dsl.lsan03.pacbell.net
[xxx.xxx.xxx.xxx
by secure.xxx.com (Postfix) with ESMTP id A53705C06A
for <[email protected]>; Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
From: "Don" <[email protected]>
To: "'xxx'" <[email protected]>
Subject: xxxxxxxxxxxx
Date: Sun, 1 Apr 2007 12:42:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
Thread-Index: Acd0leZOFQiAXPX4SiiIv9XdFIE5ZQ==
Message-Id: <[email protected]>

Hope this helps. Thanks for your ideas.

- Don

:

There is no reason for messages to "bounce" just because of
using Windows-1250 encoding. Can you post one of these
bounce notices?

Gary VanderMolen

I did an upgrade from XP Pro to Vista Business. I'm still using Outlook
2003. Everything seemed fine...at first.

After a bit I received some bounced messages because the character encoding
is set to windows-1250 instead of US English. Sure enough, all my emails are
going out with this encoding. However, every place I can find to change that
setting shows US English.

It appears to be specific to Outlook. I installed Thunderbird and no
problem. I also uninstalled and reinstalled Outlook and Office in it's
entirety several times. I just can't find where this windows-1250 is coming
from.

Any ideas?
Click to expand...
Click to expand...
Click to expand...
 
Yes. Checked that. It was set to US English

. said:
Doesn't ur have an encoding menu/sub menu. It winmail / OE it is on the
format menu.
Don said:
Yup, I agree. It would make it difficult!

Generally I wouldn't care. Of course because of it I see my email is
encoded incorrectly and, although it shouldn't make a difference, it does.
I
can't figure out how to fix it. I've checked all the places I can think
of
and find for the character encoding for Outlook, Office and Windows in
general and they are all showing US English. I even when so far as to
check
the Outlook values in the registry...as scary as that is. Still can't
find
the problem.

Gary VanderMolen said:
That rule (no non-Western character sets) might make it tough for
Eastern European or Asian folks to communicate in their native
language with relatives in the US.

Gary VanderMolen

Here's a copy of some of the pertinent info from a reject:

The user does not accept email in non-Western (non-Latin) character
sets.

--- Below this line is a copy of the message.
Received: (qmail 1590 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO pre-smtp04-02.prod.mesa1.secureserver.net)
([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by smtp14-02.prod.mesa1.secureserver.net (qmail-ldap-1.03)
with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: (qmail 22255 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO secure.xxx.com) ([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by pre-smtp04-02.prod.mesa1.secureserver.net (qmail-ldap-1.03)
with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: from localhost (localhost [127.0.0.1])
by secure.xxx.com (Postfix) with ESMTP id 5CC1F5C06B
for <[email protected]>; Sun, 1 Apr 2007 12:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at xxx.com
Received: from secure.xxx.com ([127.0.0.1])
by localhost (secure.xxx.com [127.0.0.1]) (amavisd-new, port xxxxx)
with ESMTP id CB7zPfLybGTH for <[email protected]>;
Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
Received: from Partagas (adsl-xxx-xxx-xxx-xxx.dsl.lsan03.pacbell.net
[xxx.xxx.xxx.xxx
by secure.xxx.com (Postfix) with ESMTP id A53705C06A
for <[email protected]>; Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
From: "Don" <[email protected]>
To: "'xxx'" <[email protected]>
Subject: xxxxxxxxxxxx
Date: Sun, 1 Apr 2007 12:42:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
Thread-Index: Acd0leZOFQiAXPX4SiiIv9XdFIE5ZQ==
Message-Id: <[email protected]>

Hope this helps. Thanks for your ideas.

- Don

:

There is no reason for messages to "bounce" just because of
using Windows-1250 encoding. Can you post one of these
bounce notices?

Gary VanderMolen

I did an upgrade from XP Pro to Vista Business. I'm still using
Outlook
2003. Everything seemed fine...at first.

After a bit I received some bounced messages because the character
encoding
is set to windows-1250 instead of US English. Sure enough, all my
emails are
going out with this encoding. However, every place I can find to
change that
setting shows US English.

It appears to be specific to Outlook. I installed Thunderbird and
no
problem. I also uninstalled and reinstalled Outlook and Office in
it's
entirety several times. I just can't find where this windows-1250
is coming
from.

Any ideas?
Click to expand...
Click to expand...
Click to expand...
 
Thanks Hal. You're right, I already checked that and it was set correctly.
That's part of what's so frustrating. But thanks for the idea! If you have
any others I'm game to try them.

Hal Hostetler said:
You've probably already checked this, but, FWIW:

http://office.microsoft.com/en-us/outlook/HP052428821033.aspx
Change message encoding used to send messages in other languages

Hal
--
Hal Hostetler, CPBE -- (e-mail address removed)
Senior Engineer/MIS -- MS MVP-Print/Imaging -- WA7BGX
http://www.kvoa.com -- "When News breaks, we fix it!"
KVOA Television, Tucson, AZ. NBC Channel 4
Still Cadillacin' - www.badnewsbluesband.com

Don said:
Yup, I agree. It would make it difficult!

Generally I wouldn't care. Of course because of it I see my email is
encoded incorrectly and, although it shouldn't make a difference, it does. I
can't figure out how to fix it. I've checked all the places I can think of
and find for the character encoding for Outlook, Office and Windows in
general and they are all showing US English. I even when so far as to check
the Outlook values in the registry...as scary as that is. Still can't find
the problem.

Gary VanderMolen said:
That rule (no non-Western character sets) might make it tough for
Eastern European or Asian folks to communicate in their native
language with relatives in the US.

Gary VanderMolen

Here's a copy of some of the pertinent info from a reject:

The user does not accept email in non-Western (non-Latin) character sets.

--- Below this line is a copy of the message.
Received: (qmail 1590 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO pre-smtp04-02.prod.mesa1.secureserver.net)
([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by smtp14-02.prod.mesa1.secureserver.net (qmail-ldap-1.03) with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: (qmail 22255 invoked from network); 1 Apr 2007 19:42:36 -0000
Received: from unknown (HELO secure.xxx.com) ([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by pre-smtp04-02.prod.mesa1.secureserver.net (qmail-ldap-1.03)
with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: from localhost (localhost [127.0.0.1])
by secure.xxx.com (Postfix) with ESMTP id 5CC1F5C06B
for <[email protected]>; Sun, 1 Apr 2007 12:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at xxx.com
Received: from secure.xxx.com ([127.0.0.1])
by localhost (secure.xxx.com [127.0.0.1]) (amavisd-new, port xxxxx)
with ESMTP id CB7zPfLybGTH for <[email protected]>;
Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
Received: from Partagas (adsl-xxx-xxx-xxx-xxx.dsl.lsan03.pacbell.net
[xxx.xxx.xxx.xxx
by secure.xxx.com (Postfix) with ESMTP id A53705C06A
for <[email protected]>; Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
From: "Don" <[email protected]>
To: "'xxx'" <[email protected]>
Subject: xxxxxxxxxxxx
Date: Sun, 1 Apr 2007 12:42:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
Thread-Index: Acd0leZOFQiAXPX4SiiIv9XdFIE5ZQ==
Message-Id: <[email protected]>

Hope this helps. Thanks for your ideas.

- Don

:

There is no reason for messages to "bounce" just because of
using Windows-1250 encoding. Can you post one of these
bounce notices?

Gary VanderMolen

I did an upgrade from XP Pro to Vista Business. I'm still using Outlook
2003. Everything seemed fine...at first.

After a bit I received some bounced messages because the character encoding
is set to windows-1250 instead of US English. Sure enough, all my emails are
going out with this encoding. However, every place I can find to change that
setting shows US English.

It appears to be specific to Outlook. I installed Thunderbird and no
problem. I also uninstalled and reinstalled Outlook and Office in it's
entirety several times. I just can't find where this windows-1250 is coming
from.

Any ideas?
Click to expand...
Click to expand...
Click to expand...
 
In the message window Format menu. The main window View menu is for
viewing.
Don said:
Yes. Checked that. It was set to US English

. said:
Doesn't ur have an encoding menu/sub menu. It winmail / OE it is on the
format menu.
Don said:
Yup, I agree. It would make it difficult!

Generally I wouldn't care. Of course because of it I see my email is
encoded incorrectly and, although it shouldn't make a difference, it
does.
I
can't figure out how to fix it. I've checked all the places I can
think
of
and find for the character encoding for Outlook, Office and Windows in
general and they are all showing US English. I even when so far as to
check
the Outlook values in the registry...as scary as that is. Still can't
find
the problem.

:

That rule (no non-Western character sets) might make it tough for
Eastern European or Asian folks to communicate in their native
language with relatives in the US.

Gary VanderMolen

Here's a copy of some of the pertinent info from a reject:

The user does not accept email in non-Western (non-Latin) character
sets.

--- Below this line is a copy of the message.
Received: (qmail 1590 invoked from network); 1 Apr 2007
19:42:36 -0000
Received: from unknown (HELO
pre-smtp04-02.prod.mesa1.secureserver.net)
([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by smtp14-02.prod.mesa1.secureserver.net (qmail-ldap-1.03)
with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: (qmail 22255 invoked from network); 1 Apr 2007
19:42:36 -0000
Received: from unknown (HELO secure.xxx.com) ([xxx.xxx.xxx.xxx])
(envelope-sender <[email protected]>)
by pre-smtp04-02.prod.mesa1.secureserver.net
(qmail-ldap-1.03)
with SMTP
for <[email protected]>; 1 Apr 2007 19:42:36 -0000
Received: from localhost (localhost [127.0.0.1])
by secure.xxx.com (Postfix) with ESMTP id 5CC1F5C06B
for <[email protected]>; Sun, 1 Apr 2007 12:42:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at xxx.com
Received: from secure.xxx.com ([127.0.0.1])
by localhost (secure.xxx.com [127.0.0.1]) (amavisd-new, port xxxxx)
with ESMTP id CB7zPfLybGTH for <[email protected]>;
Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
Received: from Partagas (adsl-xxx-xxx-xxx-xxx.dsl.lsan03.pacbell.net
[xxx.xxx.xxx.xxx
by secure.xxx.com (Postfix) with ESMTP id A53705C06A
for <[email protected]>; Sun, 1 Apr 2007 12:42:37 -0700 (PDT)
From: "Don" <[email protected]>
To: "'xxx'" <[email protected]>
Subject: xxxxxxxxxxxx
Date: Sun, 1 Apr 2007 12:42:36 -0700
MIME-Version: 1.0
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16386
Thread-Index: Acd0leZOFQiAXPX4SiiIv9XdFIE5ZQ==
Message-Id: <[email protected]>

Hope this helps. Thanks for your ideas.

- Don

:

There is no reason for messages to "bounce" just because of
using Windows-1250 encoding. Can you post one of these
bounce notices?

Gary VanderMolen

I did an upgrade from XP Pro to Vista Business. I'm still using
Outlook
2003. Everything seemed fine...at first.

After a bit I received some bounced messages because the
character
encoding
is set to windows-1250 instead of US English. Sure enough, all
my
emails are
going out with this encoding. However, every place I can find to
change that
setting shows US English.

It appears to be specific to Outlook. I installed Thunderbird
and
no
problem. I also uninstalled and reinstalled Outlook and Office
in
it's
entirety several times. I just can't find where this
windows-1250
is coming
from.

Any ideas?
Click to expand...
Click to expand...
Click to expand...
 
Back
Top