Skip to main content
The common use is a ticket that asks to allow or block a sender: the agent finds the user or the customer the ticket is about, adds the allow or block rule at that level, and releases the mail the filter held when the ticket asks for it.
Automatically enabled when you configure Mailprotector permissions in your agent workflow.

What It Does

  • Add and remove allow and block rules for a sender address or domain, for one user, a user group, a domain or a whole customer
  • Read the quarantine at every level, with why each message was held, and release chosen messages
  • Read message logs: whether a message was delivered, held, bounced or encrypted, and why
  • Find a user by address, and add, change and remove users, user groups and aliases
  • Read each domain’s user syncs and their schedule, turn a sync or its schedule on, and set how often it runs
  • Read and change services (Bracket, SafeSend, SecureStore, XtraMail), domains and mail routing, settings and managers, and read statements

Permission Groups

Neo always asks a technician before it deletes a customer, a domain or a user group, turns a service off, or sets a password or secret, whatever the group’s approval setting. It never releases a level’s whole quarantine at once, and never deletes your reseller account. On a ticket, the agent works only on the Mailprotector customer mapped to the ticket’s company.

Setup

See Connecting Mailprotector to Neo.