Limits on Role-based Addresses

Role-based addresses are typically company addresses defined by a job rather than a person, and are often managed by several people or eventually fall into disuse. Some of these types of addresses are associated with high bounce rates and spam complaints, so Mailchimp blocks them from your import. Role-based email addresses also cannot be used to sign up for a Mailchimp account.

Blocked addresses

  • abuse@
  • admin@
  • billing@
  • compliance@
  • devnull@
  • dns@
  • ftp@
  • hostmaster@
  • inoc@
  • ispfeedback@
  • ispsupport@
  • list-request@
  • list@
  • maildaemon@
  • noc@
  • no-reply@
  • noreply@
  • null@
  • phish@
  • phishing@
  • postmaster@
  • privacy@
  • registrar@
  • root@
  • security@
  • spam@
  • support@
  • sysadmin@
  • tech@
  • undisclosed-recipients@
  • unsubscribe@
  • usenet@
  • uucp@
  • webmaster@
  • www@

Subscriber signup

Subscribers with role-based email addresses can still join your audience. It's only during an import that these are blocked.

  • A new subscriber with a role-based address should use your signup form to subscribe. Share your signup form link with that potential subscriber, so they can opt in to your audience.
  • If you have express permission to add a role-based subscriber to your audience, add them as a single subscriber.
  • If a subscriber is willing to share an alternate address that is not role-based, you can edit their contact profile with the new address or ask them to update their profile.

Was this article helpful?

Anything else we can do to improve our site?