[quote user="Joerg"]But in that case are only you able to check the spam folder, since your mailbox is locked when in use? If so, are you permanently in charge for checking company's spam? With us, different persons are in charge to check the spam account regularly, especially if users miss any mails and it's also no problem when I'm on vacation etc.[/quote]
Our mailbox configuration is such that each user has his own mailbox, the accounting dept. has one for invoices, and there is a General mailbox that is advertised for all non-user specific correspondence. That General mailbox is one of the three instance of Pegasus Mail that I normally have running on my machine. The Spam mailbox is added to its folder list as an added mailbox which make me the primary spam handler. When I'm not here, an associate runs a General mailbox instance on his machine and handles the spam. Should neither one of us be here, one of us checks it via IMAP.
I also use POPFile instead of Spamhalter. One of the advantages of POPFile is that it maintains a copy of messages for 3 days (I think this number is configurable). This provides a method of retrieving a message that was tagged as spam and missed during review for false positives.
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="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.
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:
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.
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.