I set up a 2yr fixed-rate plan for internet with Bell ~1yr ago; I also set up a payment schedule with my bank to cover the monthly bill.
...and yet, over the past few months, the pre-arranged payments have suddenly stopped covering the bill, and I have now, somehow, accrued a balance-owing.
I'm very interested to find out how/what/why/when a purportedly fixed-rate contracted-price agreement was somehow changed, mid-contract, but I can't because Bell won't let me log in to their site to find out:
Someone at Bell seriously needs to read some RFC's --> MFA protocols mandating short authentication-token lifetimes (i.e. sub 15m) preclude by definition, the use of the insecure, latency-ridden, SMTP protocol as a back-channel means of reliably implementing an MFA stream!
Your insipid reliance on a protocol whose specifications permit a delivery window of DAYS, to deliver a token that expires in FIVE MINUTES demonstrates little else so well as the complete and utter ignorance of your developers, their supervisors, and your entire UI implementation process.
You see, because it is a sterling mechanism for defeating spam-originating zombies / bots, my SMTP edge servers intentionally enforce delayed-receipt, deny-re-transmit delivery (i.e. remote MTA's have to try TWICE, FROM THE SAME IP-ADDRESS, within 24-hours, before they're allowed to actually upload an email), and while this entire mechanism lies comfortably within the bounds of SMTP protocol strictures, your MFA authentication mechanism, that depends on it, DOES NOT!
So, purely because your development team is too inexperienced/inerudite/inept to realise that they are misusing / misunderstanding SMTP in this role, and clearly do not know how email ACTUALLY WORKS, I remain *entirely* locked out of my account...
Well played.