[quote user="Brian Fluet"]

The VIEWER.PM files make up the list displayed in the Content Viewer.  I say "files" because there can be two.  One is system-wide (valuable for you).  It resides in the PMail executables directory.  The other one is user specific and resides in the users mailbox directory.  In Content Viewer, the black entries are from the user file and the blue are from the system file.[/quote]

But system-wide VIEWER.PM is only available when we're talking about a Pmail network installation, where all local users start it's Pmail session from the same server shared executables. In case you prefer a single installation on each computer, you could not use this advantage.

[quote user="Aimo Maileri"] P.S. Sorry, this was mailed in wrong department. Belongs to "Pegasus", not "Mercury".  [/quote]

I suggest re-posting this inquiry in the Pegasus Mail support forum where it will get the attention of the appropriate brain power. 

As a starter though you can try Ctrl+W to open the IMAP new mail folder.  That key combination opens the default new mail folder. 

Receiving an email addressed to email1@domian.com, an alias sends it to a particular user - user1.  If it's for another user, user1 will manually forward it to them.

ClamAV 0.102.2 has been released

Details here: https://blog.clamav.net/2020/02/clamav-01022-security-patch-released.html

[quote user="Joerg"]Only one e-mail caused that problem? Delete it and the problem is gone. This is the most fast solution. [/quote]

If only the message has been worthless.  Unfortunately, it wasn't disposable.  It contained a form in its body that had to be printed, filled in, signed, scanned, and returned.

[quote user="Joerg"]Or try to forward it to another user (not bouncing, but with editing before forwarding), deleting it, and returning it back from the other user to the original user. Does the problem keep?[/quote]

I've already copied the .cnm to multiple other mailboxes and tested on different machines.  I can only duplicate the crash when running as that user, regardless of the machine.

[quote user="Joerg"]Another try is to remove the personal viewer.pm from the affected user and replacing it with the one from another user where this e-mail works. The viewer.pm  file is still a suspicious file for me without complete understanding[/quote]

The purpose of rebuilding the mailbox was to get all new configuration files, that included viewer.pm.  Only message files, folders, address books, and the recently used file where brought in from the old mailbox.

[quote user="Invictus"]

Slightly embarrassing - permission settings included for LOCAL admin not Domain admin...all seems ace now.

Thanks for reading my post

G 

[/quote]

[Y] 

Thanks Rolf. That's good news.Having had both cataracts done myself, before the age of 54, I can empathise with David.It's quite a surreal world you see in brilliant white afterwards! :-)

Tym

CWSCAN 3.2.4.9

Introduction

This program works alongside the ClamWall daemon from Lukas Gebauer.

It takes the messages flagged by ClamWall as bad, adds the reason for

rejection as a header, and inserts the message into a specific user's mailbox.

It is designed to be used when you have false positives (FPs) and want to

receive those messages normally.

See Mercury Add-ons area for downloading 

Of course! Say that you want all mail to mydomain.com to go to the mailbox MyDomainDM. First create a user called MyDomainDM. The go to the Local domains tab in Core configuration and add an entry like this:

DM=MyDomainDM             mydomain.com  

Domain changes sometimes require a restart of Mercury so you may need to to that as well. 

[quote user="Brian Fluet"]PaulW mentioned IMAP as a multi-user protocol which makes sense but got me to thinking about filtering.  I don't use IMAP so am not knowledgeable about filtering capabilities.  Could simultaneous filtering by multiple connected users be a problem or is filtering just local?[/quote]

I would take for granted that the filter rules are nevertheless working as expected, since all mailboxes will still be polled via POP3 Mercury D from our ISP mailboxes. And also the sending process will still be carried out via Mercury C and has to pass the Mercury Core Module.

[quote user="Brian Fluet"]I know very little about Roundcube but believe that it sits between Mercury and the user with user login to Roundcube and not directly to Mercury I.  If true. this would explain the lack of a lock file as compared to IMAP via Thunderbird or an iDevice directly to Mercury I.[/quote]

But in the end Roundcube is also only an IMAP client. Roundcube is installed as a webserver in our company LAN (Linux server) providing an webmailer GUI where the user has only to navigate to an URL and needs the login credentials to its mailbox. Roundcube is directly interacting with your local (Pmail) mailbox, via Mercury I.

I will made further tests during the next days to check whether any inconsistencies appear when different users simultaneously operating in one PMM file.

[quote]Best choice so maiser gets a plain text mail is to have formulars by ...

• enabling the webinterface of mercury or ...
• creating a web contact formular by your own calling a script that sends a plain-text-mail to maiser (had that with option for subscribe and unsubscribe).[/quote]

ClamAV 0.102.1 and 0.101.5 patches have been released!

Details here:   https://blog.clamav.net/2019/11/clamav-01021-and-01015-patches-have.html

Thanks Jim.  I ended up with only 54 entries in the distribution list and didn't experience any issues other than the expected handful of delivery failures.

What we experienced: Do not save any changed Mercury D settings when Mercury D is just retrieving mails or polling mailboxes. In that case Mercury is not taking over the changes. Our Mercury D is polling our 20 mailboxes every 120 seconds and I have to wait for the finish of such a polling cycle before using the SAVE button of Mercury D. Alternatively you could set Mercury in offline mode until you've made your changes.

Depends on the installed version of SSL. Please read  

I found the problem.   Running clamd.exe in a command window showed in invalid entry in clamd.conf, the result of an error by me.

I have upgraded.  All seems well.

Did look through the files to see if any issues. Also had the ISP setup an outer perimeter spam filter in hoping it catches one of these emails that are getting bounced. My understanding is that the sender will not get any return errors or message so that might be an option for hints 

Hi Brian,

first of all: happy new year and all the best for 2020!

[quote]My thinking is to create a global filter in Mercury that could detect and delete such autoforward messages. 

Would a filter that looks for "To:*utf-8*" work?[/quote]

Yes ... but this will filter all mails with utf-8-encoded header TO. Because you only want autoreplies to be filtered, you should add someting like:

AND "Subject:*Autoreply*"

 Bye    Olaf

I just talked with a support tech at our domain host. He was able to see some of the messages coming in without a date header but said they can't do anything about it.  His understanding is that the sending SMTP server should be adding a date header to any message submitted without one.  The organizations from which I receive these messages are huge companies running their own SMTP servers do there isn't any hope of me initiating a resolution.