Skip to content
Bexxo Help

Help PhishTrainer Setup

Allow simulations in your email system

For administrators PhishTrainer Updated on 18 November 2026

Have your email system recognise PhishTrainer simulation emails, whatever your filtering solution, so that they reach your employees' mailboxes without being blocked or treated as a real attack.
On this page
  1. Why allow simulations
  2. The authorisation header
  3. The rule to create
  4. Sending IP addresses and domains
  5. Guides by solution

Why allow simulations

Anti-spam and anti-phishing filters, mail gateways and reporting tools do their job: a simulation email looks like phishing, so they may block it, quarantine it or classify it as junk. An email the recipient never sees measures nothing: the campaign is skewed.

Your IT department therefore declares PhishTrainer simulations as allowed. Several solutions exist, each with its own console, but the principle stays the same.

The authorisation header

PhishTrainer adds a header to every simulation email of your organisation:

  • its name is X-PhishTrainer-Auth;
  • its value is a secret specific to your organisation.

The header is present whether the email is sent through a Bexxo sending profile, your own profile or your organisation's agent. Simulation text messages do not carry it.

The name and value are shown in the portal, My organization › PhishTrainer › Spam filters, with the PhishTrainer Administrator role.

Keep the value confidential: anyone who knows it could pass an email off as an allowed simulation. Only click Regenerate in agreement with your IT department: until its rules are updated, new simulations are no longer recognised.

The rule to create

In your solution, your IT department creates a rule whose condition is: the X-PhishTrainer-Auth header is present and its value is exactly that of your organisation. Emails that meet it are then treated as allowed simulations:

  • they bypass anti-spam and anti-phishing filtering, and quarantine;
  • their links are neither rewritten nor opened in advance by a scanning tool, if the solution allows it: an automatic opening can skew the campaign results;
  • they trigger no security alert or incident;
  • in a reporting tool (the email system's report button, the mailbox where employees forward suspicious emails), a reported email carrying the header is recognised as a simulation, not as a threat to handle.

Depending on the product, this rule is called a content rule, mail flow rule, policy or exception, and each setting sits in a different place: follow your solution's documentation. Once the rule is in place, run a small test campaign to a few addresses to check that the emails do reach the inbox.

Sending IP addresses and domains

Some solutions also, or only, allow simulations by their sending IP addresses and domains: this is the case with Microsoft 365. If your solution allows it, combining the header and the IP addresses makes the rule stricter. For the sending profiles provided by Bexxo, the values are as follows.

Sending domains
Sending IP addresses

If your campaigns are sent through your own sending profile (always the case when your organisation's encryption is enabled), the domains are still those of the links to the landing pages; add the ones your simulations use as sender. The IP addresses only apply if your profile uses Bexxo's sending servers; otherwise, declare those of your SMTP server. The header stays the same.

Guides by solution

Microsoft 365 has its own step-by-step guide, with the Defender screens. For another solution (Google Workspace, Proofpoint, Mimecast, Hornetsecurity, SEPPmail, Cisco, etc.), apply the rule above by following the vendor's documentation; our support can help you.

Allow PhishTrainer in Microsoft 365 DefenderAllow PhishTrainer in Microsoft 365 DefenderManage sending profilesSet up a sending profile

Didn’t find the answer? Contact us