Antispam for organizations with many divisions

Give each division its own admins, rules and protected identities while your central IT team keeps one view of every domain. SpamFoo runs on servers you control or on an isolated instance we host.

01Policies

Set rules once for the organization and let each division add its own

System admins set rules that apply to every domain on the server. Each division's domain admins add rules and protected identities for their own domain. Users keep their own Spam Rules, and their corrections apply only to their mailbox.

  • Server rules for the whole organization
  • Domain rules and protected identities for each division
  • Personal rules and corrections for each user
Server rules, set by central IT
Emails from bulk-mailer.exampleSpam
Senders in 203.0.113.0/24Spam
Emails from payroll-partner.exampleNot spam
Applies to
Every domain on the server
Domain rules for retail.northwind.example
Emails from shelf-supply.exampleNot spam
Emails from deals-daily.exampleSpam
Protected identities
Pat Jones · Division president
Accounts Payable · ap@retail.northwind.example
Dana's Spam Rules
Emails from trail-outfitters.exampleNot spam
Trained Rules from Dana's corrections
Emails from rewards-desk.exampleSpam
Emails from maplestreetrx.exampleNot spam

02Dashboard

Each division's admins see their own domain

Central IT sees every domain and can open any division's view. A domain admin sees the domains they manage, with totals for each mailbox rather than the messages. Staff see only their own mail.

03Where it runs

Fits the way your divisions already run mail

Divisions can share one mail server with a domain each, or run mail servers of their own. SpamFoo Client runs on Windows, Linux or Docker next to each mail server or on another server you control. A division that would rather not run it can use an isolated instance we host in the region it chooses.

Each mail server that runs SpamFoo has its own license, and every license is listed in your SpamFoo account.

04Availability

Filtering that doesn't depend on a connection to us

SpamFoo's checks run on your own servers. If a server loses its connection to SpamFoo's online services, it keeps checking mail with the models and lists it already has, and picks up new updates once the connection returns.

If your organization needs more than one SpamFoo server, tell us how your mail is laid out and we will plan the deployment with your team.

  • Checks keep running without internet access
  • Health and readiness checks your monitoring tools can watch
  • Model updates are normally applied without restarting the service
  • No GPU or outside AI service required

Questions from larger organizations

Can each division have its own admins?

Yes. SpamFoo follows the system admin, domain admin and user roles in your mail server. A domain admin manages rules and protected identities for their domain, and one person can look after several domains and switch between them.

Can one division's admin see another division's mail?

No. A domain admin sees only the domains they manage. Even inside those domains, they see totals for each mailbox, not the messages.

Do all divisions have to use the same mail server?

No. Divisions can share a mail server or run their own. Each mail server that runs SpamFoo needs its own license, and you manage all of them from one SpamFoo account.

Do we have to change our MX records?

No. Your mail servers keep receiving and delivering mail the way they do today. They ask SpamFoo about each message and act on the answer.

Some of our divisions use Microsoft 365. Can they use SpamFoo?

Yes. SpamFoo for Microsoft 365 connects to your Exchange Online organization and checks mail in the mailboxes you choose.

Planning SpamFoo for a larger organization?

Tell us how your divisions and mail servers are set up, and we'll help you plan where SpamFoo runs and who manages what.