diff options
Diffstat (limited to 'README.remote-auth')
| -rw-r--r-- | README.remote-auth | 31 |
1 files changed, 31 insertions, 0 deletions
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 @@ | |||
| 1 | Docs for http://www.qmail.org/qmail-remote_authenticated_smtp.patch | ||
| 2 | a patch to convince qmail-remote to use Authenticated SMTP when | ||
| 3 | talking to certain hosts. | ||
| 4 | |||
| 5 | This version of the patch has been modified by Robert Sanders so that | ||
| 6 | base64 encoding of usernames and passwords is done automatically by | ||
| 7 | qmail-remote. | ||
| 8 | |||
| 9 | After applying the patch, the username password go into | ||
| 10 | /var/qmail/control/smtproutes like so: | ||
| 11 | |||
| 12 | domain:relay username password | ||
| 13 | |||
| 14 | The domain:relay part is identical to a normal smtproutes entry (see | ||
| 15 | the qmail-remote man page). For sites that require authentication, you | ||
| 16 | simply add two space separated fields to the line, where the first | ||
| 17 | field is the username, the second is the password. For example: | ||
| 18 | |||
| 19 | inside.af.mil:firewall.af.mil:26 johndoe secret | ||
| 20 | |||
| 21 | would send mail for inside.af.mil to firewall.af.mil, port 26 using | ||
| 22 | username 'johndoe' and password 'secret' | ||
| 23 | |||
| 24 | Since smtproutes will contain plain text usernames and passwords | ||
| 25 | you might want to make the file owned by qmailr and set its permissions | ||
| 26 | to 0600. Of course, the entries are going to go over the wire in the clear | ||
| 27 | anyway as part of the SMTP transaction. | ||
| 28 | |||
| 29 | Good luck. | ||
| 30 | |||
| 31 | j. | ||
