Something about mailbox naming conventions

Having started “mail for a domain” on Yandex , I decided to open free registration to outside users of mailboxes on my “trendy” domain. In addition to including the catch-all function, which sends all incoming mail of non-existing mailboxes of my domain to my main mailbox, I had to reserve all the “standard” mailbox names so that there were no misunderstandings when an outsider had already scored some name, and all the "service" mail does not go to you. In PDD You can, of course, at any time, expropriate any mailbox of the domain under control, but after all, the sediment remains. I was puzzled: what are the names of mailboxes are standard and system? Yandex technical support responded that they reserve only the name postmaster @ for each domain in order to track complaints and problems with the mail, and that at the moment the question about the set of reserved names they have left open. Further, the search result on the Internet was a bit predictable.
^{(in the picture: the famous black mailbox, a place of pilgrimage for amateur ufologists)}

RFC

First and foremost, what I wanted to find was the RFC, which turned out to be RFC 2142, MAILBOX NAMES FOR COMMON SERVICES, ROLES AND FUNCTIONS ( mailbox names for common services, roles and functions ), in the last 1997 edition. I will cite only the information that interests us. Based on the document, the following mailboxes must exist and have the following purpose:

Business mailboxes:

info @ - Marketing department, here you can find brief information about the organization, products, services.
marketing @ - Department of marketing and sales interaction.
sales @ - Sales, product ordering and ordering information
support @ Customer support, problems with the product or services.
abuse @ - Customer relationship, the box should always be working and valid, customer complaints are sent here, including messages about “Inappropriate public public behavior” .
')

Work with the network:

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

Technical support for individual 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, we will simply list the main ones, there is a whole galaxy of official names and a bunch of RFCs, for example RFC2369 )
list @
list-request @

_{It seems to me that this RFC 2142 was approved at the time of the dot-com heyday, which means that the need for such agreements was very relevant. It was assumed, apparently, that the employees on the machine should be able to send mail to the well-known addresses and expect appropriate competent answers.}

Thus, you should make aliases of these names to your “primary” email, so that no one could open a usenet conference on your domain, stop billing felt boots from the “sales department” and did not subscribe the network administrator to the entire network from the noc @ box.

/ etc / aliases

The de facto standard for * nix systems is the mailing name convention contained in the / etc / aliases file. Which is de jure based on the RFC and other documents for each individual service.
The mailbox assignment paradigm for people in * nix sounds like this: each user receives a mailbox on a workstation with the same name as his login. After creating a username in the system, you can already send and receive mail to your account. (there will be its “but”: if it permits root and MX is correctly spelled out ). If you want to get a trendy alias - contact your administrator, he will register it in / etc / aliases or else where in the mail system.
The same goes for system services. There are a lot of backup names like nobody , clamav @, www-data @, which correspond to the system accounts of services, are not used by anyone in real life, except for these corresponding services and are mail aliases of the system root user, so we will not take them into account, because we already learned all the meaningful names of the network service boxes from the previous paragraph. Add only
root @

Modern Internet and other unofficial naming conventions for mailboxes.

Let's try with you to find the most frequent names that domain owners reserve for themselves and use as administrative, business and personal contacts.
admin @
administrator @ (people who know a lot can add localized admin names in Windows, like administrador, administrateur )
user @
mail @
blog @
office @
job @ (and sometimes resume @ and hr @) - for sending and receiving applications for work and resumes.
spam @ - sometimes it is set as an alias to abuse @ or postmaster @, for spam complaints, obviously.
billing @ - for billing. K.O.
account @ - for accounting and account support.
domain@domain.tld - the box name repeats the domain, obviously, for aesthetics.
alex @, boss @ - feel free to score your first and last names and nicknames to eliminate the social engineering factor when, for example, your name is Alexey, and your wife, knowing perfectly well that you bought yourdomain.com, gets it from the box alex @ yourdomain .ru letter of dubious content - an hour will not believe an attacker.
You can add something to this sheet.

Besides this, I know almost nothing about mail name conventions on Windows systems, do they really exist?

Thus, having reserved all these names as aliases for your main mailbox on the domain, you will protect yourself, including the number from mailbox squatting and malicious use of mailboxes with “system” names. Also, all the "official" correspondence on your domain, which can come to the system names will not be ignored. If you are organizing mail for the office, then such agreements can also be useful to you.