We don't have postmaster@ or abuse@ set up
RFC 2142 mandates postmaster@ and abuse@ aliases. Some RBLs and large receivers actively check for them.
support/email-aflevering/postmaster-abuse-aliassensteps: 4
Try this first
- Create postmaster@yourdomain as an alias to the IT mailbox
- Create abuse@yourdomain as an alias to IT or the security team
- Both must actually receive mail and be read
- On reports: fast response helps reputation and compliance
When to bring us in
Ignoring entirely leads to RBL listings and refusal at large receivers.
See also
- Our emails land in spam for some recipientsAlmost always an SPF, DKIM, or DMARC setting that is wrong or missing, or a sender name that mimics a well-known brand.
- Someone reports receiving phishing emails "from us"Read: spoofing. Someone is abusing your sender name, not necessarily your actual mailbox.
- An email bounces (NDR): delivery failedThe NDR text usually states the exact reason. Reading it is step one.
None of the above fits?
Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.
Or skip the DIY entirely
Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.