I updates my system to Windows 11 and during the course there must have been an update to the MAPI32.DLL in C:\windows\syswow64 (running Outlook 32bit).

It seems to be that the Mailenable connector is not compatible with that DLL, as it is missing ordinal 241 entrypoint.

Can anybody from ...

Did the update to 2.73 solve the problem for anybody here?
What is described here is the biggest problem I experience with Mailenable (second to that are the alway appearing Sync dialogs).
I Have the Add-In in 2.74 version and the most current Mailenable.
I have plenty of mailboxes in Outlook 2016 ...

I have the same issue.
It would be great if the "Updating Inbox" window could be changed so that it does not take the focus or can be hidden totally.

I also really appreciate this update.
To everybody previously evaluating Mailenable and putting it down becuase of the bad performance when working with Outlook.
Give it a second chance - it is not the same bad experience anymore.
Way to go guys - keep up the good work.

@Mailenable MAPI Development: Could this be one of the reasons for the performance problems? http://stackoverflow.com/questions/22617539/setfilecompletionnotificationmodes-seems-to-not-work-properly
I figure that everything speeds up a littel if I switch Use Completion Ports off - but than it is ...

Sadly I need to correct myself. This NB opening did not solve the problem.
I really cannot use MailEnable with huge mailboxes because MAPI Outlook integration is too slow,
Is there anything that can be done about that - besides not using Oulook and reducing the mailbox size?

I experience the very same phenomena. If I open the NB ports everything works fine.
If I close them I experience always stuck and slow problems with the MAPI connector.
Is there any possibility (workaround or configuration) that can be done withoout opening the NB ports and still experience adequate ...

Could this be solved by installing 9.15?
I have 9.13 running at the moment?

I have the very same problem with Outlook 2010.
Is there any way to solve this?

I am not sure, since I did not try it yet, but I think it should also be possible to get SSL working with hostheaders.
The requirement will probably be that you have a valid multidomain certificate.

http://blogs.iis.net/thomad/archive/2008/01/25/ssl-certificates-on-sites-with-host-headers.aspx ...