UTF8: Cert namechecks always use a-label

[users/heiko/exim.git] / doc / doc-txt / experimental-spec.txt

diff --git a/doc/doc-txt/experimental-spec.txt b/doc/doc-txt/experimental-spec.txt
index 234bac0ab3e16503d2cb3108b3006473f33a51cc..d446f6b67716c19932c4e29cf4f85d6f5f48d231 100644 (file)
--- a/doc/doc-txt/experimental-spec.txt
+++ b/doc/doc-txt/experimental-spec.txt
@@ -1299,6 +1299,9 @@ the appendfile transport, will have utf8 name.
 Helo names sent by the smtp transport will have any utf8
 components expanded to a-label form.
 
+Any certificate name checks will be done using the a-label
+form of the name.
+
 Log lines and Received-by: header lines will aquire a "utf8"
 prefix on the protocol element, eg. utf8esmtp.
 
@@ -1318,12 +1321,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