Another option is to use fsynonym.exe. Create a text file (e.g. mail-names.txt), which maps to local mail account name:

jony@domain1.com == jony1
jony@domain2.com == jony2

You then use fsynonym to parse the contents of the text file to a file named synonym.mer

Check out the documentation. We use Mercury to manage the mail for 3 different domains and this works fine.

I found the reason:
Mercury is RunAs different user on my system. Two users cannot access the sound system simultaneously ("Another application is playing audio. You can either interrupt the application or wait until it is done. Then try using Sound Recorder again.").

So it's neither a bug in M/32 nor that common file formats wouldn't work in M/32.
Just for the record: A possible workaround was to Run a program with the parameter C:\WINDOWS\system32\runas.exe /savecred /user:[LoggedOnUser] "C:\WINDOWS\system32\sndrec32.exe /PLAY \"C:\MERCURY\notify.wav\" /CLOSE"
or such. I did not test that out though as a system monitoring is running on that server anyway where I just add a log file test for system.log.

 HTH, Rainer

P.S. Happy new year [D] !

[quote user="Brian Fluet"]Changes to the .conf files are indeed rare but I prefer to do a file compare of the samples from the existing and new version and then use the new ones when there are changes.
[/quote]

I agree - that's best [;)]

[quote user="Brian Fluet"]

I am using Mercury in a Windows environment but have the same problem.  I first discovered it when I upgraded from v4.74 to v4.80.  See my thread here:

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

The response made me  wonder if I was lucky that mailbox corruption didn't occur but it sound like you had users operating the same as I did with no problems.  It cerrtainly doesn't sound like it is a good idea to override the lock [/quote]

I'm sure that's true and is the way I've always understood it.

I've just seen a similar problem and posted details (including a session log) in a separate topic here:

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

Googling the error I saw had some interesting results, as discussed here: 

http://openssl.6102.n7.nabble.com/openssl-update-1-0-1f-to-1-0-1g-broke-sendmail-SSL23-GET-SERVER-HELLO-tlsv1-alert-decode-error-td49242.html

In this case it looks like a fix implemented in 1.0.1g of OpenSSL caused some compatibility issues in certain mail servers, resulting in the same error I saw with Mercury 4.8.  Mercury 4.8 shipped for me with OpenSSL 1.0.1h.  Not sure if the same issue is still in the 'h' release, but it seems related.

Mark 

According to David Harris, there is no fixed limit of number of subscribers in Mercury mailing list.

I would also recommend to update to v4.80

In past wee also experienced occasional Mercury crashes from time to time, often in connection with the establishment of SSL connection to our ISP. Sometimes once a week, sometimes only once per month or more rare. But since we have updated to v4.80 at the beginning of this year, no further crashes. We are happy.

Please let us know if a daily maintenance restart does not reset that counter.

Edit:  I withdraw this clarification inquiry because a during a reread of Rolf's post it became apparent he is talking about an OS restart and not a Mercury restart.

Send a mail via SMTP to yourself and have a look at the received headers.

But what is the problem stopping and starting Mercury?

Regards

    Olaf

I noticed that the last couple of years messages from one folder were missing.

My fix:
I knew some text that would be in the most recent missing email, so I searched the MAIL\username folder for that text using Agent Ransack.
This identified a PMI/PMM pair that held the missing emails.
They had a different filename from the current truncated files.
I closed Mercury and concatenated the files together, via the good old 'copy /b' DOS method.
Starting Mercury again and looking at the folder with 'eM Client', I see the messages now exist, but only the Date column is correct, not message content.
Then I tried mxmaint_ui.exe - A 'Check' showed invalid index numbering or something. A 'Repair' completed with a not-too-scary warning.
Starting Mercury again, then eM Client..... all my messages are there!!! (Just had to mark some as read).

Hope this can help anyone else who strikes the same problem.

I see. Many thanks. 

Last post in this thread.

Today I sent a message to 7 local addresses. I added the addresses to the Cc field via an address book which lists all local accounts. Two accounts did not receive them. Mercury had 'killed' them.

I chose 'resend this message' and sent it to them individually and they received the messages.

Neither of these accounts are subject to mail filtering at all.

This is a PITA, but I can't see any way around it.

I've not upgraded to 4.8 yet as I have a ton of other things to do. Hopefully, that will sort this weird issue out.

No need to respond.

They may be the cause of the "still trying" messages - but in this case the messages were delivered OK.

That's basically it, switch modules and restart Mercury. I assume you already checked that the new ISP isn't blocking port 25 for outgoing messages and that there is a reasonable PTR record for the IP address.

OK so I made another test:

I opened a mailbox with IMAP, removed the connection to the network from the computer running the IMAP client, and closed the IMAP client. The connection was still up in Mercury's console, and the lock file was still there. I reconnected the network and opened the mailbox again. Mercury now showed two concurrent IMAP connections to the mailbox. The mailbox was fully accessible, except messages could not be deleted (which is expected behavior with more than one IMAP connection).

Multiple IMAP connections to the same mailbox are allowed, so if one connection is lost due to client side failure it makes no difference for creating a new one.

