# `role`: the username is a role account rather than a person

info@, support@, billing@ and the rest of the open role-address list name a function, so the inbox may be shared, filtered or unread.

- Weight: +30
- Dataset: role-addresses
- Read from: `role`
- Verdict reasons it comes with: `role`, `no_reply`

The open role list of around a thousand usernames is matched against the plus-tag-free username. A no-reply pattern counts as a role too, even when the list lacks the spelling, and role_type names the family: support, sales, billing, postmaster, no_reply and so on.

It reads from the role field and comes with the role verdict reason — unless the address is a no-reply one, which gets its own reason and whose weight is added on top of this one.

**What to do.** Send transactional mail freely; keep marketing lists to personal addresses, and let the sending policy block the families you do not want.

```json
{
    "email": "support@acme.com",
    "deliverable": "risky",
    "reason": "role",
    "role": true,
    "role_type": "support",
    "risk_signals": [
        {
            "signal": "role",
            "weight": 30,
            "dataset": "role-addresses"
        }
    ]
}
```

Reference: https://spaw.co/docs/signals/role