Email port 587: Difference between revisions
Jump to navigation
Jump to search
imported>Meg Taylor No edit summary |
mNo edit summary |
||
| Line 3: | Line 3: | ||
*[http://tools.ietf.org/html/rfc5068 RFC-5068, BCP-134] - "Email Submission Operations: Access and Accountability Requirements", Hutzler, et.al. 2007. Best Current Practices recommended for operators of email submission services. | *[http://tools.ietf.org/html/rfc5068 RFC-5068, BCP-134] - "Email Submission Operations: Access and Accountability Requirements", Hutzler, et.al. 2007. Best Current Practices recommended for operators of email submission services. | ||
*[http://tools.ietf.org/html/rfc4409 RFC-4409] - "Message Submission for Mail", Gellens & Klensin, 2006. Requirements for submission of email using port 587. | *[http://tools.ietf.org/html/rfc4409 RFC-4409] - "Message Submission for Mail", Gellens & Klensin, 2006. Requirements for submission of email using port 587.[[Category:Suggestion Bot Tag]] | ||
Revision as of 16:00, 11 August 2024
Port 587 is a special TCP port reserved for authenticated submission of email messages. Authentication can be done over the standard port 25, but 587 has the advantage that it is seldom blocked by networks providing Internet access to travelers. The standard email port 25 is frequently blocked due to widespread abuse of these networks. This abuse does not occur with port 587, because servers listening on this port require authentication.
- RFC-5068, BCP-134 - "Email Submission Operations: Access and Accountability Requirements", Hutzler, et.al. 2007. Best Current Practices recommended for operators of email submission services.
- RFC-4409 - "Message Submission for Mail", Gellens & Klensin, 2006. Requirements for submission of email using port 587.