The ISP modems can or cannot block old legacy Email TCP SMTP port 25 (out email).
Your personal router/firewall is adjustable to any set of firewall rules you want.
Many folks utilize combination router/firewall/switch/wireless access point boxes.
Mostly the pieces to get to the internet are all the same.
ISP Internet ==> ISP configured Modem (router) ===> Ethernet
You can do anything you want with that Ethernet connection and mostly folks utilize a personally purchased or leased combination router (router #2), firewall, switch, access point combination box.
That saying if Email TCP SMTP port 25 is blocked on the modem; whatever you do with your firewall router box will not change this.
It started about 5-6-7 years ago.
Typically you cannot see all of the configuration of a modem.
A new modem will typically boot up, run TFTP and download the configuration for the box based on the service contract that modem has with the ISP.
These pieces configure your service to the ISP; IE: like packages you have or speed tiers.
Initially many ISP's just sent out emails to individual users that something on their network was sending out SPAM and due to that suggested to the ISP client to utilize something other that TCP SMTP port 25 for email after they had already changed the settings on the modem / router box.
They did offer alternative methodologies.
This whole fix of sorts did cause issues relating to personally owned modems as it was relating to changing basic service packages without telling the user; then a follow up message relating to spam (whether there was spam or not).
It did come to a legal civil suit case going though the court system some time afterwards (5-6 years ago?). Try to find it / google it and you will not see any records of said case.
The above said at the time of the changes I was still using multiple email services (including my personal email services). First level of support was typical. I escalated my support ticket to 2nd / 3rd level support mentioning the civil suit which was in process at the time. My TCP SMTP port 25 blocking was removed within hours of my calling support.
That was around the time I went to changing my email setups to using
STunnel on one box and routed emails via the utility.
This also relating to my Automation box software email stuff which quit working for a period of time.
A similiar issue recently (a couple of years back) came up with my Verizon FIOS account. You could set up multiple email account but for whatever reason the spam block pieces of the sub accounts had been disabled (you could see the feature though). I had to make an issue out of this in a legal sense and they did fix it.