TIP: Click on subject to list as thread! ANSI
echo: nthelp
to: All
from: Dave
date: 2004-06-23 03:12:10
subject: Re: Agent 2.0: corrupted database

From: Dave 

This is the reply I received from Forte Agent support:

_______________________________________________________________________

Hello, David.

On 6/21/2004 at 1:10 AM, d_n_b{at}swbell.net wrote:

> SuptSubject: Inbox corrupted by virus?

Not by the virus, but perhaps by the attempted virus removal.

The details of the following is specifically for Norton Antivirus, but the
general idea is for any antivirus tool:

To configure Norton Antivirus 2000 or 2001 for use with Agent, follow the
directions in NAV for enabling the email protection.  Then, configure Agent
using these directions:

In Agent, Options \ Inbound Email \ System: Username, add a slash and the
server name of the POP server after your username like this example:

       userid/pop.isp.com

then change the POP Server setting to 127.0.0.1  Click OK.

To configure Norton Antivirus 2002 or newer for use with Agent, just enable
the email scanning and make no changes to Agent.

I should note, however, that this isn't strictly needed with Agent, since
Agent is not an "active" application the same way that Outlook,
Netscape and Eudora are.  Agent does not make use of Java, HTML nor
ActiveX, which makes it impossible for virii or other malicious items to be
activated just by viewing them.   You would have to specifically
launch them, and then you'd have two layers of protection going for you: 
First is Agent's confirmation to launch an executable file, and second
Norton Antivirus' Autoprotect feature.

By the same reasoning, it is safe to set it to exclude your Agent database
from being scanned.  And as you have recently found out, recomended that
you do so.

> My Forte Agent 2.0 Inbox database has become corrupted.  I have a
> month-old  copy of my Agent\Data folder on CD-R, including all the .dat and
.idx
> files.
> How can I figure out which one of them is the Inbox, so that I can
> replace my corrupted database with the known good one?

Close Agent and edit your agent.ini file.  Look for the debugging section,
and change the following line to:

ShowUID=1

(it is a zero now).

When you get back into Agent, look at your groups and they will have a
number associated with it.  For example:

alt.usenet.offline-reader.forte-agent 0000478D.

This number is the name of the .idx and .dat files that are associated with
your groups.

Using the above example, the files could be found in your working directory
and would be called 0000478D.dat and 0000478D.idx.

When you copy the files off the CD, make sure to remove the Read Only flag.
 You need to treat the dat and idx files as a unit, or your database will
still appear to be corrupted.

--
Jeffrey Kaplan             Agent Support Team
www.forteinc.com

--- BBBS/NT v4.01 Flag-5
* Origin: Barktopia BBS Site http://HarborWebs.com:8081 (1:379/45)
SEEN-BY: 633/267 270
@PATH: 379/45 1 633/267

SOURCE: echomail via fidonet.ozzmosis.com

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.