Built for the mail server, not just the mailbox.

Thousands of tenant domains, one policy engine, and most of the junk refused before it costs you a byte of storage.

Why providers care about where the rejection happens

At provider scale, accepted spam is a storage, backup and support cost before it is a filtering problem. Refusing at the handshake means the quarantine your support team has to explain is a fraction of the size, and the disks fill with mail customers wanted.

Per-tenant policy, one console

Every domain gets its own class of service: blocklists, greylisting, rate limits, attachment rules and quarantine behaviour. Consumer domains can run strict rejection; a business tenant with badly configured suppliers can run softer policy. Resellers get delegated access to their own domains.

Abuse desk and feedback loops

Complaint feedback loops from the large receivers are ingested and mapped to the originating customer. Outbound rate limits per account and per IP keep a single compromised mailbox from putting your ranges on a blocklist. Blocklist status of your own ranges is monitored and alerted.

Deployment shapes

Cluster of Spamjadoo nodes behind equal-priority MX records, relaying to your mail stores.
Hosted by Spamjadoo, with your MX records pointing at our nodes and relay back to you.
Hybrid: hosted for overflow and disaster recovery, on-premises for normal traffic.

Recipient validation at scale

Live lookups against your provisioning database (LDAP, SQL, cPanel, or an SMTP callout) mean unknown recipients are refused at RCPT TO. No accept-then-bounce, so your ranges never generate backscatter.