-=> DARYL STOUT wrote to ALL <=-

 DS>   This may or may not be the area for this, but my wife and I have run
 DS> into an unexpected severe problem with the new version of F-Prot for
 DS> Windows.

 DS>   We have used the shareware email program, Courier, from Rose City
 DS> Software, for many months now. We feel that Courier is a much more
 DS> secure email program than Outlook Express ever could be.

 DS>   For whatever reason, the new version of F-Prot for Windows (v. 6)
 DS> DELETED Courier off of our hard drives as "a security risk". As a
 DS> result, my wife and I have no way to send or receive email...except for
 DS> non-HTML text emails on my BBS...and those would bounce back to the
 DS> sender if the BBS was down for thunderstorms, etc.

 DS>   While we do have waiting email on our ISP (Aristotle of Little Rock),
 DS> there is no way we can process it. I have sent a message to F-Prot
 DS> about this...but the problem is that with the holiday weekend, it'll be
 DS> sometime Tuesday or Wednesday before my report can be processed.

 DS>   We never have had a problem with Courier, as we view our messages in
 DS> TEXT format instead of HTML (to avoid activating hidden links). But, if
 DS> we can not use Courier, we stand to lose an extremely large amount of
 DS> email that we have saved in various folders. Our only other option
 DS> would be to switch to new virus protection software.

 DS>   In short, if you use the new version of F-Prot for Windows, be aware
 DS> that it might delete your email program as "a security risk".

well, this probably isn't timely (sorry, i've been a bit busy lately)
and it probably won't help all that much but here's my take...

while i haven't used the most recent version of f-prot (i'm still on the
old one) my experience is that f-prot comes with a rather troubling
default for what to do when it encounters a virus or other piece of
malware - it tries to correct it automatically... that sounds like what
happened in your case as well... as a default behaviour that would be
fine if the program never had false alarms, but it does occasionally
have them and so that's why i changed the default settings for my system
to notify me rather than trying to automatically correct the problem...

i can't imagine that they wouldn't do whatever they can to fix a false
alarm problem, but you might want to look at the settings to make sure
f-prot isn't prone to breaking something when it does have a false
alarm...

 
--- MultiMail/Win32 v0.43