Zaep AntiSpam Release Notes

Check here to read a detailed list of archived Zaep releases.

Zaep AntiSpam Version 4.1.0.3

Zaep 4.1.0.3 was released January 9, 2006. A complete list of changes and upgrades follows:

FEATURES:

• Added additional log strings to Zaep plug-in for certain error conditions that allow messages through unchallenged.
• Changed plug-in log message warning about a missing "From" address to more accurately identify the missing address as the "Return-Path" to avoid potential confusion.
• Improved Zaep's ability to detect forged messages where spammer pretends message is sent from yourself.
• Added the ability to have Zaep delete messages that have no return-path email address. See the Preferences window of the Administrator configuration for more information.
• Update copyright dates to 2006.

BUG FIXES:

• Corrected a bug where Zaep was unable to log in to certain mail servers due to the way responses were sent from the mail server.

Zaep AntiSpam Version 4.1.0.2

Zaep 4.1.0.2 was released November 1, 2005. A complete list of changes and upgrades follows:

FEATURES:

• Added ability to rebuild Plugin.Pending storage map from messages contained in the Pending directory. This is done automatically if no Plugin.Pending file is found during startup. It can also be forced to be done at startup by setting the value of %REBUILD_PLUGIN_PENDING% to '1' in Zaep's registry settings.
• Added checking of Return-Path for emails. If no From or Reply-To address is provided, the Return-Path is used to send the challenge (if one is present).
• White and Blacklisting of addresses now applies to Return-Path email addresses in addition to existing support for From and Reply-To email addresses.
• Removed Zaep.exe.manifest from installer. It's now included in the build of the executable.

BUG FIXES:

• Corrected an issue with releasing pending messages when installed as a plug-in where a pending message with multiple local recipients may not be properly released if all local recipients don't release the message at the same time.
• Corrected an issue with loading the Plugin.Pending storage map.
• Corrected a potential overflow bug with Zaep Plugin that could occur after a long time on busy mail servers where the pending filename generated by Zaep would become too long.
• Corrected a bug where the Reply-To email address of a message was incorrectly parsed from the message.
• Corrected a bug where the Reply-To email header was used as a comparison for list checking instead of the email address parsed from the Reply-To header.
• Corrected an issue with Zaep Plugin where messages having a different From address from their Return-Path were incorrectly tracked by Zaep making it difficult to release those messages when criteria for releasing the message was created (via a white/blacklist entry, subject word, etc).
• Corrected a bug that dealt with a flaw in Microsoft's socket support where IOCtl could return that no data was waiting to be received, which wasn't true. This could cause POP3 sessions with many messages or attachments to appear to hang.
• Corrected a bug in the Zaep Configuration Server where HTTP headers were terminated with a single instead of double when responding to certain queries.

Zaep AntiSpam Version 4.1.0.0

Zaep 4.1.0.0 was released September 26, 2005. A complete list of changes and upgrades follows:

FEATURES:

• Added ability to bind challenge sending socket to IP address used for confirmation server. This feature is useful when Zaep is running on a server with multiple network interfaces to ensure the sending IP address matches the HELO domain.
• Removed restriction on 2 connecting computers for Zaep Standard licenses. Zaep Standard is now restricted solely to 6 email accounts.
• Added support for specifying a confirmation domain name with an alternate port that differs from the port the confirmation server is listening on. This can be used for people who wish to have confirmation URLs directed to an alternate computer, where they are redirected the Zaep confirmation server.
• Added ability to specify a HELO domain/IP address to override Zaep's default setting. By default, Zaep uses the confirmation domain name in its HELO command, or the computer's local IP address if no confirmation domain is specified.
• Re-enabled ability to turn off automatic account creation for Zaep when installed as an MDaemon plugin.
• Added ability to insert the Zaep Challenge Key in to the challenge message using %CHALLENGE_KEY%.
• Removed usage of ZaepNT.exe and replaced existing Zaep.exe with a unified EXE that performs operations for both, regardless of system platform.
• Improved robustness of Zaep's ability to parse the Zaep challenge key from the subject of challenge responses. Previously, some mail clients would insert erroneous spaces into the key or break up the key across multiple lines of the message headers.
• Increased receive buffer size for improved performance.
• Reduced susceptibility to MDaemon API changes by limiting the functions loaded through MDaemon's user API to only those explicitly required by Zaep.
• Added RTF license file to installer.
• Replaced existing "About" and "Register" dialogs with enhance, unified SAPrefs style dialogs that contain more relevant information and is consistent with the style and presentation of other RhinoSoft.com applications.
• Added support for enhanced XP style pop-up menu from the system tray icon.
• Various minor tweaks and performance enhancements.

