That has been my experience. You could check the log files to verify for yourself that those emails were actually passed through the process after being scanned.

Cheers,
Brett

Those files are just copies made for ClamWin to process. I always delete them as the originals have been processed, one way or the other.

Cheers,
Brett

Was there ever a resolution to this problem ?

I am experiencing the same BlockFileLock error running 10.16 Enterprise on Windows 2016 64 bit, although I don't see an IMAP crash of any sort.

Cheers,
Brett

In your Outlook accounts you must specify a logon user name and password. That logon user name must be of the form user@postoffice.

If, in MailEnable, your user is named M1 and their account is in the postoffice named X2.com, then the account logon name must be M1@X2.com.

Cheers,
Brett

In Outlook accounts make sure your login name is of the form user@postoffice. If the @postoffice part is not present then the designated default post office is used, which is why it works for you when changing the default post office.

Cheers,
Brett

I use ClamWin, but not the one supplied by ME, I download mine from http://oss.netfarm.it/clamav/ and installed the service version.

Right now I have two ClamWin background processes running, one of 2.8MB and the other with 582.5MB.

Cheers,
Brett

Rather post a support request with a Defect category at https://www.mailenable.com/support.asp. You get much better response from official channels.

Cheers,
Brett

Under the Servers branch in MailEnable Management right-click the localhost (what it says on my server) and select Properties. On the General page you can enable postoffice bindings and assign IPs per post office.

Cheers,
Brett

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 ...