Features / Inbound Antispam
Spam stops before your server
A dedicated filtering appliance is queried on every incoming message before it touches a mailbox: spam and malware are dropped upstream, included on every plan.
How it works, technically
When a message arrives for your domain, your mail server consults an enterprise filtering layer first: sender reputation, content analysis, malware scanning, and phishing heuristics score the message before delivery is accepted. Junk is rejected at the door rather than sorted into folders after the fact.
Doing this upstream has compounding benefits: mailboxes stay clean, storage is not wasted on sludge, and your server spends its cycles on real mail. The filtering layer learns continuously from traffic across the platform, so a campaign hitting one domain hardens the defense for all of them.
One message, filtered upstream
Position
Before your mailbox, at accept time
Checks
Reputation, content, malware, phishing
Learning
Platform-wide signal sharing
Cost
Included on every plan
FAQ
Inbound Antispam, answered.
Where does filtered spam go?
Clear spam is rejected at the connection, so senders of legitimate mail get a bounce they can see, and quarantined borderline mail remains reviewable.
Can I adjust the aggressiveness?
Per-domain tuning is possible: support can adjust thresholds, allowlists, and blocklists for your domains.
Does this replace mailbox-level filters?
It sits in front of them. Your own rules and filters still apply to what gets delivered; they just have far less junk to deal with.
Your server runs. You sleep.
Fully managed hosting from people who have been doing this since 2001.