![]() And so did the (mostly outmoded) non-SMTP protocols (eg UUCP mail) that were used in the email ecosystem of old together with SMTP-based systems. SMTP, and much of the software built around it, uses hosts, not ip addresses, as its "native currency" - if an "address literal" is usable as a "host", so be it. However, this RFC - from 2008, which actually makes it very NEW, does sanction the use of "address literals" as "allowed" ("To bypass this barrier, a special literal form of the address is allowed as an alternative to a domain name.") in Section 4.1.3 but still discourages it as a "SHOULD NOT" in 2.1.4. Appendices to RFC 821 describe some of them." While this document specifically discusses transport over TCP, other transports are possible. RFC 2821 (from 1989) considers using numerical addresses "discouraged".Įven far more modern versions of the specs uphold that philosophy to some degree, from RFC5321: "SMTP is independent of the particular transmission subsystem and requires only a reliable ordered data stream channel. If you look at the original RFC 821, a "TCP transport" is defined. While SMTP works well layered on TCP,it is, at least in its original form, not in itself a protocol BASED on TCP/IP. It should work if all involved parties use really modern software. There isn't really that much use of SMTP for IoT devices. The usage of SMTP port 25 is very limited on consumer grade internet connections due to abuse (spambots). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |