suzanne.soy/racket
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

doc clarification on TLS and SSH for SMTP

Browse Source 
svn: r5796
This commit is contained in:
Matthew Flatt 2007-03-19 22:07:33 +00:00
parent 32c07dbaca
commit 10ffbe0cb8
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
collects/net/doc.txt
View File

@ -554,7 +554,7 @@ PROCEDURES -----------------------------------------------------------
server via SSL. server via SSL.
If the optional #:tls-encode keyword argument supplies a procedure 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 SSL communication with the server. The procedure given as the
#:tls-encode argument should be like `ports->ssl-ports' from `(lib #:tls-encode argument should be like `ports->ssl-ports' from `(lib
"mzssl.ss" "openssl")'; it will be called as "mzssl.ss" "openssl")'; it will be called as
@ -564,6 +564,11 @@ PROCEDURES -----------------------------------------------------------
and it should return two values: an input port and an export port. 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 See the "head.ss" library for utilities that construct a message
headers and validate mail address strings. headers and validate mail address strings.