Hi,

There was an issue addressed in the 10.31 beta in web mail that you may want to upgrade to to see if this addresses your problem. If the upgrade does not help then please lodge a support ticket and provide the example message so we can emulate locally.

Hi,

Error (9005): Could not resolve MX list for domain [gmail.com]

The above error usually indicates that the DNS addresses you have specified within the MailEnable SMTP properties are not able to resolve correctly. Try and change to only use google DNS to see if this works (8.8.8.8 and 8.8.4.4).

Hi,

Answered your support ticket.

Hi,

If your ISP blocks inbound or outbound then your only solution is to have the port unblocked or change to a plan that allows port 25 traffic. Here is an AT&T forum thread: https://forums.att.com/conversations/att-fiber-account/unblocking-port-25-2018-version/5deff557bad5f2f6066bc3f3

Hi,

We would need access to log files and the server to troubleshoot in more detail (you will need to lodge a support ticket for this). If you have AV software on the client machine then try to disable the email filtering in the AV app. Try another IMAP email client.

Hi, The MailEnable MAPI Connector for Outlook is not ActiveSync. It provides similar sync functionality as ActiveSync and Exchange services but uses IMAP as the transport method. Therefore when you created the Outlook account did you select the MailEnable Server as the transport or did you create an...

Hi, What version of MailEnable Enterprise are you running? The web mail should list what is on the server. The only reason it wouldn't is if the _index.xml file located within the users folder is corrupted. You can force an index update by creating a change flag file. Open Windows Notepad and save a...

Hi,

There are no issues executing Outlook rules. How are you connecting to the MailEnable server? Via IMAP, POP, MAPI connector or ActiveSync? Would need to know which rule is not executing and how its formatted. I.e: criterion, action etc.

Hi,

Yes it was. It is in the 10.31 beta on our beta page.

Hi, What parameter is not changing when you edit the option in the administration console? What version of MailEnable are you referring to? If you run the MailEnable diagnostic report are there any errors relating to database connectivity? Also if you are trying to migrate MailEnable configuration a...

Hi Martyn,

For a managed response, yes. Will be easier for a tech to gain access to the server to check further.

Hi, Order doesn't matter. Are there any errors logged within the Windows event log viewer under the "Application" log relating to when the licensing error occurs? Would need access to the server via RDP or Teamviewer to check further but for this to occur you will need to lodge a support request. ht...

Hi, Sounds like the Windows environment variable paths for the MailEnable BIN and BIN64 folders have not been set. Open a Windows command prompt and type: path. In the output check to see whether the MailEnable installation paths for BIN and BIN64 are present and match your active MailEnable install...

Hi,

You need to check the created date of the mai to see if it meets the criteria you have set in the mailbox cleanup agent. The purging agent checks the created date of the message file.

Hi,

Ensure that you have restarted the MailEnable server after you installed MailEnable as the environment variables need to take affect.