Deloosh will not send campaign email to role accounts — shared, non-human addresses like noreply@, postmaster@, and abuse@. The denial code is list_quality, and the reason is exactly: “{recipient} is a non-human role account”.
Which addresses count
The check looks at the part before the @. These are rejected:
noreply · no-reply · no_reply · donotreply · do-not-reply · do_not_reply · postmaster · abuse · mailer-daemon · mailerdaemon · bounce · bounces
It applies to marketing and cold-outreach sends.
Why they are a hard reject
These addresses represent functions or automated systems rather than an individual marketing recipient.
abuse@ and postmaster@ receive operational reports. noreply@ and mailer-daemon@ are automated sender addresses. None is a suitable campaign recipient, so the list-quality check rejects them before sending.
Rejecting them removes non-human destinations from the audience and avoids unnecessary deliverability risk.
What to do
Remove the rejected role address from your list and review how it entered the contact data.
Where contacts came from is recorded during import. Use that provenance to check whether the rest of the source is appropriate for campaign email.
For the full battery of pre-send checks, see SEND-2, Why was my send blocked? (denial reasons index).