Web lists-archives.com

Re: exim4 and TLS Once Again

On Mon 28 May 2018 at 15:32:44 (-0500), Martin McCormick wrote:
> 	After about two weeks of going down all sorts of rabbit holes
> and wasting tons of time, I am at a loss trying to get
> exim4 to resume the ability to send messages via the smarthost
> used by our ISP.  The real trouble here is that all one really
> knows is that something's broken.  It happens as soon as exim4
> contacts the server.  The server immediately aborts.  It's the
> ultimate "Check engine" light.  30-thousand moving parts and one
> is bad.  Go figure.
> 	It was all working fine for nearly 3 years save for a
> hiccup of some kind at the ISP's site last January but this time,
> it is on my end and I know that for sure.
> 	Connections are made using TLS on port 465.

Why do I read the attached then?

> 	Originally, what one did was to enter the user name and
> password in to a file called /etc/exim4/passwd.client as follows:
> # password file used when the local exim is authenticating to a remote
> # host as a client.
> #
> # see exim4_passwd_client(5) for more documentation
> #
> # Example:
> ### target.mail.server.example:login:password
> *.suddenlink.net:martin.m@xxxxxxxxxxxxxx:deepsecret
> The other modification was to a file called
> /etc/exim4/update-exim4.conf.conf which is a debian-specific file
> that configures the configurations hence .conf.conf.
> 	One added a couple of lines to indicate we are using the
> protocol called smtps.
> 	After that, one ran dpkg-reconfigure  exim4-config and
> selected to send mail through a smarthost and receive via
> fetchmail.
> 	It all worked until I upgraded to stretch at which point
> the smarthost began dumping the connection upon the login
> attempt.  At least that is what appears to happen.
> 	Actually, I couldn't even run the reconfigure because it
> complained about the protocol = smtps line and refused to build
> /var/lib/exim4/conf.autogenerated file.  I had to remove that
> line and then it built a dead-on-arrival conf.autogenerated file
> that still allows exim4 to deliver local mail but always gets the boot
> from the suddenlink server.

And exim's logs say …?


Attachment: sudden.png
Description: PNG image