Per RFC 2142 and best practices, the following addresses could be created:
RFC 2142 - Section 3 - Marketing
| Username | Usage / Rationale | Comments | Decision |
|---|---|---|---|
| info@ | Information about the organization, | Seems a never implemented practice | ↪️ Redirect to contact@ |
| marketing@ | Product marketing and marketing communications | Not relevant for us | ❌ |
| sales@ | Product purchase information | Not relevant for us | ❌ |
| support@ | Problems with product or service | Need Zammad (T1105) or another solution (T1104) | ↪️ Redirect to desk service per T1104 |
RFC 2142 - Section 4 - Network operations
| Username | Usage / Rationale | Comments | Decision |
|---|---|---|---|
| abuse@ | Complaints | For Nasqueron Operations SIG | ↪️ Redirect to ops@ |
| noc@ | Network operations | For Nasqueron Operations SIG | ↪️ Redirect to ops@ |
| security@ | Network security | Now also use to report security issues | ➕ Create mailing list |
RFC 2142 - Section 5 - Support mailbox names
| Username | Usage / Rationale | Comments | Decision |
|---|---|---|---|
| postmaster@ | RFC 821/822 | For Nasqueron Operations SIG | ↪️ Redirect to ops@ |
| hostmaster@ | RFC 1033/1034/1035 | For Nasqueron Operations SIG | ↪️ Redirect to ops@ + update DNS records |
| usenet@ | RFC 977 | We don't maintain newsgroups | ❌ |
| news@ | synonym for usenet@ | >> | ❌ |
| webmaster@ | RFC 2068 | Who maintains sites? | ➕ Create mailing list |
| www@ | synonym for webmaster@ | >> | ↪️ Redirect to webmaster@ |
| uucp@ | RFC 976 | Superseded by SMTP and Usenet, we don't maintain | ❌ |
| ftp@ | RFC 959 | See also T1852. For Nasqueron Operations SIG. | ↪️ Redirect to ops@ |
GDPR recommandations
| Username | Usage / Rationale | Comments | Decision |
|---|---|---|---|
| dpo@ | Reach the data protection officer | We notice more adoption for privacy@ | ↪️ Redirect to privacy@ |
| privacy@ | Privacy questions and requests | For Nasqueron Operations SIG (temporarily) | ↪️ Redirect to ops@ |