> 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.
