"Jason R. Mastaler" <[EMAIL PROTECTED]> writes: > I'd just use /etc/tofmipd+CRAM-MD5, or setup some SSH port-forwarding > between the MUA and tmda-ofmipd.
I've been playing with ssh port forwarding a bit, using a setup like the following: $ tmda-ofmipd -p localhost:8525 -R apop://acl.lanl.gov $ ssh -N -n -f -g -x -L 8025:localhost:8525 localhost tmda-ofmipd is running on localhost:8525. The ssh command forwards localhost:8025 to localhost:8525. The `-g' option allows external hosts to connect to port 8025. Now, clients can set their MUAs to connect to your.server.dom:8025, and the connection will securely be forwarded to tmda-ofmipd. As long as you choose an authentication method for tmda-ofmipd which doesn't transmit passwords in the clear (e.g, apop, imaps, /etc/tofmipd), the whole transaction should be protected, even when using PLAIN or LOGIN style SMTP authentication. _________________________________________________ tmda-workers mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-workers
