I use Postfix 2.0.10 with TLS patch, cyrus-imapd 2.1.13, sasl 2.1.13
The problem is as follow:
When a message with russian charset characters (KOI8-R, WIN1251) in Subject
field arrives or is moved into the Sent Items folders by Outlook Express,
each russian character is replaced by an X (ex: Re:
On Thu, 5 Jun 2003, NOwlar wrote:
I dumped mailboxes with cyrdump, the Xes are in.
What can be wrog?
I will appreciate any help.
The sending client included raw 8-bit data in the headers, which is not
allowed.
Cyrus dealt with this problem by munging the header to be valid. You can
set
NOwlar wrote:
I use Postfix 2.0.10 with TLS patch, cyrus-imapd 2.1.13, sasl 2.1.13
The problem is as follow:
When a message with russian charset characters (KOI8-R, WIN1251) in Subject
field arrives or is moved into the Sent Items folders by Outlook Express,
each russian character is replaced by
NOwlar wrote:
I use Postfix 2.0.10 with TLS patch, cyrus-imapd 2.1.13, sasl 2.1.13
The problem is as follow:
When a message with russian charset characters (KOI8-R, WIN1251) in Subject
field arrives or is moved into the Sent Items folders by Outlook Express,
each russian character is replaced by
On Thu, Jun 05, 2003 at 08:57:38PM +0400, NOwlar wrote:
I use Postfix 2.0.10 with TLS patch, cyrus-imapd 2.1.13, sasl 2.1.13
The problem is as follow:
When a message with russian charset characters (KOI8-R, WIN1251) in Subject
field arrives or is moved into the Sent Items folders by Outlook
Einar Indridason wrote:
On Thu, Jun 05, 2003 at 08:57:38PM +0400, NOwlar wrote:
I use Postfix 2.0.10 with TLS patch, cyrus-imapd 2.1.13, sasl 2.1.13
The problem is as follow:
When a message with russian charset characters (KOI8-R, WIN1251) in Subject
field arrives or is moved into the Sent
On Fri, 6 Jun 2003, Einar Indridason wrote:
In my opinion, this breaks the Be liberal in what you accept, strict in
what you send.
Actually, munging the data to Xs *is* being liberal in what is accepted
and strict in what is sent.
Since 8-bit characters in headers are nonsensical (there's no
