Using the web interface, users are frustrated that they cannot have their spam immediately removed from their lists.  They prefer to delete small groups of emails at a time and slowly trim their lists down, but when they select spam to delete, press "Delete" and the spam still remains on their list, they get understandably frustrated.

Why the hour delay with the web interface, but instantly with the GUI interface?

The delay for the web interface is terribly frustating.

I was in the process of creating a Administrator Web interface so I wouldn't have to use the crippled GUI, but the delay is even worse so I am shelving that idea for now.

The web interface should not show quarantine entries that have been marked for deletion. The SQL statement that shows the list of messages should filter out the records that have the "Expire" and "Deliver" fields set to true. Are you using the PHP or the APS interface?

Roberto Franceschetti
LogSat Software

I am using the Access db that was included with the latest version although I doubt that is the issue.  Basically when users hit the Delete button thier screen refreshes but the checked items remain but become unchecked again.  Checking the db, the items are tagged in the db field for deletion, but it is not reflected in the web interface for them.

Ideas?

Are you using the ASP or the PHP web interface?

Roberto F>
LogSat Software

I am using the ASP interface.

I think I found the problem.  I looked in the db and noticed that items tagged for deletion are changed from 0 to -1, but in the SQL string in the ASP page, it is filtering Expired items that are marked <>1

 SQL = SQL & "WHERE (Deliver <> 1) "
 SQL = SQL & "AND (Expire <> 1) "

Adjusting the ASP to "(Expire <> -1)" seems to do the trick.

The "(Deliver <> 1) " does appear to work properly.

Is this a coding error in that Expired items in the db should be set to 1 if marked for deletion?

Alan,

In the file "ResolveSpam.asp" there should be the following:

  SQL = "UPDATE tblQuarantine "
  If cmd = "Delete" Then SQL = SQL & "SET Expire = 1 " Else SQL = SQL & "SET Deliver = 1 "

(Without the "Word Wrap")  Or the Access DB equivalent.  The Deliver is to be set to "1" not "-1"

Dan S.

Bizarre.  I checked that ASP page and it does say "SET Expire = 1"

Pasting from my editor:
  SQL = "UPDATE tblQuarantine "
  If cmd = "Delete" Then SQL = SQL & "SET Expire = 1 " Else SQL = SQL & "SET Deliver = 1 "

Yet expirations get set to -1 in the db.  Really strange.

Strange nobody caught that before. Good call! We'll most likely change the web code to say (Deliver = 0) and (Expire = 0) so that it will work in all cases. MS Access does indeed change the field to a -1 even though it's set to 1.

Roberto Franceschetti
LogSat Software

You aren't talking about changes to the existing behavior are you?  I don't use the "Standard ASP code ... all custom stuff.  Also, for ref, isn't MS Access a bit wimpy for this application?  My MS SQL database is hovering around 3GB.  I was not aware that access would function at that level.

Dan S.

It appears this issue applies specifically to Access and two conflicting lines of script in two of the basic ASP pages that were available for download.  Modifying one line of script from <>1 to = 0 resolves the issue.