> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Mailprotector

> Let Neo agents allow and block senders, release held mail and keep Mailprotector users and user syncs up to date

Mailprotector is an email security service for MSPs: CloudFilter filters each customer's mail, Bracket encrypts it, SafeSend protects outbound mail, XtraMail keeps mail flowing in an outage and SecureStore archives it. Each of your clients is a Mailprotector customer. Connect it, and Neo agents can change a customer's allow and block lists from the ticket, release mail the filter held, and check why a new user is missing.

## What Neo can do with Mailprotector

* **Sender rules:** allow or block a sender address or domain for one user, a domain or a whole customer, and remove a rule
* **Quarantine:** find the email a user is missing, see why it was held, and release it
* **Message logs:** show whether a message was delivered, held, bounced or never arrived
* **User sync:** read each domain's user sync and its last and next run, turn it on, set how often it runs, and add a new user who cannot wait for the next run
* **Users and domains:** find a user by address, and add or change users, groups, aliases and domains
* **Services and settings:** read and change each group's products and each level's settings, and read statements

See [Mailprotector API](https://docs.neoagent.io/agents/tools/security/mailprotector-api.md) for the permission groups.

## Your customers are mapped to companies

Neo matches your Mailprotector customers to the companies in your PSA and keeps the mapping on the Mailprotector card's **Organization Mapping** tab, refreshed on each PSA metadata sync.

Matching uses the customer name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Next comes one of the customer's mail domains that matches a company's website. Last comes an AI match for the long tail.

**A name match, or one you confirm, is handed straight to your agents.** A domain match or an AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it.

Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync.

On a ticket, an agent works in Mailprotector only on the customer mapped to the ticket's company. A company with no mapping that agents can use gets no Mailprotector calls until you set or confirm one on the tab. Agents with no ticket, such as a chat or a scheduled report, reach every customer.

## Running a user sync now

A user sync runs on its domain's schedule. Neo turns the schedule on and sets its interval, and reads when the sync last ran and runs next. To run a sync at once, a technician opens the domain's **User Sync** tab in the Mailprotector Console and clicks **Sync & Save** under **Manual Sync**; the agent tells the technician this when a ticket cannot wait, and can add the user directly in the meantime.

## Next steps

> [card] [Connect Mailprotector](https://docs.neoagent.io/integrations/mailprotector/connecting-to-neo.md)
>
> Copy a reseller role's API key and save it in Neo with your Reseller ID.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.