palm treo, windows mobile 5, pocket outlook, error synchronizing

We have a barracuda spam firewall, so our MX record simply points to our main external IP, and our checkpoint firewall has a rule set up to redirect and SMTP traffic to the barracuda spam firewall. It does appear any redirections are in place for POP3, so I am not sure how this was ever working. There is nothing in the NAT settings of the checkpoint that points any incoming traffic directly to our mail server. I can't imagine this was ever working...

Maybe he had the POP3 account set up only for sending (come to think of it, his pop3 inbox was empty). When i go to "Tools > Options", only the POP3 account is listed.

Are exchange accounts set up somewhere else on the device?

Ok, thanks for the link. It is already set up to receive by exchange (i didn't know that).

On the device, I am receviing the message "The security certificate on the server is invalid. Contact your Exchange Server administrator or ISP to install a valid certificate on the server.

Support Code: 0x80072F0D"

I can browse fine to it using Firefox, IE6, Opera, Safari 3 (Windows), and Google Chrome, without any security warnings.

One thing that just occurred to me, is that i am able to visit the site within our network, while it is resolving to a IP on our local network. Is an IP address part of the certificate? If so, how can I see what IP address it is using? Could the certificate have been requested with the local IP?

Here is the details fo the error message provided by Cingular Support:

This issue occurs because an intermediate certification authority (CA) certificate is not present on the device or on the Exchange Server server with which you are synchronizing.

Windows Mobile-based devices do not generally contain intermediate CA certificates in their certificate store. Internet Information Services (IIS) will send the whole certificate chain to the device. However, IIS will do this only if it can verify the whole chain. By default, the device does not contain these certificates. Therefore, the server must send them. The device must contain only the root certificate in its certificate store.

Frequently, this issue occurs with GoDaddy certificates because either the root CA certificate or the intermediate CA certificate is missing from the certificate store on the server that is running Windows Server 2003.

Frequently, this issue occurs with VeriSign certificates because the intermediate CA certificate in the certificate store on the Windows Server 2003 server is expired.


So it seems the root certificate that would validate a cert from ssl genie is not on the device right? How would I obtain that root cert?

Ok, I attempted to visit https://owa.myserver.tld/oma in my browser, and was presented with a security warning that the certificate was issued by a ca that i have not chosen to trust., then there were green check marks for the cert has not expired and the cert appears valid.

I have narrowed it down, it appears that the device currently doesnt trust sslgenie.com as a root authority. I am going to post a new question on how to configure it to trust the sslgenie.com certificates as the question is now much more direct, it should get more attention.