On September 17, 2025, the A records for mxa.expurgate.net, mxb.expurgate.net, and their .de counterparts will be updated to match those of mxtls.expurgate.net.
Some customers are currently using MX entries that include additional hostnames alongside or instead of mxtls.expurgate.net. These configurations may cause issues with certificate validation or allow spammers to bypass filtering.
This change affects: - Legacy hostnames such as mxa.expurgate.de, mxb.expurgate.de, mxa.expurgate.net, mxb.expurgate.net, mxtls.expurgate.de. - Customer-specific mail server hostnames (e.g. mail.your-domain.com) listed in MX records in addition to or instead of mxtls.expurgate.net.
Recommended actions: - Remove all legacy hostnames from MX records to prevent certificate validation failures. - Remove your own mail server hostnames from MX records to avoid direct delivery that bypasses filtering. - Use only mxtls.expurgate.net in MX configurations. These additional entries are not needed for redundancy, as mxtls.expurgate.net is designed for high availability.
Note: mxtls.expurgate.net supports both encrypted (TLS) and unencrypted SMTP connections.
The rollout will be done gradually throughout the day.
If you have questions or require assistance, please contact our support team at support@eleven.de.
Posted Sep 10, 2025 - 09:33 CEST
This scheduled maintenance affects: my.eleven Cloud Email Security (Email Processing - Inbound) and eXpurgate.Cloud (Email Processing - Inbound).