Hi, Best way forward would be to lodge a support ticket and provide access to the log files and MailEnable server so we can troubleshoot in more detail. If you use the [domain]/[username] reported in the migration utility activity log exactly the way its formatted to authenticate via the EWS URL doe...

Hi,

Nothing has changed that would cause the type of behavior your seeing. Best way forward is to lodge a support ticket and then provide the relevant information so we can help you further.

Hi,

I've answered your support ticket with more detail. However are you able to telnet to the gmail host names listed in the screenshot outside of the MailEnable application within a Windows command prompt to see if you can establish a connection?

Hi, Would need details of the domains your trying to send to that are hosted within MailEnable. Do you see the incoming transactions in the SMTP log files that complete successfully? Also check the SMTP Debug log file and search for the same message ID's in the SMTP Activity log file to see if there...

Hi,

What was was the solution? A restart?

Hi, Can you click on the "Activity" button under the "Monitor" tab where the mailboxes are queued within the migration utility. Check the username that is being used to authenticate and then use the exact same username when you perform your tests in a browser or via the Microsoft test connectivity w...

Hi,

The beta kit has been updated can you try the new release on the beta page.

Hi,

Did you restart the SMTP connector after enabling the option? Also try and telnet locally on the server to "localhost" on port 25 and then check to see if the "StartTLS" extension is reported. This is a test to ensure that a proxy or gateway is not causing problems.

Hi,

Please see: https://www.mailenable.com/documentation/10.0/Enterprise/SMTP_props_-_Inbound.html

Hi,

Would need specific details of the domain names etc of all servers. Your best way forward here would be to lodge a support ticket and provide all the detailed information and log files.

Hi,

Nothing has changed int he administration console to affect the available global filtering options. Do you get options if you right click on the "Filters" node?

Hi, If you restored the registry from the old license server and the CPU count and server name on different on the new server then this will be your problem. You need to follow the steps in the article below and request an updated license key for the new server. https://www.mailenable.com/kb/content...

Hi,

There are other significant fixes and improvements to MailEnable core services that you require, therefore upgrading is recommended.

Hi,

What is reported within the SMTP activity and debug log files? Are you routing external emails via a spam proxy/firewall?

Hi,

Have you reviewed the migration utility documentation and configured the utility to capture the mailbox details? Otherwise you would need to export the mailbox details from hMailserver to a csv or txt file and then import the mailboxes into the relevant postoffice in MailEnable.