Title: Message
Eric and Greg,
I'm basing the compatibility thing on reports to this list, and those
reports prompted Declude to change it's architecture for processing
messages. Something clearly was happening, but I don't recall ever
hearing exactly what the cause was. I haven't tried 2.0.6.16 with
IMail 8.22 myself yet, but I'm considering falling back.
Matt
Erik wrote:
Thanks Matt.
We are running Imail 8.22 (2005.10.19.3) and
Declude version 2.06.16 on a Windows 2000 Sever version 5.00.2195
Service Pack 4 with will no issues other then the ones I submitted to
Declude for support and what I've mentioned on this list (which they
"declude" will not not provide us support on since we do not run their
"current" version)... but the problem even exists in their "current"
version according to the lists of others postings. So unfortunately,
Declude will not provide us support (even though we are a paid customer
of their product) based on the version we run.
So I'd be interested to know on our your servers
run the latest 3.0X version of Declude.
Thanks!
-Erik
Erik,
Honestly, I was between a rock and a hard place. Declude 2.x doesn't
work with IMail 8.2+, and IMail 8.15- has issues with killer messages
that crash the Queue Manager service (which I found out the hard way,
and 8.21 apparently fixes). For a while the killer messages were
somewhat common, and all it took was one leaking through Declude to
crash the services, and then you had to dig it out of the spool.
So to keep my Queue Manager stable, I had to make the leap.
I'll follow up with some comments about my experience.
Matt
Erik wrote:
LOL, had to laugh at Nick. I'll wait to hear
from Matt after his upgrade before we attempt to do it again. I think
Matt's and our servers handle about the same email volume.
-Erik
Hi Matt,
Matt wrote:
I'm
trying an upgrade from the 2.x release for the first time,
Why on earth would you want to do that? Was 2x too bug free and you
need some excitement?
-Nick
|
- Re: [Declude.JunkMail] What happened to the logging since ... Matt
-
