Kids, kids, kids. <<RELAX>>
Code doesn't just mysteriously start acting differently. It does what you tell it to do, plain and simple. Crying that MailEnable's code just "broke" out of the blue it is a Tell Tale sign of a rookie/armature (note, there is NO negative tone here).
This is a fact: something changed. Period. Now, once you get your head wrapped around that concept, examine what might have changed on your environment. MailEnable suggests that the ms03-039 patch may have broken their code and that they are validating it.
3. The "419" permission error is most likely the result of a security update released by MS last Thursday: http://www.microsoft.com/security/secur ... 03-039.asp
This would explain why systems that were working have suddenly started experiencing issues. We are also validating this.
I'm not saying that Microsoft's code doesn't work. Quit the opposite, actually- I'm a huge MS supporter; they have the best products on the market right now. The patch could very well have broken ME's code or their security model. That's ME's problem to deal with and they are in fact dealing with it, so cut them some slack.
My point was this and this alone: test every single change that you make to a production environment. If you chose not to, that's fine-- just be prepared to live with the consequences.
Finally, before you go off on another 500 word temper tantrum, RBogan, I'm sure you're a great IT person. If you feel that my suggestion to test things before implementing them was a personal insult to you, them I'm sorry. Here, in fact, let me give you a hug. <<HUGG>> There. Itâ€™s alright. Everything is better.