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

It is your fault OP.

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

Hi this is my first post here.
I'm having an annoying issue with mail for exchange. I searched through the forum but couldn't find an answer. I setup my account fine over wifi at home. It syncs perfectly over wifi. For the first day it also worked fine over 3g. Now I can't get it to work over 3g at all.
It's an SBS 2008 server that I run. That's Exchange 2007.
Anyone have any ideas?
Thanks in advance
Joshua

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

Hello guys !

I just want to wish you all (and in particular Vitaly) a beautiful HAPPY NEW YEAR !!

I understand that many of you are on vacation during these days...and finally I'll go for some days of skying also :-) ... I really need them...

As soon as you come back, please look at my last posts (#647 and 648) and if you can, try to reply to me.

I take the opportunity to ask if there is some better email client than Modest, that support also the MFE sync with Exchange and Outlook function of N900. I badly need it to implement a better PIM or a complete GTD application (with To do list, task, Action etc...) synced with my Office 2003/exchange 2003 side.

Thanks in advance,
Cesare

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

Some questions: How exactly doesn't it work over 3G? Time out? What do the server logs show? Do other data transfers work on the same connection? Does MfE still work over wifi?

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

It says "exchange server is not responding" MfE works perfectly over wifi. Everything else works over 3G. Where do I find the server logs?
Sorry I've only just started messing with my new server. I'm trying to learn.

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

This is an awesome community and I'm sad to say that I have to return the N900 due to being unble to sync outlook exchange 2007 mail and calendar, as the N900 is not provisionable. I now work for a 15,000 person company, I can't even find out who the Exchange admins are, let alone get them to change their policies for me.

I cannot find an acceptable workaround and need to carry one phone to use for work and home, and I can't afford to keep the N900 as well. I've lost a lot of time and some money.

I wish you all well and all the best for 2010...jow

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

pardon me if i got this all wrong!
the N900 is a non provisional devce.
In the upcoming 1..1 will it BE a provisioning device?
I get the "error incommunication with the exchane server"- error msg. our company uss exch2007
My intentions with this device is using it in my job, but if I cant sync mail I cannot do that :(
Am hoping in vain that fw1.1 will resolve my problem?
Feel free to include me for testing the updated firmware.
In general the device is wonderfull, and this post is written on it!

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

Based on what I have read in here, the N900 will likely not become a provisional device at all (unless updating it to maemo 6 is possible and it makes some huge changes). The next version of Maemo has a much better chance of doing so, just based on how it is designed from the ground up.

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

canabal: thank you for that information.
though it makes me a little bit pissed off at nokia.
Really bad marketing this device with support for exchange.
"limited exchange support" would be a better word.

I have search for info about the "error communication..." errorcode.
But I haven´t found if that errorcode is the result of non provisioning support in the exchange server. Might there be anything else that causes the same error code?

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

With a lot of help from Vitaly, I created a small app which should do 2 things:
- enable/disable MfE sync on a folder by folder basis
- rename localy synced folders (just the local copy)

I attached the first version, I would be grateful if somebody could help me test it. The basic functionality is there, but is still needs polish and packaging.

Known issues:
-it doesn't check for the existence of an MfE acc
-it doesnt check if an MfE sync is running (please finish sync before running)
-it doesn't check if Modest is running (please close it before running)
-it doesn't back up your qmailstore.db yet (just to be sure please back it up by hand)

Mail For Exchange (MfE) Heartbeat and FAQ
 

This thread is so huge now that it is really hard for newbies to keep track of the discussion and to use this thread to solve the real problems. Yes, most of the issues which newcomers are facing, have been already discussed in this thread. In page 17, 28 or (may be) 41 :)

I have decided to put the most frequently asked questions to the separate wiki page: http://wiki.maemo.org/Mail_For_Excha...rtbeat_and_FAQ

Current version does not contain as much data as it should. This is just a first attempt. I would be happy if active members of this thread would be able to find time and energy to contribute to that wiki page.

I suggest to continue active discussion in this thread but also to populate the wiki page with the data which is important for every or almost every Maemo MfE user.

Happy New Year to everybody!

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

The detailed instructions for turning the logging ON are available here.

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

SMTP has nothing in common with MfE which is discussed in scope of this thread.

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

This is not the bug. This is missed feature (support of EAS protocol 2.5). This feature will be available in the next MfE sw. update.

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

No. They will not.

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

This is what I see:

2.5 means Exchange 2003 server. See FAQ for the details. Sorry. You need to wait for software update (or to ask your company admin to upgrade Exchange server).

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

Great idea about the wiki. I am going to see if there is anything I can add.

One thing I noticed... in the s60 V Maemo table, you use OK and NOK, I think it would be better to use YES and NO or some sort of check/X boxes. I dont want to change that without running it by you first.

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

Fixed. http://wiki.maemo.org/Mail_For_Excha...ted_in_N900.3F

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

It works like it should, but is it possible to just uncheck a folder from automatic update. But let the folder be visible in modest and allow manual sync of that folder?

Re: Mail for Exchange (MfE) and Calendar
 

Yes. You are right.

No. You will not loose it.

This is mostly about features of N900 calendar per se. MfE does not support multiple calendars.

Exactly. This is how N900 calendar works.

Hmm. Then you will not see these colors in N900. But they will not disappear from your Exchange calendar.

No.

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

Thanks a lot for reporting this. In fact, it was (bad) surprise for us.

However, this is automatically fixed in the upcoming MfE sw. update as we have stopped to use the symlinks mechanisms at all. Now MfE works with the certificate storage folder directly, without symlinks.

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

Are you looking to include provisioning support in a future update ? MfE is usless to me until this is available. As an end user of corporate email I have zero influence on their secuirty policies and wouldnt expect them to change their exchange config just for me. I have been using blackberry and recently tested MfE on the iPhone, would have liked to see how it worked on the N900.

(I checked the WiKi and there's nothing on there about future support for this, can you add something to say what your plans are ?)

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

I am not the Maemo spokesperson and can not communicate our marketing plans. All I can say is that we are currently doing activities in the provisioning area. But I can not say when and what exactly will be available.

Provisioning is not as simple as to add support in MfE. Adding support for provisioning commands in MfE, is the simplest part of the equation.

Just one concrete example to illustrate this. Server administrator can specify the number of failed attempts to enter PIN code (unlock the device) after which the device will be wiped. But the device does not have this functionality at all now. And how to do wipe? Is re-creating of the filesystem enough (quick format) or shall we really WIPE the device (cat /dev/zero > /dev/mmcblk<something>?). If we shall really wipe the device, then we need to do it fast. Otherwise, the attacker will be able to stop the wiping process and restore the files. But writing the data to mmc is slow. The fast way is to use cryptographic filesystem and remove the keys. But device does not have cryptofs support in place...

This example was just to illustrate the complexity of the task. And this is not only (and mostly) about sw. development per se. This is about business and legal decisions (like, "what does wipe really mean?").

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

thanks for the reponse, sounds like whatever route you take it will be sometime before this feature is available. I am suprised that Microsoft doesnt provide guidelines around how to implement the provisioning on devices. I would assume (hope) that remote wipe is specific only to the corporate data that is sync'd from exchange, and storing this information in a crypto layer would be vital, esp if you were to dock the phone via USB etc.

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

Works for me.

My remarks:

1) No debian packaging yet => no way to integrate it to extras yet. Don't forget about optification when doing debian packaging, pls.
2) You can create project page at garage.maemo.org if you wish
3) The folders are shown as a list, not as a tree. Hierarchy is lost from end-user PoV :)
4) Would be better to have the nice launch icon in Applications. This way, the application will be available not only for geeks but for wider audience.
5) [ Dream :) ] The perfect way is to implement this application as a control panel applet. Control panel applet is a so-file, loaded into the CP process in run-time, it can not be written directly in python. I am not a python programmer but I can imagine the schema like this: C-function calls python interpreter to build widgets inside C-application. Some kind of mix. I was doing this with Tcl/Tk several years ago. I believe it could be possible with python also.

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

