In this case, an extraordinarily unusual confluence of two unrelated issues were happening at the same time. Since the E-junkie Admin logins were disabled due to the other issue unrelated to your USPS rate issue, we could not log in here to post any notices nor reply to your own post about the USPS issue until the login issue was already fixed.
Fortunately, we had already laid the most difficult groundwork anticipating the USPS change they'd announced for May, knowing they'd burnt us on rollout dates in the past; thus, when we saw your forum post and realized they'd sprung it on us unannounced yesterday without any warning whatsoever, our Development team was able to implement the final integration with the rest of our system and roll out an update fairly quickly while continuing to test and tweak details on-the-fly.
Normally, if they'd adhered to their published update schedule, we could be at the ready the moment they switched over, to finalize the integration and make the usual assortment of final adjustments (since what we actually get to work with is often slightly different than what was promised and documented in advance). Sometimes they even provide a testbed version of the new API available for us to interface with and test in advance, but even that may not be quite what they wind up rolling out. We pretty much have to work with what we're given, no matter how much more and better we may want from any third-party service, and this time we got even less cooperation than usual along with a few nasty surprises, so seat-of-the-pants time it had to be, however much we'd wish otherwise.
