10-03-2012 08:29 PM
10-04-2012 07:41 AM
10-04-2012 08:12 AM
I don't have the option at the moment to upgrade our Exchange Server at work. This is partially fixed as far as I can tell. I installed the update, rebooted, tried email, got a Red X but no duplicates... removed that account from the PB, rebooted, then added it back in... still get a Red X but no duplicates.
Looks like those red X's might cause a problem though... I have three of them on my screen now, sending from my Exchange account to various accounts and I have not received the last email I sent to another internal Exchange account from my Exchange account.
Pretty annoying. I am the ONLY person at work now that stands up for RIM and I happen to be the IT manager. I am starting to look like a fool for doing so. I'm not sure I trust that BB 10 will be worth the wait any longer.
10-04-2012 08:15 AM - edited 10-04-2012 08:19 AM
One more update. I just checked my BB Phone and see the last message I sent to an internal Exchange account from my Exchange account and it was received, one of them was not. Neither show up on my PB. I'm pretty annoyed at this point...
10-04-2012 03:12 PM
Now I don't get email duplications, but while that matter is solved, now I can't send emails at all on my exhange account! Just get a red x. I receive emails fine. I have rebooted and recreated accounts. Now just frustrated. Gmail account works fine.
10-05-2012 12:22 PM
One more update. My Exchange account is sending all the emails, with no duplicates but there is that red "x" that comes up everytime. The message I thought hadn't gone through was actually caught by my spam filter. :-)
I'm not sure what that red X is all about, but it is better than sending out multiple emails. Not quite there, but better...
10-06-2012 02:29 PM
I'm getting the same as everyone else, no more duplicate sent emails, but two sent items showing, one with a check mark, one with a red X. Receiving emails normally. Using Exchanger Server 2007. I can live with this, but still very disappointing that this used to work perfectly, an upgrade screwed it up, and months later RIM still can't fix it.
10-06-2012 02:35 PM