You are in a sticky situation. Read below --

On 5/3/07, Voxen <[EMAIL PROTECTED]> wrote:
Hi,

My application is storing email messages in a SQLite database (raw email
messages as they are downloaded from the mail server).
This is done under a transaction.

Sometimes I get the SQLITE_MISUSE error and by watching the antivirus
(Avast) log, I found this:
Sign of "Uruguay 6/7/8" has been found in "C:\Documents and
Settings\Voxen\Application Data\MyApp\mail.db-jounal" file.

This means the antivirus found a virus in the transaction journal file and
removes it. Its altering the journal file and then produces a
SQLITE_MISUSE error.

How can I work around this?
Do I need to ZIP or encode the email message before storing it in the
database?


Your antivirus software is doing you a favor by removing the virus,
and you really don't want to stop it from doing so, else your db will
be carrying the virus within it.

On the other hand, the antivirus software is really like another user.
Just like you can't stop a user (or yourself) from destroying the
journal/db file, you can't really stop the antivirus software from
doing so.

Perhaps you could implement an antivirus scanning _before_ you insert
the messages into your database. Of course, then you would not only
have to write such an antivirus software portion yourself, you will
have to distribute the antivirus-strengthened email program to all
your users.

Otherwise, yes, you would have to stop your av software from scanning
your db, but that means your db will be carrying viral payloads.

Dang!

--
Puneet Kishor http://punkish.eidesis.org/
Nelson Inst. for Env. Studies, UW-Madison http://www.nelson.wisc.edu/
Open Source Geospatial Foundation http://www.osgeo.org/education/
---------------------------------------------------------------------
collaborate, communicate, compete
=====================================================================

-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------

Reply via email to