[exim-cvs] UTF8: docs update. Bug 1516

Top Page
Delete this message
Reply to this message
Author: Exim Git Commits Mailing List
Date:  
To: exim-cvs
Subject: [exim-cvs] UTF8: docs update. Bug 1516
Gitweb: http://git.exim.org/exim.git/commitdiff/9479146eba39483724dc791ad814efe829def406
Commit:     9479146eba39483724dc791ad814efe829def406
Parent:     0ec7e94825af4ec45b9ab92f9a2d22cf59952600
Author:     Jeremy Harris <jgh146exb@???>
AuthorDate: Wed Apr 22 13:31:47 2015 +0100
Committer:  Jeremy Harris <jgh146exb@???>
CommitDate: Wed Apr 22 13:31:47 2015 +0100


    UTF8: docs update.  Bug 1516
---
 doc/doc-txt/experimental-spec.txt |   17 +++++++++++++----
 1 files changed, 13 insertions(+), 4 deletions(-)


diff --git a/doc/doc-txt/experimental-spec.txt b/doc/doc-txt/experimental-spec.txt
index 234bac0..f0490b0 100644
--- a/doc/doc-txt/experimental-spec.txt
+++ b/doc/doc-txt/experimental-spec.txt
@@ -1318,12 +1318,21 @@ by "control = utf8_downconvert/0". The value "-1"
may also be used, to use a-label for only if the
destination host does not support SMTPUTF8.

+If mua_wrapper is set, the utf8_downconvert control
+defaults to -1 (convert if needed).
+
+
+There is no explicit support for VRFY and EXPN.
+Configurations supporting these should inspect
+$smtp_command_argument for an SMTPUTF8 argument.
+
+There is no support for LMTP on Unix sockets.
+Using the "lmtp" protocol option on an smtp transport,
+for LMTP over TCP, should work as expected.
+
Known issues:
- - Currently LMTP is not supported.
- DSN unitext handling is not present
- - no provision for converting logging from UTF-8
- - VRFY and EXPN not handled
- - mua_wrapper not handled
+ - no provision for converting logging from or to UTF-8

--------------------------------------------------------------
End of file