Milter-greylist

If you're using milter-greylist, 'delayed for' will show all the  
tuples that didn't match extant autowhitelist entries or manual  
whitelist entries. Thus, the number of incoming messages that were  
greylisted. Subsequently looking for 'autowhitelisted' shows the  
number that then were retried and were automatically whitelisted.

Thus, in my example, 658 out of 23231 were passed through (nearly all  
were non-spam) and the remainder were never retried. From these  
numbers, greylisting is working fantastically.

Keep in mind that these numbers were the first 9h of today on this  
particular relay. Some days the number of non-retried email tops  
300,000.

-Paul


On Oct 7, 2009, at 10:28 AM, Jason Bertoch wrote:

> > -----Original Message-----
> > From: milter-greylist@yahoogroups.com [mailto:milter-
> > greylist@yahoogroups.com] On Behalf Of Paul Venezia
> > Sent: Wednesday, October 07, 2009 10:19 AM
> > To: milter-greylist@yahoogroups.com
> > Subject: Re: [milter-greylist] Is greylisting still a valid  
> technique?
> >
> >
> >
> > Since my previous message to the list this morning has apparently  
> been
> > lost somewhere, yes:
> >
> > root@mx ~]# grep -c "delayed for" /var/log/maillog
> > 23231
> > [root@mx ~]# grep -c "autowhitelisted" /var/log/maillog
> > 658
> >
> > Make sure you're looking for the right data.
> >
>
> How is "delayed for" greater than "autowhitelisted"? "delayed for"
> indicates a previously unseen host that was delayed but then retried.
> "autowhitelisted" should match on all hosts that have been seen  
> before. I
> wonder if this is related to the greylist delay, in my case 7m. I can
> imagine a relatively high delay setting might cause more hits on a  
> "delayed
> for" count where servers often retry before the countdown has expired.
>
> Jason A. Bertoch
> Network Administrator
> jason@...
> Electronet Broadband Communications
> 3411 Capital Medical Blvd.
> Tallahassee, FL 32308
> (V) 850.222.0229 (F) 850.222.8771
>
>
>