Roland Rosenfeld wrote:
Hi!
I noticed the following problem in dovecot-1.2-sieve-0.1.14:
The following vacation causes trouble with the Subject line:
if not exists ["List-Id", "List-Post"] {
vacation :days 7 :addresses ["t...@netcologne.de"] :subject "=?utf-8?b?w4TDlsOc?= sadasd" "Bin gerade nicht hier.";
}
As you can see, the Subject is already MIME encoded according to
RFC2047.
Starting with sieve 0.1.14 the subject is now encoded by sieve again,
so I get the following in my vacation mail:
Subject: =?utf-8?q?=3D=3Futf-8=3Fb=3Fw4TDlsOc=3F=3D?= sadasd
As you can see, the RFC2047 encoding is RFC2047 encoded, which results
in an unreadable subject.
According to RFC5230 section 4.3 this shouldn't happen:
The ":subject" parameter specifies a subject line to attach to any
vacation response that is generated. UTF-8 characters can be used in
the string argument; implementations MUST convert the string to
[RFC2047] encoded words if and only if non-ASCII characters are
present. Implementations MUST generate an appropriate default
subject line as specified below if no :subject parameter is
specified.
If I understand this right, sieve should do the RFC2047 encoding only
if the string is non-ASCII. But the RFC2047 encoded string is already
ASCII, so it should not be encoded a second time.
Fixed:
http://hg.rename-it.nl/dovecot-1.2-sieve/rev/219a6f0d6bf6
Regards,
Stephan.
