The things moved to the database are items such as domains, email addresses, mailbox options. Greylisting, exceptions, and a variety of other things are not moved to the database. Generally, unless you need to access the configuration directly in a database you only need to move it if you are going ...

If the server has not rebooted yet after installation, try rebooting. The MEUPDATE.DLL is in the Mail Enable\bin and Mail Enable\bin64 directories. If the PATH environment variable does not include these paths, the error can happen. The installation will add these, but if you just installed the soft...

This happened since you were sharing namespace with another server, so it tried to deliver locally and the address was not configured locally. So in shared namespace it needed to be configured as described at:

https://www.mailenable.com/kb/content/article.asp?ID=ME020699

This will happen if you are using a 32bit version of Outlook. i.e. whether you use the 64bit or 32bit version of the PSTToMailEnable utility depend on the bitness of Microsoft Outlook, not the OS. If you don't know which it is, the following article describes how you can check the About Outlook wind...

You can have the full length of email addresses. There is a limit on the username and postoffice length though, so these are 64 characters for username/mailbox and 128 for postoffice. So if you want to create a long email address then the username will be different to the email address.

You could only do this if you have an LDAP server, which requires the Enterprise version of MailEnable. The Standard version of MailEnable does not have a protocol for viewing contacts, except through webmail.

If you add or change a file in the filesystem, you should create a file called _change.dty in that folder. This will instruct the services to update the index file. You don't want to delete the index file since it contains message flags and other things that will be lost if deleted.

Seems as though the email is generated on another server that is using a from address on a domain on your server. Possibly SPF may help, or you can make a filter to remove them. In order to be generated on the MailEnable server you would need to relay through your server to another MailEnable server...

The From header is:

From: medical examination <info@news.easypromo.nz>

But you don't have *news.easypromo.nz* in your filter.

That looks ok, the services not installed are not in the Standard version.

For webmail the \mewebmail is a virtual directory if you are running it under another site. But you can just add host headers to the IIS site "MailEnable Webmail" to access webmail as mail.example.com. The webmail runs as an IIS site or virtual directory, we don't do anything odd with the URL handli...

Sorry, there is not a way to do this on the server.

The more recent versions should use slightly less CPU than earlier. Your issue may be due to what the clients are doing and the data they are trying to access. You'd need a support person to examine your server IMAP logs to see what is going on. High CPU is generally caused by lots of partial reques...

It will use the first valid certificate that it can use with that domain. So it will not use the expired one unless it cannot find another. It will not differentiate between self-signed and others though, so if you don't want the self-signed certificate used, you may need to remove it.

The only way to do this currently is to have a group that you add new mailboxes to when you create them. When you remove a mailbox it will be removed from the group.