After years of running Pegasus mail without issues, a problem with receiving new mail has arisen and I hope someone can help me. Upon start-up the Pegasus mail “you have new” mail pop-up banner appears (as normal) and may repeat many times if there is a lot of mail to download (as normal); however, no new mail appears in my inbox. I tried upgrading from version 4.80 to the new 4.81 Beta, but that did not solve the problem. However, if I shut down Pegasus mail and then re-start Pegasus the new mail now appears (under my red "is urgent” mail). Another new problem that seems to have occurred simultaneously with the above problem is that Pegasus mail very often will not close normally anymore. I must use Task Manager to force Pegasus to shut down. Hopefully you may know a fix without a complete re-install? However, if I do need to do a uninstall /fresh install to solve this problem how can I make sure that my past inbox /outbox and all my folders will be brought back into the program normally, without losing emails or setting preferences?
Thank you in advance for your help! Kind Regards, jacobsfw November 16, 2023
T 20231106 112910 65480d05 Established ESMTP connection to 22.214.171.124 W 20231106 112910 65480d05 421 4.7.0 [TSS04] Messages from 126.96.36.199 temporarily deferred due to unexp T 20231106 112910 65480d05 Job MO000013 processing complete.
unexp what exactly?
I've noticed repeatedly that the error logs cut off half way through any meaningful message.
The mobile versions of Microsoft Outlook have broken support for using STARTTLS during an IMAP connection. After sending the first STARTTLS command and receiving a reply, they send a second, spurious STARTTLS command. This gets misinterpreted as a bizzare, implausibly high TLS version by OpenSSL, which causes it to cut the connection. Outlook then reports an alleged "certificate error".
Outlook Mobile is still able to connect using the legacy port which uses TLS from the beginning. However, if you connect to the normal port, if it detects STARTTLS support it will attempt to use it even if you attempt to configure it not to.
There's a Python mail suite called Twisted that includes an IMAP server implementation and TLS implementation in pure-ish Python. I was able to build a toy server and patch it so that if received a TLS version of 63.48 (for example), instead of immediately disconnecting it tried to reinterpret that packet as a cleartext IMAP command and, if it was STARTTLS, send another affirmative reply and restart TLS from there. With this patch, Thunderbird, Outlook desktop, Outlook mobile, and Twisted's client libraries were all able to connect and run without issue.
I know this is awful, that OpenSSL goes out of its way to make it hard to support this -- and with good reason -- and that Microsoft should fix their application to comply with the IMAP specification. However, I've reported this problem to them several times and they won't fix it. There is no MercuryI Events support in the DDK (and its internals are specifically and explicitly not documented, unlike most of the rest of Mercury) so I can't fix this on my end; if I'm to get this to work, I'll need it in Mercury itself.
(I'm posting this here because the Feature Suggestions forum doesn't allow new topics, I don't think this is within the scope of a technical support incident, and Mercury's licensing system is down anyway so I couldn't file one even if I was wrong.)
We almost exclusively use Thunderbird as IMAP client here. It works very well and fast with the Mercury IMAP server. However, we noticed one thing ... In TB we always move edited/read emails to other mail subfolders, so that the inbox folder remains clear. But if you switch back to Pmail in between, there is a completely different, higher number of mails in the inbox folder. I.e. there are sometimes quite a lot of mails still in the inbox folder, which have long been moved to other subfolders in TB. The moved mails also arrive in the subfolders and are also visible there in Pmail.
Moving mails is also not accompanied by any error message. A consistency check of the individual mail folders in Pmail also shows that everything is fine.
Furthermore, we can also access our mailboxes using Roundcube IMAP web client. There I can at least see that the affected emails have already been marked as "deleted" (disabled). So to me it looks like mails are copied to the subfolders, but then only marked as "deleted" in the inbox folder.
Is there a "timer" somewhere when mails marked as "deleted" are finally deleted?
I like automation, for what else do we have computers!
Assuming some people, like me, could use a little advise to automate the renewal of the Certificate process for Mercury, I had created a batchfile which will renew the Certificate using , copy and rename the files to be able to use by Mercury and run it at a certain time using the Task Schedule. There is also Apache involved, as I am running Roundcube for my IMAP connections. In my case I am using the standalone version and therefore I need to shut down Apache to have port 80 or 443 free to use by Certbot spinning up a small webserver.
And I just did a succssfull run.
Certbot located at c:\certbot Mercury located at d:\mercury
Here we go: create a batchfile and call it by Task Schedule with elevated user rights.
First: stop Apache service: net stop apache2.4
Second: start the Certbot renewal process: cd to certbot\bin and call certbot renew which will renew one or all certificates which are close to expire.
Third: start Apache service: net start apache2.4
Fourth: copy the files needed by Mercury TO Mercury and rename them at the same time. Files needed are: c:\certbot\live\domain\fullchain.pem and c:\certbot\live\domain\privkey.pem To make this happen we use xcopy xcopy c:\certbot\live\domain\fullchain.pem d:\mercury\mercury.pem /y xcopy c:\certbot\live\domain\privkey.pem d:\mercury\mercury.prk.pem /y The /y switch is set to quitely overwrite the files after the first renewal.
Comments: Name of Apache service my differ. IMPORTANT Note: do not rename the files in the original certbot folder as the renewal process is looking for the original file names. If you want NOT to move the files to d:\mercury and keep them in the original file location, that will propably work, but I have not tested it. I like to keep things clean and seperate.
The full batch file will look like this. You can add comments as you wish.
@ECHO OFF :: :: stop apache net stop apache2.4
:: start renewal process of all certbot certificates :: cd to certbot.exe
cd certbot\bin certbot renew
:: start apache net start apache2.4
:: copy certificate from your domain for mercury. Files to copy & rename :: are fullchain.pem > mercury.pem ; privky.pem > mercury.prk.pem :: use xcopy to overwrite file quietly /y :: rename isnot possible as certbot is looking for the original filenames xcopy c:\certbot\live\domain.com\privkey.pem d:\mercury\mercury.prk.pem /y xcopy c:\certbot\live\domain.com\fullchain.pem d:\mercury\mercury.pem /y
The only manual change is to set a new date in Task Schedule for the next renewal.
This is very basic and I am sure there maybe other ways. Maybe we can add them and make it better?
Hi, first I have read through a bunch of posts looking for answers on here but nothing really relates to my issues I am having as such. I will first explain my setup then explain what I have tried.
My router (192.168.1.1) which is forwarding all traffic to my computer (192.168.1.2). Ports opened for the mail server are 25, 143, 587, 465 and all point to 192.168.1.2 which is my only computer, nothing else connected to my router. Windows Firewall disabled, no other firewall or antivirus (fresh OS install) and I am using windows 11 Pro.
My ISP is talktalkbusiness and to connect to their smtp servers I use port 25 strait connection plain text and not secure. I use my username and password they provided for me.
The smart host name I use is smtp.talktalkbusiness.net
it was all working fine for years and I changed nothing but a few weeks ago connections began to be refused or timed out when connecting to my ISP's server. The message I was getting was Error FF queue job.
The log files really told me nothing apart from conenction timed out. I have been in contact my with ISP and they say over n over n over again it is my end not theirs.
I can not really find a realistic step by step guide on how to properly configure Mercury Mail but I did have it working fine before despite changing nothing.
Under Protocol Modules I have the options ticked as follows...
AFAIK the auto-reply (e.g. out-of-office notification) functionality of Mercury could only be controlled by Pegasus which is adapting and changing the file extension of the "areply" file.
In the meantime more and more colleagues retire Pmail and replace it by Thunderbird which is collaborating great with Mercury.
But a simple adjustment of Mercury's auto-reply function by another Mail client is missing. Either we have to keep installed another Pmail installation, only started for switching the areply function, or we have to edit the areply file manually. But we don't want to grant every user full write access to its mailbox directory.
So the pdf file for mercury mail says that if you use the run a program option for a filter..
"The Run Program rule action will start the specified program, passing a temporary copy of the message on the commandline"
Well it's not working! I thought i was imagining it so i used a small test program i have for displaying parameters that are passed via the command line... no parameters are passed to it from mercury mail.
It does indeed start the program but it does not pass any parameters containing the email.
I really need this as i need to run a second mail server on the same machine on a different port (it's custom for another website and sends email via http to a url). If mercury can call another program and pass the email then the second program can simply pass the email via tcp connection to my other mail server.
Without the email being passed though, i'm unable to get this working.
I have not been able to send emails from Win-Pm to my Spectrum account since July 20th using Win-Pm .. I can still receive and download messages as normal. Accd to the error message log the email address I used for authentication is not the same as the address I've sent from. I've redacted my addresses in the log below, but they are the same. Also I can send email using an identical profile from my iphone or using the web-mail site. The problem occurs ONLY with Pegasus (both 4.8 and 4.81).
12:31:58.786: --- 30 Jul 2023, 12:31:58.786 --- 12:31:58.786: Connect to 'smtp-server.carolina.rr.com', timeout 30 seconds, flags 16842753. 12:32:00.005: >> 220 p-impout006.msg.pkvw.co.charter.net cmsmtp ESMTP server ready 12:32:00.005: << EHLO [192.168.1.19] 12:32:00.070: >> 250-p-impout006.msg.pkvw.co.charter.net hello [188.8.131.52], pleased to meet you 12:32:00.070: >> 250-AUTH LOGIN PLAIN 12:32:00.070: >> 250-SIZE 30000000 12:32:00.070: >> 250-ENHANCEDSTATUSCODES 12:32:00.070: >> 250-8BITMIME 12:32:00.070: >> 250-STARTTLS 12:32:00.070: >> 250 OK 12:32:00.077: << MAIL FROM: SIZE=2244 12:32:01.080: >> 550 5.1.0 XXX@sc.rr.com sender rejected. The email address you are sending as must match the email address you used to auth. Please check your SMTP settings. AUP#Out-1500
Hi, I have set mercury to save PDF-attachments from e-mails. Now Mercury should "Highlight" this e-mail in colour red. Unfortunately, the function is not executed.
If I use the Filter-action "Add a header to the message" (X-PMFLAGS: 128 1), the e-mail is displayed in red, but unfortunately the formatting does not fit for some emails. Is there a way to insert X-PMFLAGS: without formatting the email?
Since the last MS updates of April, which we've installed on our MS Server 2016 on weekend, Mercury GUI has been terminated automatically different times.
No any error messages found, neither in Mercury logs nor Windows event logs. Has anybody an idea?
The Mercury service will be started on each server restart. And on next opportunity we quit the service and start the Mercury GUI manually to permanently see the Mercury "dashboard" on the server desktop. This worked for years.
Our organisation has recently migrated to Microsoft 365. Since then I have been unable to access emails using Pegasus.
Instructions were sent that as yet do not include Pegasus, but do include Thunderbird.
Here are the settings for Thunderbird.
I have noted that there is an option in Thunderbird to use Oauth2 as a method of authentication. This option is not available in Pegasus. I noted and found the option for gmail when setting up a new account but this does not work for my usual email address.
In addition I did find the settings provided by the Kansas State University to access emails using Microsoft 365, no mention was made of Oauth2 and these settings did not work.
I was successful in accessing my yahoo domain email address by following the instructions provided by Yahoo. It gives an option of using Pegasus as a third party app and provides a one time password.
Any solutions would be very much appreciated. I have been using Pegasus since the 1990’s, and continue to appreciate it.
I have setup a moderated mailing list in Mercury 4.91 with 2 moderators. Listmembers are able to send to the list and should get their own replies. I just tested the list with my member address and Mercury started working the list. And than came the strange and buggy part: The sender was not my member address The From address was formed of the 2 moderators email address. It created a total mess.
MercuryE log: T 20230424 212520 64473626 Begin processing job MO000016 from email@example.com firstname.lastname@example.org T 20230424 212523 64473626 Established ESMTP connection to 184.108.40.206 T 20230424 212523 64473626 MAIL FROM:<email@example.com firstname.lastname@example.org> SIZE=1368 E 20230424 212523 64473626 553 5.1.3 <email@example.com firstname.lastname@example.org>... Invalid route address T 20230424 212523 64473626 Connection closed normally.
I can't see any wrong settings in my list configuration which could cause such behavior. I have 2 lists with 130/150 users. Years ago with Mercury 4.01 I did not have such problem.
We have setup mercury to receive emails by SMTP and then distribute the emails to POP3 mailboxes.
However, I don't seem to be able to find an option to tell mercury what domains to accept emails on and which to reject.
I've found the global filtering rules for distribution, but the only way I can find to receive emails is to untick this option "do not permit SMTP relaying of non-local mail" - however when I do this, although I do receive emails, my IP address is then advertising as an open smtp-relay when I run an SMTP check on the IP at mxtoolbox.com website.
Hopefully I am missing something here, and hoping someone can point me in the right direction.
Hopefully once this is all sorted, I can then purchase a licence to help support the development of the product.
Hi all, why do I receive the same message inbox more than one, sometimes there can be up to 4 copies in the inbox. This happens when a non-local sender sends a message to more than one email address (to, cc).
That I have now successfully TLS working with Mercury, I am wondering how to improve the cypher list Mercury is using. As I have not found any settings in this regard, is there some way ? And if, where and/or what has to be done ?
I am experince a strange problem with Mercry's authentication. It does not matter if STLS is advertised by Mercury and/or used by the clients. Depending on the module I can authenticate or I am not able to authenticate.
Testing different clients it all comes down to that I can only authenticate using PLAIN authentication which I find quite strange. CRAM-MD5 no way to be successful.
Mercury 4.91 with: Pegasus 4.80 pop3 is working smtp session gives me "wrong username or password" even if I tick "do not use CRAM-MD5 if advertised" tried smtp with seperate username/password pair and the pop3 login. No success
Thunderbird imap & smtp only with plain username possible, with & without STLS offered by Mercury and used by Thunderbird
Roundcube imap & smtp only possible with plain username. Do not use STLS as it is on the same server.
Mercury C 4.7 smtp client from a different location sending to Mercury 4.91 with CRAM-MD5 not possible using MercuryD to pickup mail no problem
All error messages are "wrong password or username" as mentioned above.
Is this normal? How are you authenticating, plain or CRAM_MD5 or...? I don't know where to look anymore.
In Pegasus mail smtp I can't even choose how to authenticate. I am totaly stuck. How is pop3 authenticated, as it is working ?