Sam, we seem to like your option better as we would not want to pre-define all the domains that reside onto the server. Also, being we run a cleanup script to remove stale older than graylist-max-secs + 1 hour files and we cleanup empty folders right after it in order to reduce consumption on disk space, we would have to complicate the scripts logic if we were to use the greylist-level=always schema.
Just to clarify that this is clearly understood. If we want to have graylisting to be skipped for an entire domain which is called optedoutfromgraylistdomain.org we'd first instruct the main config file with a directive called config-dir=/etc/spamdyke/spamdyke-conf-dir and than we 1)create a directory called /etc/spamdyke/spamdyke-conf-dir/ 2)and within it, we'd have a file called optedoutfromgraylistdomain which will reside within the /etc/spamdyke/spamdyke-conf-dir/_recipient_/org/ folder which will contain one line of directive namely graylist-level=none Is my understanding correct? Thanks all. ------------------------ Erald Troja Sam Clippinger wrote: > Eric's suggestion will work fine, although you don't need version 4.0 to > use it -- the previous versions could be configured that way as well. > > Another solution is to use spamdyke version 4.0 and create a > configuration directory (using the "config-dir" option) for each of the > recipient domains that want immediate delivery. In your global config > file, enable graylisting as normal. In the configuration directory > files for the specific domains, disable graylisting. The advantage of > this technique is that you can still use > "graylist-level=always-create-dir" in the global config file to > automatically create domain directories as needed. > > Either solution will accomplish the same thing. > > -- Sam Clippinger > > Eric Shubert wrote: >> Erald Troja wrote: >> >>> Folks, >>> >>> is it possible to simply allow immediate delivery >>> to a handful of domains, while graylisting the rest >>> to the standard defined graylisting policy? >>> >>> Seems some folks would rather just get instant >>> gratification and spam, rather than have a minimal delay >>> with the extra protection graylisting offers. >>> >>> I'm not able to pinpoint it in the docs. >>> >>> I noticed graylist-exception-rdns-dir yet this >>> seems to apply to remote servers, and we're interested >>> into the local domains we receive email for. >>> >>> Thanks. >>> >>> >>> >> You need spamdyke >=4.0 for this. If I understand correctly, use the >> greylist-level=always >> in your config, and then be sure that there's no domain directory contained >> in the greylist-dir directory. >> See http://spamdyke.org/documentation/README.html#GRAYLISTS >> >> > _______________________________________________ > 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
