Jump to content

Postmaster (computing): Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
No edit summary
Tags: Reverted Mobile edit Mobile web edit
m Reverted edits by 2403:6200:8810:2629:6D8F:9313:5226:3CEE (talk) to last version by Jimjohn55
 
Line 1: Line 1:
{{one source|date=April 2014}}
{{one source|date=April 2014}}
In [[computers]] anmaster''' ismail server]]. Nearly every domain should have the [[e-mail address]] postmaster@example.com where errors in [[elecil|e-mail] directed. Erroils automatl transfer a]s usually appear to have been sent to the postmaster address.
In [[computers]] and [[technology]], a '''postmaster''' is the administrator of a [[mail server]]. Nearly every domain should have the [[e-mail address]] postmaster@example.com where errors in [[electronic mail|e-mail]] processing are directed. Error e-mails automatically generated by mail servers' [[Mail transfer agent|MTA]]s usually appear to have been sent to the postmaster address.


Every domain that supports the [ for electronic mail id by {{IET and, as early as 198C|822|link=no}}, to have the postmaster address. The rfc-ignorant.org website used to maintain a list of domains that do not comply with the RFC based on this requiremut was shut down in November 2012. The website [httcluele RFC<sup>> Realtime List] expanded to include rfc-ignorant's lists after they shut down.
Every domain that supports the [[SMTP]] protocol for electronic mail is required by {{IETF RFC|5321|link=no}} and, as early as 1982, by {{IETF RFC|822|link=no}}, to have the postmaster address. The rfc-ignorant.org website used to maintain a list of domains that do not comply with the RFC based on this requirement, but was shut down in November 2012. The website [http://rfc-clueless.org/ RFC<sup>2</sup> Realtime List] expanded to include rfc-ignorant's lists after they shut down.


Quoting fromte>
Quoting from the RFC:
Any that includes an SMTP server supporting mail relaying or deliMUST support the reserved mailbox "postmaster" as a [[case s|case-initive]] local name. This postmasdress is not strictly necessary if the server always returns 554 on connection opening (as describeection 3.1).<ref>In the case oction-opening resmeans "No SMTP service here", and may contain explanatory information.</ref> The requirement to accept mail for postmaster implies that RCPT commands which specify a mailbox for postmaster at any of thins for which the SMTP server provides mail service,ell as ST be supp


<blockquote>
<bloc
Any system that includes an SMTP server supporting mail relaying or delivery MUST support the reserved mailbox "postmaster" as a [[case sensitivity|case-insensitive]] local name. This postmaster address is not strictly necessary if the server always returns 554 on connection opening (as described in section 3.1).<ref>In the case of a connection-opening response, 554 means "No SMTP service here", and may contain explanatory information.</ref> The requirement to accept mail for postmaster implies that RCPT commands which specify a mailbox for postmaster at any of the domains for which the SMTP server provides mail service, as well as the special case of "RCPT TO:<Postmaster>" (with no domain specification), MUST be supported.
SMTP systems are expected to make every reasonable effort to accept mail directed to Postmaster from any other system on the Inch as to contain a denial of service attack or oMTP server may block mail dire Postwever, such arraents SHOULD be nalored so as to avoid blocking messages
</blockquote>


<blockquote>
Since most domains have a postmaster it is commonly targeted by [[e-mai operations. Even if not directly spammed, a postmaster address may be ] spam from other servers that mistakenly trust fake [[return-path]]s commonly used in spam. <! spammer tries sending email to someone@somedomain.com, and it bounces (due to any number of reasons) and the fake retuyourdomain.com, then an automatic email will be generrdomain.com informing
SMTP systems are expected to make every reasonable effort to accept mail directed to Postmaster from any other system on the Internet. In extreme cases (such as to contain a denial of service attack or other breach of security) an SMTP server may block mail directed to Postmaster. However, such arrangements SHOULD be narrowly tailored so as to avoid blocking messages which are not part of such attacks.
</blockquote>

Since most domains have a postmaster address, it is commonly targeted by [[e-mail spam|spamming]] operations. Even if not directly spammed, a postmaster address may be sent [[bounce message|bounced]] spam from other servers that mistakenly trust fake [[return-path]]s commonly used in spam. <!--For example, if a spammer tries sending email to someone@somedomain.com, and it bounces (due to any number of reasons) and the fake return address is you@yourdomain.com, then an automatic email will be generated to postmaster@yourdomain.com informing --><!-- this needs to be completed -->


==References==
==References==

Latest revision as of 12:25, 18 December 2024

In computers and technology, a postmaster is the administrator of a mail server. Nearly every domain should have the e-mail address postmaster@example.com where errors in e-mail processing are directed. Error e-mails automatically generated by mail servers' MTAs usually appear to have been sent to the postmaster address.

Every domain that supports the SMTP protocol for electronic mail is required by RFC 5321 and, as early as 1982, by RFC 822, to have the postmaster address. The rfc-ignorant.org website used to maintain a list of domains that do not comply with the RFC based on this requirement, but was shut down in November 2012. The website RFC2 Realtime List expanded to include rfc-ignorant's lists after they shut down.

Quoting from the RFC:

Any system that includes an SMTP server supporting mail relaying or delivery MUST support the reserved mailbox "postmaster" as a case-insensitive local name. This postmaster address is not strictly necessary if the server always returns 554 on connection opening (as described in section 3.1).[1] The requirement to accept mail for postmaster implies that RCPT commands which specify a mailbox for postmaster at any of the domains for which the SMTP server provides mail service, as well as the special case of "RCPT TO:<Postmaster>" (with no domain specification), MUST be supported.

SMTP systems are expected to make every reasonable effort to accept mail directed to Postmaster from any other system on the Internet. In extreme cases (such as to contain a denial of service attack or other breach of security) an SMTP server may block mail directed to Postmaster. However, such arrangements SHOULD be narrowly tailored so as to avoid blocking messages which are not part of such attacks.

Since most domains have a postmaster address, it is commonly targeted by spamming operations. Even if not directly spammed, a postmaster address may be sent bounced spam from other servers that mistakenly trust fake return-paths commonly used in spam.

References

[edit]
  1. ^ In the case of a connection-opening response, 554 means "No SMTP service here", and may contain explanatory information.
[edit]
  • RFC 5321: The SMTP Protocol