On 10/1/22 20:44, Viktor Dukhovni wrote:
I do have it listening on port 465, hopefully I got the config right
so that does not allow authentication. I think I also disabled TLS
below 1.2 on port 587.
What would be the use of "465" if SASL authentication is not allowed?
It is should be configured essentially the same way (modulo wrapper
mode, and the service name) as port 587.
I am leaning towards completely disabling smtps and removing the permit
on the AWS firewall. Since 465 is not an actual standard, I think
everyone is using 587. I guess if I disable 465 and anyone is using it,
I'll hear about it.
Thanks,
Shawn
