Important Notification - Your action may be required The Reflexion infrastructure is undergoing a significant upgrade that will improve both performance and resiliency. After the upgrade, all services will continue to operate in our IP space 126.96.36.199/22, however some IPs will be repurposed. To avoid any disruption in email delivery, it is critical that all solution providers and their customers remove any static references to Reflexion IP space directly no later than Sunday, July 5th, 2020. This includes custom created DNS A-records to our MX or RELAY (smart host) entry points. In particular, 188.8.131.52 and 184.108.40.206 are commonly assigned directly by customers and should be avoided and corrected as soon as possible.
Applies to the following Sophos product(s) and version(s) Reflexion
Please reference the Quick Start Guide and make sure your MX and Smart host records are correct: https://tickets.reflexion.net/index.php?/Knowledgebase/Article/View/reflexion-quick-start-configuration-guide
Proper MX records should include ONLY the following:
asp.reflexion.net [Preference = 0]
mx-100.reflexion.net [Preference = 100]
mx-110.reflexion.net [Preference = 200]
(please remove any other values from your MX record or we cannot ensure proper handling of your inbound email)
(please remove any custom created A.CUSTOMERDOMAIN.COM records that mimic our A-records, the IP may change)
Outbound Smart host should only use the following value:
(please check your scanners, copiers, MAPI-clients for static IP settings, the IP may change)
Reflexion IP space reference:
220.127.116.11 /22 255.255.252.0
18.104.22.168 /24 255.255.255.0
22.214.171.124 /24 255.255.255.0
126.96.36.199 /24 255.255.255.0
188.8.131.52 /24 255.255.255.0
(can be referenced in multiple ways depending on limitations of network equipment or hosting provider)
We provide the Reflexion IP space to allow customer to make appropriate changes to their firewall settings to restrict email traffic to between Reflexion and our customers. It is imperative these IP addresses are not used for the purposes of routing email traffic. Only the specified host names for MX and Smart host should be used for routing traffic.
Last updated: 6/24/20 (no later date extended to July 5th, 2020)
This article will be updated when information becomes available.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. For technical support post a question to the community. Or click here for new feature/product improvements. Alternatively for paid/licensed products open a support ticket.