Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-13 23:57 UTC

Thread

from+to exclusions?

from+to exclusions?

2004-05-28 by Dan Hollis

We plan to deploy milter-greylist for our ISP customers.

Right now we have web interface which lets individual users enable/disable 
greylisting for their account. We use milter-greylist with -T and specify 
individual users in greylist.conf who want greylisting.

Individual users will want to whitelist individual senders from 
greylisting. Their individual whitelist selections _must not_ affect other 
users. E.g. a whitelist must be specific to that user. A user's whitelist 
for *@*.uu.net _must not_ affect any other users.

I can't see any way to do this with existing milter-greylist. Am I wrong?

-Dan

Re: [milter-greylist] from+to exclusions?

2004-05-28 by manu@netbsd.org

Dan Hollis <goemon@...> wrote:

> Individual users will want to whitelist individual senders from 
> greylisting. Their individual whitelist selections _must not_ affect other
> users. E.g. a whitelist must be specific to that user. A user's whitelist
> for *@*.uu.net _must not_ affect any other users.
> 
> I can't see any way to do this with existing milter-greylist. Am I wrong?

You are not wrong (i.e. you are right), there is no way of doing that
yet. per-recipient configuration is a good idea, but it's clearly a post
1.4 project.

I think we could have rcpt subsections:

rcpt toto@... {
        addr 192.0.2.0/24
        domain example.com
}

Of course that would only work in testmode. Probably testmode is a bad
name, because when I look at this I think it should be the default. More
problems to think at... 

To sum up, it's not possible yet, it will be possible some day, and if
you are impatient to have it, nothing prevent you from writing the code
:)

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

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.