Frequently asked questions

Spamjadoo is deployed as the primary MX for your domains. Inbound connections reach a Spamjadoo node first, pass the handshake checks, and accepted mail is relayed to your existing mail server (Exchange, Google Workspace, Zimbra, Postfix, anything that speaks SMTP). It can be hosted by us, or run on your own hardware or virtual machines.

Provisioning is done within one business day. Cutover is a single MX record change on your side and takes effect as your DNS TTL expires.

Nodes scale horizontally. A single node on ordinary cloud hardware handles millions of connection attempts a day, because most are refused before any message is transferred. ISP deployments run clusters of nodes behind equal-priority MX records.

Yes. Spamjadoo sits in front of either and relays accepted mail to it. Google Workspace needs its inbound gateway setting pointed at Spamjadoo so that it trusts the relay; see the integrations page.

JMail is Spamjadoo's system of rule-bound email aliases. Each alias is a real address that forwards to your mailbox under conditions you set: who may send to it, until what date, how many messages. Give a different alias to each website or supplier and your real address is never exposed.

Revoke it. Mail to a revoked alias is rejected at the handshake with a 550, so the spammer learns the address is dead and your mailbox never sees it.

No. Plus addressing (you+shop@example.com) exposes your real address and cannot be revoked or bound to a sender. JMail aliases are independent addresses with their own policy.

During the SMTP conversation the server evaluates the connecting IP, greeting, envelope sender and recipient, and answers with a permanent 550 error before the sender is allowed to transmit the message body. The message is never accepted, stored or scanned.

Fewer than content scoring, because each rejection is tied to a checkable fact (blocklist entry, non-existent recipient, SPF failure) and the sender receives the reason in their bounce. A legitimate sender can see and fix the problem. A message dropped into quarantine by a content score gives the sender nothing.

Yes, on the traffic that passes the protocol checks. Spamjadoo runs SMTP-level antivirus, Bayesian classification trained per deployment, and DKIM and DMARC verification on that remainder.

Yes. Every threshold and action can be set per domain, per IP range and per user, which Spamjadoo calls class of service. An ISP can run strict rejection for consumer mailboxes and a softer policy for a business tenant.

Yes. Spamjadoo advertises SMTPUTF8, normalises domains to punycode before DNS checks, and applies full policy to EAI mail in any script.

Hosted plans include email support during Indian business hours. ISP, MSP and enterprise licences include a named engineer and 24x7 escalation.

Yes, a one-month hosted trial on your real traffic, with no card required. Keep your existing filter running behind it and compare results.

Hosted nodes are in India by default. On-premises deployments keep everything inside your perimeter.