Postmaster (computing)

Quality 0.50 · 1 view · Updated 2 months ago

title: "Postmaster (computing)" type: doc version: 1 created: 2026-02-28 author: "Wikipedia contributors" status: active scope: public tags: ["email"] topic_path: "general/email" source: "https://en.wikipedia.org/wiki/Postmaster_(computing)" license: "CC BY-SA 4.0" wikipedia_page_id: 0 wikipedia_revision_id: 0

In electronic mail, a postmaster is the administrator of a mail server. Nearly every domain should have an e-mail address like 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 from 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.{{Cite IETF |rfc=822 |title=RFC 822 - STANDARD FOR THE FORMAT OF ARPA INTERNET TEXT MESSAGES |editor-first=David H. |editor-last=Crocker |editor-link=Dave_Crocker_(engineer) |publisher=IETF |date=1982-08-13 |access-date=2025-02-13 |url=https://datatracker.ietf.org/doc/rfc822/ |url-status=live |archive-url=https://web.archive.org/web/20250127102258/https://datatracker.ietf.org/doc/rfc822/ |archive-date=2025-01-27 |quote=6.3. RESERVED ADDRESS It often is necessary to send mail to a site, without knowing any of its valid addresses. For example, there may be mail system dysfunctions, or a user may wish to find out a person's correct address, at that site.

This standard specifies a single, reserved mailbox address (local-part) which is to be valid at each site. Mail sent to that address is to be routed to a person responsible for the site's mail system or to a person with responsibility for general site operation. The name of the reserved local-part address is:

Postmaster

so that "Postmaster@domain" is required to be valid.

Note: This reserved local-part must be matched without sensitivity to alphabetic case, so that "POSTMASTER", "postmaster", and even "poStmASteR" is to be accepted.

Specification

RFC 5321, which defines the Simple Mail Transfer Protocol, specifies that all mail servers featuring the ability to relay or deliver email must have a "postmaster" mailbox, and that the postmaster should receive all mail sent to it in as much as possible (except, for example, in case of a denial-of-service attack). Email send to the postmaster mailbox must also be received by a real person who's capable of handling issues with the mail server.

Unless the mail server has a real account called "postmaster," the postmaster mailbox should be defined as an e-mail alias that expands to the address of a real user on the mail server.

Use

The purpose of the postmaster mailbox is to receive messages about issues with the mail server that hosts it. This mailbox follows the same pattern as the hostmaster and webmaster addresses, which are intended to receive DNS and web-related complaints respectively.

For example, if email sent to another server is bounced, the receiving server may notify the sending server by sending a message to its postmaster. Mail programs are typically designed to notify the postmaster automatically when they detect problems, and users can also use this mailbox to notify the administrator of a mail server about issues on their own.

It is convention to send copies of bounced emails to the postmaster mailbox, however this is optional. Sending the postmaster all bounced emails can pose privacy concerns for users, so some mail servers first pass all such messages through a filter to remove the e-mail's body, preserving only the headers to diagnose issues

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

Bibliography

  • {{Cite IETF |rfc=5321 |title=RFC 5321 - Simple Mail Transfer Protocol |first=John C. |last=Klensin |author-link=John Klensin |publisher=IETF |date=October 2008 |access-date=2025-02-13 |url=https://datatracker.ietf.org/doc/rfc5321/ |url-status=live |archive-url=https://web.archive.org/web/20250101215956/https://datatracker.ietf.org/doc/rfc5321/ |archive-date=2025-01-01

References

  1. {{harvnb. Klensin. 2008
  2. {{harvnb. Klensin. 2008
  3. {{harvnb. Costales. Jansen. Assmann. 2008
  4. {{harvnb. Costales. Jansen. Assmann. 2008
  5. {{harvnb. Lucas. 2024
  6. {{harvnb. Costales. Jansen. Assmann. 2008
  7. {{harvnb. Lucas. 2024
  8. {{harvnb. Costales. Jansen. Assmann. 2008

::callout[type=info title="Wikipedia Source"] This article was imported from Wikipedia and is available under the Creative Commons Attribution-ShareAlike 4.0 License. Content has been adapted to SurfDoc format. Original contributors can be found on the article history page. ::

email