This is a multi-part message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
Hello all :)
in regarding to this very old message i found at my websearch, i got the
same problem now.
i use an autoresponder-router and transport
routing is fine, now the transport fails while reading subject from
databasefield because of 'unprintable character 10'
ok, i wrote my own form to update database, and strip all \n \r and html
tags and some 'special characters' from the autoresponder-subject
but always fail with the same error.
some links on the net say character 10 is \n, but \n is already
stripped from the subject......
i think this problem is not in exim, because buglet is about 6 years
old... but any needful hints would be very nice 8---)
many thanks in advance
volker
attached message:
_______
-
[EXIM] autoreply: newlines in text cause it to bomb. Help.
-
On Tue, 17 Nov 1998, Mark Buckaway wrote:
-
->/ I've created a DB file via perl for Exim to read for the autoreply
transport.
/->/ However, there seems to be some unprintable character in the text that
/->/ exim does not like. The "unprintable" character appears to be a
newline.
/-
-That appears to be a buglet. Exim tests for non-printing characters in
-the various autoreply options, but it looks as though it is being
-stricter than it need be. I will investigate in due course. Thanks for
-the report.
-
-
-Philip Hazel University of Cambridge Computing Service,
____
--
