Utility converts the .101 files quarantined by Clamwall to Pegasus Mail CNM files. See the
text file included in the zip file for details

Program POPWatch runs on background of Mercury/32 and blocks "bad"

connections to MercuryP (Mercury POP3 server). It should mitigate brute force

attacks to POP3 server.

So blocked is such address, from which more than "AuthFailures" connections

was done AND delay between them was shorter than "ClearTime" minutes

AND in no one connection was done successfull authentication.

So such address, from which something repeatedly tries to login with

incorrect credentials.

This is a small Daemon for Mercury/32 that disables the close button for the various module windows, and adds a Display control sub menu under Configuration. Hiding a window will not close it, only make it invisible. This should otherwise not affect the functionality of Mercury in any way.
When you need to access the dialog window for a module again just select it in the menu and it will reappear.This version of the Daemon is updated for Mercury 4.7x and 4.80.
DlgCtrl.zip

Program WSMTPEx "moves" emails from given inboxes of the Mercury program to another SMTP server. It is suitable e.g. for relay of some mail accounts to another server - in fact it works opposite way to the MercuryD module.

It expects mailboxes in the form of Pegasus Mail / Mercury mail server (or anything, what stores mails in folder as CNM files in plain text RFC822/RFC2822/RFC5322 format).

WSMTPEX.EXE works on Windows.

• It works with Windows 2000, 2003 and WindowsXP. It was never tested on Vistas.
• It has BadMail folder - mails with permanent errors are moved to separate folder
• It has support for domain mailboxes (looks into mail file for real address to send to)
  
• Uses the X-Envelope-To: address added by Mercury/32 when the mail is put into the domain mailbox.
  

Version: 0.28

This is an event daemon for Mercury. An event daemon has the ability to interact closely with Mercury modules, in this case the SMTP server module, and change the way a message is processed.
The SmtpEvt daemon is based on the previous RcptEvt and RcptCheck daemons but has some added functionality.
In most cases it's probably a good strategy to leave the option "Accept mail for invalid local addresses" unchecked in MercuryS configuration and have the SMTP server refuse deliveries for non-existent local mailboxes. Still there may be circumstances where you prefer to receive mail even if for instance the recipients address has been slightly misspelled (which is why the option exists, obviously).
The SmtpEvt daemon will attempt to combine the information known by MercuryS before the message body is received to reject messages for non-existent local mailboxes that most likely are junk. It will check for X-Blocked headers added by blacklists and sending characteristics often used by spam bots, and will see if the message is a notification (delivery failure notifications to non-existent mailboxes are presumably never worth receiving).
Testing has shown that this actually works surprisingly well. The daemon itself is very lightweight and should not increase system load noticeably. Still, I would not recommend using it in production unless you have first verified that it behaves satisfactorily in your environment.
To install it, copy SmtpEvt.dll to the Mercury directory and add the following line to the [Daemons] section of DAEMON.INI: SmtpEvent = smtpevt.dll
Additional features:

• The daemon has the option to block messages with a bad local sender address. If a MAIL FROM command with an address that belongs to a local domain is issued the daemon will check if the mailbox exists. If not, the connection will be terminated. If 5 such messages are received within 5 minutes the host will be added to the short-term blacklist.
• If a message with identical MAIL FROM and RCPT TO is found it will receive an informational header saying "X-Identical: From and Rcpt identical". If the sender is on a blacklist the connection will instead be terminated.
• The daemon will watch out for mass mailings with big attachments from local users that will be likely to put the server under heavy load. If the number of recipients is too high and the message is too large the message will be refused.
• Check Subject header for spam indicators that you have added to a list. If there is a match and the message is either for a bad local recipient or the host IP is a DNSBL hit the session is terminated and the host is added to short-term blacklist. To enable the configuration dialog for this feature please add the following line to the [Daemon_Config] section of DAEMON.INI: SmtpEvent = smtpevt.dllFile updated March 2019.

SmtpEvt.zip

This is a small daemon that simply sets the display state of the Mercury window when the program is started. It defaults to showing the program maximized (covering the entire screen), but with a parameter it can for instance be used to minimize the window.
MercMax.zip

<p>These pages allow you to view and add new accounts quickly and easily. They also detect and remedy duplicate logins - do if JS1 exists, it will create JS2.</p><p>Also - these pages will create an ALIAS using the forenames and surnames used at logon creation :


Thanks

Bozmeister
</p>