BUG FIXES:

• Corrected a non-compliance with RFC2821 where IP addresses used in HELO command sent during a challenge weren't enclosed in square brackets.
• Corrected problem where Zaep couldn't locate the paths of certain queues in MDaemon when installed as a plug-in. Older versions of MDaemon made using non-default queue locations easier. Zaep now retrieves queue locations from the MDaemon.ini file.
• Corrected a plug-in bug where only the initial challenged message would be approved when an address was manually whitelisted.
• Corrected a rare plug-in bug where if Zaep could hold the original message for challenge, but was unable to also hold the corresponding CTL file, the original message would be lost.
• Corrected an issue where an update to MDaemon changed the format of a CTL file, causing Zaep to be unable to determine the sender of a message. Zaep now checks for both values and will parse the .msg file for the sender address if the CTL file does not contain this information.
• Corrected a problem where logging out the Windows user when installed as a plugin would cause Zaep to shutdown, which forced MDaemon to shutdown as well.
• Corrected a bug where a GPF could occur while checking the registration ID before installing a new version.
• Zaep Setup message boxes now contain the application name in the window title bar rather than the name of the executable.

Zaep AntiSpam Version 4.0.0.5

Zaep 4.0.0.5 was released June 9, 2005. A complete list of changes and upgrades follows:

BUG FIXES:

• Corrected potential bug where archived information totalling less than 100 bytes may not be saved properly.
• Corrected a problem with some email servers, when data packets were potentially divided by the client, the server would become confused making large email transfers appear "hung".
• Corrected a problem with MFC socket core where application was not always notified of new received data.
• Corrected a mistyped version number in Version.txt (this file).

Zaep AntiSpam Version 4.0.0.4

Zaep 4.0.0.4 was released May 5, 2005. A complete list of changes and upgrades follows:

BUG FIXES:

• Corrected the usage of an incorrect default challenge template.

Zaep AntiSpam Version 4.0.0.3

Zaep 4.0.0.3 was released May 4, 2005. A complete list of changes and upgrades follows:

BUG FIXES:

• Corrected text display error in final dialog of Zaep Setup Wizard.
• Corrected bug that caused original sender's message subject not be used in challenge messages.

Zaep AntiSpam Version 4.0.0.2

Zaep 4.0.0.2 was released April 18, 2005. A complete list of changes and upgrades follows:

BUG FIXES:

• Fixed bug that could cause challenge messages to be incorrectly sent.
• Fixed bug that showed Plug-in configuration menu when Zaep wasn't installed as a plug-in.

Zaep AntiSpam Version 4.0.0.1

Zaep 4.0.0.1 was released April 15, 2005. A complete list of changes and upgrades follows:

FEATURES:

• Added support for Zaep to run as a plug-in with MDaemon 8.0. As a plug-in, Zaep does not run as a proxy for mail clients and is not tied to any mail delivery protocols.
• Zaep can now create new accounts using default values stored in DefaultUser.ini.
• Added percentage information to statistics pages.
• Updated to MFC 7.1.

BUG FIXES:

• Zaep no longer supports Windows 95.
• Fixed bug where Zaep couldn't parse key from email challenge responses when responder's mail client breaks subject header on to multiple lines in the middle of the key.
• Fixed links to DNS4Me web site in confirmation web server help documentation.
• Pending challenges for addresses added to the white list via "sent message to" approval are now cleared from pending challenges list.
• Fixed bug where mail retrieval would fail the first time it was performed on an automatically created account.
• Fixed bug where automatically created accounts didn't preserve a global POP3 server port value that was non-standard.
• Various minor configuration enhancements and corrections.