New Version Of Mail For Exchange - M4E 1.5
For all of you out there relying on Mail For Exchange for your push email access to Microsoft Exchange it's time to upgrade. Nokia has released Mail For Exchange version 1.5. The new client contains a number of bug fixes and new features and will work with any Eseries device with a firmware of 1.610.04.02 or later.
New features in this release include:
• Configurable heartbeat interval
• Detailed admin logging
• Notification improvements for “new emails”
• Ability to set importance flag for sent messages
• Improved handling for IT Policy updates
• Support for “Send As” capability
• Support for Microsoft Exchange 2007
• Support for Microsoft Small Business Server
• Support for F-Secure
• Support for Symantec
I haven't confirmed this yet but I have heard that This version no longer can be run on the Nseries devices. (As opposed to the previous versions of Mail For Exchange that worked on Nseries) The new client is available for download here:
February 6th, 2007 at 8:25 am
I read the release notes and they say “Eseries ONLY” and also they have this note:
6. NOTES
• Using Nokia PC Suite to sync emails, contacts or calendar entries after installing and using Mail for Exchange on your phone will corrupt the phones memory
Was it always like this??
February 6th, 2007 at 8:27 am
ability to use WiFi for email?
February 6th, 2007 at 8:34 am
What is the benefit of having a Synch option that that might corrupt the memory if PC Suite was used, isn’t PC Suite the Official Nokia Software for Synching. I do not think that we should have to chose between the two, they must be inter-operable.
February 6th, 2007 at 9:23 am
Installed it on my E61 and it worked fine using IP Passthrough. PC Suite does not have email synching capability on my E61, does anyone know if its available on other model?
February 6th, 2007 at 9:24 am
The benefit is that it’s much better to have your contacts, calendar and emails synched no matter where you are, vs PC Suite where you only get the updates when you’re chained to your computer. The value of mobile email is that you stay up to date when you’re mobile.
You’re still able to use PC Suite to sync your device, just that you won’t need to sync your calendar, contacts and email since they are already up to date. But you can use PC suite to maintain your music, pictures, files etc.
February 6th, 2007 at 9:41 am
I need both, pc suite sync and wireless sync: I sync contacts and calendar with Outlook on my work pc, but i cannot access our exchange server from outside the office. I use Mail2web to sync my private mails. So should i stick with the old version?
February 6th, 2007 at 9:55 am
I don’t notice any difference, are we suppose to see some different options or somethig>
February 6th, 2007 at 10:48 am
Unfortunately, still doesn’t work with access point groups. Why is this great feature unutilized even in Nokia’s OWN software ? I have to switch my access point 2-3 times a day.
February 6th, 2007 at 11:00 am
Hi guys,
I use mail for exchange (the previous version) just to sync calendar and contacts. I have online folders on my exchange mail server (with server side rules) and MfE only syncs the “Inbox”. In my pocket PC I could select the sub-folders but in my version of MfE, it only lets me get Inbox. Does anyone have an idea if this new version would let us sync subfolders too?
Thanks!
February 6th, 2007 at 1:05 pm
They blocked non E series version. Not working on my N80
February 6th, 2007 at 1:19 pm
Still no access point group ??? WHYYYYYYYYYYYY ???
It works with the simple e-mail client in e61…
And what about meeting request ? Is it now possible to accept or deline them from e61 ?
And what about e-mail sync ? instead of choosing time range of sync in the past, i’d like too choose only unread e-mail messages for example…
February 6th, 2007 at 5:52 pm
hey any one can send me the link or file of the old version of mail of exchange for my noka n80ie.. thanks, marco_are@hotmail.com
February 6th, 2007 at 6:00 pm
Any other issues aside, I think the heartbeat improvement will be a life saver for me, provided the data connection is retained.
Here’s an interesting post on the topic:
http://discussions.nokia.co.uk/discussions/board/message?board.id=messaging&message.id=1289
I noticed a major improvement on battery life when I went from always on to 15 minute intervals during the work day. According to the link above, that scenario saves batter power, but no wasted data load. Now I’ve set the phone for always on, but slowed the heartbeat to 15 minute intervals instead of 5. This potentially can give a battery life similar to that when using Blackberry (which is not provisioned by my carrier).
February 6th, 2007 at 6:10 pm
I was hoping M4E to support the sync’ing of Tasks
Apparently this is not on their agenda.
February 6th, 2007 at 6:35 pm
Sorry for the newbie question, but what exactly would be the difference between setting Mail for Exchange to sync every 15 minutes and setting it to “always on” with a heartbeat interval of 15 minutes? From an email perspective wouldn’t I be getting email updates at the same rate?
thanks!
February 7th, 2007 at 12:59 am
Has anybody noticed that the timestamp on sent emails is wrong after you upgrade to v1.5?
Email has the correct timezone (+02:00) in the headers, but has translated the time to the equivalent GMT time, ie. two hours earlier.
February 7th, 2007 at 2:15 am
thanks for the heads up:) cant wait to upgrade to the newer version:)
February 7th, 2007 at 2:57 am
The reason why sync-data is corrupted is because ActiveSync, which is the function on MS Exchange 2003 that allows for this data to be pushed down to mobile phones, uses another protocol when syncing but the PC Sync in the PC Suite uses another protocol (apparently this is a Microsoft issue).
That’s why things get corrupted!
February 7th, 2007 at 3:27 am
One bug i would like them to fix is M4E coming on the Standby Screen every time a sync profile is edited.
February 7th, 2007 at 5:53 am
If someone could explain more in details the “heartbeat” story I would be gratefull !
February 7th, 2007 at 6:02 am
Upgraded and found that it’s actually version 1.0.5(0). A fairly minor upgrade. The .SISX file is wrongly labeled.
February 7th, 2007 at 6:34 am
@boonkui, no, its not 1.0.5. On the contract page (the one where you click continue… it is labeled as 1.05 which would be 1.5.0
so it is a newer version.
February 7th, 2007 at 7:26 am
Basically all of the push-mail solutions, including Blackberry, use a heartbeat signal that tells the server “hey, I’m still here and ready to get something at any time”.
The heartbeat is different from syncing itself in the amount of information passing between the client and server. If you follow the link I posted above, you can see that in the version of M4E current last summer the heartbeat signal was about 1.5 kb in traffic each time while the syncing (for instance setting it to actually sync at 15 minute intervals) was 6 kb in traffic each time. When you sync from idle, you have to establish a data connection if it’s not up, log in to the server, request all of the headings or a delta of the headings, receive and acknowledge, update the inbox and then log out. When you’re always on, the heartbeat is just like a ping, basically just a one off every so often.
And no, if you set your heartbeat to 15 minutes you will still receive the pushmail as soon as the server sends it because the server is supposed to assume that you have a valid connection up and running as long as it gets a heartbeat every 30 minutes. If you set to sync every 15 minutes, you’ll only get your mail at 15 minute intervals, not immediately. And although you save energy by not keeping a data connection live, you lose a good bit by making the system send/receive as much data as four heartbeats.
I’m no real expert, but this is what I’ve gathered from what I’ve read.
February 7th, 2007 at 8:42 am
Thanks Quist for this explanation ! But does this means that if I set the heartbeat to 15 minutes instead of 5, I will save significant battery life ? Or I will just save a a very very little something even not worth mentionning ?
February 7th, 2007 at 8:43 am
Has anyone dared to try if syncing with pc suite and exchange at once will really corrupt the phone data?
February 7th, 2007 at 8:51 am
I upgraded and am syncing : for the moment no problem !
February 7th, 2007 at 9:16 am
Where do u set the heartbeat?!?
February 7th, 2007 at 9:20 am
Is it possible to use an accesspoint group rather than an accesspoint in mail for exchange? Will this be supported in a future version?
February 7th, 2007 at 10:05 am
I tried changing the heart beat to 15 and I no longer recieve emails as soon as they hit my mailbox. It takes few minutes before I get it on my phone. If I change heart beat to 1 I start recieving them immidiately. Is this going to drain my battery even sooner then it used to with the older version of M4E?
February 7th, 2007 at 12:47 pm
@Michael: It’s not possible to use accesspoint groups instead of accesspoints. This is still one of the major omisses of Mail for Exchange.
@Param: I’ve had mine set to 1 for about 7 hours and my battery life seems fine.
February 7th, 2007 at 12:53 pm
Ice, theoretically you should save a good bit of battery life. I am not absolutely sure however and am running my own tests, but I’ll get back to you once I’m satisfied with my fihndings.
Param, I’m interested in hearing how you tested and found a delay in deliveries. As per the link I posted earlier versions of m4e were prone to losing the connection and not realizing it and it sounds like this may still be an issue, but in that case mail would just not arive instead of being delayed. I have yet to notice a delay so it may be a server or network issue.
Also if you set the heartbeat at 5 minutes the new version shouldn’t draw any more power than the old in which a 5 minute heartbeat was hardcoded. If the heartbeat setting is somehow causing your delay, a 5 minute setting should also return it to how your old version performed re. delay/no delay.
February 7th, 2007 at 1:25 pm
Quist, Sitting right in front of my laptop if I change my heart beat to 15 I notice emails popping up in my laptop, but dont recieve them on my phone for like 5-10 mins. However, once I change my heart beat to 1, I immidiately start recieving emails at the same time they pop in my laptop. I tried this 3 times so far and same results everytime.
February 7th, 2007 at 3:19 pm
LINK IS DEAD!! CAN SOMEONE MAIL THE SISX TO ME!!! CANT FIND IT ONLINE!
alexwidegren@mail2web.com
thanks!!!
February 7th, 2007 at 5:45 pm
I have a problem with this twice already. I first installed and create a new exchange profile. It works fine in the beginning but it would prompt me that I don’t have exchange profile and advise me to create a new profile. However, at this point, I could no longer launch Mail for exchange setting. It simply doesn’t show up. Any idea?
Pat
February 7th, 2007 at 6:02 pm
Hhrrmm, not sure what to tell you Param.
I’ve just run a series of tests over about 3 hours (to spread them out and see if my heartbeat setting caused a loss of connection).
I’ve found that depending on where I send email from (different SMTP accounts, webmail on a pop account, webmail on my actual Exchange server), the delivery time from the send button to my IMAP connection with the Exchange server on my computer varied from a few seconds to 15 minutes (going directly and through forwarded email addresses). This time was of course not affected by my heartbeat on my phone as the phone wasn’t even involved in that part of the test.
I was really interested in the delay between the time mails showed up in my IMAP account on my computer linked to the Exchange server and when the first flash came on my E61 showing me a new mail was on the way in. In testing, regardless of my heartbeat setting this delay was consistently 2-20 seconds. This means there is a delay from when the mail first arrives at the Exchange account and is pushed to the phone, but it does not seem to be affected by the heartbeat setting.
That said even in this version the release notes mention a known problem of the client losing the connection with the Exchange server and not properly realizing it. This was confirmed by others’ tests (see the link I posted above) on previous versions. I can only surmise this has to do with how they implemented the data connections in the E61 and the fact that they in part have to deal with potential mobile roaming issues over 3G, GPRS or EGPRS, and in part wifi issues.
For this version, however, it does mention “improved error handling”. I’m wondering if their “improved error handling” means that if the data connection is of poor quality or cycles, they introduced a partial fix for the client to recognize a loss of connection and re-establish it through a renewed sync. This could explain some of your delay.
It’s interesting that you experience a 5-10 minute delay with a 15 minute heartbeat and their original default setting of a 5 minute heartbeat. Another possible explanation could be how your Exchange server is set up (maybe it’s set to only push within 5 minutes of a received heartbeat).
If anyone is interested I used mail2web’s Exchange server, connected with a link to my 3G provider (there’s also a 3G mast across the street) and have fring running in the background on the same connection. The longest send to IMAP delay was through my broadband provider’s smtp server, over a forwarded email address into mail2web. The delay on forwards was an average of about 3-4 minutes from bouncing off the first mail and into mail2web. The shortest delay from send to IMAP was of course sending directly from the mail2web web interface into my own account (2-7 seconds). There was roughly a 10 second delay from the first E61 flash to the vibrate and pop-up with a very small email (noticed this varied depending on the size of the email).
For my set-up and in my location setting the heartbeat to 15 still gives me reliable pushmail with a 2-20 second delay (a delay that was not affected even when the heartbeat was set to 1).
February 7th, 2007 at 6:41 pm
Quist, what do you mean by “the first E61 flash”?
February 7th, 2007 at 6:57 pm
Here’s a potential answer to your conundrum Param:
Looking at the following site you can see that the default setting of the connection time-out on the enterprise firewall can be as low as 2 minutes:
http://support.microsoft.com/kb/905013
This would explain why you’ve achieved success by setting the heartbeat to 1 minute (the connection through the firewall(s) between you and the Exchange server does not have time to expire even if it’s set to 2 minutes).
If the firewall timeout is not larger than the heartbeat, this will cause a disconnect. For me, the mail2web firewalls must be set to a window of longer than 15 minutes. I can also imagine my 3G carrier’s firewalls must also have a longer window (and they should since my carrier markets their own ActiveSync service en lieue of Blackberry).
I do not know how M4E handles such firewall related disconnects, but I can imagine it may think it’s still connected and just gets lucky when the Exchange server receives a heartbeat when it has a mail pending and has time to handle the push before the connection times out. This would be why your delay varies so widely. Theoretically, M4E could be so unfortunate that the Exchange server never has time to process a push and your mails would never arive (although this is unlikely - even statistically it should be able to get a hit on occasion).
For everyone else wondering about how the heartbeat ping works, have a look at this website on ActiveSync:
http://www.msexchange.org/tutorials/Exchange-2003-Mobile-Messaging-Part1-Microsoft-DirectPush-technology.html
Here’s the process:
1. Device sends PING request to Exchange 2003 Server.
2. Exchange 2003 Server holds the pending request until the heartbeat interval expires.
3. If no mail arrives before heartbeat expires, the device will send another PING request.
4. If new mail arrives before the heartbeat expires, the server notifies the device that a change has occured in the mailbox.
5. Device promptly requests the Exchange Server to send mail; upon completion the process repeats.
And I quote:
“Because the mobile device doesn’t send any empty syncs, as is the case with scheduled or manual syncs, the device reduces its power consumption which again increases battery life. Additionally data charges are reduced significantly.”
February 7th, 2007 at 10:44 pm
Ok, I have an E62 and I installed the new version and I can not find Heart Beat anywhere also i can not figure out how to change the priority of an email .
Any help would be great
thanks
pedro
February 8th, 2007 at 1:17 am
I get error “Untrusted certificate received from server” when I try to synchronize. How do I fix this error?
February 8th, 2007 at 6:45 am
Volkov, by the first E61 flash I mean that I have my phone set to flash it’s message notification light (upper left-hand corner of the phone) for 2 minutes upon received messages.
For email on the way in, the screen first becomes active, 1-2 seconds later there’s an initial flash of the light, then depending on the size of the file or rather number of headers being downloaded, there’s a 10+ second delay until it’s all done, my phone vibrates and/or the email sound signal rings and the pop-up on the active idle screen shows up. I used the first flash of the light for my tests because it was easily visible when watching my stopwatch and was a good indication that the phone new there was a change in my Exchange inbox.
Tunde, the heartbeat can be set from the new version of M4E by going to settings-email-M4E-edit profile-Sync schedule and its in the menu all the way down (need to scroll down).
For those looking for a replacement link for the download here’s another one including the release notes:
http://www.businesssoftware.nokia.com/mail_for_exchange_downloads.php
The only problem I encountered when installing over the older version 1.3.1 was that although my profile was kept my inbox was erased and had to resync. In the release notes they say that if you have a version older than 1.3.x you need to uninstall it before installing this one.
February 8th, 2007 at 6:51 am
What about the “Send AS” function? I miss the ability to send email from my work email address (using a free service like mail2web); it allow you to change on the fly the sendere address? And how?
ginomi
February 8th, 2007 at 7:49 am
To: mcangeli
I see. I think it’s 1.5.0 although the App. Manager indicates it as 1.0.5
February 8th, 2007 at 7:53 am
To: mcangeli
Oops! I checked again and saw what you mean. It’s 1.05 really. Thanks
February 8th, 2007 at 9:05 am
Thanks Quist… I reverted back to 1.3… i kept on getting disconnected from the server and it would reconnect some 5+ minutes later on “Always On”… i dont have that problem with 1.3 (yeah it would disconnect at times but it would immedaitely reconnect)
very minor upgrade and STILL no meeting response support.
February 8th, 2007 at 9:17 am
Quist,
Thanks a lot. I think that is the case with my Exchange server the timeout window is pretty small. However, seems like battery life is not much affected by changing the heart beat to 1, so I am happy.
February 8th, 2007 at 9:18 am
Quist
- In other words, you are saying if you keep your connection on “always on” - you will use less data in comparison to scheduled on 15 minutes interval?
- Also are you suppose to notice a change when yo install the new version, I see no heart beat change option, no send as option, nothing has changed for me?
February 8th, 2007 at 9:47 am
Using PC Suite after will not corrupt the phone’s memory. It may erase or you may get duplicates of Calendar and Contacts items. Basically only user data will be affected. This is true if using any two sync applications.
February 8th, 2007 at 9:50 am
If you use PC Suite for calendar and contacts and MfE for email, you will be ok. It’s only if you use two sync methods with the same data that you will encounter a problem.
February 8th, 2007 at 9:56 am
Quist, you may have interpreted the Ping Interval purpose incorrectly. You may save some battery life, but it might also use more. It depends on your server/proxy/carrier. If you notice that your connection is dropping when you are using always on, you should decrease the setting from 15. A good place to start is 7-8.
Also, make sure your AP settings do not include proxy setting under Options>Advanced
February 8th, 2007 at 10:05 am
Oops, sorry Quist. I saw your later posts. The rest of my post still applies.
February 8th, 2007 at 12:29 pm
When are we going to be able to process meeting requests? This would be the one thing that my E61 sorely lacks.
Nokia - c’mon - its the most obvious feature an exchange user needs
February 8th, 2007 at 1:06 pm
I think if you use PC Suite to sync emails,calendar,contacts from your outlook it writes to the same memory area that Mail for Exchange does and it “can” currupt your phones memory.
PC Suite can still be used with the device just those PIM data cannot be synced. It makes sense since 2 different apps writing to the same memory can cause problems on any hardware.
February 8th, 2007 at 1:09 pm
This new release is only for Nokia’s Eseries device … older versions would install on other Nokia phones. They are locking it down to Eseries only now which will not affect us.
February 8th, 2007 at 2:08 pm
So I’ve tried the Always On with the heartbeat setting from 15 all the way down to 1 and it still has a problem being connected. Any suggestions?
February 8th, 2007 at 4:29 pm
Send As capabilities? I don’t get is working. Any suggestions? Thanks
February 8th, 2007 at 5:16 pm
Vakul, theoretically you should be able to save some battery power by using an always on mode with a longer heartbeat because the device is not being burdened with recurring “somewhat” heavy processing of requests as it does with a 15 min sync schedule. This is however a trade off depending on how much energy the individual device uses to maintain a data connection irregardless of the open session with Exchange. Apparently the E61 doesn’t do this very well in all kinds of connections or with varying strengths of radio signals.
If we think about Param’s and others’ experiences with this new version, it seems as though battery life has been improved in this version regardless of how fast a heartbeat you set. If you have a set-up that’s good with regards to keeping an open session connection with your Exchange server (no or very few disconnects in M4E) and can have a heartbeat of up to 15 minutes you should see even more battery life improvements.
Good news is that if you had problems with the old version re: battery life this version should help. More good news is that if your firewall time-out window is very short, you can now make the heartbeat so fast as to maintain a connection with the Exchange server, and from what others have seen shouldn’t experience too much if any shortening of battery life.
If 15 minutes doesn’t work for you, 7-8 minutes is the next thing I would try as Killer says (there’s another threshold in Active Sync at the 9 minute mark).
If however you repeatedly get disconnected when using always on regardless of the heartbeat (ase499), you can do what tunde did and revert back to the 1.3.x solution.
Those still looking for the heartbeat setting, you can either open the M4E in the Installs menu or go to Messaging-Settings-Email-M4E and then choose Options-Edit profile. The heartbeat setting is listed at the bottom of the Sync scheduling menu (you need to scroll down to see it) and the default is set to 5 minutes.
For me at this point I haven’t really been able to run a properly scientific evaluation of the battery life because I use my phone for so much else at the same time that the results would be obscured. I have however noticed that I can now have my M4E always on 24-7 with a 15 minute heartbeat and battery life has been notably improved over my old schedule of Always on 8:00-18:30 and 15 minute interval syncing otherwise. This may be a factor of both the heartbeat setting and a new algorithm for handling the connection in general implemented in the 1.5.0 version.
(By new algorithm, I’m beginning to wonder if earlier versions instead of being hardcoded at 5 minutes didn’t try to automatically adjust the heartbeat setting to maintain a connection. That would explain why this version is much easier on battery load regardless of the heartbeat setting - the processor has to work much less in general - but so many people seem to have to set their heartbeat way below 5 minutes or may still be getting repeated disconnects because it’s no longer dynamic. This just a wondering, though.)
I’ve only noticed a disconnect once so far, but I think it had to do with another app that I was closing and having some trouble with at the time.
February 8th, 2007 at 5:30 pm
Although not thoroughly investigated, here’s what I’ve noticed so far regarding battery life and my personal settings:
In my first set-up with the old version of M4E, I tried staying Always on round the clock with a strong 3G signal and had SIP wifi always connected. This gave me only about 6 hours of battery time.
Then I was Always on 8:00-18:30 and 15 min. syncs otherwise with M4E with a strong 3G connection and used SIP for 8 hours a day with my wifi. With this I got about 20 hours of battery life.
Then I switched to 15 min syncs 8:00-18:30 and 30 minute syncs otherwise and reduced my SIP-wifi usage to about 4 hours a day. With this I got about 50 hours of usage.
Now, with this new version of M4E, I’m Always on round the clock with M4E (15 min heartbeat) and have added fring round the clock (both on the same strong 3G signal) and have SIP-wifi up the same 4 hours a day. With this set-up I estimate I’m getting about 50 hours. I haven’t dared run down to a full discharge of the battery yet because I’m so reliant on my phone during the business week.
If my estimate is close, this means that this new version with my set up gives me a bit more battery power in always on round the clock than I previously had with 15 min syncing for 10.5 hrs of the day and 30 min syncing the rest of the clock day.
So far I’m pretty pleased to be getting push-mail around the clock and use fring and some SIP and be well within a daily charge of my phone.
February 8th, 2007 at 7:53 pm
Quist,
If I go into profile - sync schedule
all I see is peak sync, off peak sync, peal start time, peak end time, and peak days. Nothing about heart beat? Am I missing some5hing?
Also… so do you save data by keep it on always on rather than having on 15 mins?
February 9th, 2007 at 7:26 am
I have M4e on Nokia E60 and there is no heartbeat option. Maybe it is only for the E61
February 9th, 2007 at 7:49 am
reverted to 1.3 version, I noticed that in the new version I can’t disable the sound/vibration alert for new messages… I’m very disappointed about the 1.5!
Gino
February 9th, 2007 at 11:57 am
For those with problems finding your heartbeat! Make sure you change the schedule allways - if you have it on 15 minutes or somethings else the heartbeat options doesn’t show.
February 10th, 2007 at 8:13 pm
SO here is the BAD news. v1.5 WILL NOT INSTALL on MY N73, it complains UPSUPPORTED DEVICE, it seems that nokia has installed version checking in the install and if its not E series device forget it. that means back to version 1.3 for me.
1.5 works great in my E61.
i think its stupid they restrict the install to the E series devices. especially when it worked
quite well with all of their mobiles.
February 10th, 2007 at 9:19 pm
Andre I agree what purpose it serves them, but I guess they are making it exclusive for business devices.
February 11th, 2007 at 12:01 pm
Andrew & Vakul,
It could be a license restriction from Micro$oft:
http://press.nokia.com/PR/200502/980375_5.html
February 11th, 2007 at 10:42 pm
I get an error “Untrusted certificate received from server” when I try to synchronize. How do I fix this error?
February 12th, 2007 at 2:00 am
I can’t find the hearbeat option on E50.
February 13th, 2007 at 2:06 pm
Does anyone know where I can get the older version of mail for exchange. Just bought my N80 and the release on the nokia site doesn’t work. E-mail screasey@lineone.net
February 13th, 2007 at 3:01 pm
I also get the “Untrusted certificate received from server” message. Which means that i’ve had to uninstall 1.5.0 and reinstall 1.3.0. Too bad. Any help on the certificate issue will be appreciated.
February 13th, 2007 at 4:04 pm
Hi Harrall, any chance you could send the version 1.3.0 that you have.
February 14th, 2007 at 1:21 am
Old version (1.3.1) can be downloaded from http://www.businesssoftware.nokia.com/mail_for_exchange/registration.php?f=32 Found the link by changing the the last number from the link http://www.businesssoftware.nokia.com/mail_for_exchange/registration.php?f=35 where version 1.5.0 is downloaded from.
February 15th, 2007 at 3:18 am
I tried installing both 1.3.0 and 1.3.1 on a N73 (Softbank Japan 705NK) but
got “System error.Please try again later ” Also tried 1.5.0 but it does not support Nseries anymore. You guys encounter this problem ? Any suggestions on how to make it work ? I am also evaluating Roadsync V3 for symbian S60 smartphones and surprisingly it works perfectly, except it costs $99…
February 15th, 2007 at 5:21 am
*Support for “Send As” capability*
what is this feature? is it the same as email address masking? wherein you can use your mail2web email account but have another email address appear in your from parameter? if yes, how do you enable this feature? i cant find this feature. thanks in advance.:(
February 16th, 2007 at 2:32 am
支持中文吗？
February 18th, 2007 at 11:24 am
I am having the same issue as Param. when i have hearbeat set to 1 it is always connected if it is set to anything higher the current status is idle. in the idle state i do get the mail but it takes a lot longer.
February 18th, 2007 at 2:20 pm
Flexte - I switched back to 1.3. Will have to wait for the next upgrade of M4E.
February 18th, 2007 at 5:03 pm
PARAM: i think i am going to just keep it set to 1.. i get emails in a few seconds this way and as long as my battery lasts all day im fine with it. by the wa my carrier is tmobile and im using the tzones plan and 4smartphone.net as my exchange server. who are you using. it may be the exchange server or my carrier thats causing the disconnects.
February 19th, 2007 at 7:37 am
I am also on T-Mobile US. I have the unlimited internet plan. I connect to my company’s exchange server. So you just need t-zones plan to get emails? I dont need to have the unlimited internet plan?
February 19th, 2007 at 2:09 pm
yup only need the tzones plan. i get the same edge speed an everything. i switched back to 1.3 as well and now my emails are coming in seconds again and im always connected to the server.
February 21st, 2007 at 8:46 am
anyone have a link to software that works with n80 IE today?
February 21st, 2007 at 9:49 am
Willfa,
The previous version of Mail For Exchange is still available for download. Just read Alexander’s comment, which is still there, as of 2 seconds ago:
Alexander Bore:
http://www.e-series.org/archives/258#comment-9712
February 22nd, 2007 at 3:10 am
I’ve been using M4E 1.3 with my german O2 “Surf & eMail Pack” for 5€/month but had regulary disconnects after about 2min 45sec of idle (maybe 2:30 idle + 15sec to syncronize). This doesn’t produce high costs as it’s an WAP flat fee and O2 can’t identify the M4E client when using secure connection (HTTPS). But this is a real battery drainer
When using WiFi at home it stays connected forever but you can’t configure accesspoint groups and switching manually is really annoying.
I hoped 1.5 would have solved this issue by setting the heartbeat to 1 but now it’s disconnecting just after 1minute and doesn’t reconnect for the next minutes so eMails are delivered really late… And there is no possibility to set the heartbeat lower than 1 (e.g. 0.5min).
The M4E application is showing “idle” as connection state…
Any ideas how to fix this? It seems i have to switch back to 1.3…
Jerome: yes you can set the from adress of your leaving emails. BUT you have to subscribe at least the “Personal Exchange” service at mail2web for $1.99/month to use your own from adresses. Additionaly you have to configure this from adress on support.mail2web.com as an valid smtp from adress.
February 22nd, 2007 at 3:57 am
How to set heartbeat in M4E 1.3:
1. install M4E 1.5
2. configure your settings
3. set heartbeat to 1
4. don’t uninstall M4E 1.5!
5. install M4E 1.3
6. confirm installation of 1.3 over 1.5
M4E 1.3 now uses an heartbeat intervall of 1 minute as you can see in the connection manager under “active connections” (just watch the data counter which increases every minute).
Disconnects occur much lesser and the device stays connected for around 8mins.
Note for german o2 “Surf & eMail Pack” users:
Make sure you’re using your WAP profile and change the “Zuganspunkt” to “wap.viaginterkom.de”!!! Otherwise your data will be charged as normal internet connections which can be verry expensive (up to 1.80€/MB and more). Note: this information is without warranty and please don’t blame me when you’re get billed for your traffic.
March 2nd, 2007 at 5:25 pm
Hi,
Does anyone have any experience of configuring Exchange Server to work with Mail For Exchange?
It works fine for manual sync but always on shows:
“mail for exchange server does not support always on sync schedule”
Thanks
Ian
March 3rd, 2007 at 4:37 pm
I’ve found the answer now - you just need to install Exchange SP2 on the server and it works fine
Ian
March 4th, 2007 at 3:13 am
Hi,
Does anyone knows if it sync. the Public folder as well?
10x
March 5th, 2007 at 7:59 am
So, I still don’t undersand the difference between setting the heartbeat interval to 15 minutes and setting the peak schedule to 15 minutes
Currently I have peak set up at ‘always on’ and heartbeat at 15….it appears that the phone is connecting every 5 minutes and looking for the mail…any help is appreciated. Seems like it drains my battery faster tahn before when I only had peak set up at 15 minutes.
Any help?
March 5th, 2007 at 3:40 pm
Not sure if your Exchange server is properly handling the ActiveSync connection or if there are firewal issues in play, but with the 1.5.0 version of M4E, my E61 sends a ping to mail2web’s Exchange server every 15 minutes, as soon as a mail drops into my inbox the Exchange server notifies M4E to initiate a sync and the mail is received.
My battery usage with an always on 3G connection with a very strong 3G signal from 3-Sweden (who has properly set firewall timeouts etc in their network) is far better than I can get with a 30 minute sync schedule.
In my case, the actual data connection isn’t the major culprate in terms of power, but rather the processing needed to handle more data and processes involved in an actual sync.
Simply put: Setting the heartbeat to 15 minutes with an always on connection should mean that your phone sends a ping to the Exchange server every 15 minutes and only syncs when the header listing on the phone is different from that on the server. A 15 minute sync schedule on the other hand means that your phone is not connected most of the time, but actually does a full sync process with the server every 15 minutes.
I’m not sure why your phone would be connecting every 5 minutes to sync, but this version of the software is very touchy when it comes to network settings. I think your best bet would be to revert to 1.3.x version of M4E and forget about the 15 minute heartbeat.
March 8th, 2007 at 7:55 am
have installed 1.5 on company E70’s but showing no additional features from 1.3 which it overwrote. Anyone know if my firmware is too old. Phones only about 4 months old.
March 8th, 2007 at 5:30 pm
Interesting reads above. I have installed M4E 1.5 on my e70 and am having a few probs. First off needed to install certs so have not got root and intermediate CAs on the device (see nokias quite helpful quide on this) but now when I try to sync the device says: “Server requires secure connection. Change Profile > Connection > Secure Connection to Yes”
Well it is set to this in the M4E profile. I am accessing presently vie WLAN for the time being but this also occurs when accessing via mobile network…
What am I missing?
Jon.
March 10th, 2007 at 12:30 pm
I get the “Untrusted certificate received from server” message. Any help on the certificate issue will be appreciated.
March 12th, 2007 at 6:43 pm
just found that the link to the older version is as simple as replacing 1.5.0 with 1.3.0 in the link for downloading version 1.5 at the top of the page
March 22nd, 2007 at 8:06 am
Finally I found a solution for disconnects after 00:01:00 (1.5) or 00:03:45 (1.3). You have to disable the proxy server! This doesn’t work on the o2 WAP connection but on the regular o2 Internet connection. This also increases battery life:
>>
Options - Advanced
1) Menu
2) Tools
3) Settings
4) Connection
5) Access Points
6) New Access Point - Use Existing Settings (and pick MediaNet or Cingular-GPRS etc)
7) Name it MediaNet/NoProxy or something obvious
9) Clear out Proxy Serv. Address and port
10) Back (to save)
11) Back (to save)
You are done.
Make sure your browser and MailForExchange use the new ProxyLess connection.
On my E70-1, it nearly doubles battery life.
March 22nd, 2007 at 8:07 am
March 22nd, 2007 at 8:07 am
(found on http://www.allaboutsymbian.com/forum/showthread.php?t=57526&page=2)
My connection is stable for at least 00:28:00 with a heartbeat of 5mins. Maybe you can still increase the heartbeat intervall…
March 22nd, 2007 at 8:31 am
still connected 00:52:06…
longest M4E connection over UMTS ever…
March 24th, 2007 at 4:05 am
Jon (or anyone else),
Is there a solution to this? I have the same problem on an E61 and Cingular…
+++++++++++++++++++++++++++++++++++++++
Interesting reads above. I have installed M4E 1.5 on my e70 and am having a few probs. First off needed to install certs so have not got root and intermediate CAs on the device (see nokias quite helpful quide on this) but now when I try to sync the device says: “Server requires secure connection. Change Profile > Connection > Secure Connection to Yes”
Well it is set to this in the M4E profile. I am accessing presently vie WLAN for the time being but this also occurs when accessing via mobile network…
What am I missing?
Jon.
March 26th, 2007 at 9:59 am
Battery Life
I use my E61 for 2 hours of talk time - daily on an average
synching 24 times a day - interval of 1 hour through the peak & non-peak hours on GPRS.
I do not use any game / multi-media function on a business trip.
The problem is that battery of this phone does not lasts for more than 16 - 20 hours.. which becomes very annoying.
Please advise what should be the average battery life based on above scenario and should i buy a new battery to get more juice from this phone or is there any other way out?
any help will be appreciated.
Regards,
Kumar
March 26th, 2007 at 5:39 pm
ATTACHMENTS
I had been able to download attachments with the very first verion of M4E that came with the phone about 4 months back. Bit lately with version 1.0.3 or 1.0.5 i am not able to download the attachments.
it shows RETRIVING ATTACHMENT and nothing comes.
please advise if any setting that has to be changed.
regards
kumar
March 28th, 2007 at 7:01 am
Hi,
we just installed exchange 2007. now mail 4 exchange won’t work?
on exchange 2003 it worked but now it can’t make a connection….
anyone who solved this problem?
April 14th, 2007 at 1:36 am
Can anyone recommend a way to get mailbox folders to be usable on an e61 ? I want to be able to view folders other than just my inbox via Mail for Exchange (though im not fussed about moving to a different package if i have to).
I heard this was scheduled for yonks ago, but havent seen it yet
Olly
April 20th, 2007 at 6:12 am
I NEED TO INSTALL TO MY MOBILE E65
April 20th, 2007 at 6:04 pm
new version of roadsync will get you subfolders….i’ve just installed it and evaluating it. Having some issues with it, but for the most part its seems to do the trick
April 29th, 2007 at 5:14 am
read through the blogs and didnt find this simple question…mail for exchange works great… but nokias”notes” doesnt sync with outlook- as there is no such field in outlook and “tasks” from outlook is not an option on the phone… so how do you auto sync your notes/ tasks?
April 29th, 2007 at 8:40 am
Hi shlomo,
You could set up PC Suite to sync notes/tasks. You can either sync it via cable or BT.
Cheers
April 29th, 2007 at 1:57 pm
so no way to have it go through m4e?
May 1st, 2007 at 9:27 pm
Has any one tried to sync with Exchange 2003? I am not talking about using POP3 or IMAP4… I am talking about proper direct push that is available for Mobile 5 type devices.
I have got Mail for Exchange installed on the device, disabled SSL requirement on the server. Other devices are synchronizing (dopod) no worries but Nokia E65.
If anyone was successful in that matter any help would be much appreciated.
May 2nd, 2007 at 1:16 pm
Hi
Just found major downside to M4E 1.5: when roaming the sync is not possible. I downgraded back to 1.3.1 and it works again fine…
Check with some friends and they experienced the same problem.
Does anyone know, why Nokia is not bringing more updates with more feature support??
E61 is a great tool, desperately waiting for my new E61i but it hurts to see that they are not working on the most important piece of software with it…
Cheers
Michael Lützenkirchen
May 2nd, 2007 at 2:17 pm
Hi Michael,
Syncing while Roaming is a setting in Mail For Exchange.
It is a setting under the “Connections” tab. Just set “Sync while roaming” to “Yes, always”
Cheers!
May 3rd, 2007 at 12:39 am
Hi Admin
Thxs for the reply. The feature setting “Sync while Roaming” I am quite aware of.
Yet, I wasn’t precise enough. I meant, that when I was roaming with M4E 1.5., I could not even access the Sync Configuration nor could I manually start a sync…
When I am travelling I am changing the configuration of M4E a lot in order to avoid high data charges. Most oftenly I only sync manually. This is not possible any more with vers. 1.5… The software freezes or returns to the initial screen without any reaction.
A phenomena many of my friends with a e61 have experienced as well since they upgraded to 1.5.
Cheers
Michael Lützenkirchen
May 4th, 2007 at 6:43 am
@Graham: Did You solve that problem with wrong shifted time in sent mails???
Please!
May 31st, 2007 at 2:04 pm
Dear All,
I am a system administrator for a small company. I am trying to implement Mal For Exchange 1.5 to our Exchange 2003 SP2 on SBS 2003 SP2 using a private certificate which is untrusted by any root authorithy. OMA is working, but M4E is not. Its an E61 and it will not sync because of the certificate. I read through these posts (and others).
I learned a lot about exporting the cert in DER format, Base64 format to a .cer file on ( http://support.dataviz.com/support.srch?docid=13796&pid=165. )
Only Base64 seems to be recognised by the phone, but if i open it on phone it will not import it into the trusted certs list.
Is ther a way to put an end to these kinds of posts ?
May there ba an ultimate solution ? I really hope so.
Take care
June 1st, 2007 at 12:09 am
Download the certificate through the E61’s webbrowser. That’s how I solved it on my E61i
June 20th, 2007 at 4:28 am
I just got my E65 back from service, where they kindly updated my software. Now Mail for Exchange no longer works. I have a pristine SSL certificate from THAWTE on my server, and it worked perfectly berfore the service. But now I get a “Untrusted Certificate” error whenever I try to connect. Anyone know a workaround? Or should I go back with the phone and demand a downgrade?
Sincerely
K.
October 31st, 2007 at 8:28 am
Hello All,
“Server requires secure connection. Change Profile > Connection > Secure Connection to Yes”
Solved!
I ran into the same issue when configuring M4E, Nokia E61i and Microsoft Small Business Server 2003.
The solution is simple yet strange. Here’s what you should do.
1. Isntall the certificate authority on the SBS server.
2. Create a (self signed) certificate.
3. Copy this certificate onto your Nokia and install it via you certificat management. (Also test your oma/owa-website to see if the certificat works).
4. Use Microsoft’s KB-817379 method 2 on your SBS server.
5. In IIS got-to Microsoft-Server-ActiveSync and right-click, Properties. Choose directory-security, IP-address and domain name restrictions.
Remove everything you find under: Granted Access and Denied Acces.
6. Now create your profile on your Nokia.
Your done.
February 24th, 2008 at 6:58 am
How do i download the certificate onto my e61i? i am trying to sort out the “untrusted cert recvd from server” error.