Sorry I messed up again, that's Petr Jaklin not Jacklin. I can't edit the post either to hide my error. ;-(

This and other daemons/software by Petr Jacklin can be found at http://www.3net.cz/software/softe.htm

There is a newer version with a bug fix MercFwd0002.zip at http://www.3net.cz/software/

Deprecated - please use the new SmtpEvt daemon instead!

This is an experiment with the new event daemon type that was presented in the recently released Daemon Developer Kit for Mercury. An event daemon has the ability to interact closely with various Mercury modules, in this case the SMTP server module, and change the way a message is processed.
In most cases it's probably a good strategy to leave the option "Accept mail for invalid local addresses" unchecked in MercuryS configuration and have the SMTP server refuse deliveries for non-existent local mailboxes. Still there may be circumstances where you prefer to receive mail even if for instance the recipients address has been slightly misspelled (which is why the option exists, obviously). To avoid bouncing a lot of spam to (usually faked) sender addresses GrayWall is a great tool. Blacklists like Spamhaus, however, that normally are good spam fighting tools, won't help much in this case if set for tagging rather than rejecting (which is the most secure way to use them).

The RCPT Event Daemon will attempt to combine the information known in MercuryS before the message body is received to reject messages for non-existant local mailboxes that most likely are junk. It will check for X-Blocked headers added by blacklists, it will check for sending characteristics often used by spam bots, and will see if the message is a notification (delivery failure notifications to non-existent mailboxes are presumably never worth receiving). If no such indication is found and the RCPT is accepted the daemon will still increment the failed RCPT count for the transaction so the compliance check of failed RCPTs can be performed for multi-RCPT messages. Any action taken by the daemon can be seen in the MercuryS console window and log file.

Some testing has shown that this actually works surprisingly well. The daemon itself is very small and should not increase system load noticably. Still, I would not recommend using it in production unless you have first verified that it behaves satisfactorily in your environment. It requires Mercury 4.5 or higher version.

To install it, copy RcptEvt.dll to the Mercury directory and add the following line to the [Daemons] section of DAEMON.INI:
RcptEvent = rcptevt.dll

In some installations of Mercury the function to stop sending more than one autoreply to the same recipient during a 48 hour period doesn't work. This is a small daemon that restores original functionality by making sure that timestamp for the .kfl file is actually updated when it should be. Additionally, the daemon gives the opportunity to filter out autoreplies to certain addresses that never should receive any (like "noreply@somedomain.com". Please see the enclosed readme file for further information.

This is version 1.2.0 of the web admin package for Mercury/32 that I

originally created in 2004. It was first created mainly to provide my

users with a web interface for changing auto-replies and forwarding,

but additional admin functionality for showing server status, viewing

log files etc was included as well. Version 1.1.0 added tools for

creating new user and new alias, starting, stopping, and restarting

Mercury, and putting server offline. In this version the program has been updated to support Mercury 4.61, and log files for SpamHalter, GrayWall and ClamWall can now be viewed.

Please read the included readme

file for more details. You will need to edit the http.ini file before

running the program. For creating new users you should have at least one Maiser

password defined, otherwise a restart of Mercury is required.

The

package includes all needed server functionality, no additional HTTP

server software is required. Web templates are user-customizable if you

want a personalized look. Networking is based on , created by Lukas Gebauer.

/Rolf 

Hi

   When I uploaded "mercury acl" I inadvertently only uploaded the source code.  I received a request for the binary to be included. The attached file now includes the program binary and an html description of what it does.

Cheers Richard
 

I downloaded this but am not clear on how it works. There doesn't appear to be any executable files in the archive and I also copied the files to my mercury directory, thinking something might show up in mercury but so far, nothing. Am I suppposed to compile them somehow. I like what it says it will do I just can't get it to do it.

Graywall is a program that adds a graylist (or greylist) feature to the Mercury/32 SMTP server. It uses the Mercury/32 API facility that has been introduced in version 4.51. You must have at least this version of Mercury/32 to run Graywall!

Information about graylisting in general can be found at: . We recommend that you read this first.

Graywall is a program that adds a graylist (or greylist) feature to the Mercury/32 SMTP server. It uses the Mercury/32 API facility that has been introduced in version 4.51.

Virprot is a silent 32 bit console application that is invoked by Mercury, and in turn
invokes the user choice of anti-virus scanning software.
The result of the scan is passed back to Mercury in one of two ways:
  Return code method
  Sentinel file method
 

See Virprot.txt included in the distribution zip file for details on setup and options available.