Thread: Mail for Exchange (MfE). Blame me here, pls
View Single Post
punto is offline punto
2010-04-02 , 23:34
Posts: 182 | Thanked: 40 times | Joined on Apr 2010
#1308
Originally Posted by labra View Post
Hi!

Now I managed to solve this. I added the cert to the certificate store. By going though the /home/user/ directory I found out that these certificates are put to /home/user/.maemosec-certs/ssl-ca/ -directory. The /home/user/.activesync/certs/ -directory does not have any symlinks to there. I manually symlinked the imported certificate from the .maemosec-certs/ssl-ca/ -directory to the activesync's directory, and it works!

(though it shouldn't be this hard)...

BR, Lari
Hi

Sorry if this has been asked before, but I'm a new N900 user and I haven't got a clue what the above means, or whether it would help in my situation.

I'm trying to get a cobbled-together Exchange setup working on the N900. I've successfully installed the self-signed cert but as pretty much expected given MfE's apparent dilligence for certs, it didn't work.

The problem is that the server is behind a dynamic IP address and the DynDNS service, fetching emails from another domain so the auto-assigned certificate points to another domain, so I guess the self-signed certificate for the server is invalid. I've actually tried to stick in a CNAME from the email domain, but that doesn't work either.

So putting it in a nutshell:

- Server fetches email addressed to foo.com via POP3
- Server's self-sign cert is for remote.foo.com
- .pfx Cert installed on N900
- Server is behind foo.dyndns.com
- Connecting to foo.dyndns.com didn't work
- Set up CNAME for remote.foo.com -> foo.dyndns.com
- Connecting to remote.foo.com didn't work either (works OK via web on the N900 after adding permanent exception)

How would I get MfE to work, if at all?
Last edited by punto; 2010-04-02 at 23:43.