Hello Bruce,

Please see this link - I think your issue is to do with Google account security, and this KB article should help.

https://support.google.com/accounts/answer/6010255?hl=en

I would start by making sure that the settings in Pegasus are correct for Google security.

Hope this helps

John.

Hi thanks for the suggestions regarding the rules.  I think I am ok just putting a 10mb limit on mercury as this has all come up because the bounce back for large mail wasnt working when it was set to zero.

Thanks Graham

[quote user="Greenman"]You can use Group Policy to force a screensaver to kick in after xx minutes. It locks the server/client.[/quote] We have such a GPO additionally in force. Locks all client machines after 15 minutes inactivity. [:D] We had to implement additional security measures after the great EU General Data Protection Regulation came in force this summer.

Cheers

Joerg

I think I have this working.  I'll be sending test files from home tonight so will know for sure in about 13 hours.

Acknowledgement and thanks to Lauri for files sent.

Thanks. I did wonder if you might have been thinking of Pegasus, but I use Thunderbird so am not familiar with it. I've been doing it at client level in Thunderbird, but my android device doesn't seem to have the facility and I was hoping to do it at server level. I can see why, on reflection, that it's not really a server function. Anyway, thanks for your help, as I now know that what I was trying to do is impossible, so can stop trying.

[quote user="Joerg"]

[quote user="Greenman"]Surreal. I've never used the Mercury as a service feature. [/quote] ... This is my solution for Windows Server 2016 Standard. Maybe not the best but I can live with.

Cheers

Joerg

[/quote]

I'm all for this. My comment was related to the rivalry you mentioned. I've never used the 'service' aspect simply because as a charity we do not have a license. Also, like you, I need to see what is going on. It's how I pick up on persistent unauthorised connection attempts, check that messages have been sent when Pegasus Mail leaves a sent message on screen etc.

Some answers here:

http://community.pmail.com/forums/thread/48975.aspx 

https://blog.clamav.net/2018/10/clamav-01002-has-been-released.html

[quote user="Supur"]You can now create an empty file called MSGIDS.MER in any mailbox

directory (i.e, a directory where a .CNM file gets created), and this

signals to Mercury that it should suppress duplicate messages in that

mailbox. Duplicate detection is based on a combination of sender and

message-ID, and only the last 200 messages delivered to the mailbox are

actually remembered.

It is a bit unclear what does it mean "only the last 200 messages delivered to the mailbox are

actually remembered"? I have thousands of messages in these folders - for which I would like to stay there (and not to be.. deleted). Probably it means that a new incomming message will be compared for duplicates only with last 200 messages in folder. Which would be good.[/quote]

We have msgids.mer in place for each of our local user mailbox accounts. Works fine as long as you don't use additional "public mailboxes". In that case Mercury has some problems in identifying of duplicates.

As soon as you put an empty msgids.mer into the user's mailbox directory, Mercury starts holding the incoming mails (for that user) additionally in a kind of cache. But this "cache" is limited to 200 mails to prevent an extensive memory using and/or processing duration. This "cache", after built up, will permanently renewed where new mails will be added and old mails will be removed. Whenever a new mail will be retrieved by MercuryD for that user, Mercury is checking its "last-200-mail-cache" whether this new mail was already delivered in past. And in case it's a duplicate, Mercury will drop this new mail.

Apparently there's wail2ban...

https://alternativeto.net/software/fail2ban/?platform=windows 

Five days without a problem... I've marked this thread as resolved.

For the outgoing mail, I found a solution using a "Filtering Rule / Outgoing Rule". As the first line, I have an "Always trigger" rule, with a "copy to another user" action. It copies all outgoing mail to my archiveoutgoing mailbox. At the same time it solves the problem that I had before using the General Ruleset. It does not copy all the internal traffic any more.

For the incoming mail I established a forwarder, as @Brian supposed. Now all  filtered spam is also forwarded to the archives. (I have only one testing set in my Content control and only one spam account. If one had more, he would need a forwarder for each).

Thank you Brian and Joerg.

Can't you run php on IIS?  IIRC that's what Roundcube is written in (same as Squirrelmail).

Hi Paul,

Yes, I did. Indeed, it was a problem with the ISP. But irrespective of this reason I was not aware that Mercury Core is always waiting for MercuryC. Especially internal mails between local users should be processed independent from Mercury's SMTP Client, isn't it?

Just received notice of the release of ClamAV 100.1

Details here:  https://blog.clamav.net/2018/07/clamav-01001-has-been-released.html

Hmm - checked my statistics and got the same.

Because all other entries in the list are real, existing users (have Novell Netware running) it may be, that these ÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌÌ are aliases pointing to an external mailaddress or are mailinglists. However - I don't see any entries for aliases and mailinglists.

Bye    Olaf

Thanks, Greenman. The settings available to me seemed correct, but I was awaiting the original link to do some testing. The sender has now said that the removal seems to have occurred at his end, possibly it's his AM that's over zealous.

I'm still a bit puzzled that one email client re-saves the CNM file on the server and the other doesn't, but it's not causing any issues so I'll consider the thread complete.

I wonder if we could tweak it to be a little more verbose......killed my global move filter rule..or somesuch

Thanks Joerg for the response. I eventually did the same. Great backward compatibility is maintained.

 At that time the mails just dropped all of a sudden.and didn't have time to test any upgrades in my working config.

Update to v4.8 solved it.

 Thanks Thomas but I'll have to try the Apache OpenSSL DLLs in a test environment over the weekend. 

That setting won't stop much spam anyway so no need to have it enabled. Alternatively you could add the sender address to the exception list to exclude it from compliance checks.