No idea but I assumed that, as it was part of MailEnable, giving one of their accounts full access couldn't hurt. You could experiment by granting lesser rights and checking when the warning disappears.

Cheers,
Brett

I had the first warning after moving a server from 32 bit Windows 2003 to 64 bit Windows 2016. I just gave IME_SYSTEM full access permissions to that file and the warning was cleared. The second warning means you haven't set up auto-discovery, so can safely be ignored. The third warning is because y...

I added a DNS blacklist for cn.countries.nerd.dk which is blocking quite a few Chinese connections.

Why not simply change the inbound SMTP port on your ME instance to a non-standard value? As long as your spam filter can be set up to communicate on this non-standard port, your ME instance will no longer be locatable by the general public.

See my reply to your other post on the same question. The system needs to differentiate between users with the same login name in different post offices, which is why there is a requirement to include such. The default post office just simplifies the process by automatically adding the default post ...

Only users in the default post office can log in without having to use the post office name in their login. Everyone else must use the post office name as you have already discovered.

MailEnable Enterprise Release Notes =================================== 9.79 7th November 2017 ---------------------- IMP: Significant Upgrades to Mobile WebMail 9.78 22nd September 2017 ------------------------ FIX: Migration Strategy for Exchange would raise an exception in the Migration Console ...

It looks as if you are checking that there is a valid DKIM key rather than checking the email itself.

Use the checker at https://9vx.org/~dho/dkim_validate.php and paste the entire raw contents of the email to check whether DKIM is passing or failing.

Cheers,
Brett

The account can also get locked if, for instance, the incorrect POP (and probably other) password is entered three times in a row. Seen this happening with one of our employees who can't seem to remember any passwords at all.

Cheers,
Brett

Here is some code from a vb script that dealt with the SMTP-DENY tab which might help you: FUNCTION OpenMailEnableAccess Response "Opening Mail Enable SMTP-DENY configuration..." dim obj set obj = WScript.CreateObject("MEAOSM.Access") Response "Done.<br>" set OpenMailEnableAccess = obj set obj = not...

ME Console > Servers > localhost > Extensions > Domain Keys (DKIM). Right-click the Domain Keys entry and select Properties then enable DKIM functionality (I assume this is why you get the "not enabled globally" message).

Cheers,
Brett

You are welcome - glad it is still helping people.

Cheers,
Brett

I don't use the URL blacklisting, only DNS. I had to get rid of Barracuda because it was blocking legitimate (for us) mail sources. I use SpamCop and SpamhausSBL-XBL. We get quite good results from those two. Stats for this month are SpamhausSBL-XBL blocks at 12,886 and Spamcop blocks at 17,964. Che...

I happily added the [*.*.*.*] entry for EHLO blocking only to find that all the company Android and Apple devices could no longer send email. They were being rejected as they all use their IP address for EHLO/HELO and I can find no way to change this behaviour.

Can it please be confirmed that the wildcard feature mentioned by @Admin is available in 9.54. There is no mention of it in the changelog.

Regards,
Brett