SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request]

Mon Jan 14 16:30:27 UTC 2019

Your sarcasm detector might need a bit of a tweak. :)

On Fri, Jan 11, 2019 at 9:18 PM Viruthagiri Thirumavalavan <giri at dombox.org>
wrote:

> While we're at it, let's deprecate IPv4 now that IPv6 is fully deployed
>
>
> Come on Mr. Herrin.
>
> Blocking a port is much easier than deprecating a heavily used protocol.
> Google stats show ~75% use IPv4.
>
> On Sat, Jan 12, 2019 at 7:30 AM William Herrin <bill at herrin.us> wrote:
>
>> On Fri, Jan 11, 2019 at 5:52 PM Viruthagiri Thirumavalavan
>> <giri at dombox.org> wrote:
>> >> In addition, it bypasses all the security folks have built around the
>> >> idea of blocking port 25 traffic from sources which should not be
>> >> operating as mail servers. Let's not make the network less secure in
>> >> the name of making it more so.
>> >
>> > I already addressed this issue in the "security considerations" section.
>> >
>> > "Port 26 will be a secure alternative for Port 25. So Internet Service
>> Providers are adviced to take precautions to prevent email spam abuse. They
>> are advised to block port 26, if necessary."
>>
>> While we're at it, let's deprecate IPv4 now that IPv6 is fully deployed.
>>
>> -Bill
>>
>>
>>
>> --
>> William Herrin ................ herrin at dirtside.com  bill at herrin.us
>> Dirtside Systems ......... Web: <http://www.dirtside.com/>
>>
>
>
> --
> Best Regards,
>
> Viruthagiri Thirumavalavan
> Dombox, Inc.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190114/6afbcd44/attachment.html>