On Mon, 21 Nov 2005, Clive McDowell wrote:
> are there any known problems with the autoresponder if there are
> non-english characters in the subject header? I've just seen the
> failure -
By "non-english" I presume you really mean "non-ASCII", that is
byte values not in the range 32-127 (or tab, which is also allowed).
You can make characters 128-255 valid by setting
print_topbitchars = true
in your Exim configuration. However, you are then generating messages
that do not strictly conform to the standards.
> Expansion of "${if def:h_Subject: {Autoreply: $h_Subject:} {Auto-response}}" in uservacation
> transport contains non-printing character 207
>
> The actual subject header was -
>
> Subject: =?iso-8859-7?Q?FW=3A_=CF=E9_=E1=EB=EB=E1=E3=DD=F2_=F3=F4=E7_=E8?==?iso-8859-7?Q?=E7=F4=E5=DF=E1?=
>
> There appears to be a double '=' character in there so I think this is due to a broken client.
Not necessarily. You are allowed to have multiple "encoded words" in
succession. Indeed, you have to if the text is long enough.
Instead of
Autoreply: $h_Subject:
try
Autoreply: ${rfc2047:$h_Subject:}
This will ensure that the text is re-encoded if necessary.
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
Get the Exim 4 book: http://www.uit.co.uk/exim-book
