Re: Mail for Exchange (MfE). Blame me here, pls
 

Well, all of my other e-mail accounts display HTML properly, only MfE account does not... so that's why I ask in the MfE thread. :)

My co-workers with iPhones receive HTML email from the same server, I receive HTML email in Outlook Web Access and in Outlook proper.

Does someone else here use MfE with Exchange 2003 and receive HTML emails?

Re: Mail for Exchange (MfE). Blame me here, pls
 

Sorry if I'm repeating someone else's statement (I didnt read all 50 pages of replies), but:

it seems to me that MailForExchange IS working on the N900 (at least the Calendar syncing is). Is that not normal?

Re: Mail for Exchange (MfE). Blame me here, pls
 

what should i write into server and port columns?

Re: Mail for Exchange (MfE). Blame me here, pls
 

I have been able to sync the n900 with my ms exchange 2003 to sync email and contacts. When I tell it to sync the calendar it runs the sync but never finishes and hangs (appears to). The items never make it to the calendar.

Can anyone point me in the right direction for correcting this?

thanks
Tom

Update: I do have the latest firmware on the n900

Re: Mail for Exchange (MfE). Blame me here, pls
 

More info... If I look at the details I do see that 244 items have been added to the calendar, however the status continues to say synchronizing and never stops. If I stop the process the changes are lost and the items never get to the calendar. I am not sure what is hanging up the process.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Hi tomster,

thanks for the reply, how does one install it. I have added maemo extras in the application catalogs but cannot see it to download.

Excuse the ignorance. I feel like im back in the days of the Zaurus.

Eug

Re: Mail for Exchange (MfE). Blame me here, pls
 

I'm not at the phone right now. Could be that it's in extras-devel or extras-testing. pls. check there.

Re: Mail for Exchange (MfE). Blame me here, pls
 

If any of the Nokia guys are still monitoring this thread, can anyone tell me if there's still work being done to address 2003 connectivity issues? If so, is there any way I can help?

Also, is the source available for the exchange / activesync stuff, or is it proprietary? I could probably fix it. :)

Re: Mail for Exchange (MfE). Blame me here, pls
 

vitaly,

Excellent work on this, I see that the "server exists at a URL that contains more than just FQDN" issue I was seeing has been fixed in the 1.1 release, and I can certainly get further along, but I now see a new issue.

When I setup the account according to my workplace's EAS instructions, I get to the point where it's going to attempt the first synchronization when it reports that "Mandatory Exchange server policy failed. Access refused". What's got me going is that other (to my knowledge) non-provisionable devices work fine when syncing to the server. Following are some pertinent logs from my device and the server (sanitized for personal info)

From server:
From phone:
Note the HTTP 449 return code, which seems to be linked to provisioning, but as I said above, I am almost certain that non-provisionable devices work with the server.

Anyone seen something similar? vitaly, thoughts? Additional troubleshooting steps?

EDIT incomplete thought completed :)

Re: Mail for Exchange (MfE). Blame me here, pls
 

You need the extras-testing repo.
There's also a more hm. bleeding edge version in extras-devel.

There's more info HERE.

How to reset gconf settings...
 

So... I nuked my settings because MfE was hanging at one point (yes, I should have sent logs then) and I shut down the device. Since then, as-daemon was sucking my battery dry (I had tried to remove the account and that hung too, then later tried to remove the cal, and that hung too, etc... )

Basically, any time I was trying to add the account back in, it was hanging at about 80% on the "Calendar and tasks" progress.

Suffice to say, I jacked it up myself ;)

So, to keep it from doing anything for the time being (this was a bit severe, not recommended, and may not have the intended results) I nuked my settings with the following command.

NOTE: Don't run this unless you are plain silly and like to jack things up.
gconftool-2 --recursive-unset /apps/activesync/ActiveSyncAccount1

At this point, I shutdown the device and restarted it (may not have been needed), went to settings -> Mail for Exchange after booting up, reconfigured my account, etc. and...

still hanging. Damn.

Let me know what logs you'd like to see, or what you'd like me to test out...

