Re: exim4 authentication in etch? - SUCCESS!
- To: debian-user@lists.debian.org
- Subject: Re: exim4 authentication in etch? - SUCCESS!
- From: Chris Davies <chris-usenet@roaima.co.uk>
- Date: Tue, 07 Oct 2008 10:57:52 +0100
- Message-id: <[🔎] 0eorr5xck1.ln2@news.roaima.co.uk>
- Reply-to: chris@roaima.co.uk
- References: <bk7ni-X6-7@gated-at.bofh.it> <bk7ni-X6-9@gated-at.bofh.it> <bk7ni-X6-11@gated-at.bofh.it> <bk7ni-X6-13@gated-at.bofh.it> <bk7ni-X6-15@gated-at.bofh.it> <bk7ni-X6-17@gated-at.bofh.it> <bk7nj-X6-19@gated-at.bofh.it> <bk7nj-X6-21@gated-at.bofh.it> <bk7ni-X6-5@gated-at.bofh.it> <bkaXX-5m3-3@gated-at.bofh.it>
Thomas H. George <lists@tomgeorge.info> wrote:
> |MAIN_TLS_ENABLE = true|
> |AUTH_CLIENT_ALLOW_NOTLS_PASSWORDS=yes|
Chris Davies <chris-usenet@roaima.co.uk>:
> What you've done there is to enable TLS (encryption), but then
> immediately say that you're happy not to use encryption to protect
> your username/password combination.
s. keeling <keeling@nucleus.com> wrote:
> So, the answer is to avoid providers who require this? Or is there
> any alternative action he could employ?
Fair question. Re-reading the exim4 configuration code again, I can see
that MAIN_TLS_ENABLE is required. (Without it, it seems that none of
the certificate configuration settings is included.) I forgot to mention
this in my original suggestion because I've had it enabled for so long
I'm still puzzled why the OP needs the AUTH_CLIENT_ALLOW_NOTLS_PASSWORDS
setting, which I also have mis-represented above. For correction, it
allows inbound client connections to one's own server to use passwords
without TLS encryption.
Chris
Reply to: