Bug#346260: exim4: autoreply problem with $reply_address and non-7bit chars

[Andreas Metzler]

On 2006-01-07 Andreas Metzler <ametzler at downhill.at.eu.org> wrote:
> On 2006-01-06 Andreas Edler <e0601 at han.sserv.de> wrote:
>> Package: exim4
>> Version: 4.50-8
>> Severity: normal

>> With the vacation_transport shown below a sender gets an error message
>> stating:

>>  Expansion of "${reply_address}" in vacation_transport transport
>>  contains non-printing character 195

>> An example from line of a mail on which occurs this error is:

>>  From: =?iso-8859-1?Q?Florian_Mei=DFner?= <email at address.removed>
[...]
>>  to = "${reply_address}"
>>  user = mail
> [...]

> Hello,
> I suspect exim4 does rfc2047-decoding. However I don't think it should
> do that for ${reply_address}, but only for $h_ expansions, afaict from
> the documentation.

Just for reference this is going to be fixed in 4.61:

PH/04 Changed $reply_address to use the raw form of the headers instead of the
      decoded form, because it is most often used to construct To: headers
      lines in autoreplies, and the decoded form may well be syntactically
      invalid. However, $reply_address has leading white space removed, and all
      newlines turned into spaces so that the autoreply transport does not
      grumble.

cu andreas
-- 
The 'Galactic Cleaning' policy undertaken by Emperor Zhark is a personal
vision of the emperor's, and its inclusion in this work does not constitute
tacit approval by the author or the publisher for any such projects,
howsoever undertaken.                                (c) Jasper Ffforde