Thanks,
.jason

Re: How to reset gconf settings...
 

Update - the more I mess with this, the more I think it's my calendar that is screwing things up - I tried to remove the old cal I had in there and it still hangs in limbo... now to go mess with that some more...

Re: Mail for Exchange (MfE). Blame me here, pls
 

Hi guys,

I've just received my N900 and I'm trying to connect MfE with the exact same settings I have on my E71.

I tells me that the Host Address is invalid on the exchange server (translation from french);

Anyone know what I can do ?

Edit : could it be because my employer asks for a lock on MfE for Symbian ? However I used roadsync on symbian before without a lock and it worked fine...

Re: Mail for Exchange (MfE). Blame me here, pls
 

Hi Vitali,

First a warm congratulations on the 102 pages in this thread - that is impressive, and completely impossible to find your way around, if you are "just a normal user, who thought you bought a well-functioning business phone" like me - coming from a Nokia N95 8Gb.

I may very well be asking the same question that someone else already did, and for that I am sorry - but Nokia can not expect normal people to read through all of this. Much of it so technical, that you lost me.

My questions are:
- Why does mfe syncronization (with a 2003 server - Yahoo - managed to find that information!) put all answers to meeting-request first in my inbox? I have 14 accepts/rejects and even some "undeliverable" messages on top on my Nokia N900 inbox, but they are not on top when I open Outlook at my laptop.

- Why is it impossible to see who sent the accept/reject message? It says no recipient (translated from danish) - which is confusing, since I must be the recipient - I need to know who the sender is! Bottom line is, that I receive a lot of accepts/rejects - but cannot see who they are from. Why is this?

- I was used to be able to look up contacts in my company adress book, but this is no longer possible - thus preventing me from being as effective as I was with my old phone. I've seen that I should wait for the next firmware update in the mfe Wiki, but thats not an answer.

Now that I am at it, I'd like to take this opportunity to speak my oppinion about the software release policy of Nokia. Let me give an example: If I buy a new car, take it out for a drive and find out it only turns left, no matter what I do, I'll take it to the garage and expect them to fix it. I do not expect them to tell me to wait patiently without any clue about when my car will work. Why is Nokia any different? Do you expect your customers to have different standards when they buy an expensive phone?

I would like to encourage Nokia to change this standard, whether it is an industry norm - it is annoying your customers! And this comes from one of the most loyal ones you've ever had!

Regards, Morten

Re: Corporate mail for exchange not syncing
 

There's apparently a way to go around this as Roadsync on S60 does not ask me to give a lock code while MfE does...

I'm really praying that this will be added in the very near future as I'm not able to use my corporate email now...

Tx !!

Re: Mail for Exchange (MfE). Blame me here, pls
 

Just for information, N900 synchronize well with OBM 2.3 since a recent patch just for that: http://code.google.com/p/o-push/source/detail?r=293

Thanks to o-push devellopers and OBM ones: http://obm.org
Both on GPL license.

--
_r1_

Re: Corporate mail for exchange not syncing
 

The MfE client could just "lie" to the server advertising features which are actually not implemented (remote wipe, locking, etc) but Nokia clearly stated that they do not intend to go this route, and as far as I understand the situation/platform full provisioning is not something we can realisticaly expect.

I love my N900 dearly, it's absolutely the best gadget I had in years, but whoever thinks it's an enterprise phone, is sadly mistaken, and it will never be, and looking back at things I don't think it was ever intended as such. I'm just sorry for the users who bought it for that purpose.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Does anyone know if the activesync code used on the n900 is open?

If Nokia can't or won't allow our devices to lie about its capabilities (understandable), certainly we could build an extras package that does.

I really need exchange support but there is 0 chance corporate will change the server policy just for me.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Ugh, so. 102 pages of thread and we don't have a work-around for the google incompatibilities? bummer.

