Hi Andrew, yes, it's sorted out with the update to 6.70, but the MailEnable Server shows up Version 6.60... By the way, is it planned, that MailEnable will support multiple contact information (e.g. addresses) like MS Exchange respectively MS Outlook in the future? With the actual version it's not p...

Hi Marco,

yes, it's correct. I've done it this way, and it works fine now.

Regards
Christian

Hi Robert, thanks for your postings, these helped to solve my identical problems I had with the update from 6.56 to 6.58 respectively 6.59 (see posting MailEnable 6.58 Update damaged WebMail Installation). I did the "repair" manually and activated .NET 4.x, but ME Mobile works only with .NET 2.x. Wi...

Hi, it's me again :-( Seems that the upgrade to 6.58 confound my complete MailEnable Installation that worked properly for the last years. Since today EAS is no longer accessable (changed nothing since the last days). In the MailEnable ActiveSync Management Console / Verification I get the message: ...

In the meantime I solved the problem partially myself... - installed .NET Framework 4.x handler binding manually were necessary. - clicked the binding for .NET 4.x with right mouse button and selected "reset to parent" - WebMail and Web Admin works fine :-) - Mobile Mail still doesn't work, since it...

2nd addition:

Just saw that 6.59 is available - installed.
Same effects as before

Since the installer deletes .NET Framework 4 handler binding again and again; is it really required? And what is the correct configuration?

Addition to my posting: I've made an update installation this morning, to see whether "the damaged parts" will be repaired. After the installation WebMail, Web Admin etc. didn't work with error 404.17 again. Checked the IIS settings and saw that the handler binding for .NET Framework 4.x was deleted...

Hi, as I wrote a few day ago in the "MailEnable Exchange ActiveSync (EAS) - Contact Details" thread, the update from 6.56 to 6.58 damaged the "web parts" of MailEnable (Web Mail, Web Admin, Mobile). With a lot of inquires in the web a found information about the 404.17 error, that occured. The handl...

in the meantime I did a "repair installation" with the 6.58 installer.
No chance to get the web services work...

Has anyone an idea how to sort this out?
Thanks.

Hi Andrew, thanks for your reply. I've updated my MainEnable Installation (Version 6.56) with your new version 6.58. Installation was no issue, as always, but with this update WebMail, Web Administration and Mobile Mail doesn't work any longer. Whenever I want to use e.g. WebMail I only receive an e...

Hi Andrew or someone else from MailEnable,

would you please be so kind and answer my question, since I want to go on with the implementation.
Thanks for your support in advance.

Regards
Christian

Hi, I'm not sure whether this is a feature or a bug that I saw with my evaluation of EAS in combination with WebMail and Microsoft Outlook 2010 (MAPI client). Contacts in Outlook may have up to three email addresses and up to three physical addresses. On the iPhone and iPad with EAS only the first e...

Hi, I'm also still working on the evaluation of EAS and got the biggest issues with the help of Andrew respectively with software updates sorted out (umlauts with EAS). But I can also confirm Nik's posting that the mail app is crashing with EAS configuration on the Iphone and Ipad. IMAP and POP3 has...

Hi Andrew,

thanks again for your support.
I've installed the new MAPI client, and now it works fine

Regards
Christian

Hi Andrew, thanks for the new MAPI Client, but this didn't help to solve this issue. I've deleted the mail account in Outlook, deinstalled my MAPI client (1.42) and installed it completely new. Absolutely the same effects. Following is the content of the cal-file, after changing an entry on the iPho...