On Wed, 23 Feb 2000 08:16:57 -0500 Bruce Bowler wrote:
> user@??? <user@???> D=uservacation
> T=uservacation: Expansion of "${if def:h_Subject: {Autoreply:
> $h_Subject:} {Automatic reply to your message}}" in
> uservacation transport contains non-printing characters
> Here's the transport...
> uservacation:
> driver = autoreply
> user = ${local_part}
> once = ${home}/vacation
> file = ${home}/vacation.txt
> log = ${home}/vacation.log
> once_repeat = 7d
> to = "${sender_address}"
> subject = "${if def:h_Subject: {Autoreply: $h_Subject:} {Automatic
> reply to your message}}"
> Folks who didn't have a vacation message set didn't have any problems
> receiving the message, the folks who did have vacation messages set had the
> transport successfully used for other messages. From that, I conclude that
> there must have been something in the subject of the inbound message that
> "caused the problem".
> It does look like there might be a carriage return embedded in the subject.
> How can I get exim to "not care" about the non-printing character in the
> macro expansion?
> Bruce
Mmmhhh.... I also had this problem. Basically, you need
print_topbitchars = true
in the first part of the configure file, and then
subject = "Vacation-reply: ${escape:${length_50:$header_subject:}}"
The problem I had was that some MTAs inserted <CR> when the subject
header was too long (ie > 80 chars), or something similar. Since
I introduced this I no longer had any problems.
Regards,
Bernard Stern, SWITCH
____________S_W_I_T_CH___Swiss Academic_______________________________________
mail: SWITCH Head Office a Tel: +41 1 268 1520
Limmatquai 138 n Fax: +41 1 268 1568
CH-8001 Zurich d e-mail: stern@???
________________________________________Reseach Network_______________________
