Le 2 sept. 2015 à 17:03, Sergey Schwartz a écrit :
Guys,
I'm completely stuck, so asking for advice. My user has a sieve script which checks message header if it contains words in russian like 'Лист бронирования отправлен'.
Pritty simple script
# rule:[Отправлено] if allof (header :contains "subject" "LDS (robot): Лист бронирования отправлен", header :contains "from" "noreply@bgoperator.com") { fileinto "Отправлено"; }
I don't have errors compiling the script or executing it via LMTP, but it doesn't work. Normally user receives messages from robot with subject encoded as quoted-printable
Subject: =?UTF-8?Q?LDS_(robot):_=D0=9B=D0=B8=D1=81=D1=82?= =?UTF-8?Q?_=D0=B1=D1=80=D0=BE=D0=BD=D0=B8=D1=80=D0=BE=D0=B2=D0=B0=D0=BD?= =?UTF-8?Q?=D0=B8=D1=8F__=D0=BE=D1=82=D0=BF=D1=80=D0=B0=D0=B2=D0=BB=D0=B5?=
When I send a test message via Thunderbird with required words - sieve works fine and subject is encoded in base64
Subject: =?UTF-8?B?0JvQuNGB0YIg0LHRgNC+0L3QuNGA0L7QstCw0L3QuNGPINC+0YLQv9GA?= =?UTF-8?B?0LDQstC70LXQvQ==?=
It is the same text, but encodind is different - base 64 works fine and quoted-printable does not. Is it possible to have both supported for sieve ?
Hello Sergey,
IIRC, many enhancements have been brought to dovecot/sieve handling of encodings over the consecutive past releases. What version are you running?
Axel