Indeed. So it would seem I have been lost in the dark. Thanks for sharing that
reference, makes sense now. Purely a sending mta configuration issue, nothing
more complex than that.
-Andrew
On 7/10/2021, at 19:04, Viktor Dukhovni wrote:
>
> On Thu, Oct 07, 2021 at 06:50:22PM +1300, AndrewHard
On Thu, Oct 07, 2021 at 06:50:22PM +1300, AndrewHardy wrote:
> Looks like as long as STARTTLS is present in the server response then
> it doesn’t matter if it’s a hyphen or space and the s_client.c library
> suggests it just looks for that keyword so that confirms it. Helps to
> tell it to encrypt
Viktor, you are an absolute legend.
Couldn’t see the woods through the trees.
Looks like as long as STARTTLS is present in the server response then it
doesn’t matter if it’s a hyphen or space and the s_client.c library suggests it
just looks for that keyword so that confirms it. Helps to tell i
On Thu, Oct 07, 2021 at 06:01:45PM +1300, Andrew Hardy wrote:
> The core of my issue is that the sending MTA receives the 250 STARTTLS
> from the receiving MTA but never replies with STARTTLS. The sending
> MTA has smtpd_tls_security_level = may defined.
There's you problem "smtpd_tls_security_le
Hi All,
I’m hoping someone on this mailing list could help me with understand a
particular behaviour I’m seeing with an upstream mail service and hoping
someone has some more in-depth knowledge than me who can look at the below
scenario and advise what the expected behaviour should look like
