It's not the BES that cannot re-establish the MAPI connection. The BES uses the MAPI subsystem wich generates MAPI worker threads. Once the Exchnage Server is restarted, new threads are needed as the old ones lose their session to Exchange.
It's not poor coding on RIM's side, Microsoft's side actually.
I like to complain about Microsoft, but compared to RIM, Microsoft is flawless.
Hahahahahaha, good one! Microsoft and flawless do not belong in the same sentance together. RIM is not perfect either, no software package is.
If you guys are always restarting GC/DC and/or Exchange then plan for it and do things right.
Quit complaining because a product does not work when not used properly. If you know that the BES needs to be restarted after an Exchange reboot then reboot the damn BES. Don't b*tch when it doesn't work and you know why.
If you're BES need to be restarted constantly and it's not due to a DC/GC/Exchange reboot then collect some logs and send them to RIM. If there is a BES issue they will find it.
If the issues are mostly due to DC/GC/Exchange reboots then maybe you should look into why you have to reboot those servers so much.
Sorry to be going off on you but when I see someone complaining about these things, it gets under my skin. It's like buying a car and driving it off a harbour and then complaining because it sinks.
Seriously though, if your BES are falling apart after a period of time start getting to the bottom of the issue. Call RIM or whoever you have to.
Look for patterns, time frames, there should be a commonality between all 5 BES, hopefully.
Let us know if you find anything or if you peform any testing. I'd like to know what is causing the BES isssues.