Implemented, but bug in openssl call somewhere.

[lambdamail.git] / README

diff --git a/README b/README
index 3521943..3c04fd7 100644 (file)
--- a/README
+++ b/README
@@ -5,22 +5,19 @@ This is an _extremely simple_ SMTP server designed specifically for
 running on personal servers with a very small number (~1) users.  It
 is probably best defined in terms of what it does not support:
 
-- It does not (yet?) support TLS connections.
 - It does not relay messages between remote addresses.
 - It does not spawn threads to allow simultaneous inbound connections.
 - It does not respond with honest errors on failed deliveries.
 
-Apart from the lack of TLS, I consider these features.  There's no
-(obvious) way for LambdaMail to become a source of spam, the lack
-of multithreaded operation is a built-in rate limiter (not to mention
-its side effect of making all delivery operations "atomic"), and
-its penchant for just responding "250 OK" to almost everything means
-that it doesn't leak information about users on the system.
+I consider these features.  There's no (obvious) way for LambdaMail to
+become a source of spam, the lack of multithreaded operation is a
+built-in rate limiter (not to mention its side effect of making all
+delivery operations "atomic"), and its penchant for just responding
+"250 OK" to almost everything means that it doesn't leak information
+about users on the system.
 
-LambdaMail is still under active development and, given that it was
-written for a single use case, lacks any documentation.  However
-it's a pretty simple Scheme program, so glancing over the code should
-suffice.
+LambdaMail lacks any documentation.  However it's a pretty simple
+Scheme program, so glancing over the code should suffice.
 
 License
 -------