This is exactly the kind of thing configuration directories are designed to do.
If I'm reading your email correctly, you should first enable graylisting globally in the main configuration file. Then you should create a configuration directory. First, create a path for the most specific case -- a single user ([email protected]) wants to disable graylisting for a single remote host (11.22.33.44). In that case, the path would look like this: <path>/_recipient_/com/domain/_at_/joe/_ip_/11/22/33/44 The last element of that path (44) should be a text file that contains spamdyke configuration commands. In this case, it should contain "graylist-level=none". Other options are possible too -- users can define their own white/blacklists, for example. And of course you can create lots of other paths/files in that same configuration directory for other domains, users and IP addresses. Allowing the user to turn off graylisting by rDNS name (mail.reverse.com) is also possible: <path>/_recipient_/com/domain/_at_/joe/_rdns_/com/reverse/mail Again, the last element (mail) should be a file, not a folder. To disable graylisting for a whole domain (domain.com) instead of a specific user, create a path that doesn't include the username: <path>/_recipient_/com/domain/_ip_/11/22/33/44 To turn off graylisting for the entire domain for all IP addresses, you should create a path like this one: <path>/_recipient_/com/domain HOWEVER, because the last element (domain) should always be a file, you can't put this path in the same structure as the ones above -- it's not possible for a file named "domain" and a folder named "domain" to coexist in the same folder. So you'll have to create a second configuration directory: <path2>/_recipient_/com/domain Then in the main spamdyke configuration file, use the "configuration-dir" option twice: configuration-dir=<path> configuration-dir=<path2> spamdyke will search the directories in the order they are given and find the best match it can. -- Sam Clippinger On Dec 19, 2011, at 7:33 AM, Marcin Orlowski wrote: > Hi, > > I think I'd like to have option to let my users disable > graylisting. But since I'd like it to be per user > therefore I'd like to be able to define > graylist-exception-ip-file and graylist-exception-rdns-file > (or -dir as that would be faster) per *receipient's email or domain*. > Here's how I'd think it might be implemented. Say I host [email protected]. > I'd like to be able to define that if mail comes from remote server > (with IP A.B.C.D and rdns mail.reverse.com) and receipient is > [email protected], spamdyke would check if there's > <path>/domain.com/[email protected]/graylist-exception-ip-dir/A.B.C.D > and if so, skip graylisting. If not such file it'd check > <path>/domain.com/[email protected]/graylist-exception-rdns-dir/ > mail.reverse.com if exists - graylist is skipped. if not > it now (depending on the settings as I believe some may not > want such detailed configurability) would check > <path>/domain.com/graylist-exception-ip-dir/A.B.C.D and > <path>/domain.com/graylist-exception-rdns-dir/ > if no match, global settings apply. It needs some thoughts on > how fallback (email->account@domain->domain) should work > assuming both white and black lists are used but that's > quite obvious. Any thoughts? > > Regards, > -- > "Daddy, what "Formatting drive C:" means?"... > > Marcin http://wfmh.org.pl/carlos/ > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
