Author: Jeremy Harris Date: To: exim-users Subject: Re: [exim] Configuring for non-encrypted MUA to localhost.
TLS-on-connect, exim to smarthost.
On 06/04/2023 19:53, Jeremy Harris via Exim-users wrote: > On 05/04/2023 17:49, Peter via Exim-users wrote:
>> 19:40:02 9597 TFO mode sendto, no data: EINPROGRESS
>> 19:40:02 9597 connected
>> 19:40:02 9597 ╭considering: $primary_hostname
>> 19:40:02 9597 ├──expanding: $primary_hostname
>> 19:40:02 9597 ╰─────result: dalton.invalid
>
> Something tells me you didn't wait long enough
> (which could be, like, ten minutes if it's this
> end exim timing out waiting for the target system
> to speak).
Actually, I'm not convinced that your transport
actually has "protocol = smtps". The TLS client-side
startup should be visible pretty soon after that "sendto"
(which initiates the TCP connection).
If you look backward in that file there should be a line
like "remote delivery to jgh@??? with transport=send_to_server1" -
take that transport name off the end and check it's
the transport in your config
that you are expecting. Then do
# exim -bP transport <the_transport_name>
to dump the actual config (at least, from a freshly loaded
config... you *did* restart exim after any config edits?)
--
Cheers,
Jeremy
