I’m using Merak mail server with a third-party antivirus software. The antivirus is configured to scan the outgoing mail only, but for some reason the incoming mail is also scanned for viruses. What can I do to avoid it?

Unfortunately, this is a feature common to all mail servers that do not support mailbox-level filtering (that includes SmarterMail and Merak mail servers), and, thus, cannot be avoided. If a mail server doesn’t support mailbox-level filtering, incoming mail will be always checked for viruses.

The only exception from this rule is MailEnable mail server which supports mailbox-level filtering and, thus, gives you an option of avoiding the scanning of the incoming mail. All other mail servers currently supported by Plesk do not support mailbox-level filtering.

When I try to remove a mail box from a domain Plesk returns me error:Unable to remove the mail names: mailmng failed: MEAOPO.Mailbox.GetMailbox failedMEAOPO.Mailbox.RemoveMailbox failedMEAOAM.AddressMap.RemoveAddressMap failed for domain aliasetest.com [aliasetest.com]

When I try to remove a mail box from a domain Plesk returns me error:Unable to remove the mail names: mailmng failed: MEAOPO.Mailbox.GetMailbox failedMEAOPO.Mailbox.RemoveMailbox failedMEAOAM.AddressMap.RemoveAddressMap failed for domain aliasetest.com [aliasetest.com]

The most probable reason is that the mail box or the mail domain are not present within MailEnable configuration.
You can resolve this misconfiguration using Plesk utility:

“%plesk_bin%\mchk.exe” –domain –domain-name=

This utility will reconfigure MailEnable records in accordance with Plesk database. Then you will be able to remove this mail box.

When I send e-mail it returns with message: MailEnable: Message delivery has been delayed. Can it be fixed some how?

When I send e-mail it returns with message: MailEnable: Message delivery has been delayed. Can it be fixed some how?

This message means that your SMTP connector is not configured properly. To check it, take a look into SMTP connector properties

Mail Enable Administrator > Servers > localhost > Connectors > SMTP > Properties

The following setting should be configured correctly:

DNS server should be correct. It must resolve any valid host name.

Fully Qualified Domain Name (FQDN) should be properly resolved in DNS.

Bound IPs for SMTP should have properly resolved PTR DNS records (Mail Enable Administrator > Servers > localhost > Connectors > SMTP > Properties > Inbound tab)

You can check using http://www.dnsstuff.com/

Go to `Reverse DNS lookup` section and type your IP(s) that bound by SMTP. Request should return a valid host name or domain.

If these parameters are set up correctly you can check

“%plesk_dir%\Mail Servers\Mail Enable\Config\ADDRESS-MAP.TAB”

The first line should be the following:

[SMTP:*] 0 System

Check, if your server can access to remote SMTP servers.
You can check it using telnet tool

C:\> telnet mx1.mail.yahoo.com 25
Trying 67.28.113.71…
Connected to mx1.mail.yahoo.com.
Escape character is ‘^]’.
220 mta173.mail.re4.yahoo.com ESMTP YSmtp service ready

Connection output should be similar to this one. If it is not, you would need to find out why the connection does not get through.

How to upgrade MailEnable to a newer version or release

How to upgrade MailEnable to a newer version or release

RESOLUTION

Use the application creator’s solution:

http://mailenable.com/kb/Content/Article.asp?ID=me020040

But first we strongly recommend making a backup of MailEnable before starting upgrade.

http://www.mailenable.com/kb/content/view.asp?ID=ME020024