Purelymail uses a multi-layered filtering pipeline to block inbound spam and protect outbound sending reputation for all users on the cluster.
1. Inbound Defense Layers
- DNSBL & Reputation Edge Rejection: Connecting server IPs listed on Spamhaus Zen (
zen.dq.spamhaus.net) or flagged for severe spam abuse in Purelymail's internal IP reputation system are rejected immediately at the SMTP connection stage (550 5.7.1). - Greylisting: Unfamiliar sending servers that lack valid reverse DNS (rDNS) or use generic dynamic/residential hostnames receive a temporary
451 4.7.1 Try again later (greylist)deferral on their first attempt. Standard RFC-compliant mail servers retry automatically after 1 to 15 minutes and are whitelisted for future deliveries, whereas automated spambots drop off (see Troubleshooting: Missing or Delayed Inbound Emails). - Apache SpamAssassin & Custom Heuristics: Accepted messages are scored by SpamAssassin:
- Default Threshold (
5.0): When Enable spam filtering? is checked on a mailbox (see Mailbox Settings & Deletion), any message scoring 5.0 or higher is automatically delivered to yourJunkfolder. You can also write custom score rules using Sieve filters. - Purelymail Custom Signals: Includes reply thread verification (
VALID_MESSAGE_ID_REFERENCE, which deducts5.0points when a message is a reply to aMessage-IDalready in your mailbox), attachment size adjustments (LARGE_MESSAGE), DMARC alignment scoring (PM_DMARC), and internal sender IP reputation (PURELYMAIL_IP_REPUTATION).
- Default Threshold (
2. Outbound and Forwarding Protections
To ensure high inbox placement for all accounts, Purelymail protects its sending IP reputation through automated outbound safeguards:
- Forwarded Email Spam Protection:
- When routing rules forward incoming mail to external providers like Gmail, Outlook, or Yahoo, incoming spam is not forwarded externally.
- If an incoming message is identified as spam, Purelymail places it in your local Purelymail
Junkfolder instead of forwarding it out. This prevents external providers from flagging Purelymail's sending IPs as sources of spam and throttling your forwarded messages (see How to Create Email Aliases & Forwarding Rules).
- Outbound Spam Scanning: Outbound emails sent through SMTP or Webmail are scanned prior to dispatch. If a user account is compromised and begins sending spam or phishing messages, outbound delivery is paused to protect the domain and server reputation.
- Token-Bucket Rate Limits: Outbound sending volume is regulated by automatic rate limits that replenish over time to prevent sudden bursts of abusive traffic (see Sending Rate Limits and How to Request a Volume Increase).
- Prohibited Sending Practices: Scraped mailing lists, cold outreach, and automated email warming tools are strictly prohibited (see Third-Party Cold Email & Warming Tools).
Still Need Help?
If you've followed these steps and are still running into trouble, check our Purelymail Support guide.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article