Re: https://<FQDN>:<port> vs. https://<IP address>:<port>.
On Mon 10 Apr 2023 at 12:13:15 (-0700), peter@easthope.ca wrote:
> [ … ]
Others have covered your "oddity", likely caused by a certificate
that seems normal.
> As expected, login at https://hornby.islandhosting.com:2096 and at
> https://mail.easthope.ca:2096 appear equivalent.
I notice that 2096 is often a webmail port. Does that mean you've
given up on sending emails by their submission port? Your emails
on this topic suddenly stopped after March 26.
I would point out that there's a small but important difference
between the Debian READMEs on bullseye and bookworm:
$ diff -ubw README.Debian-bookworm README.Debian-bullseye
--- README.Debian-bookworm 2023-02-04 06:33:00.000000000 -0600
+++ README.Debian-bullseye 2023-04-10 22:32:29.989821250 -0500
@@ -767,9 +767,7 @@
REMOTE_SMTP_SMARTHOST_TLS_CERTIFICATE/REMOTE_SMTP_SMARTHOST_PRIVATEKEY
respectively.
- To use TLS on connect set "protocol = smtps" on the respective
- transport. (For the remote_smtp_smarthost transport the macro
- REMOTE_SMTP_SMARTHOST_PROTOCOL can be used.
+ TLS on connect is not natively supported.
2.2.2. TLS support for Exim as server
So if the method I suggested doesn't work, you could try out the
version of exim4 from bullseye-backports, which also contains
this change.
Cheers,
David.
Reply to: