-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, October 08, 2002, [EMAIL PROTECTED] wrote...
>> The temp files are there so that TB can write the file locally >> before trying to insert into the message base..... As for the >> reason the files are there, and not deleted, you gave yourself the >> reason. Your virus scanner reads all data being written to the >> drive, and as it sees the virus signature, it stops the write, this >> returns an error to TB! as your virus scanner returns a simple file >> lock message (a cheating way to stop a program from writing data), >> so TB! cannot write to the file, so assumes it cannot destroy it >> either. This would mean there is something wrong with it, so it >> skips onto the next message. > If I understand you correctly, under normal circumstances, where no > virus is present, the temp file gets erased once it is scanned and > found clean so that the message body can be inserted into the > database. Correct? Yes under normal circumstances, and in a perfect environment. Unfortunately Windows is faaar from perfect ;) > If so, this raises several questions: > 1. why would there be more empty bat*.tmp files than error messages > warning of a virus. [...] Shouldn't there be a one-for-one > correspondence between the number of virus warnings I get and the > number of empty bat*.tmp files sitting in the Temp directory? Not always, but in theory yes. The problem arises when your virus scanner monitors all file system activity, both read and write to the disk. The order of things works like so: - Mail Comes in - TB Creates Temporary File - Virus scanner checks temporary file - TB Writes data to temporary File - Virus scanner reads data - TB moves temporary data out of temporary file into message base - Virus scanner reads data movement between two - TB tries to delete temporary file - Virus scanner reads delete attempt - TB *might* get a file lock if virus scanner is still scanning, at which point TB leaves the file. It is the last two events that cause the temp files to stay in most cases. If the virus scanner has hold of the temporary file for just a little too long, then the file cannot be deleted. Did I make it a little clearer this time? At least that is the way I'm seeing things working anyway. I write software, and we have a hell of a time with temporary files and virus scanners because of the above order of things. > 2. Because I use eZTrust antivirus, I don't have a plug-in for The > Bat. I thought plug-ins were what allowed incoming messages to be > scanned. However, it seems that I am getting those messages scanned > anyway, correct? So, what does a plug-in do that my setup doesn't > already accomplish? Yes and no. Yes your mail is being scanned, but that is because it is being written to a temporary file first, and your virus scanner is set to scan for disk read/writes. If you were to do it via a plugin, the method of scanning would be while the message is being put into the stream inside TB and would result in no disk writing until the scan is complete. If a virus is found, then it follows the settings in your plugin. - -- Jonathan Angliss ([EMAIL PROTECTED]) -----BEGIN PGP SIGNATURE----- Version: 6.5.8ckt iQA/AwUBPaMVSyuD6BT4/R9zEQK/3ACfZXDWEHFtYzceWbHMaXf0vqZQITUAnRiy nO1UKMeecQLm2Xj6K6GR5fIw =gEpX -----END PGP SIGNATURE----- ________________________________________________ Current version is 1.61 | "Using TBUDL" information: http://www.silverstones.com/thebat/TBUDLInfo.html
