smtp.rfc2142.abuse
abuse@ Not Accepting Mail
What we check
We send a RCPT TO:<abuse@domain> command during the SMTP session to verify that the server accepts mail for the abuse role address. RFC 2142 defines abuse@ as the standard mailbox for receiving reports about network abuse, spam, and policy violations.
What this finding means
The server rejected RCPT TO:<abuse@domain>. The abuse address is either not configured, aliased to a non-existent mailbox, or explicitly blocked by recipient restrictions.
Why it matters
- Blocks abuse reports. Abuse desks at ISPs, hosting providers, and anti-spam services send complaints to abuse@. If the address bounces, those reports are lost — the operator never learns about compromised accounts, spamming users, or blocklist entries.
- Industry expectation. RFC 2142 recommends abuse@ for every domain. Anti-spam best practices (including the Messaging, Malware and Mobile Anti-Abuse Working Group — M3AAWG) treat it as mandatory.
- Blocklist removal. Some blocklist operators attempt to contact abuse@ before listing or as part of the delisting process. An unreachable abuse address can delay or prevent removal.
How to fix
Create the abuse alias. For Postfix:
# /etc/postfix/virtual or /etc/aliases abuse@example.com admin@example.comThen rebuild the alias database:
postalias /etc/postfix/aliases # or: postmap /etc/postfix/virtual postfix reloadFor hosted mail (Microsoft 365, Google Workspace): configure the abuse alias in your admin console.
Monitor the mailbox. An abuse address that exists but is never read is not much better than one that bounces. Route it to a team or individual who will act on reports.
How it's graded
A rejected abuse address is a warning and carries no point penalty. While strongly recommended, RFC 2142 uses "SHOULD" language for abuse@ (unlike the "MUST" for postmaster@). See Grading Methodology for the full scoring model.
Evidence example
C: RCPT TO:<abuse@example.com>
S: 550 5.1.1 <abuse@example.com>: Recipient address rejected: User unknown