I'm glad that it appears this issue has been resolved.  We have not done anything on our end as of this time that could be attributed to fixing this issue.  Hopefully it was just a glitch somewhere along the route that has gotten fixed.  

With that said, sorry for the late reply - we've been busy addressing some other items the past few days. If anyone is still having issues, please let me know.