For the "DoNotDeleteExpiredEmailsFromQuarantine", please see this entry from our documentation:

;Use this option to prevent SpamFilter from performing the routine cleanup of the
quarantine database by deleting old archived emails. Useful if admins want to perform
their own cleanup
DoNotDeleteExpiredEmailsFromQuarantine=false

With the default setting - 0 - SpamFilter will perform the routine cleanup.

However the other parameter, "DeleteExpiredEmailInterval", is used to determine how often (in minutes - 60 is the default value), SpamFilter performs the database cleanup. If this is set to 0, as in your case, SpamFilter will never perform the cleanup, having the same effect of the above parameter. If this is 0, you should be using a different method for purging the database. Some admins use scheduled scripts/stored procedures in Microsoft SQL Server to perform the purge if they have large databases (several GB in size) as these can be optimized to put less strain on the SQL Server (we have a sample SQL Server script available if you wish, but do not have one for MySQL).

The "ArchiveSpamDays" is used to tell SpamFilter to delete emails older than those many days when performing the routine cleanup (which is not occurring however in your case).

The emails should be delivered as the manual states when the Deliver field is set to 1. If that is not happening, if you can please zip and email us SpamFilter's activity logfile for a day (along with the to/from email addresses involved), we'll take a look. If the zip is over 5MB in size, please upload it to our FTP server (I'll PM the login details to you).

Looking at your entries from the database (thanks for including them even without us asking! Without them I would have not been able to make the following theory) we may have spotted the issue.

All the records below have the value "2" for the "serverid" column. The "serverid" is used by SpamFilter in installations where there are multiple servers running SpamFilter. Each server must be able to "recognize" the spam it inserted into the database in order to allow that server to them deliver those emails if needed. This is accomplished by using another table, the "tblServers". If you look in that table, it should list an old server with an ID of "2", and your current server with a different ID.

As these IDs are incremental, it looks like at one point you installed multiple copies of SpamFilter on different servers (or renamed the server's name). This caused the current serverid in the "tblServers" to be out-of-sync with the existing "serverid" column in the tblQuarantine. Since the serverid values now mismatch, your current SpamFilter is not able to deliver emails that were quarantined by the server corresponding to serverID 2.

The solution is rather simple. You can either locate the correct "serverid" value for your server in the tblServers, and change all records in the tblQuarantine to match it. Alternatively, we use the special reserved serverid of "0" to act as a wildcard, allowing any SpamFilter server the ability to send that email.

You can thus either issue the following query (replacing the "1" with either the correct serverid for your server, or using 0) :

UPDATE tblquarantine SET serverid = 1;
or
UPDATE tblquarantine SET serverid = 0;

If you are using multiple SpamFilter servers rather than a single one, do not use the "0" but rather do use the correct ID.

If this is not the problem, please email us your SpamFilter.ini file so we can take a better look.