Skip to main content

Compliance: Understand Role-based Email Addresses

Understand why you shouldn't send emails to role-based email addresses

Written by Paulius
Updated today

Role-based email addresses (like info@, support@, or noreply@) are shared company inboxes managed by multiple people or automated systems. Because they're linked to high bounce rates, spam complaints, and spam traps, Omnisend automatically blocks them to protect your sender reputation.

This article explains what role-based addresses are, why they're blocked, and how to remove them from your contact list.

Why Omnisend Blocks Role-Based Addresses

Role-based addresses are email addresses tied to a function or department rather than an individual – for example, [email protected] or [email protected]. They're often monitored by multiple people or automated systems.

Sending to role-based addresses damages your email deliverability in three ways:

  1. Bounces: Addresses like postmaster@ or devnull@ often reject all incoming mail, increasing your bounce rate.

  2. Spam traps: ISPs and anti-spam organizations use addresses like abuse@ and spam@ to catch senders with poor list hygiene.

  3. Complaints: Shared inboxes (like info@) mean multiple people see your emails – and one may mark it as spam.

Blocking these addresses before they reach your campaigns protects your domain reputation and inbox placement.

Blocked Addresses

Omnisend blocks the following role-based email addresses:

  • abuse@

  • abuses@

  • compliance@

  • devnull@

  • dns@

  • domains@

  • donotreply@

  • ftp@

  • hostmaster@

  • info@

  • inoc@

  • ispsupport@

  • ispfeedback@

  • list@

  • list-request@

  • maildaemon@

  • no-reply@

  • no_reply@

  • noc@

  • noreply@

  • null@

  • paypal@

  • phish@

  • phishing@

  • post@

  • postmaster@

  • privacy@

  • registrar@

  • reportabuse@

  • root@

  • security@

  • spam@

  • sysadmin@

  • tech@

  • unsubscribe@

  • undisclosed-recipients@

  • usenet@

  • uucp@

  • webmaster@

  • www@

How to Unsubscribe Role-Based Addresses

If you've already imported contacts with role-based addresses, follow these steps:

  1. Go to Audience → Segment → Create segment → Create from scratch.

  2. Filter by email address (e.g., "Email address contains info").

  3. Select the contacts → Click Actions → Select Unsubscribe.

Note: Unsubscribing contacts prevents them from receiving email campaigns and promotional messages. They remain eligible for transactional emails, such as order confirmations, shipping updates, and account notifications.

FAQ

What happens if I try to send to a blocked address?
The email message will bounce, and you can see it under Reports → Campaigns as Failed Delivery.

Can I request an exception for a specific role address?
Yes. While this is a platform-wide policy to protect sender reputation, our Support Team can unblock role-based addresses if you have explicit consent to email them. Contact us via the in-app chat or email [email protected].

Have any additional questions? Feel free to contact us via in-app chat or at [email protected].

Related Articles
Prevent Campaigns from Landing in Spam
Compliance: Understand Contact List Management
Clean Your Email List to Improve Deliverability
Meet Google, Yahoo, AOL Email Sending Requirements (2024)
Omnisend Reports: Deliverability
Did this answer your question?