MXroute @mxroute@freesocial.co
MXRBL has been rebuilt from base. Moved from PowerDNS to RBLDNSD for the RBL itself. Scales much better.
Though it’s impossible for us to actually know, we suspect that the correlation between your password ending in “123” and being terminated for repeat instances of poor password security is high. You are responsible for your passwords, we won’t tolerate a failure on this repeatedly.
Getting closer, we think. We're waiting for the devs of HostBill to get to us. https://community.mxroute.com/t/what-is-up-with-portal-mxroute-com/1923
Today several customers saw this message from Outlook: "Please contact your Internet service provider since part of their network is on our block list." You weren't supposed to see this, we were supposed to work around it and get the email there anyway. This is being investigated, and is presently mitigated differently during the investigation.
Emergency reboot on Longhorn to update server. (Emergency as it relates to immediate performance and reliability)
Longhorn server is presently unresponsive. Working upstream to resolve.
Working on Longhorn server
Rebooting Acadia, OOM. Wasn't expecting that considering how few tenants are on the box.
We tried to alert Microsoft to a huge portion of their Hotmail IPs having no reverse DNS: https://www.reddit.com/r/microsoft/comments/mmy345/microsoft_official_support_thread/h1ax762/?utm_source=reddit&utm_medium=web2x&context=3
They asked us to open a ticket. Couldn't make this stuff up.
Large portions of Microsoft's 40.92.0.0/15 range, if not all of it, seem to be lacking valid reverse DNS records. Can't reach anyone at Microsoft who can use this, but expect delivery issues with them due to failure to maintain their infrastructure.
QuadraNet is having a significant spam problem, moving around to new IPs constantly. We just blacklisted 192.161.188.0/22 and will review individual removal requests.
Today we experienced an issue with outbound mail for roughly an hour. The details are too extensive to go into here, but have been posted in our #postmortems channel at chat.mxroute.com.
This issue doesn't seem to be what it initially appeared to be. As we continue to work on it, this seems to have occurred when multiple multi domain certs were made. For example, selected Domain1 and made a cert for all domains, selected Domain2 and made a cert for all domains, selected Domain3 and made a cert for all domains. Now all 3 domains have 3 Dovecot SNI certs in conf files for each domain.
We believe we may have identified an issue with Dovecot's handling of multi-domain SSL certs. If you have one cert signed at once for more than one of your domains (for custom mail subdomain, for IMAP/POP/SMTP), Dovecot may continue to serve an expired certificate even after successful renewal. Investigating.
Eagle maintenance complete.
Planned maintenance on Eagle right now. Any inbound mail sent to the server during this time will be received when it comes back online.
Banshee server is set for emergency migration as soon as possible. We're looking at hardware failure but impossible to tell how much time we have. As long as it's functioning, we're going to keep it in production and aim for a seamless migration. This is an older cPanel box, not equal to our current hardware standards. It will be post-migration.
Rebooting Banshee again to satisfy vendor in troubleshooting KVM connectivity.