The best shot at finding out what actually happens when your user gets locked out is probably still to try to catch it in a session log. 

[quote user="RP_Joe"]So if you have a small office can  multiple people on workstations access the same mailbox?[/quote]

Yes, but not simultaneously.

[quote user="RP_Joe"]I am thinking about the webmail feature. 

If we set this up to pop our addresses from the web hosting company, then two of us can process the email from the local Mercury server, using webmail.  Is that possible ?

Could two of us use a imap client? [/quote]

Yes, but with some limitations, one of which being that a simultaneous IMAP connection to the same mailbox prevents either user from being able to delete messages. 

If the need is to share the same mailbox with full functionality by each user then you have no choice but to take turns.  If you just need to share messages then there are a few ways that come to mind using a multiple user configuration in Mercury.

• Use a filter in Mercury to copy messages to the second user.  Configuration can be such that it appear to recipients that replies made be each user came from the same sender.  Alternatively, the copied message could be filtered to a folder associated with a specific identity configured such that replies appear to come from the appropriate sender (assuming Pegasus Mail is the email client).  A permanent BCC in the configuration can copy the other user on all replies if that is needed.
  
• Use a filter to copy messages to a directory that is added to each users folder list as an added mailbox.  One problem with this approach is that changes made by one user (like deletes) are not reflected in the other users message list until the mailbox is manually refreshed.
  
• Create a public folder and filter messages to it.  Public folders are visible in the folder list to all users of the system.
  

A problem with the last two options is the handling of copies to self as this can not be automated if it is important that each user have access to the copies to self.  They will need to be manually directed to a copies to self folder in an added mailbox or to a second public folder (public folders can not contain trays).  Obviously the best option depends on the ultimate goal of the sharing.

Hi folks 

Can anyone confirm the following behaviour and suggest some way I may work around it? 

I'm using a SYNONYM.MER file to customise the email addresses used by Pegasus in the FROM field of outgoing emails.

My current synonym.txt file I created years ago contains 37 lines.  7 of them are like email1@example.com == username(1-7), and the other 30 are email2@example.com == username(8-37).  Therefore,  username on each of the 37 lines is different, but there are only 2 email addresses shared amongst the 37 users. 

I'm trying to change 3 of the 30 lines from email2@ to email3@, but as my subject states, the  FSYNONYM.exe program which accepts the synonym.txt file as an input and SYNONYM.MER as an output claims that 1 email address can not be mapped to multiple users.

The Mercuy help file regarding the subject hasn't changed since I last made a modification, but it seems that the FSYNONYM.exe program has, and not for the better.

Any and all help appreciated.

Thanks 

EDIT1:  After some looking I believe I see where this problem is.  I suspect the last time I ran FSYNONYM.exe I was using Mercury4.7x.  The program there states it is "Mercury File Import Synonym Database Builder v1.00".  While in Mercury 4.8x, the FSYNONYM.exe version is v2.00.  v1.00 had no issue with synonyms to multiple users, but v2.00 does.

EDIT2: Since edit1, it solution is quite obvious.  Thankfully I have a backup of the Mercury4.7x files, and used the FSYNONYM.exe from there to update my SYNONYM.MER file.  And then simply copied that file to the places it needed to be.  However, I would hope that the change in behaviour from v1.00 to v2.00 of FSYNONYM.exe was for a good reason.  So, is there a new, more suitable method to using the old program, or is this change unexpected?

Hi, i will share you my Website, where you can Download the latest OpenSSL 1.0.2x for your Mercury. Many Binary Builders switching to OpenSSL 1.1.1x so its hard to find the old LTS Version. My Build is Compiled with standard options of Openssl and is full compatible exept of the HEARTBEATS option wich is disabled. Just Download the ZIP and copy the 3 Files inside the BIN Directory, to your Mercury Folder. You have to use the VC-32 Version.

https://www.bk-net.tk/?cat=15 < Normal Build

https://www.bk-net.tk/?p=1206 < Special Mercury Build (without sslv2, sslv3 and rc4) 

No solution.  The problem is exactly as you describe.  Mercury locks the mailbox when it is being accessed by IMAP, Pegasus Mail locks the mailbox when it has access.  One thing that makes it frustratingly worse is that iDevices do not release the IMAP connection even when the device is turned off which is causing real problems for our people who what to use the Pegasus Mail client while at their desks but rely on IMAP access from a variety of iDevices when traveling. They have no choice but to ignore the lock warning of Pegasus Mail.  I think I have had to repair folder corruption only once because of this.

The questions was asked regarding why it is a problem in v4.8 but wasn't in v4.74 and the response was that v4.74 must have been broken because simultaneous mailbox access can cause corruption regardless of the type of connections.  For me it would be helpful if a connection attempt by Pegasus Mail on an IMAP locked mailbox generated an option to disconnect and block any IMAP connections during the session.  This would work because my folks already know to call in and have someone shut down their Pegasus Mail when IMAP attempts hit a locked mailbox. 

FWIW, Mercury handles all of our mail processing and spam filtering so there is no advantage for a user to leave Pegasus Mail running.

Switch on session logging for MercuryD temporarily to see exactly what happens!