Articles in this section

Creating a Connector in Microsoft 365

NOTE: The following method of safelisting has been deprecated as of 09/01/2021. You will want to implement the new Advanced Delivery rules for Microsoft 365 clients. If you implement the new rules and still experience bounced/deferred emails, follow the steps in this article. 

Overview

A connector can be used to help deliver emails in high volume campaigns. If you are experiencing deliverability issues in Microsoft 365, you may need to configure a connector. This step can help bypass graylisting, which Microsoft has implemented on PhishingBox simulated phishing emails (for more information on graylisting, see article: Fix email delivery issues for error code 451 4.7.500-699 (ASxxx) in Exchange Online).

Create a Connector

Follow the steps below to configure a connector in Microsoft 365:

  1. Navigate to admin.exchange.microsoft.com.
  2. Expand Mail Flow and click "Connectors.
    mceclip0.png
  3. Click the 'Add a connector' button to start the New Connector wizard.
  4. Connection from: Partner Organization.
  5. Connection to: Office 365
  6. Click "Next".
  7. Name: Enter a descriptive name for the connector, such as 'PhishingBox Connector'. Adding a connector description is optional.
  8. Ensure the Turn it on checkbox is checked.
  9. Click "Next".
  10. Click the 'By verifying that the IP address...' radio button.
  11. Add all necessary IP addresses. PhishingBox mail server IP addresses are below:
    • US - Phishing and Training Mail: 64.191.166.196, 64.191.166.197

    • US - System Mail: 69.72.47.194

    • EU - Phishing and Training Mail: 64.238.34.10, 64.238.34.11, 64.191.166.197

    • EU - System Mail: 161.38.205.202

      mceclip5.png

  12. Click "Next".
  13. Ensure the 'Reject email messages if they aren't sent over TLS' checkbox is checked.
    mceclip6.png
  14. Click "Next" to navigate to the last step.
  15. On the final page, review the connector's settings and click Create connector to enable the connector.
    mceclip7.png

Back to top

Was this article helpful?
0 out of 0 found this helpful