Although not (yet) formally released, the 3.32 version can be downloaded for quite a while now. It includes the following features:
- Has a new MercuryS compliance page option to allow failure after a certain number of relay attempts.
- Should allow authenticated users to submit mail even if they connect from a blacklisted source.
- The mail server now has its own password file, created and managed on the "Mail server" configuration page. This is not covered in the help yet, but you can create any number of mail server passwords that can be used in a "PASSWORD" command to handle the new operations described below. If you have no password file, then no password will ever succeed and the new operations will fail automatically - hence the operation is secure by default. Mail server passwords are simply one-per-line (like everywhere else) and cannot contain the character ';' (semi-colon).
- A new mail server command, "KILLFILE" has been added. This command allows you to manipulate the MercuryS killfile by mail. At present, the only implemented command is "KILLFILE ADD", which adds the parameter you supply to the MercuryS killfile. An example:
To add *@163.com to the MercuryS killfile, issue these commands (foo4u is a demo password here):
PASSWORD foo4u
KILLFILE ADD *@163.com
This command need to be preceded by a PASSWORD command specifying a valid password from the password file created in the mail server configuration dialog.
- A new mail server command, "RELOAD" has been added. This command allows you to force Mercury to re-read certain configuration files by mail. At present, the only implemented command is "RELOAD USERS", which takes no parameters, and tells Mercury to reload the user database, PMAIL.USR.
To force Mercury to reload its user database, issue these commands:
PASSWORD foo4u
RELOAD USERS
This command need to be preceded by a PASSWORD command specifying a valid password from the password file created in the mail server configuration dialog.
- This version includes a new "compliance" option for MercuryS: the new option is called "Check originator address fields against the killfile", and it works in conjunction with the standard MercuryS envelope killfile test. If the option is enabled, MercuryS will check the "From", "Reply-to" and "Sender" fields of the message against the killfile as it processes the DATA state; if any matches are found, the message is discarded (so it never passes through the queue), and an error diagnostic is returned to the client.
- IMAP CREATE commands will now fail if a folder already exists with the specified name.
- MercuryI will no longer crash on very large COPY or SEARCH commands, and the allowable length of these commands has been significantly extended.
- This version has a couple of very fundamental changes to deal with UID problems identified recently. Most significantly, it
now generates significantly more arbitrary filenames when creating new mail messages.
- There is a new feature in MercuryE - transcript generation. With fewer and fewer servers supporting confirmation of delivery now, it's getting increasingly more difficult to get any kind of real proof that a message has actually got to its destination. To get around
this, MercuryE can now be instructed to generate a transcript showing
acceptance of the message by a remote system. To do this, turn
transcript processing on in the MercuryE configuration dialog, then add the following custom header to your mail message:
X-Transcript-To: <address>
where <address> is the address to which the transcript should be sent.
When MercuryE sees this header, it records the details of the transaction with the remote server and sends them on as a kind of documentary evidence that a message was processed at a particular time. The X-Transcript-To: header is removed during processing, so you can't get "transcript cascades" as a message bounces around. Transcripts are also only generated when a message actually contains at least one successful delivery, so you won't get a flurry of transcripts showing repeated delivery failures.
- Folder creation via IMAP should now generate some diagnostics in the system messages window.
- The "exceptions" logic in the MercuryS "Compliance" page should now correctly reduce addresses to their minimal form before checking them. So, an address like "<David@pmail.gen.nz>" will now be reduced to "David@pmail.gen.nz" before comparing against the list.
- In particular this version should no longer have problems creating folders
|