I think you missed the message previous to yours, where the solution was posted.

[quote user="Brian Fluet"]... A known solution is to use the Pegasus Mail Notsplit utility to generate message files from the .PMM for re-integration back into Pegasus Mail folders but what could the approach be when Pegasus Mail is not in the picture?  An obvious answer of placing the .cnm files into a mailbox directory isn't practical when there's hundreds if not thousands of them.[/quote]

I believe in that case you've got a problem. Also in case your server (where Mercury is running) or your accessing client is a 64bit system, any IMAP client wouldn't access the mailbox directly but always via the 32bit Mercury-I. And 32bit software can address max 2GB of RAM (except some special cases of 32 bit software which is able to address up to 4 GB). Don't know whether other (64bit) IMAP server are able to access Mercury/Pmail mailboxes? Maybe someone has tested it already?
I regularly check the mailboxes of my users and carry out a search for files larger than 1 GB. If I find something, the user get a message to remove big attachments or to create a new mail folder to avoid a further increasing.

ClamAV 0.101.1 Patch has been released.  This version fixes a header problem for developers.  It doesn't appear important to us but I expect we'll soon start seeing 'version out of date' entries in the log.

https://blog.clamav.net/2019/01/clamav-01011-patch-has-been-released.html

15:37:15.971: >> 554-Bad DNS PTR resource record.<cr><lf>

The arrows pointing to the right denote the remote server's response/query (arrows pointing to the left are your server's responses/queries).

As Rolf says you need to ask your ISP to set a PTR (PoinTeR) record (a reverse lookup record which the opposite of an A Record).

As you are probably aware a DNS query for a name requests the A record so that the name (e.g. google.com) can be resolved to an IP address. A reverse record, known as a PTR record allows you to resolve an IP address to a name. Mail servers use it as a way to ensure the name the server announces itself as matches the IP address the mail message originated from.  

I think there is no need for enable > fetch > disable or not in every case. Are the iDevices from your company? If so, then let the guys run the vpn the entire time or at least for the working hours.

[quote user="Rolf Lindby"]I sent an email June 25th with the download link, let me know if I should resend. [/quote]

Has been caught in the spam filter [:$] 

4.80 backed up and 4.81 installed (update option). Setup without any problems. Mercury is running as usual so far. I will report in case anything is weird.

Thanks Rolf.

Hallo  Brian

I find this message in every logfile since 2016, so it seems it's completely normal. Why, no idea ...

 Best wishes,

Thomas

Hello Jerry,

Transaction filtering supports the "M" command which checks the Mail From field of the header. I use commands like this to filter unwanted "From" domains

M, "*.magix.net*", BS, "554 Sender MAGIX.NET is sending unsolicited email - connection dropped."

For instance,

Hope this helps

John.

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.