[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request]
- Subject: SMTP Over TLS on Port 26 - Implicit TLS Proposal [Feedback Request]
- From: giri at dombox.org (Viruthagiri Thirumavalavan)
- Date: Sat, 12 Jan 2019 22:13:44 +0530
- In-reply-to: <[email protected]>
- References: <CAOEezJQ0mJYvKW=SdbbE4ZC2Vx6_9FD5Z0SpkF2840r580vZ5w@mail.gmail.com> <[email protected]> <CAOEezJTKiE_mKYgUXiRGQ5R=Skyaw3qyy9NKdgbVmDNOwC0bkQ@mail.gmail.com> <[email protected]>
What makes you think I never did any research?
https://medium.com/@Viruthagiri/smtp-ports-25-vs-587-vs-465-de1046f57636
On Sat, Jan 12, 2019 at 10:10 PM James Downs <egon at egon.cc> wrote:
> > On Jan 12, 2019, at 08:14, Viruthagiri Thirumavalavan <giri at dombox.org>
> wrote:
>
> > My solution is intended for clients. A client should decide whether to
> transmit mails in clear text or not.
>
> You should spend some time doing research by reading RFCs, and doing a
> little searching on the internet. Your proposal, would, canonically be
> called SMTPS.
>
> If you put that into a search engine, you'll find not only is it
> deprecated, but has an assigned port number of 465.
>
> https://en.wikipedia.org/wiki/SMTPS
>
>
--
Best Regards,
Viruthagiri Thirumavalavan
Dombox, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20190112/0c5e6293/attachment.html>