THINGS THAT MUST BE DONE

* The whole "rfd" thing shoudl be rewritten to use FILE. It would be more efficient.

* Don't remove the debugging stuff; you always wnat it there. 

THINGS THAT COULD BE IMPLEMENTED

o New configuration file format and parser. It seems to work quite ok
  for people, and I don't want to waste time if I don't have to :)
  Granted, it is not hard to make a mistake while editing configuration
  file, but I have better things to do with my time :) Please, always
  run "# virge -C" and "# virge -R" after any changes to configuration
  file or extensions file. Don't forget to actually *read* the
  output :)

o Usage of "templates" for easier layout of notification mails

o Setting up the order of scanning (virus/attachments - and vice-versa)

THINGS THAT WILL NOT BE IMPLEMENTED

o "Rewriting" mails infected with viruses. In past 12 months, I have
  not seen (a single time) a mail with virus that had any valuable
  content in it. Either it was a trojan, a worm, or just plain stupid
  virus. Gone are times of people sending Word documents  with virus
  attached, *on purpose*. Simply, I am not going to put effort in such
  a feature. If someone else wants to add it, please go ahead.

o I have no intention of "hacking" Virge to work with command line
  scanners like TrendMicro's "vscan", Sophos's "sweep" and others.
  It could be possible to do it, but then the whole point of making
  Virge in the first place is lost. Virge is *light on resources*,
  and I want it to remain that way.
  
  NOTE: If someone can (by some miracle) get TrendMicro to release
  their API specs for their LIBVSAPI library, I'd be happy to make
  "Sophie 2" (or whatever we can call it :) and integrate it with
  Virge. I have tried to get specs, but they wouldn't give it away.


