Hello David, Tuesday, March 9, 2004, 1:06:42 PM, you wrote:
KD> a. Using %ALLRECIPS% can cause problems when there is a larger KD> number of recipients. Some of the parameters may not be passed KD> or may be are stripped off due to limitations of the length of a KD> command line. (Not sure of the exact length) Oooh, yea. Didn't consider that. KD> b. A better solutions is to open and process the Imail envelope KD> header. The file is in the same location as the Email and the KD> first character of the file is changed to a "Q". For example, Duh. I guess I can get all the envelope info out of the Q file. Wonder what Imail does though if it's a Store and Forward? KD> 2. You also have to consider what happens when there is a conflict. KD> You can be receiving a message for multiple domains (or even KD> users within the same domain) and one user could whitelist the KD> entry and another could blacklist it or have no preference. That's the hardest issue. Right now we've just decided to use the most lenient setting. If any "to" wants it, they all get it. KD> I have written an external test that at the domain level allows KD> the administrator decide whether the "domain" or "user" level KD> has priority when whitelisting or blacklisting. What's your logic in that? KD> I still have the issue when multiple domains are being processed KD> in the same message. I have checked and some of the larger KD> companies that process for spam and viruses and each of them KD> has a method for processing the message for individual recipients KD> something that Declude is missing. Yep. KD> 3. You also want to look at how matches are being processed. (i.e. KD> is it an exact match, partial match, does it start with or end KD> with the string being compared.) We're going to keep it simple at first only allowing: [EMAIL PROTECTED] @example.com KD> 4. The other request that has been made by a number of people is a KD> way to move the messages marked as spam to a specific folder on KD> the server. Scott mentioned that they were looking into this KD> but to the best of my knowledge there is no way to do this at the KD> present time. We wrote C++ that parses every message from /spam and moves it to a use specific folder, then give users access to folder through web GUI and auto-delete after 10 days old. BEWARE...NTFS doesn't like lots of nodes in one root. Right now we have about 3 million files and have broken them down by drive:/Spam/<A-Z>/Domain.ext/<A-Z>/username/Q and D files. Sure there are better ways, but breaking down by A-Z was easiest. Holding spam with a file structure spam/domain/user took WAY too long on disk access. Also, you should format your drive with a smaller cluster size than DEFAULT. Remember 1/2 of all your files on that drive will be less than 1k. And...if you're using RAID controller, disable Read-Ahead caching. --- [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.
