Apologies if this has already been mentioned, but this may be a quick easy way to find 
out exactly what messages(and quantity of messages) never got scanned by Declude on a 
per server basis:  If you have Declude configured to add anything consistent to the 
headers, like an x-note: or whatever else, you can use the 'copy all mail to a box' 
feature of Imail, then write a processing rule on the copy box to delete all mail in 
the copy box that has the x-note: data from Declude header.  Then, you can 
periodically check that box to see how many are being missed, because the only mail 
that will end up in that box will be mail that Declude never tried to scan.  There are 
perhaps other ways to use domain proc rules to do this as well but this would be my 
preferred method.    

  

    

-----Original Message-----
From: Kami Razvan [mailto:[EMAIL PROTECTED]
Sent: Sunday, December 07, 2003 1:35 AM
To: [EMAIL PROTECTED]
Subject: RE: [Declude.JunkMail] Declude not taking action


"I figure that each individual E-mail on my system has about a 0.00006%
chance of being stolen and delivered by the queue."

Matt:

I have spent a lot of my years in the field of mathematics.  A study done a
while back and it is related to data-mining stated.. "men buy baby diapers
and orange juice on Tuesdays more than any other day of the week".

While it sounds interesting it is real hard to make any use of it. :)  -- I
am either very lucky or the 0.00006% is only concentrating itself to my
mailbox.

On our very small volume server I got 2 last night and that is only me  -
others are probably getting it and not letting us know.

Attached is an email that IMail added its headers but Declude never saw.

I get about 2-3 daily.

Regards,
Kami
---
[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