Email port 587: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>David MacQuigg
(stub article)
imported>David MacQuigg
m (Tried to add a definition, but messed up the link.)
Line 4: Line 4:


'''RFC-5068 BCP-134''' Hutzler, et. al., "Email Submission Operations: Access and Accountability Requirements", 2007.
'''RFC-5068 BCP-134''' Hutzler, et. al., "Email Submission Operations: Access and Accountability Requirements", 2007.
{{r|http://tools.ietf.org/html/rfc5068 RFC-5068, BCP-134 - Email Submission Operations: Access and Accountability Requirements}} - Best Current Practices recommended for operators of email submission services.


'''RFC-4409''' Gellens, Klensin, "Message Submission for Mail", 2006.
'''RFC-4409''' Gellens, Klensin, "Message Submission for Mail", 2006.
{{r|http://tools.ietf.org/html/rfc5068 RFC-5068, BCP-134 - Email Submission Operations: Access and Accountability Requirements}} - Best Current Practices recommended for operators of email submission services.


{{r|http://tools.ietf.org/html/rfc4409 RFC-4409 - Message Submission for Mail}} - Requirements for submission of email using port 587.
{{r|http://tools.ietf.org/html/rfc4409 RFC-4409 - Message Submission for Mail}} - Requirements for submission of email using port 587.

Revision as of 11:21, 29 August 2009

Definition: TCP port reserved for authenticated submission of email messages.

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 Hutzler, et. al., "Email Submission Operations: Access and Accountability Requirements", 2007.

RFC-4409 Gellens, Klensin, "Message Submission for Mail", 2006.