Re: Lite SMTP server/daemon
- To: Celejar <firstname.lastname@example.org>
- Cc: debian-user <email@example.com>
- Subject: Re: Lite SMTP server/daemon
- From: Steve Kemp <firstname.lastname@example.org>
- Date: Tue, 08 May 2018 13:22:07 +0000
- Message-id: <[🔎] email@example.com>
- In-reply-to: <firstname.lastname@example.org>
- References: <4BD1E3C5.23069.11D86AA@export.hope.cz> <4BD2B938.email@example.com> <firstname.lastname@example.org> <4BD56156.3715.912CDB@export.hope.cz> <email@example.com> <firstname.lastname@example.org> <20100430221011.GA1567@steve.org.uk> <email@example.com>
> > qpsmtpd? It is small, plugin-based, and also written in Perl.
> I couldn't discern, BTW, whether it supports TLS / SSL to an
> upstream MTA? I did find this thread:
That thread, I think, is about presenting TLS to the clients
who submit mail - rather than piping from the proxy itself to
the upstream/"real" server.
When I've used qpsmtpd in the past I used the `exim-bsmtp` process
to talk to exim4 on the local-system. That didn't involve using
TLS, just a pipe.
The "smtp-forward" plugin doesn't seem to support TLS either, for
what that's worth.
Generally I'd assume:
internet -> qpsmtpd -> [exim|postfix|whatever on the local host]
So the lack of TLS on the final hop hasn't been a concern to me
personally. I can appreciate others might disagree.