Re: test Mon, 16 Jun 2025 17:35:47 -0500
Jeremy Harris via Exim-users <[email protected]>
| Newsgroups | gmane.mail.exim.user |
|---|---|
| Message-ID | <[email protected]> |
On 2025/06/16 11:35 PM, Martin McCormick via Exim-users wrote: > 2wb5agz martin tmp $ delivering 1uRCBl-000BhD-39 > R: smarthost for destination.net > T: remote_smtp_smarthost for destination.net > Transport port=25 replaced by host-specific port=587 > Connecting to smtp.altice.prod.cloud.openwave.ai [66.179.105.209]:587 ... TFO mode sendto, no data: EINPROGRESS > connected > SMTP<< 220 altprdrgo002.altice.prod.cloud.openwave.ai ESMTP Service ready > SMTP>> EHLO wb5agz You didn't say how you produced that, but it's not the full extent of available debug output from exim (PS: only Debian call it "exim4". Exim version 3 went out-of-date over twenty years ago). Look into the "-d" option: https://exim.org/exim-html-current/doc/html/spec_html/ch-the_exim_command_line.html#SECID39 Also: it's telling you that certificate verification failed. We can guess it's talking about the certificate presented by the remote. Do you want to discover *why* they are presenting a cert that your end declares bad? In what sense it is "bad"? Turn off the verification (and risk that your comms to there are being intercepted)? Turn off TLS entirely (and risk having your comms trivially sniffed)? -- Cheers, Jeremy -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## [email protected] ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/