My BlackBerry is connected to my home Exchange server using the BlackBerry Internet Service (BIS) via IMAP.  For the last couple of days, I've noticed that I wasn't receiving my email on my mobile device but everything else was working fine.

Unfortunately for me, I thought it was related to a bunch of environment changes I made earlier this week.  So I've spent quite a bit of time troubleshooting non-existent issues only to find that for some reason that is totally beyond me, the IMAP service on my Exchange machine had stopped.  I used the following PowerShell commands to sort out the issue:

• get-service (Gets a list of all services and their status)
• get-service MsExchangeImap4 (oh look, it's stopped)
• start-service MsExchangeImap4

I then doublechecked the status by opening up the Services Management Console and verified the service is still set to "Automatic" and is now running.  And now that I'm looking at it, there are a bunch of Exchange services set to "Automatic" that aren't running!  Jeez, time for a reboot...

UPDATE

... it seems that the services not running aren't the only problem.  I still wasn't able to connect until I lowered my IMAP and POP3 authentication settings.  What's happened here?  Why would this suddenly stop working?

The only explanation I have so far is that a couple of months ago I rekeyed my SSL certificate to a different name and for a different machine.  I created a Terminal Services Web Access machine so I could launch Outlook remotely, rendering my OWA setup + it's associated SSL certificate unnecessary.  Shortly after, I noticed this did cause a problem for my fiance who lost ActiveSync connection from her iPhone.  An SSL connection (thus certificate) is required for ActiveSync, but she didn't use it much anyway so it wasn't even an issue.  But why would it now refuse my IMAP connections?  It's been months!  I have a feeling I'm missing something but it's back up and running now and I have plenty of other things to do.

UPDATE 2009-06-11

I managed to really mess things up trying to solve this problem.  I fixed the IMAP problem above, but managed to create a much worse problem I didn't discover until later.  Thankfully, I've sorted it all out here:

http://www.bunkerhollow.com/blogs/matt/archive/2009/06/11/exchange-2007-edge-queue-4-7-5-certificate-validation-failure.aspx