Skip to content
Spamjadoo

Antispam that works in every language.

EAI-ready antispam software applies full spam-filtering policy, SPF, DMARC, blocklists, rate limits, to email addresses written in non-Latin scripts such as Devanagari, Arabic, Chinese and Cyrillic, not just ASCII addresses. Spamjadoo is built this way and applies the same policy to राम@डाटामेल.भारत as to ram@example.com; most filters, written when an address was seven-bit ASCII, are not.

What EAI changes

Email Address Internationalization (RFC 6530 to 6533) allows Unicode in both halves of an address. The domain half can be represented in ASCII as punycode and will resolve either way. The local part cannot: it exists only when both servers advertise SMTPUTF8. Read the glossary entry for the standards.

Where other filters fail

  • Reject the MAIL FROM as malformed and bounce legitimate mail from Indian-script domains.
  • Skip SPF and DMARC lookups because the domain was never converted to punycode before the query, so authenticated mail is treated as unauthenticated.
  • Score UTF-8 headers as suspicious because the training corpus never saw them.
  • Show mojibake in quarantine, so administrators cannot tell what they are releasing.

What Spamjadoo does

EAI session · illustrative 
C: EHLO mail.xn--11b4c3d.xn--h2brj9cS: 250-SMTPUTF8C: MAIL FROM:<राम@डाटामेल.भारत> SMTPUTF8     · domain normalised: xn--11b4c3d.xn--h2brj9c     · SPF: pass (ip4:203.0.113.0/24)S: 250 2.1.0 Sender ok

Every DNS-based check runs on the punycode form. Every policy, alias and class-of-service rule accepts Unicode. Logs and the console render addresses in their native script. The handshake rejection you get for an ASCII sender is the same for an EAI sender.

Why this matters for India

With .भारत and the other Indian-language top-level domains in production and government programmes putting email in local languages, EAI traffic is real inbound mail for ISPs and public-sector bodies. A filter that bounces it is a filter that bounces citizens.