As far as I understand the system, this is not possible atm; maybe Vitaly can prove me wrong.

(Theoreticaly, if there would be a folder class which is not synced but still displayed by the mail client, it would be possible)

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

Yep, I'm on this right now, but this beeing my first Maemo app, it takes some research into the whole packaging,optifying issue.

True, but I couldn't find a hildonized tree widget yet, and not even an example on the device. I will either try how a gtk tree widget looks on the device, or will try to fake a tree using buttons.

I already have the icon, it should appear in Apps when the packaging is done.

Yeah, it would be cool, but at first sight looks a little over my head :rolleyes:

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

From the excellent wiki;

"Unfortunately, there is no way to disable certificates check at the client side in the current MfE release."

Will there be the ability to do this in later releases?

The sertificate my company uses is duff [no CA or something] :(

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

You are right.

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

Not in the upcoming release. We are working on this but I can not communicate any concrete plans, schedules et cetera.

Re: Corporate mail for exchange not syncing
 

Hi Vitaly,

any news/feedback about a partial provisioning support in Maemo?

If I look at the table at
http://wiki.maemo.org/Mail_For_Excha...ted_in_N900.3F
I see that provisioning is partially (not full) supported in S60 and it would be nice to have the same partial implementation in Maemo.

Thanks for your reply in advance

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

Are there any plans that "Meeting invitations replying" will be supported in a future version of the software?

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

+1
Meeting requests would also be veeery useful :D

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

Apologies if any of these have already been covered; I tried skimming but it's a pretty big thread.

1. One of my folders has a "/" in its name. Modest does not like this. Fortunately, it doesn't seem to have trouble viewing e-mails in it as long as I catch the notification.
2. Desktop widget???? My E51 only showed the two most recent e-mails, which wasn't great, but at least that made it easy to see if I had new messages.
3. So I click the @, and I'm shown "Mail For Exchange", and I have to select that every time, even though it's my only account. That might be slightly useful, if it didn't think when it was last updated was more important to tell me than if there are new/unread messages (Hint: it's not).
4. My account is configured to automatically move certain e-mails to subfolders. Once I've opened up my account, there's still no indication as to whether or not/how many unread e-mails there are. I have to scroll though the whole list to see if there is anything unread in my subfolders.
5. My most commonly used subfolder starts with "R". Since they are listed alphabetically, starting after all of the inbox/sent stuff, I need to scroll down through 4 pages of folders before I get to it. Reordering folders would be good, as would being able to hide folders or collapse sub-subfolders.

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

