Lots of response to the issue of HTML e-mail only being supported via Exchange Activesync/Direct Push when paired with Exchange Server 2007.
I’ll admit right away that I was being a smartass when I suggested bouncing your e-mail out to a secondary POP account to get HTML e-mail on your handheld.
Right now, if you want to get HTML e-mail on a Windows Mobile 6 device OTA from your Exchange 2003 mailbox, you can always leverage IMAP to make it happen.
In other words, you’d set up your Exchange server and WM handset just like you were setting up to support The Almighty iPhone.
Which should explain the photochop above.
If you absolutely, positively, have to have HTML e-mail for your Exchange 2003/WM6 environment, then you can setup this insanely jackleg kind of configuration. Only for those who are not faint-of-heart. I’ll also admit this is a Mount Everest doc effort…simply because it’s there.
- Follow Q and Dr. Codec’s excellent IMAP setup for SBS with SSL article.
- Add a new e-mail account to your WM6 device.
- Name the account something like Outlook IMAP.
- Configure the account to use IMAP4, and use the public FQDN of your Exchange server as the Incoming mail server.
- Use DOMAIN/LogonID for User name. Be sure to check Save password.
- The Outgoing (SMTP) mail server value may be pre-configured by your mobile operator. Changing this value may stop your WM6 device from successfully sending e-mail, so document the supplied server name before making any modifications in case you need to reverse your changes.
- Set the Outgoing (SMTP) mail server value to the public FQDN of your Exchange server. Select both checkboxes. Under Advanced Server Settings, select both SSL checkboxes, and verify that the Network connection is set to the correct interface/service.
- There is no IMAP IDLE command supported by WM6 for push functionality, so set the desired Automatic Send/Receive interval, plus the amount of past messages you want to download.
- Under Advanced Settings, set your desired send/receive, roaming, and message deletion behavior.
- Set Message format as HTML (so you aren’t doing all this for nothing). Set your desired message download limit and attachment download behavior.
Point of fact…
You could even leave e-mail coming in over Direct Push, if you want, and if you don’t mind the triple-threat memory/bandwidth/space hit. That way you’d get the best of both worlds.
I’m not that desperate for HTML e-mail.