-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of John Tolmachoff
(Lists)
Sent: Monday, September 26,
2005 12:44 PM
To:
[email protected]
Subject: RE:
[Declude.JunkMail]
Anyone have any outstanding issues with the 3.0.5 release?
Current
release is 3.0.5.3
Reactions/observations
so far:
1.
Dropping known bad d and q files,
decludeproc moves them to a new folder \proc\review. The Decludeproc
did crash
and stop, but it was restarted. I am not sure if the files were moved
upon
restart or at the time of the crash. I am suspecting that what happens
is when
decludeproc is started, any files in the proc\work folder are moved to
the
proc\review folder. I can live with this unless of course the messages
that are
causing this become more prevalent. Declude is still searching for the
cause
and remedy for the crash, and I have just sent a bunch more information
to them
regarding this issue. Note that any files in the work folder are moved,
so you
should activily monitor that folder. I am doing so by copying and
modifying the
script Bill has for monitoring HOLD1 and HOLD2. If some one has a
better idea,
please let me know.
2. Hijack
and Confirm appear to be
working correctly now, waiting for a test.
3. During
the install, the default
location is not correct at all. You must change the install location to
the
Imail directory. I have responded to Declude about this recommending
that the
default location be taken from the Imail install registry key.
4. If you
make a mistake during the
install like I did, (accepting the default location,) and have to
uninstall,
you have to do a restart to clear the decludeproc from the services
list to
complete the service deletion. (This happened to me anyways, your
mileage may
vary.)
-----Original
Message-----
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Darin Cox
Sent: Monday, September 26,
2005 11:29 AM
To:
[email protected];
[email protected]
Subject:
[Declude.JunkMail] Anyone
have any outstanding issues with the 3.0.5 release?
I see 3.0.5 was released
today. Anyone know if this
fixes the reported performance and stability issues reported here with
the
3.0.x betas?