Do we have a rough timeline for the next version of MfE....

It's killing me, I went back to my N95 so I can work...

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

Hey all, i'm still fairly new to the Maemo community, but I have a quick question. My company uses MS Exchange 2007, so I had no problem getting the MFE set up and I honestly think it works pretty great. However, another huge feature for me was to be able to use VPNC to handle remote support to get into work. As i'm in the Tech Support department I have to make sure MFE is set to "always on" so I can respond to requests ASAP. I've noticed, that when i'm set to "always on" I cannot access VPNC, but if MFE is set to "manual" I have no problems. I would like to know if anyone has any idea if theres a work around to this issue, or why it's happening. Also, I was connecting to VPNC with a 3g connection, not WIFi. Thanks!

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

Are notifications controlled by Modest or by MfE? I know it's a dumb question, but i'm curious if there's a way to stop it from giving notifications for my Exchange account's junk e-mail folder. I really don't know need pop-ups on the screen telling me where I can get Viagra...at least not yet ;)

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

That's another one I was curious about. I have several folder decidated to automated responses that show up on the system. I work in a pretty large office and would love it if my phone didn't alert me everytime someone locked themselves out :D

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

I'm piling on to hopefully get a higher priority on support for Exchange 2003. My N900 is useless without it. POP access is so slow that I can't rely on it. I need Exchange 2003 support for mail, calendar and contacts ASAP.

I tried to return the phone, but missed my refund window by a day.

I now own a $600 version of an N810.

I'd love to move to the N900. Any help would be appreciated.

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

Exchange 2003 support has been implemented, so it's down to when they're releasing it (I've not heard it having been fixed in the PR1.1 RC). I've no idea who's responsible for deciding that - doesn't seem to be the developers though.