Robert,

With IMail 8.15 HF2, there are no Declude stability issues on my system and I am processing about 150,000/day with Declude, two virus scanners, Sniffer and other external apps.  McAfee does unfortunately have a habit of throwing errors in dialog boxes almost daily, but it hasn't caused a crash (this gets dangerous when you get 40+ dialog boxes open at one time however because of Windows heap issues).

My recommendation would be to drop back to IMail 8.15 or wait patiently for Declude to figure it out and release a patch.  IMail 8.20 introduced an entirely new multi-threaded SMTP engine, and I believe it is wise to wait at least a month following any major IMail release in order to monitor for compatibility issues.  There are often at least smaller issues created by IMail upgrades, and Declude must be reactive to such changes since they are a completely separate company.

Matt



Robert Shubert wrote:

I too have a serious issue with Declude remaining stable on my system. I’ve tried each of the 2.0.6.x betas as they came out, but the problem hasn’t gone away. I did have the mentioned SMTPd memory/crash issue when I originally went to 8.2, but with HF2 installed, that as gone away. My server runs an average of 70 mail/min with a peak of about 200.

 

My question is: what version of declude should I rollback to? I’ll gladly give up features as long as I have the stability, when declude crashes (and puts up a dialog, which I have to clear) no mail is delivered.

 

Thanks for any help,

 

Robert

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mailing Lists
Sent: Friday, July 15, 2005 11:30 AM
To: [email protected]
Subject: Re: [Declude.JunkMail] [Declude.Virus] Brief Update

 

Bill,

 

does that mean days, weeks, months?

 

I dont know if you are aware but we reported this many many months ago, before 2.0.6 was released.

 

We have a real problem with customers trying to explain that we cannot guarantee mail delivery because of Declude. So customers will rightfully ask for a timeframe and we wont install new installs until we know this is fixed. But a timeframe is required since it has taken so long to acknowledge and address.


Sal

----- Original Message -----

From: Bill Billman

Sent: Friday, July 15, 2005 9:29 AM

Subject: RE: [Declude.JunkMail] [Declude.Virus] Brief Update

 

Hi Darin,

 

We expect to be testing in a few high volume production environments in the very near future.  If all goes well we will offer a general beta shortly after that.  We intend to perform a thorough QA cycle and will not release until we are satisfied this version meets or exceeds expectations.

 

Thanks,

 

Bill Billman

Declude

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Darin Cox
Sent: Thursday, July 14, 2005 6:52 AM
To: [email protected]
Subject: Re: [Declude.JunkMail] [Declude.Virus] Brief Update

 

Hi Bill,

 

Do you have a target release date?

 

Thanks,


Darin.

 

 

----- Original Message -----

From: Bill Billman

Sent: Thursday, July 14, 2005 6:31 AM

Subject: RE: [Declude.JunkMail] [Declude.Virus] Brief Update

 

Thanks Sal.

I agree.  Orphaned emails are unacceptable and the issue is indeed being addressed.

 

Quality, stability, and performance are the goals for this release and that is what we will deliver.  We spent a fair amount of time analyzing the issues and designing our solutions.  I believe it was time well spent and I thank all our customers for their patients.  So far we are very pleased with the results from our tests.

 

Bill Billman

Declude

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mailing Lists
Sent: Wednesday, July 13, 2005 9:23 PM
To: [email protected]
Subject: Re: [Declude.JunkMail] [Declude.Virus] Brief Update

 

Also I hope the issue of orphaned emails is being addressed with Declude and SM.

 

This is a real pain, we had to go to back to Declude 2.0.5.76 because 2.0.6 release would break up the hdr and eml files (so you would get orphaned hdr in the /proc and .eml in the spool). 2.0.5.76 doesnt check for emails forgotten by declude so we check the /proc directory with a script. Obviosuly this is not the best way to run a mail server.

 

I believe we worked with Ralph on this issue for several months, but no solution yet.

 

Sal

----- Original Message -----

From: Bill Billman

Sent: Wednesday, July 13, 2005 8:52 AM

Subject: RE: [Declude.JunkMail] [Declude.Virus] Brief Update

 

Thanks Mike.

We are making great progress.  We’ve managed to address the issues and make Declude far more efficient.  Internal testing is beginning.  I believe that you will be pleased with the performance and resource utilization of this version.  Too early for me to make specific claims but I’m very optimistic from a stability and performance perspective.

 

Bill Billman

Declude

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Michael Hardrick
Sent: Tuesday, July 12, 2005 2:47 PM
To: [email protected]
Subject: RE: [Declude.JunkMail] [Declude.Virus] Brief Update

 

Any new news on this issue?

Basically, version 2.X is useless to me.

If there is any way I can assist by sending debug info, lmk.

--Mike

TNWEB

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Bill Billman
Sent: Wednesday, June 29, 2005 15:24
To: [email protected]; [email protected]
Subject: RE: [Declude.JunkMail] [Declude.Virus] Brief Update

You’re spot on Mike.  In cases like this it comes down to finding the circumstances that trigger the problem and then simulating those conditions.  It is difficult but at the very least a potential problem is identified and removed.  If all goes well analysis of the fix and conditions will give a high degree of confidence that the target problem is the one that has been fixed.  That confidence will grow as testing without failure continues through beta.

 

Bill

 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Mike Nice
Sent: Wednesday, June 29, 2005 3:51 PM
To: [email protected]
Subject: Re: [Declude.Virus] Brief Update

 

 

   This one must be a bugger - we changed nothing in our configuration and the SMTPd memory problem has not reoccurred since May 29.  So how is it possible to test unless it can be reproduced?

 

   

----- Original Message -----

From: Bill Billman

Sent: Wednesday, June 29, 2005 3:13 PM

Subject: [Declude.Virus] Brief Update

 

Hi Folks,

 

Declude development is still in the process of investigating issues surrounding resource utilization and we will report back in two weeks or sooner if possible.

 

 

--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.6/33 - Release Date: 6/28/2005

 

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.6/33 - Release Date: 6/28/2005

 

--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.13/47 - Release Date: 7/12/2005

 

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.13/47 - Release Date: 7/12/2005

 

--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.13/47 - Release Date: 7/12/2005

 

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.13/47 - Release Date: 7/12/2005

 

--
No virus found in this incoming message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.15/49 - Release Date: 7/14/2005

 

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.15/49 - Release Date: 7/14/2005


-- 
=====================================================
MailPure custom filters for Declude JunkMail Pro.
http://www.mailpure.com/software/
=====================================================


Reply via email to