As we need to relay e-mails from a private network to gmail, we tried Mercury to replace an old free mail server we were using until now.
Everything was working good, until I closed and re-opened Mercury, authentification with gmail smtp server failed after that. I identified the problem as Mercury unable to read the hash sign (#) correctly from mercury.ini. We have such a sign in our gmail password (and can't easily change it as we have several sites already using it), and even if SMTP_Password has the right value when closing Mercury, when re-opening it the value is only read until this #.
Is there a known workaround? I tried escaping it (\#,##) but it is not working. We'd really like to buy the license so that we can start it as a service, but right now we need to retype the password in the configuration screen each time after starting it.
I cant find the way to change (enlarge) the fonts used in the To: Subject: & cc: windows when creating new mails or replies. Its easy to change the fonts in the message window, but this doesnt do anything for the other windows and for some reason unknown they have recently gotten much smaller than i recall them bieng before. Using Pmail 4.7 in Windows 7.
Is there a specific file where all these data are stored?
I have an old listserver that uses Mercury Mail. When I say old I mean prior to 2011 and running on Windows 2003 Server. I will be upgrading this to a newer version of listserver but in the meantime I need to gain back more disk space. My question is, can I safely delete .CNM files? There are several hundred thousand. They all appear to be log files of delivery failures.
I migrate from version 4.80 on March 19. (Windows Server 2012 R2). No problems occurred during and after the migration. For one week I get the following error message in the System log : The Mercury32 service terminated unexpectedy. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service. The Mercury32 service is restarted either directly by the system or by the Zabbix monitoring system. The problem is that each time Mercury32 is restarted, a new instance of the clamd.exe process is created and each instance takes 1 Gb of memory. The only information I can find in the log is the Windows Event ID (7031). Does somebody know where I can find some more information to track the problem ?. Many thanks for your help
I use Spamhalter for round ten years. And after the update to Mercury 4.8 it doesn't work no more. As always - I didn't change a thing. Any ideas? It starts up and tells "Spamhalter is running" - but obviously it doesn't work.
Hi. New standalone server on my PC. Some parts working. But right now my question is about creating the SSL certificate. I followed the manual. Popup window is 'Certificate Creation Error' stating 'The system cannot find the file specified'. I even tried a fakeout by creating a file with the same name i.e.'a.pem'. Help.
I used to run a licensed Mercury server for our company years ago but was forced to switch to MS Exchange by a new manager. I am now trying to setup my own Mercury server for personal use because I'm sick of my provider putting almost EVERYTHING in my junk folder. Unfortunately I have forgotten much of what I knew regarding the setup of Mercury. I am at the point where I am able to receive mail for my domain but I can not get aliases working. My local user name is "dstevenson" and this is what I entered in c:\mercury\mercury\alias.mer:
(domain name changed for privacy)
email@example.com == dstevenson
I exited and restarted Mercury and sent test emails from a different address but they get rejected with user not known.
What could I have done wrong with my setup? Not sure where to look. What information should I post to get help?
Hello again. I just upgraded to 4.9, and I noticed something strange. Let's say I have a mailbox on internet, called firstname.lastname@example.org M32 polls the mailbox via pop3, and deliver the mail to the local user called dummy. User dummy has a forwarding file like this
which forwards the mail to the local users userME06 etc.
Before the upgrade, this was the output in the core windows, when mail was processed
Sat 22, 11:56:23: Job MG000001: from email@example.com (non-local) To: dummy (local) -OK Sat 22, 11:56:39: Job MG000002: from firstname.lastname@example.org (local) To: userME06 (local) -OK To: userME07 (local) -OK To: userME08 (local) -OK To: userME09 (local) -OK To: userME10 (local) -OK
So, the first two lines mean that Core delivers the incoming mail to dummy, and the remaining lines mean that the mail was forwarded from dummy to the other users.
After the upgrade to v.4.9, this is the output
Sat 22, 11:56:23: Job MG000001: from email@example.com (non-local) To: dummy (local) -OK Sat 22, 11:56:39: Job MG000002: from ErrorHandler-ECA@mydomain.it (local) To: userME06 (local) -OK To: userME07 (local) -OK To: userME08 (local) -OK To: userME09 (local) -OK To: userME10 (local) -OK
Why "ErrorHandelr-etc..." instead of "dummy"? The system seems to works flawlessly, but I'd like to know the meaning of "ErrorHandler"...
Hi, the manual reports that the simplified phishing protection is account based, meaning that in case of wrong password the account becames locked for 30 minutes. Just to be sure: does this mean that, after a lock, the legitimate user, using it's own legitimate and correct password, cannot access his account for 30 minutes? Best regards Filippo
Hi. Maybe I didn't fully check the forum, but I did a search and got 0 results.
I came here to see if there were any tutorials for how to set up a mail server. Last time I had one, I also had a proper domain with A- and MX-records and all that, but that was probably 15 years ago when me and a friend ran a small web hotel that never were that popular.
We did manage to get that working (mDaemon for Windows) and it was very straight forward with explainations and FAQs. This was a long time ago, and I haven't used any mail servers since, so I'm afraid I've forgotten the most part.
Anywho, this Mercury seems very capable, and it's a bit out of my league, and I've been playing with it a bit, but I can't connect to it with my mail client, and I was hoping, as per the title, to find a simple tutorial on how to set up a functional mail server with the basics working. I was a bit disappointed not to find that here, but as I wrote, I didn't do an extensive search for anything.
Would be nice with pictures and explanations for dialogs and such.
I'm looking to rearrange the account entries in the MercuryD module. The entries themselves are obviously encrypted and simply rearranging the lines didn't work. I seem to remember something from a long time ago saying that there was a way to write the unencrypted entries to the MercuryD.dat file but I forget how. Is there a way to decrypt the entries or some other way to rearrange the order of the accounts other than re-entering them by hand?
Maybe for the last month or so, when viewing mail in the New Mail folder, I have been receiving emails where the From field and/or the Subject field are blank.
When I examine a regular email using the Raw View, I see that those fields are plain text (appropriate email addresses or subject text). When I examine an email where the From field or Subject field are blank, I see something like this:
From: =?UTF-8?B?4oCq4oCq4oCq4oCq4oCqTmV1cm9wYXRoeVRyZWF0bWVudEdyb3Vw4oCq4oCq4oCq4oCq4oCq?= <deleted for privacy>
We use the Pegasus public folders for archiving and filing. Since e.g. appointments sent from Outlook are not displayed in Pegasus, some colleagues use Outlook and Pegasus in parallel as mail programs. Unfortunately, simultaneous access to an account (with Pegasus directly and with Outlook via the Mercury IMAP interface) is not possible.
Mercury will prevent IMAP access to the account while Pegasus is open. Is it possible to change this way of working, especially since there should be no problems with Pegasus > 4.0 (see note when installing Mercury)?
If you use both the IMAP server and locally installed copies of Pegasus v3.x to access maiboxes, you must ensure that you never access the same mailbox using both at the some time.
So, you must not start a copy of Pegasus Mail accessing a mailbox that is currently being accessed by the IMAP server. Equally, you must not login via IMAP to a mailbox that is currently being accessed by a copy of Pegasus Mail.
Failure to observe this requirement may result in damaged folders and loss of data!!
Note that it is OK for multiple IMAP connections to exist to the same mailbox. The prohibition only applies to simultaneous access by MercuryI and Pegasus Mail. This problem was addressed in Pegasus v4.0, and only applies if you are using an earlier version of Pegasus Mail to access your IMAP mailboxes.