debugging Rogers verified email sending issues - problem solved?

So I have a secondary account, lets call it sendexample@rogers.com, that I use as the login credentials for the SMTP server when sending from my own domain.

This is the way I have always had sending set up for my domain in Entourage.
I never touch the sendexample account, I don't think it can even receive email.
I never log in to it.

When I verified my own domain email, I verified it under a different secondary account, let's say I verified foo@example.com under secondaryexample@rogers.com

It appears this approach may be what is breaking Rogers verified email sending.
It appears that Rogers will only accept sending if

1. You have verified the email from within one of your accounts, using the steps they provide.
2. When you send the email, you use THE SAME ROGERS ACCOUNT under which you verified, for your SMTP authentication.

If I use any account other than the one under which the address was verified, including sending using my primary account credentials, the message is rejected with a 553 error.  I assumed that sending using ANY of my accounts would work, and as well I assumed it was a hierarchy, with the primary account being a master for all others, but this does not appear to be the case.  While you may appear to have a "global" set of Rogers accounts in some views online, not in this one.

I suspect many people may be in this situation, whether they verified under their primary account but send using secondary account credentials, or vice-versa.

So in summary:
If you have logged in as secondaryexample@rogers.com, and verified foo@example.com,
you must use user: secondaryexample, pass: (secondaryexample password) for SMTP verification or it won't send.

I'm guessing that earlier this month they were only partially set up, so people were round-robining to a server that wasn't checking for verified emails and that was what was enabling them to send after multiple tries.

Previously:
May 28, 2008  Dear Rogers: Go 553 yourselves