Here is something about the agreements of mailbox names

imageWhen I opened a mail for the domain on Yandex, I decided to open a free registration for unauthorized users to the mailboxes on mine “fancy” domain. In addition, I enabled catch-all feature, which directs all incoming mail of nonexistent mailboxes of my domain to my main mailbox. I faced necessity to reserve all the “standard” names of mailboxes for myself in order to avoid confusion, when some name already has been reserved by another user, and all “service” mail goes to someone else. Of course, you can any time expropriate any mailbox that is under control of domain. I'm puzzled: what are the names of mailboxes standard and system-defined? Yandex technical support said that they reserve for themselves only the name of postmaster @ for each domain to keep track of complaints and problems with the mail. Further, the search of results on the Internet was a bit predictable.
(On the picture is: the famous black mailbox, a place of pilgrimage for UFO enthusiasts)


First, I wanted to find RFC, which is RFC 2142, MAILBOX NAMES FOR COMMON SERVICES, ROLES AND FUNCTIONS (mailbox names for the public services, roles and functions), which was last amended in 1997. Here is just interesting information for us. Based on the document, the following mailboxes should exist and have the following functions:

Business mailboxes:

info @ - Marketing department, here you can find brief information about the organization, products and services.
marketing @ - Marketing department and sales interactions.
sales @ - Sales department, ordering products and information about the orders.
support @ Department of customer support, the problems with the product or services.
abuse @ - Interrelations with the customers, the mailbox should always be functional and valid, here are sent the customer’s complaints, including reports of “Inappropriate public behavior”.


noc @ - Network operations, network infrastructures.
security @ - Network security, notifications, alerts, or requests.

Technical support of separate internet services

postmaster @ - SMTP, [RFC821], [RFC822]
hostmaster @ - DNS, [RFC1033-RFC1035]
usenet @ - NNTP, [RFC977]
news @ - NNTP, Synonym for USENET
webmaster @ - HTTP, [RFC 2068]
www @ - HTTP Synonym for WEBMASTER
uucp @ - UUCP, [RFC976]
ftp @ - FTP [RFC959]

Maillist service

(We will not consider it, just list the main points, there are many official names and a lot of RFC, for example, RFC2369)
list @
list-request @

Thus, we should make aliases of these names for our main email, so no one can open usenet conference on our domain, and sign as the system administrator of network from the mailbox noc @.

/ Etc / aliases

The de facto standard for * nix systems is the agreement on the mail names that are contained in the file / etc / aliases. Which de jure is based on the RFC and other documents for each separate service?
The paradigm of assigning the mailboxes for the people in * nix looks like that: each user gets mailbox on the workstation with the same name as user’s login. After the user name was created in the system, you can send and receive the mail to your account. (Here is as well “but” if a root allows and MX are recorded correctly). If you want to get fancy alias - contact the administrator, he will register it in / etc / aliases or the postal system.
The same goes for the system services. There are lots of spare names such as @ nobody, clamav @, www-data @, which correspond to the system services, in the real life they are not used by anyone other than these existing services and they are the mail aliases of system user (root), so we are not going to take them into account, because all relevant mailbox names of network services, we already learned from the previous paragraph. Let us add only
root @

The modern Internet and other confidential agreements of mailbox names

Let us try together to find the most common names, which owners of domains keep for themselves and use as the administrative, business and personal contacts.
admin @
user @
mail @
blog @
office @
job @ (sometimes [email protected] and [email protected]) for sending and receiving the job applications and resumes.
spam @ - sometimes is used as an alias to abuse @ or postmaster @, apparently for spam complaints.
billing @ - for billing purposes.
account @ - for bookkeeping and account support.
[email protected] - name of mailbox repeats domain.
alex @, boss @ - do not hesitate to reserve your names and nicknames, in order to eliminate the factor of social engineering, when your name is Alex, and your wife knows that you bought, receives from the mailbox alex @ vashdomen . ru a letter with questionable content, she could believe the attacker.
You can add something to this list.

Besides, I do not know much about the agreements of mailbox names in the Windows’ systems, do they exist in reality?

Thus, when you have reserved all these names as aliases for your main mailbox on domain, you protect yourself from mailbox-squat and malicious use of mailboxes with the “system” names. Also, all “service” correspondence to your domain, which may come to the system names, will not be left without attention. If you set up a mail for the office, then such arrangements can be useful for you.

“Translated from another resource”
ZimerMan 6 october 2011, 19:56
Vote for this post
Bring it to the Main Page


Leave a Reply

Avaible tags
  • <b>...</b>highlighting important text on the page in bold
  • <i>..</i>highlighting important text on the page in italic
  • <u>...</u>allocated with tag <u> text shownas underlined
  • <s>...</s>allocated with tag <s> text shown as strikethrough
  • <sup>...</sup>, <sub>...</sub>text in the tag <sup> appears as a superscript, <sub> - subscript
  • <blockquote>...</blockquote>For  highlight citation, use the tag <blockquote>
  • <code lang="lang">...</code>highlighting the program code (supported by bash, cpp, cs, css, xml, html, java, javascript, lisp, lua, php, perl, python, ruby, sql, scala, text)
  • <a href="http://...">...</a>link, specify the desired Internet address in the href attribute
  • <img src="http://..." alt="text" />specify the full path of image in the src attribute