Re: exim4 and TLS Once Again

2018-06-03 Thread Martin McCormick
The problem (actually 2 problems) are solved. The one I was actually posting about turned out to be that I had put a line which says protocol = smtps in the wrong place in a file named /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smarthost This caused dpkg-re

Re: exim4 and TLS Once Again

2018-06-02 Thread Brian
On Fri 01 Jun 2018 at 17:18:39 +0100, Brian wrote: > TLS, so the remote server sees no point in going any further. > > Create /etc/exim4/conf.d/main/00_my_custom_macros and in it put > > TLS_ON_CONNECT = true > > To the end of > /etc/exim4/conf.d/transport/30_exim4-config_remote_smtp_smartho

Re: exim4 and TLS Once Again

2018-06-01 Thread Brian
On Tue 29 May 2018 at 12:00:20 -0500, David Wright wrote: > On Mon 28 May 2018 at 21:26:59 (-0500), Martin McCormick wrote: > > > > David Wright writes: > > > And exim's logs say …? > > > > 2018-05-28 14:56:38 1fNL0J-0003CQ-70 H=smtp.suddenlink.net [208.180.40.68]: > > Remote host closed conne

Re: exim4 and TLS Once Again

2018-06-01 Thread Brian
On Wed 30 May 2018 at 20:58:12 -0400, Michael Stone wrote: > On Wed, May 30, 2018 at 06:22:49PM -0500, David Wright wrote: > > AIUI 587 is the standard email submission port and 465 is now > > deprecated but often still in use. I think they differ in the > > details of how they handle encrypting t

Re: exim4 and TLS Once Again

2018-05-30 Thread Michael Stone
On Wed, May 30, 2018 at 06:22:49PM -0500, David Wright wrote: AIUI 587 is the standard email submission port and 465 is now deprecated but often still in use. I think they differ in the details of how they handle encrypting the session. From a protocol standpoint 587/tcp is identical to 25/tcp,

Re: exim4 and TLS Once Again

2018-05-30 Thread David Wright
On Tue 29 May 2018 at 12:25:03 (-0500), Martin McCormick wrote: > > David Wright writes: > > My previous post posed two posers. Port? > > It is supposed to be port 465. That's what the > conf.autogenerated file showed it should be but it could be doing > something contrary like port 25-- anythi

Re: exim4 and TLS Once Again

2018-05-29 Thread Martin McCormick
David Wright writes: > My previous post posed two posers. Port? It is supposed to be port 465. That's what the conf.autogenerated file showed it should be but it could be doing something contrary like port 25-- anything but the right one. I have joined the exim-users mailing list as o

Re: exim4 and TLS Once Again

2018-05-29 Thread David Wright
On Mon 28 May 2018 at 21:26:59 (-0500), Martin McCormick wrote: > > David Wright writes: > > And exim's logs say …? > > 2018-05-28 14:56:38 1fNL0J-0003CQ-70 H=smtp.suddenlink.net [208.180.40.68]: > Remote host closed connection in response to initial connection > 2018-05-28 14:56:38 1fNL0J-0003

Re: exim4 and TLS Once Again

2018-05-28 Thread Martin McCormick
David Wright writes: > And exim's logs say …? 2018-05-28 14:56:38 1fNL0J-0003CQ-70 H=smtp.suddenlink.net [208.180.40.68]: Remote host closed connection in response to initial connection 2018-05-28 14:56:38 1fNL0J-0003CQ-70 == mar...@okstate.edu R=smarthost T=remote_smtp_smarthost defer (-18

Re: exim4 and TLS Once Again

2018-05-28 Thread David Wright
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 her

exim4 and TLS Once Again

2018-05-28 Thread Martin McCormick
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