On Wed, 8 Jul 2009 12:41:38 +0200 Axel Luttgens <AxelLuttgens@swing.be> wrote:
Le 8 juil. 09 à 12:04, Nikita Koshikov a écrit :
Hello list,
I have noticed that sieve vacation action breaks some non-english
letters in the subject. I tested with russian language, if subject contains letters from
specific diapason russian alphabet, the message received with
unreadable subject, but text in the body with the same letters looks
ok. Here is example of full subject header, it contains russian alphabet: Subject: абвгде�?жзийклмноп�?�?�?�?�?�? �?�?�?�?�?�?�?�?�?�?Maybe this headers will be usefull: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit
.dovecot.sieve file looks correct, here is it: require ["vacation"]; # rule:[test] if anyof (true) { vacation :days 1 :addresses ["user@domain.com"] :subject
"абвгдеёжзийклмнопрстуфхцчшщъыьэюя"
text: Тестовое русское сообщение(Test russian
message). ; }I'm running dovecot-1.1.16 with dovecot-sieve-1.1.6 and
managesieve-0.10.6.Please tell, is it possible to fix this ?
I don't know whether dovecot-sieve is supposed to do the conversion
automatically, but it is sure that an RFC822 header MUST be in US- ASCII (so as to be 7bit-clean).The required encodings are described in: http://www.rfc-editor.org/rfc/rfc2047.txt For example, a subject header with the french word "Résistance" could
be encoded as: Subject: =?iso-8859-1?Q?R=E9sistance?=Could you try by inserting the encoded subject line directly in the
config file and see what gives?
This made a trick, I have tried variant with =?UTF-8?B? - that worked for me, but this is not "user way". I think, the best way will be to exlain my users not to put non-english characters in the subject.
On the other hand, perhaps does sieve provide the needed tools itself;
someone?Axel
Thanks everyone for replies.