Scott has mentioned on this list many times in the past the process order
between IMail and Declude:

Here is the order (from Scott):

[1] IMail's Control Access file
[2] IMail's Kill List
[3] Declude Virus
[4] Declude Junkmail
[5] IMail rules

Looks like all "global" filter processing by IMail has historically been
done before messages were passed to Declude.  Only individual IMail rules
were processed after Declude passed the messages back to IMail for delivery
(which certainly makes sense to me).  So, since statistical content
filtering is completely new in IMail v.8, how do you possibly come up with
the conclusion that this type of filtering has always been done as part of
queue management (which, by the way, is also new in IMail v.8, and even runs
as a separate service, in case you hadn't noticed).

So once again, I just feel that IPSwitch should have been consistent in
their "global" spam processing and done it all before passing onto
third-party plug-ins.  Why hold out on just one of these "global" spam
processing filters and none of the others--how much sense does that make?
Wouldn't it make much more sense that if you were going to delete messages
that fail statistical content filtering, that you would do that instead of
passing the messages onto third-party plug-ins?  Why unnecessarily waste the
added resources of passing these messages onto third-party apps for
additional processing when they are going to get deleted anyway after being
sent back to IMail and failing the statistical content filtering--again, how
much sense does that make?

I know we are getting way OT here, but I just don't see the logic or
rationale for your claims.

Bill

----- Original Message ----- 
From: "Sanford Whiteman" <[EMAIL PROTECTED]>
To: "Bill Landry" <[EMAIL PROTECTED]>
Sent: Friday, June 27, 2003 10:22 AM
Subject: Re[6]: [Declude.JunkMail] Test on Imail X-header


> > How  are  queue  management  and  statistical content filtering even
> > remotely related to each other?
>
> Message  filtering  and  delivery  have  ALWAYS been paired within the
> IMail process flow. I don't think you've been polite enough to deserve
> an  explanation of the similarities in implementation across versions,
> but  if  you  do  your  due  diligence  in  this  area  perhaps you'll
> understand it better.
>
> > Name some other mail servers that you know combine these processes.
>
> This  isn't  about  other  mail servers. It's about the evolution of a
> product  from version to version while preserving central paradigms in
> order  to  avoid  needless  ground-up rewrites. In terms of other mail
> servers,  unless  you're  doing streaming content filtering during the
> SMTP  conversation (which would be resource suicide), you've signed on
> to  doing  post-submission  filtering,  then  delivery. Whether or not
> other  mail servers have separate filtering and delivery stages, IMail
> has   historically   only   had   the   submission   stage   and   the
> filtering/delivery stage, and that it is why it comes as absolutely no
> surprise  that  QM  is  an high-performance implementation of the same
> paired functions.
>
> > How is it that you can speak so authoritatively about this subject?
>
> It  is  so  because  I know how IMail's process flow has worked in the
> past  and  how  it  has evolved. I have no professional alignment with
> Ipswitch,  although  I  have  been  part of the requirements gathering
> process as a beta tester for several versions.
>
> -Sandy
>
>
> ------------------------------------
> Sanford Whiteman, Chief Technologist
> Broadleaf Systems, a division of
> Cypress Integrated Systems, Inc.
> e-mail: [EMAIL PROTECTED]
> ------------------------------------
>
> ---
> [This E-mail was scanned for viruses by Declude Virus
(http://www.declude.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.
>

---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.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.

Reply via email to