From 8514473287c9594137c6fbc39f5619672ebc2430 Mon Sep 17 00:00:00 2001 From: manuel Date: Mon, 4 Feb 2013 02:32:40 +0100 Subject: [PATCH] qregex-starttls-2way-auth-20060423-mm --- README.remote-auth | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) create mode 100644 README.remote-auth (limited to 'README.remote-auth') diff --git a/README.remote-auth b/README.remote-auth new file mode 100644 index 0000000..ab91f23 --- /dev/null +++ b/README.remote-auth @@ -0,0 +1,31 @@ +Docs for http://www.qmail.org/qmail-remote_authenticated_smtp.patch +a patch to convince qmail-remote to use Authenticated SMTP when +talking to certain hosts. + +This version of the patch has been modified by Robert Sanders so that +base64 encoding of usernames and passwords is done automatically by +qmail-remote. + +After applying the patch, the username password go into +/var/qmail/control/smtproutes like so: + +domain:relay username password + +The domain:relay part is identical to a normal smtproutes entry (see +the qmail-remote man page). For sites that require authentication, you +simply add two space separated fields to the line, where the first +field is the username, the second is the password. For example: + +inside.af.mil:firewall.af.mil:26 johndoe secret + +would send mail for inside.af.mil to firewall.af.mil, port 26 using +username 'johndoe' and password 'secret' + +Since smtproutes will contain plain text usernames and passwords +you might want to make the file owned by qmailr and set its permissions +to 0600. Of course, the entries are going to go over the wire in the clear +anyway as part of the SMTP transaction. + +Good luck. + +j. -- cgit v1.2.3