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.
On 10/1/22 20:44, Viktor Dukhovni wrote:
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.
On 01.10.22 21:25, Shawn Heisey wrote:
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.
not only it is a standard for nearly 4 years, it's also better because
there's no possibility to have plaintest on 465 if you forget something
I've also had problems with AV blocking tls on 587 in the past.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Despite the cost of living, have you noticed how popular it remains?
