SF.net SVN: tmda: [2144] trunk/tmda/contrib

Revision: 2144
          http://svn.sourceforge.net/tmda/?rev=2144&view=rev
Author:   srwarren
Date:     2007-02-18 21:10:50 -0800 (Sun, 18 Feb 2007)

Log Message:
-----------
contrib: Add Amitai Schlair's simpler example of how to use TLS with tmda-ofmipd

Modified Paths:
--------------
    trunk/tmda/contrib/ChangeLog
    trunk/tmda/contrib/ofmipd-stunnel-xinetd/README.txt

Added Paths:
-----------
    trunk/tmda/contrib/ofmipd-stunnel-daemons/
    trunk/tmda/contrib/ofmipd-stunnel-daemons/README.txt
    trunk/tmda/contrib/ofmipd-stunnel-daemons/stunnel.conf

Modified: trunk/tmda/contrib/ChangeLog
===================================================================
--- trunk/tmda/contrib/ChangeLog	2007-02-08 17:41:59 UTC (rev 2143)
+++ trunk/tmda/contrib/ChangeLog	2007-02-19 05:10:50 UTC (rev 2144)
@@ -1,3 +1,16 @@
+2007-02-18  Stephen Warren  <[email protected]>
+
+	* Added ofmipd-stunnel-daemons directory, which contains an example
+	stunnel.conf from Amitai Schlair. This shows the simple way of
+	providing TLS connections to tmda-ofmipd
+
+2006-09-27  Stephen Warren  <[email protected]>
+
+	* Added ofmipd-stunnel-xinetd directory, which contains example
+	xinetd and stunnel config files. These demonstrate how to use
+	tmda-ofmipd's new "one-session" mode in conjunction with stunnel,
+	to provide TLS connections to tmda-ofmipd.
+
 2004-04-03  Bob Rogers  <[email protected]>
 
         * tmda.el (tmda-pending-buffer-kill):  FSF emacs `=' expects 2 args.

Added: trunk/tmda/contrib/ofmipd-stunnel-daemons/README.txt
===================================================================
--- trunk/tmda/contrib/ofmipd-stunnel-daemons/README.txt	                        (rev 0)
+++ trunk/tmda/contrib/ofmipd-stunnel-daemons/README.txt	2007-02-19 05:10:50 UTC (rev 2144)
@@ -0,0 +1,16 @@
+The files in this directory show how to run a daemonized stunnel to provide
+TLS encrypted connections to a daemonized tmda-ofmipd.
+
+NOTE: One issue with this approach is that tmda-ofmipd sees all connections as
+originating from the machine where stunnel is running, typically localhost.
+This may or may-not be an issue for you. Note that this client IP address is
+added into the email headers by tmda-ofmipd.
+
+It is assumed that tmda-ofmipd is already running as a daemon.
+
+The files are:
+
+stunnel.conf:
+  Add the content of this file to your existing stunnel.conf, and start,
+  or restart, the stunnel daemon.
+

Added: trunk/tmda/contrib/ofmipd-stunnel-daemons/stunnel.conf
===================================================================
--- trunk/tmda/contrib/ofmipd-stunnel-daemons/stunnel.conf	                        (rev 0)
+++ trunk/tmda/contrib/ofmipd-stunnel-daemons/stunnel.conf	2007-02-19 05:10:50 UTC (rev 2144)
@@ -0,0 +1,8 @@
+[submission]
+    # Port number to listen on
+    accept = submission
+    # Where to proxy the connections to; tmda-ofmip daemon should listen here
+    connect = localhost:8025
+    # Tell stunnel what protocol to talk, since it's an application proxy
+    protocol = smtp
+

Modified: trunk/tmda/contrib/ofmipd-stunnel-xinetd/README.txt
===================================================================
--- trunk/tmda/contrib/ofmipd-stunnel-xinetd/README.txt	2007-02-08 17:41:59 UTC (rev 2143)
+++ trunk/tmda/contrib/ofmipd-stunnel-xinetd/README.txt	2007-02-19 05:10:50 UTC (rev 2144)
@@ -1,6 +1,17 @@
 The files in this directory show how to run tmda-ofmipd from xinet.d, using
 stunnel to provide TLS encryption.
 
+NOTE: This method runs a separate instance of stunnel and tmda-ofmipd for each
+incoming TLS connection. This allows tmda-ofmipd to see the true IP address of
+the connecting client. With a typical daemonized stunnel, tmda-ofmipd will
+only see connections from localhost (or wherever stunnel is running).
+
+Note 2: One could probably still run stunnel in daemonized mode, and spawn a
+new tmda-ofmipd instance for each incoming connection, thus removing the need
+to use xinetd. I personally didn't do this, because I already run a bunch of
+servers under xinetd, so doing it this way was consistent. xinetd may provide
+you useful features too.
+
 The same general principles (i.e. tmda-ofmipd "one-session" mode) should allow
 running tmda-ofmipd under DJB's tcpserver. A previous version of this patch
 was developed for this situation, so it should work fine.


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.