Role/group address
In short: role or group addresses like admin@ or info@ belong to a function or a team, not to one person who opted in — so mailing them drives bounces, spam complaints, and spam-trap hits that damage your reputation. Zoho Campaigns doesn’t allow importing or sending to them. Collect the personal address of the individual you actually want to reach instead.
Email addresses such as admin@, security@, and info@ from various organizations are known as role or group addresses. They generally represent a company, department, position, or group of employees rather than one individual.
These addresses are created for a specific function or for internal communication — not to receive marketing email. Even if one or two people behind the address are interested in your campaign, for everyone else it’s just irrelevant, unwanted mail landing in a shared inbox. And because engagement drives inbox placement today, mailing an address that few people open sends a weak signal to mailbox providers.
Why you should say no to a role/group address
- They don’t (and shouldn’t) subscribe. A group address doesn’t sign up for marketing as a single consenting person. Maybe one member subscribed on the group’s behalf, but it’s strongly recommended not to add the address to your list. If there’s a real lead behind it, find that person and ask them to subscribe with their own personal or business address.
- High complaint risk from many recipients. Because a role address often fans out to several people, a single unwanted email can generate multiple spam complaints — and it only takes one recipient to hit "report spam." That pushes your complaint rate up fast, and complaints are now capped: Google and Yahoo require bulk senders to stay under 0.3% (aim for 0.1%). Cross it and you risk spam-foldering or blacklisting.
- Role owners can block your whole domain. Many role mailboxes belong to admins or security staff with direct network access and the authority to block unwanted senders. Provoke one and you may be blocked not just at that address but across the entire corporate domain — losing every potential lead inside that organization.
- They’re commonly used as spam traps. Anti-spam organizations and mailbox providers seed role/group addresses as spam traps to catch senders with poor list-collection practices. Hitting one is a direct hit to your sender reputation.
- They tend to bounce. Role addresses are often stale, reassigned, or abandoned, so they raise your bounce rate — another negative signal that hurts deliverability for your whole list.
For all these reasons, and to protect our customers’ reputation, Zoho Campaigns doesn’t allow importing or sending to role/group addresses. The best practice is to earn the opt-in of the specific individual you want to reach, verify addresses at signup with an email-validation tool, and suppress any role address that slips in and shows no engagement.
A related note: some role mailboxes exist by design. Internet standard RFC 2142 defines mailboxes like abuse@ and postmaster@ that a sending domain should keep monitored — mailbox providers use them (and feedback loops) to reach you about problems. Keep those working on your own domain; just don’t market to anyone else’s.Examples of role/group addresses
Below are examples of role/group addresses that are strictly not allowed. This list isn’t static — values may be modified or added as needed.
abuse@ | all@ | admin@ |
billing@ | compliance@ | customercomplaints@ |
devnull@ | dns@ | everyone@ |
feedback@ | ftp@ | hostmaster@ |
inoc@ | ispfeedback@ | ispsupport@ |
jobs@ | legal@ | list-request@ |
list@ | maildaemon@ | noc@ |
no-reply@ | noreply@ | null@ |
phish@ | phishing@ | postmaster@ |
privacy@ | purchase@ | registrar@ |
reply@ | root@ | security@ |
spam@ | spoof@ | support@ |
sysadmin@ | tech@ | undisclosed-recipients@ |
unsubscribe@ | usenet@ | uucp@ |
webmaster@ | www@ | @googlegroups.com |
@yahoogroups.com | @groupspaces.com |