Hi,
as the reason string of a vacation command in SIEVE is considered to be in
UTF-8 in absence of the :mime Parameter (see the Internet Draft) wouldn't it
be correct, to set the MIME-Version and Content-Type Headers accordingly,
when sending then vacation response?
The attached diff was made
Ralf Haferkamp wrote:
Hi,
as the reason string of a vacation command in SIEVE is considered to be in
UTF-8 in absence of the :mime Parameter (see the Internet Draft) wouldn't it
be correct, to set the MIME-Version and Content-Type Headers accordingly,
when sending then vacation
On Thu, Feb 27, 2003 at 11:51:13AM -0500, Ken Murchison wrote:
Ralf Haferkamp wrote:
Hi,
as the reason string of a vacation command in SIEVE is considered to be in
UTF-8 in absence of the :mime Parameter (see the Internet Draft) wouldn't it
be correct, to set the MIME-Version
Ralf Haferkamp wrote:
On Thu, Feb 27, 2003 at 11:51:13AM -0500, Ken Murchison wrote:
Ralf Haferkamp wrote:
Hi,
as the reason string of a vacation command in SIEVE is considered to be in
UTF-8 in absence of the :mime Parameter (see the Internet Draft) wouldn't it
be
Hi,
I have posted an almost identical patch as part of a suggested fix for
[Bug 1723] Sieve notifications containing UTF-8 are not MIME encoded
though no one seems to be doing anything with it. I added a check to
see if the reason contained 8bit and added the headers in only that case.
I saw no
