port 25 unblock, Art of the (Business as Usual) Runaround, and "Is there anybody out there?"

I'm an Xfinity residential internet customer.

To me it's a simple pipe.
I don't use your email servers to send/receive.
I don't run any servers, or provide any servcies of any kind.

I do need to run diagnostics to services out on the 'net.

That includes the ability to connect to other mailservers on the 'net, to verify operation (e.g., telnet server.example.cpm 25) or grab/check an SSL certificate (e.g., openssl s_client --connect server.example.com:25 -starttls smtp).

That connection is from a simple command line shell.  It does not involve any email MTA, etc.

I'm unable to do so because Comcast/Xfinity blocks in/out-bound port 25 on IPv4/IPv6.
(Well, unable to do so without circumventing Comcast's network nonsense either via a vpn/tunnel, or just plugging into one of my other ISPs ...)

How do I know this?

(1) I can demonstrate it to myself

 shell -> Comcast connection -> any server @ port 25, no response.
 shell -> Comcast connection -> any server @ any other port, works fine
 shell -> OTHER ISP connection -> any server @ any port, works fine

i.e., only the port 25 connections over Comcast fail.

(2) Comcast SAYS that port 25 is blocked

 https://www.xfinity.com/support/articles/list-of-blocked-ports

and 

(3) says it AGAIN

 https://corporate.comcast.com/comcast-voices/updated-management-of-smtp-port-25   

 "In order to ensure a more secure network and email domain, Comcast will no longer by default allow access to port 25 for our RESIDENTIAL Internet users. In addition, we are asking comcast.net email users to migrate to port 465, which offers SSL encryption. We will continue to support the industry standard port 587."

AND then immediately continues that residential users can request an UNBLOCK,

 "Upon request to our Customer Security Assurance team this block can be removed, enabling access to use port 25 for other email domains, though the comcast.net email servers will no longer accept submission via port 25."


I called 

 COMCAST Customer Security Assurance @ 1-888-565-4329

They checked with their technical upstream, assured me that it could/would be done, and opened a Case (#IH XXX XXX XXX).

They informed me that I would need to contact the "Internet Essentials dept" (855-846-8376), give them the above Case #, "which contains all the information they need", to have the work done.

That wasn't successful.  After hours of runaround, I was sent BACK to CSA.

Who next transferred me back to Technical Support.

Rinse, repeat, for hours more.

Finally, in online chat, 'support person #8' (or thereabouts ...) FINALLY, in response to my request to:

 "Unblock port 25 access for my line/account.  Both in- and out-bound, both IPv4 & IPv6."

Answered,

 "I have successfully proceed the needful and it might take upto 60 minutes to unblock. that's the confirmation number CR Ticket #CRXXXXXXXXX"

3 hours later, still nothing.

I went back online, in the same chat, to ask, and was told,

 "As checked the ticket raised was not regarding unblocking the port 25. In order to check if the port can be unblocked I would suggest you to get in touch with our customer security assurance team at 1-888-565-4329 as they take care of such concerns and will help you out."

I.e., now at the ~9 hour, after countless phone calls & chats, mark, back to First Base.

So, one last time, I called CSA again.  As usual, they first provided their usual inistinctively knee-jerk "can't be done" response.  After I shared the above^^^ episode with them, they said "then we will transfer you to the right department" and ...

... wait for it ...

transferred be back again to Tech Support, with yet-another promised hold time of an hour or so.

I hung up.

Now I'm here.

My only question, "screaming into the void", is:

 IS THERE REALLY NOONE @ COMCAST/XFINITY THAT'S READY/WILLING/ABLE TO DO WHAT YOU PROMISE IN WRITING ON YOUR OWN WEBSITE, AND IN REPEATED CONVERSATIONS AND TICKETS?

I'm fully aware this is not an atypical experience @ Comcast/Xfinity support; it's reputation precedes it.

And I'm pretty sure I know the answer.  But thought I'd ask, anyway ...