EmailBot

2,350 servers

Moderation and Tools #email #mail #moderation #security #verify

About EmailBot

What it does

A user runs /verify, enters their email, the bot sends a 6-digit code, the user types it back, the bot assigns whatever role you set. That's the flow.

I originally built it for university servers and employee groups. Most of the servers that use it now are something in that family — places where the admin wants to know members are actually who they claim to be.

What you can configure

Allowed domains with wildcards: @gmail.com, @*.edu, @*.harvard.edu, comma-separated if you want several. Skip this and any valid email is accepted (your blacklist still applies).

Different roles per domain — for example @students.uni.edu gets a Student role and @staff.uni.edu gets Staff. Stack with default roles given to all verified users.

Blacklist with wildcards to block tempmail and specific addresses.

Allowlist (Pro): upload a CSV of specific addresses for invite-only servers. Only those exact addresses can verify, regardless of domain.

Other settings: auto-verify on join, optional unverified role for channel-locking, custom message inside the verification email, log channel for verification events. 10 supported languages.

Free for most servers

Every server gets 25 verification emails per month. Looking at usage stats from the past few months, about 95% of servers send 25 or fewer per month, so for nearly everyone, the bot stays free forever. No card on file, no signup.

If you do approach the limit, the bot warns at 80% and 95% before sending pauses at 100%. Notifications go to wherever you've set error notifications (server-owner DM by default, or a channel you pick with /set_error_notify).

Paid options

For the busier 5%, everything runs through Discord's native subscription system. Click any Premium button in /premium status to see prices and buy. Discord handles billing, refunds, and cancellations.

Standard subscription: unlimited verification emails per month, plus premium delivery via Zoho ZeptoMail (EU-hosted, transactional-only — that's a deliverability win because the IP reputation isn't shared with marketing senders).

Pro subscription: everything in Standard, plus CSV import (uploadable allowlists) and CSV export (download all verification logs).

Credit packs: one-time top-up of 100, 500, or 2,000 verifications. No expiry, roll over month to month, only consumed once your free 25 are used.

CSV unlock: one-time purchase if you want only the CSV features without a subscription.

Important: purchases attach to a specific server, not your account. After buying credits or the CSV unlock, run /premium redeem in the server you want them applied to. They become permanently bound to that server. Subscriptions automatically apply to the server you select at checkout — pick carefully.

Privacy

Email addresses are stored only as MD5 hashes, same scheme for verified users and the allowlist. Plaintext exists only at the moment of sending the verification code. SMTP runs over TLS/STARTTLS with DMARC/SPF alignment. /data delete removes your own data; admins use /delete_server_data for the whole server.

Full privacy policy (German Datenschutzerklärung) and Impressum on the website. Operator runs as Kleinunternehmer §19 UStG.

Open source

Source on GitHub under GPL-3.0. Self-host with monetization turned off if you'd rather run your own instance — toggle in config/config.json. I've been running and paying for the public instance personally for the last five years; the paid tier is how that stays sustainable long-term.

Getting started

Invite the bot, then run /role add to pick the role given to verified users. That's the only required setup.

Optional: /domain add to restrict by domain, /button to drop a verification button in a channel. Run /help inside Discord for the full command list.