Re: Outgoing SMTP authentication

Matthias Jordan <[email protected]>:

> I have to use authenticated SMTP to post my eMail to my ISP. That's
> why I have to use serialmail with authentication.

this alone is no reason to use serialmail, a default route to your
mail ISP would suffice.  but you'd still need a patch to
qmail-remote.c, which you can get from qmail.org.  after patching
you'd specify entries like:

  # $Header: /q/control/RCS/smtproutes,v 1.1 2001/11/09 20:39:52 root Exp root $
  :mail.isp.net afhsdjsdk== asjjhjdg=

there's another patch where you add login info in some other file, but
in cleartext instead of base64.

if you _want_ to use serialmail _and_ can talk to the ISP, you can
also use port-forwarding with ssh(1) without any patching.

you'd use a script like (untested in this direction!):

  [ -f ${upstream}/new/* ] && {
      ${sucmd} \
      "ssh -akgx ${identity} -L 25555:${mailhost}:25 ${mailhost} \
      maildirserial -b -t 1209600 -- $maildir $prefix \
      tcpclient -RHl0 -- 127.0.0.1 25555 \
      serialsmtp $prefix `hostname`"
  }

this will make your smarthosts port 25 (SMTP) appear as your local
machines port 25555, which you simply connect on to blast off your
maildir.  i'm using something similar for ages, but in the reverse
direction (mail isp collects my email and forwards it to me), and it's
working perfectly.  i have authentication and an encrypted channel.
drawback (for the ISP): he has to allow ssh access, which usually
means keeping a login for you.

  clemens