Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] Variable delays

2006-08-28 by Robert Stampfli

On Sun, Aug 27, 2006 at 08:11:39AM +0200, manu@... wrote:
> Rob Stampfli <res@...> wrote:
> 
> > Aside from the dnsbl checks, is there a way to impose a specific
> > delay when specifying a greylisting rule?  I have an email account
> > where I only expect to get legitimate mail from a select set of
> > specific addresses, but it is being broadly spammed and the spamming
> > engines are sophisticated enough to get past the greylisting.
> > 
> > What I'd like to do is to first whitelist the legitimate From:
> > addresses in the config file and then set a very long greylist
> > interval on mail to that address which would apply for everyone
> > else.  Can such a thing be done?
> 
> With milter-greylist 3.0 alpha2:
> 
> list "friends" from {   \
>         friend1@... \
>         friend2@... \
>         friend3@... \       
> }
> 
> acl whitelist list "friends" rcpt user@...
> acl greylist rcpt user@... delay 24h
> acl greylist default delay 15m
...
> > Super.  Just what I was looking for.  Thanks for this info.
> > I presume 3.0 alpha2 is solid enough for everyday use?  I'm
> > using 2.1.3 now.
> 
> If I had known, I would have named it 3.0 (not alpha 2). Give it a try,
> and don't forget to tell me if it works :-)


It's installed on one of my backup mail servers where a lot of
the spam seems to come in on, so I'll know in a day or so if it
is working.  I did make one change:  For the
	list "friends" from ...
specification, I used some regular expressions to specify the
list members.  e.g.:
	/.*@foo\.com/
intending to allow mail from anyone in the foo.com domain.  It
did not complain on startup, so I presume it knows how to deal
with these constructs correctly within a list.

I'll report back in a day or two with the results.

Thanks again,
Rob

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.