From 8c44ad5f0f640f0243e23e6e26324b920c5901f0 Mon Sep 17 00:00:00 2001 From: Tony Finch Date: Mon, 24 Jul 2006 11:55:15 +0000 Subject: [PATCH] note a caveat about print_topbitchars --- doc/doc-docbook/spec.xfpt | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/doc/doc-docbook/spec.xfpt b/doc/doc-docbook/spec.xfpt index 1f03f30ea..e778e5181 100644 --- a/doc/doc-docbook/spec.xfpt +++ b/doc/doc-docbook/spec.xfpt @@ -1,4 +1,4 @@ -. $Cambridge: exim/doc/doc-docbook/spec.xfpt,v 1.9 2006/07/21 16:48:42 jetmore Exp $ +. $Cambridge: exim/doc/doc-docbook/spec.xfpt,v 1.10 2006/07/24 11:55:15 fanf2 Exp $ . . ///////////////////////////////////////////////////////////////////////////// . This is the primary source of the Exim Manual. It is an xfpt document that is @@ -13441,6 +13441,13 @@ sequences, primarily to avoid messing up the layout. If &%print_topbitchars%& is set, code values of 128 and above are also considered to be printing characters. +This option also affects the header syntax checks performed by the +&(autoreply)& transport, and whether Exim uses RFC 2047 encoding of +the user's full name when constructing From: and Sender: addresses (as +described in section &<>&). Setting this option can cause +Exim to generate eight bit message headers that do not conform to the +standards. + .option process_log_path main string unset .cindex "process log path" -- 2.30.2