From: markus schnalke <meillo@marmaro.de>
  To  : <masqmail@marmaro.de>
  Date: Fri, 16 Jul 2010 00:14:55 +0200

Re: [masqmail] Plans for a 0.3 dev branch

[2010-07-15 18:24] =?UTF-8?B?QWxiZXJ0byBHb256w6FsZXogUGFsb21v?= <alberto@matracas.org>
> markus schnalke wrote: (08/07/10 11:04)
> > [2010-05-31 00:15] Alberto González Palomo<alberto@matracas.org>
> >[...]
> >>         Looking at masqmail's configuration files I see the old "get.*",
> >> the "connect route.*" entries (22 of them, for different places) and
> >> the online file="/tmp/connect route"
> >>         In the route file I use now I have auth name, auth login,
> >> auth secret, do correct helo, and wrapper (for openssl).
> >
> > Could you send me your route file (with private data removed)? I'm
> > especially interested in the wrapper stuff.
> 
>        The route file where I use the wrapper is as follows:
> ------------------------------------------------------------
> auth name = "login"
> auth login = "*****"
> auth secret = "*****"
> do correct helo = yes
> wrapper="/usr/bin/openssl s client -quiet -connect example.com:465 
> 2>/dev/null"
> ------------------------------------------------------------
>        Login and password replaced by "*****", and remote machine by
> "example.com".
>        Everything else is copied exactly.

Thanks. In the meanwhile, I became more familiar with the openssl
stuff and came to a similar solution on my own. You confirmed me.


> >>         In the others I have mail host, map return path addresses,
> >> last route, and expand h sender domain.
> >
> > Could you please explain in what way you need last route?
> 
>        I don't know why I put it there. This is only in one of the
> routes, used very rarely. It sent the e-mails through an SSH tunnel
> into an intranet.
>        I guess I just wanted to make sure that those e-mails were sent
> either through the tunnel or not at all.

Okay, that's sounds reasonable.


Thanks.


meillo