About a year ago I tried tackling getting our ActiveSync from our Exchange server working with my AT&T 8525. At that time we were in no position to alter Exchange settings and we run out OWA service on a non-standard port. The ActiveSync client has no way to specify a port other than 80 for HTTP or 443 if you are using SSL.
Flash forward a year and it's now working seemlessly after an executive in our company bought an iPhone2 and demanded that it work with our Exchange 2K3 server. So we bought a cert from Verisign, opened up SSL and bam, it all worked. For his phone, mine and a couple others in the company.
The latest "undocumented feature" I'm looking at is Outlook Messaging notifications on my phone. I have a rule that takes emails destined for our department (most of them high priority) into a subfolder of my Inbox. Anything addressed directly to me stays in my Inbox folder. Now here's the part that is bugging me.
As long as the message isn't filtered to a different subfolder and comes straight into my inbox folder, I get the notification (audible and visual) I expect. If the message is filtered into any of the subfolders, I see the folder label go bold, indicating a new message has arrived, but I get no audible or visual notification at all. It only notifies me if something lands in my Inbox. All other messages show but no alerts.
I read on an iPhone forum where they were having a similar problem and on some other forums users report similar experiences with WinMo devices such as the Blackjack and other phones.
Clearly, it appears to be a shortcoming of Outlook Messaging on WinMo. My question is; is there a registry edit or possible solution to make Messaging on ActiveSync give a notification even if the message gets filtered into a subfolder?
I've seen people workaround the issue by disabling filters when they are not at their desktop so that all message come to the inbox of the phone, then reenable the rules when they are at their desktop. While this would work, it's a clunky solution IMO.
Has anyone ever found a workaround to this? Is this shortcoming fixed in WinMo 6.1? I'm running WinMo6 VP3G AT&T Official ROM (for over a year and still happy with it!)
Thanks for any insight.
As I said before, I never repeat myself.
Ph: Cingular Branded 8525 (Herm. 100)
Rom: Build 19922.214.171.124 PV DVH
SPL: 2.10 Olipro