Inbound Email Filtering
Route incoming email through JetEmail to block spam, phishing and malware before delivery. Send filtered mail to your existing server, an application or another mailbox.
Review and release quarantined email
If a legitimate message is held, you can see why, release it and allowlist the sender from the same screen.
Each result shows the sender, recipient, subject, status and filter results. Release the message normally, or release and allowlist the sender so future messages are not held.
Account logs
Let mailbox owners manage their quarantine
Digest emails and limited portal access let users release their own messages without giving them access to the rest of your account.
Digest emails
Send each mailbox owner a daily, weekly or monthly summary of their held mail. Messages can be released directly from the digest.
The end-user portal
Portal access is limited to the user's own quarantine, sender lists and digest schedule. They cannot see other mailboxes, billing or domain settings.
Create rules for known senders
Allow, block or quarantine mail based on a sending domain, address, IP or subject. Rules can apply to one domain or every inbound domain on the account, and hit counts show which rules are still being used.
Create an allow rule to bypass spam filtering, or a block rule to reject specific emails — across every inbound domain on your account.
| Action | Name | Status | Conditions |
|---|---|---|---|
| Allow | Known suppliers Bypass filtering for domains we buy from | Enabled | 4 senders |
| Allow | Internal monitoring Alerts from our own systems | Enabled | 1 sender1 IP |
| Block | Parcel-tracking lookalikes Recurring phishing pattern | Enabled | 3 senders1 subject |
| Block | Retired campaign range Old marketing IPs, now reassigned | Disabled | 1 IP |
Choose where filtered email goes
Select SMTP, Webhook or Forward when you add a domain. Each domain uses its own delivery type and settings.
SMTP
Relay filtered email to your existing mail server.
Add up to four SMTP servers in priority order. If every server is offline, JetEmail acts as a backup MX by queuing incoming messages and retrying delivery when a server is available again.
Webhook
Send inbound email to your application.
Add an HTTP or HTTPS endpoint and JetEmail posts the email data when a message arrives.
Forward
Route addresses to external mailboxes.
Create individual address or catch-all rules, then verify each destination before mail is forwarded.
DNS Configuration
Add these records to your DNS provider, then click Check DNS to verify.
Host
acme.com Value
smtp.jetsmtp.netHost
je1._domainkey.acme.com Value
inbound.jetsmtp.netHost
acme.com Value
v=spf1 include:inbound-spf.jetsmtp.net -allHost
_dmarc.acme.com Value
v=DMARC1; p=noneForwarding domains publish MX, DKIM, SPF and DMARC records. The dashboard checks each record before accepting mail.
Set the destination, then update DNS
For SMTP delivery, add up to four destination servers in priority order. For Webhook, enter the endpoint URL. For Forward, create address or catch-all rules and verify each destination.
Once the destination is ready, update the DNS records shown in the dashboard. Existing mailboxes, clients and outbound sending stay unchanged.
If JetEmail is relaying to an existing server, restrict that server to inbound connections from the JetEmail network. Microsoft 365 and Google Workspace use an inbound connector; cPanel, Plesk, Postfix and Exim use a firewall rule.
- SMTP supports up to four destination servers
- Forwarding supports individual addresses and catch-all rules
- Released messages use the domain's selected delivery type
Trusted by
Frequently asked questions
Set up inbound filtering
Create an account to add a domain. If you manage email for customers, contact us and we will help with the setup.