From 10ffbe0cb86742445d8eb763d125fde20622fcf4 Mon Sep 17 00:00:00 2001 From: Matthew Flatt Date: Mon, 19 Mar 2007 22:07:33 +0000 Subject: [PATCH] doc clarification on TLS and SSH for SMTP svn: r5796 --- collects/net/doc.txt | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/collects/net/doc.txt b/collects/net/doc.txt index a49f403aa5..d5f51a99a8 100644 --- a/collects/net/doc.txt +++ b/collects/net/doc.txt @@ -554,7 +554,7 @@ PROCEDURES ----------------------------------------------------------- server via SSL. If the optional #:tls-encode keyword argument supplies a procedure - instead of #f, then the ESMTP STARTTLS protocol is used to request + instead of #f, then the ESMTP STARTTLS protocol is used to initiate SSL communication with the server. The procedure given as the #:tls-encode argument should be like `ports->ssl-ports' from `(lib "mzssl.ss" "openssl")'; it will be called as @@ -562,7 +562,12 @@ PROCEDURES ----------------------------------------------------------- (encode r w #:mode 'connect #:encrypt 'tls #:close-original? #t) and it should return two values: an input port and an export port. - All further SMTP communication uses the returned ports. + All further SMTP communication uses the returned ports. + + For encrypted communication, normally either `ssl-connect' should be + supplied for #:tcp-connect, or `ports->ssl-ports' should be supplied + for #:tls-encode --- one or the other (depending on what the server + expects), rather than both. See the "head.ss" library for utilities that construct a message headers and validate mail address strings.