Need a hand? We've got you covered.

Knowledge Base Home aero-right Contact Lists aero-right Why Role Based Addresses Are Not Permitted

Why Role Based Addresses Are Not Permitted

Contact Lists Updated on May 7, 2021

Role-based email addresses are usually set up by a company to manage general inquiries or issues related to that organization. These emails are managed by several people or individuals who may be part of different departments. Sending informative emails to such email addresses result in a high complaint rate, and we do not allow such addresses to be imported in bulk.

If you have been given explicit permission from a contact to send email messages, you can go to the “Add Individual Contacts” option to manually add each role-based email address to your email.

The following list of addresses are not allowed in our “bulk import” as well as the “copy-paste contacts” option but can be added one-by-one to your list if you know that a recipient on your list uses one of these as their primary email address.*

  • compliance @
  • devnull @
  • dns @
  • inoc @
  • ispfeedback @
  • ispsupport @
  • list-request @
  • list @
  • no-reply @
  • noc @
  • noreply @
  • null @
  • prime @
  • remove @
  • request @
  • security @
  • subscribe @
  • support @
  • tech @
  • unsubscribe @
  • usenet @
  • users @
  • www @

Note: This is the most current list of role-based email addresses blocked by Benchmark Email. Other role-based email addresses may be added to this list without notice.

If uploading a list via RESTful API you could see an error message for role-based emails.

Some error messages may look like this.

100 Email Email not added
100 Optin Valid email, but no email permission; (Data.EmailPerm = 0)


If you think there was an error in the list upload, and an email should have been added, please contact us for clarification or to request a review of the situation.

Did this answer your questions?
You already voted!