As of late (the last 2 weeks or so), we've been seeing mail being delivered to various xtra SMTP MTA servers (as we've been doing with these addresses for years), being accepted OK, but never getting delivered at the remote end.
Through an exhaustive process-of-elimination, we've been able to ascertain that there's no issues with our servers or DNS (not black-listed, SPF is OK, DKIM, VBR, etc, etc all OK), nothing wrong with the servers located on customer's site (same server running as-is for years now; no new changes affected for some time), which only leaves the bit in-between: xtra/telecom servers
From what I can gather, they're implemented some new, additional, internal anti-spam measure, without informing anyone, and also not acknowledging anything going wrong on their end (of course)
This is not yet a crisis, but still VERY annoying.
From chatting to some folks, it seems that recipients are to go onto their xtra "webmail" & whitelist senders or domains that they want to allow through (which is obviously not practical on SO many levels; keep in mind that some recipients that have a local server/client have not been on their webmail in YEARS), or the senders need to complete some sort of application to be submitted to xtra for whitelisting (...I thought that's what DNSBL & RBL is for...)
From a sending SMTP server's perspective, as far as I'm concerned, if I initiate an SMTP connection, go through the motions of delivering a messages & get a 200-series (220/221/250) "delivery-OK" response back, the message is delivered & no longer my concern.
Hope this helps someone & spares them the frustration we had to endure
- J