Are there special aliases that a mail provider would not want normal users to obtain

Question

Lets say, I would like to register a custom domain for email sending/receiving at Amazon AWS for a bunch of trusted users that can choose to send/receive mail with any valid mail address.

Are there still some special mail addresses that I (as the domain owner) should restrict for myself?

Are there special aliases that are defined by RFCs, that a mail domain owner should handle himself?

abuse@ and postmaster@ come to mind. – joeqwerty Sep 14 '18 at 20:01 — joeqwerty, Sep 14 '18 at 20:01

score 1 · Accepted Answer · edited Oct 07 '21 at 07:59

1

You're probably looking for RFC 2142, which summarizes a number of common mail aliases that domains need to have. Some are required by other RFCs, such as postmaster@ and abuse@; others are merely examples, such as info@ or marketing@.

Which mailbox names you handle yourself, and which your customers handle, depends on the specifics of the relationship between you and your customers. You will need to consider each of them individually. For instance, if you manage the customer's website, then you would answer the webmaster@ address, but if they run their own website, then they probably should answer that address.

edited Oct 07 '21 at 07:59

Community

1

answered Sep 14 '18 at 20:26

Michael Hampton

244,070
43
506
972

Per https://cabforum.org Baseline Rqts #3.2.2.4.4, 'one or more of' `admin administrator webmaster hostmaster postmaster` may be authorized to obtain certificate(s) for the domain (and subdomains of it). Example: https://arstechnica.com/information-technology/2015/03/microsoft-takes-4-years-to-recover-privileged-tls-certificate-addresses/ – dave_thompson_085 Sep 15 '18 at 09:45
RFC 2142 is in desperate need of an update... – Michael Hampton Sep 15 '18 at 16:57

Are there special aliases that a mail provider would not want normal users to obtain

1 Answers1