Re: Re[2]: [Declude.JunkMail] Imail 8.2 / smartermail

[David Franco-Rocha [ Declude ]]

There is a very specific reason for this process. Unlike IMail, which 
provides for a daisy-chain mechanism whereby Declude gets the msg for 
processing and hands it back to smtp32 for delivery, SmarterMail passes the 
msg to Declude and, after a set period of time, tries to deliver it. Taking 
it out of the spool prevents SmarterMail from grabbing the file until 
Declude has finished with it.

David Franco-Rocha
----- Original Message ----- 
From: "David Sullivan" <[EMAIL PROTECTED]>
To: <Declude.JunkMail@declude.com>
Sent: Friday, April 29, 2005 3:42 PM
Subject: Re[2]: [Declude.JunkMail] Imail 8.2 / smartermail


I downloaded the SM/Declude demo, thinking of moving from Imail. One
thing I noticed is that for each message, SM appeared to move it's
version of the D/Q files from spool, to a processing folder and then
process it. This seems like twice the necessary disk activity over
just processing it from the /spool folder.
Has anybody seen any SM performance hits vs. Declude because of this
on a system handling 30k msgs/hr? (Assuming use of standard Imail best
practices for disk utilization)
--
Best regards,
David                            mailto:[EMAIL PROTECTED]
---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list.  To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail".  The archives can be found
at http://www.mail-archive.com.