Roberto F.
LogSat Software 

// New to VersionNumber = '2.1.2.395';
{TODO -cNew : Added graph in Statistics tab to show emails blocked by filter type}

// New to VersionNumber = '2.1.2.394';
{TODO -cFix : Exceptions on RECEIVEMESSAGE can appear if quarantine database becomes unavailable, and remote server receives error response rather than customized error depending on filter}

// New to VersionNumber = '2.1.2.393';
{TODO -cFix : "Do not quarantine" option is enabled for a filter, a generic "500 Address Error" is returned instead of the customized response}

// New to VersionNumber = '2.1.2.392';
{TODO -cFix : If SPF filter returns a softfail or a pass, the MAPS and local IP blacklist filters are ignored}
{TODO -cFix : New MX filter caused emails with empty MAIL FROM to be rejected}

// New to VersionNumber = '2.1.2.391';
{TODO -cNew : Check valid MX record on receive}
{TODO -cNew : Add option for max connections per remote IP address}

// New to VersionNumber = '2.1.1.388';
{TODO -cFix : Fixed SPF bug introduced in build 386 - SPF queries had incorrect "none" results}
{TODO -cFix : whitelisted emails were forwarded to alternate dest SMTP server if using option new in build 387}

// New to VersionNumber = '2.1.1.387';
{TODO -cNew : Added SpamFilter.ini option to forward email tagged as SPAM to an alternate destination SMTP server}

// New to VersionNumber = '2.1.1.386';
{TODO -cNew : Modified SPF lookups to search for SPF TXT record even if hostname is not a domain}

// New to VersionNumber = '2.1.1.385';
{TODO -cNew : Add label to indicate "Bayesian Probability results show up in Corpus Database tab"}
{TODO -cFix : if more than 3 RCPT TO's were specfied, spam emails may have not been filtered}
{TODO -cNew : Add option in INI file to specify directory path for logfiles}

// New to VersionNumber = '2.1.1.384';
{TODO -cNew : Fixed "Exception occurred during RECEIVEMESSAGE: Cannot create file...." errors}
{TODO -cFix : FQDN was missing from Welcome banner}

// New to VersionNumber = '2.1.1.380';
{TODO -cNew : Removed changes to activity window introduced in build 379 as they caused performance issues}

// New to VersionNumber = '2.1.1.379';
{TODO -cFix : SPF queries that matched the MX mechanism would fail the 1st time a domain was queried. Once in the DNS cache, queries were fine}
{TODO -cFix : SPF queries check parent domain is right-hand side of email address is not a domain but a host name}
{TODO -cNew : Modified behavior of activity window - does not autoscroll unless cursor is placed at end of text}

// New to VersionNumber = '2.1.1.378';
{TODO -cNew : Added filename blocked by attachment filter in activity log}

// New to VersionNumber = '2.1.1.376';
{TODO -cFix : Incoming connections were dropped immediately when the DATA stream exceeds the max message size, sometimes before receiving the 55x error code}

// New to VersionNumber = '2.1.1.375';
{TODO -cFix : Subject keyword searches were case sensitive, not anymore}
{TODO -cFix : Faster SPF queries when exceeding max include loops, better handling of default value}
{TODO -cFix : Fix "Check if in ORBS" button access violations}
{TODO -cNew : Changed log syntax from "Will be quarantined" to more generic "Will be rejected" as the label also applied to emails being disconnected without being quarantined}

// New to VersionNumber = '2.1.1.373';
{TODO -cFix : SPF - Again fixed neutral behavior due to regression error with previous build}

// New to VersionNumber = '2.1.1.372';
{TODO -cFix : SPF - fixed issue with logfile becoming huge due to loops in SPF include directive}

// New to VersionNumber = '2.1.1.371';
{TODO -cFix : SPF neutral records were being rejected}
{TODO -cNew : Added ExpireRetryQueueHours SpamFilter.ini parameter to optionally limit retries to destination SMTP server if it is unavailable}

// New to VersionNumber = '2.1.1.370';
{TODO -cFix : Default AutoWhiteList file path now correctly defaults to SpamFilter directory}

// New to VersionNumber = '2.1.1.369';
{TODO -cFix : Unusual messages that contain <CRLF>.<CRLF> sequence in email headers are now received correctly}
{TODO -cNew : Added better support in subject keyword searches - keywords will be searched for in entire subject, not just at start}
{TODO -cNew : Blank addresses are not added to the AutoWhiteList anymore}

Hi

1. Thanks for a very good product. I'm private mail admin for about 10 users. I have some questions about the eval vs. registered version, due to some problems. You say that spamfilter eval is full functioning though I have some problems. When a user requests a password (registers) from the ASP pages the e-mail with the password aren't send before I manually "Force delivery" a mail through th GUI, is this a eval purpose, or will that work in the registered version? I have been forced to use quite a lot time to track down the problem. I can see that the e-mail is in the database with a delivery=1, but as I wrote it isn't delivered before i manually force delivery on an email.

2.A little autoWhiteListForceDelivery.txt question. The file is empty though I have forced deliveri on some false positives. The FD works, but I don't have control over it, as the txt file i empty, is this an eval problem?

3.Are you considering a small business license? I think 600$ is a lot of money for a private person. For my company though this would be no problem, I would even say cheap.

BTW: I'm running newest Spamfilter ISP 2.1.2.395 on a Windows 2003 server with Exchange 2003 backend. Running very nice, thanx again.

Best regards...

Torsten Christiansen

Hi again

1. I have read that the sample ASP won't deliver e-mail's that the user tries to send. My question was about the register function, where the user registers with his/her e-mail address. After registration the e-mail with the password is added to the database with a deliver=1. The e-mail isn't delivered until I force delivery on any email in the QDB through the GUI.

2. I didn't get an answer on the autowhitelistforcedelivery.txt question. When I get a false positive I force delivery on that email. I can see in the logs/logdisplay the spamfilter adds the sender and receiver to the txt file. But when I open the txt file the file is empty? (BTW the e-mail is delivered when I FD (Force deliver)). I just don't like I'm not in control of the the txt file. Don't like its empty. When a sender/recipient has been added, days after spamfilter still delivers e-mail with the sender/recipient information as it should, so where from does it get its information?

Best regards

Torsten Christiansen, running 2.1.2.395 EVAL hoping to get a discounted license in the future.

Thanyou very much.

Ok about the mail delivery. I'm going to register....

About the WhiteListForceDelivery.txt, in my case It has been placed under c:\windows\system32 with content, in the spamfilter.ini it was a relative path. I have now put in an absoulut path and It now works as I thought it was ment to.

Just to help others:

Before: (spamfilter.ini)

AutoWhiteListForceDeliveryFileName=AutoWhiteListForceDelivery.txt

After: (spamfilter.ini)

AutoWhiteListForceDeliveryFileName=X:\Program Files\SpamFilter\AutoWhiteListForceDelivery.txt

Thanks for very good support

Best regards...

Torsten Christiansen