right now, syncing my n900 to google contacts/calendar initially works but after I change one too many details from my n900, the sync no longer works. Methinks this stinks. :(

No I'm not saying: SOMEONE SHOULD FIX IT FOR ME xD it's ok, just bummed out to see that real support wasn't implemented. oh well.

Re: Corporate mail for exchange not syncing
 

If Apple iPhone can support provisioning, I don't see a reason why N900 could not offer it.

If N900 were not intended to be an enterprise phone, it would not have MfE in the first place. It would be waste of resources to develop the phone just for "Linux geeks" and forget "enterprise users".

Re: Mail for Exchange (MfE). Blame me here, pls
 

It isn't, at least at the moment. Vitaly said earlier that he personally would like it to be open sourced, but it isn't a decision he can make. Hope he is rooting for it behind the scenes.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Following on from MortenS; I too have an (upto date) N900, I also work in an organisation with MfE 2003, I also read the packaging where it says (and the nokia website still says) "Synchronise your contacts to Outlook." & "Push Email, calendar and contacts with Mail for Exchange.", and I studied the one page ads in some major business newpapers where the N900 is pushed as a phone (not a technical project/toy).

People who like what they have can enjoy themselves, Vitaly deserves some respect for putting his hand up, but at this point Nokia should at least change the copy.

Re: Corporate mail for exchange not syncing
 

I don't know what it was intended as, I just know what it is. The whole e-mail experience (which should be the main focus for an enterprise device) is just not on feature-parity with other smartphones on the market, not even Nokia's own. And for a new "flagship" device I don't think feature-parity as a goal is enough.

Ah, I would really, really, really like to know what's the strategy behind Maemo :-)

Re: Corporate mail for exchange not syncing
 

I totally agree with you. I understand that N900 is quite "new" but these functions are BASIC function for a "internet tablet" like NOKIA says. The Modest client is really poor !
We need better and more functions, local seach, filters etc etc.

Not to speak about Calendar app :( ! Really basic ! I think also that the problems in sync with Exchange 2003 are due to recurring events, probably not supported in calendar.

Adding functionality to MFE and these apps is the top priority I think. We can even live with no portrait mode for some months but WE NEED, as business user, solid PIM apps and sync functions.

I fear we never know these aspects.
Nokia has a great platform with Maemo but it needs to invest on in heavily and in short time...the competition is fierce and we'll have new Android and IPhone platform in few moths...if Nokia doesn't prepare a comparable product it will loose the battle for the new leading edge smartphone platform for-ever.

We'll see what will happen...for me after the inital entusiam now I a bit worried to have choosen the wrong device for my use...

Re: Mail for Exchange (MfE). Blame me here, pls
 

N900 contains a command-line tool called cmcli which you can try and use to debug this. Please try this at the terminal:

...for instance cmcli -T common-ca -v localhost:443. In your case the port number is probably something else than 443, though. Or if the chain of trust ends with a user-installed certificate and not in some of the 118 pre-installed ones, please try

The output should be something like this:

...or...

...depending whether the verification fails or not. If cmcli succeeds in verifying the connection but MfE does not, this must be a bug and it would be highly appreciated if you filed one in bugs.maemo.org.

with best regards,
Juhani Mäkelä
Maemo Platform Security

Re: Mail for Exchange (MfE). Blame me here, pls
 

Would you mind me putting this on the Heartbeat wiki?

Re: Mail for Exchange (MfE). Blame me here, pls
 

Thanks for that - it reports "Verification failed: unable to get local issuer certificate". The web browser is perfectly capable of validating the certificate though, so is this doing something differently?

Re: Mail for Exchange (MfE). Blame me here, pls
 

vitaly_repin, can you please clarify the following line in the http://wiki.maemo.org/Mail_For_Excha...rtbeat_and_FAQ

If you use PR1.0 (sales release) it is hardly advised to update to PR1.1. See PR1.1 summary for additional details and update instructions.

Does this mean it is recommended, or is not recommended, to upgrade to PR1.1? My main goal is working google calendar support, but regardless the wording of the wiki might could be tweaked for a better understanding.

And as other have mentioned, thanks for coming to the community to help aid transparency, even though it may not be what we want to hear <G>

Re: Mail for Exchange (MfE). Blame me here, pls
 

i have edited the wiki page, the upgrade to PR1.1 is recommended.
i'm pretty sure it was just a translation error.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Sorry for not appearing in this thread for so long time. I will come back next week or even week after next week. I am having extremely busy business trip now.

Sorry, guys!

Re: Mail for Exchange (MfE). Blame me here, pls
 

Obviously yes. To give a better answer I need more details. Which port did you connect to with the web browser? If it's just https://..., it will connect to port 443 and it may not be the same port the mail sync connects to. Hence, the service behind the port and the certificates it sends may be different.

One possible reason to the problem is that while the server certificate and the root certificate are OK, the sync client has problems in validating the intermediate CA certificates.

To get to the bottom of this, please do the following. Give the same command as before but this time with the -s-switch to save the certificates the server sends.

...which makes the command to write a couple of files with the .pem-extension in the current default directory. Then send those files to me. They should contain no secrets, so I guess it's all right to do this.

I updated these instructions to the Heartbeat wiki as well.

Re: Mail for Exchange (MfE). Blame me here, pls
 

This thread is growing way beyond practical use ;)

When I recieve a mail I get the blue flashing LED. If I choose to read the mail on the computer the status is changed to "read", but it´s still in the unread status and the LED is still flashing if another mail is left open when the unit locked itself.
When I unlock the device and close the open mail The led stops flashing and I do not have any new unread messages ( just as it should be)

A bug?

note: I use "always on" as sync method.

Re: Mail for Exchange (MfE). Blame me here, pls
 

I was using the same port for both. Anyway, I've tracked down the problem - the proxy I was using uses the same parameter names as Apache but for different purposes. I've changed the configuration and the certificate now gets verified okay, and MfE works without needing the intermediate certificate. I'm still not sure why the browser worked without problem though, unless I've stored an exception at some point (I don't think I did though).

Re: Mail for Exchange (MfE). Blame me here, pls
 

I've filed bug 8340 on the issue. I imagine it's more of an oversight than a bug.

The good news is that it's Modest related, which is open source, so it can be fixed even without Nokia doing it... give me a few months to get really annoyed by it and maybe I'll do it myself :)

Re: Mail for Exchange (MfE). Blame me here, pls
 

I'm glad it worked out for you. It bugs me a little bit that I still don't quite understand what was the problem in the first place and why changing the proxy settings helped. But then again, these things tend to be really complicated sometimes. So please keep comments coming if you detect any anomalies. Vitaly and the rest of us drones will try our best to have them fixed for you.

Re: Mail for Exchange (MfE). Blame me here, pls
 

The original problem was that the proxy server (which acts as a HTTPS/HTTP gateway) was only serving the immediate certificate. The configuration setting I assumed (based on Apache configuration experience) was for the CA chain, was only actually used for verifying client certificates. I needed to append the server certificate and CA chain into a single file and set the proxy to use that as the certificate file instead.

Thanks for all your help anyway :)

Re: Mail for Exchange (MfE). Blame me here, pls
 

HTTP 403 error is authorization error.
This is the same error I am getting when trying to use N900.

The company I work for uses client certificates for WinMo devices. When I setup initial sync with ActiveSync I need to enroll and get personal certificate in ActiveSync. This certificate is stored on WinMo device and used to authenticate the device to Exchange server. Check with your IT whether they will generate this cert for you.

Vitaly, (or anyone) could you please tell us if MfE supports authentication with client certificate?

Re: Mail for Exchange (MfE). Blame me here, pls
 

Hi, i have the same problem. I added a log under bug 6467

Br. Patrik

Re: Mail for Exchange (MfE). Blame me here, pls
 

Oh I care, a lot!
Lack of Java, I can live with that. MMS support is more important for me, i'm in the business of providing sms/mms services for daily newspapers and MMS is a good source of getting UGC for newspapers.

Re: Mail for Exchange (MfE). Blame me here, pls
 

Well, I don't remember enrolling my WinMO device, but maybe they changed the policy or something.

I still have my old phone... anyone know if it's possible to retrieve old certs from it?