Jakob Hirsch
Tue, 09 Mar 2010 02:04:35 -0800
l...@lena.kiev.ua, 2010-03-08 16:58:
>> I'd suggest to use ${mask:<IP address>/<bit count>} instead. regex is
>> not always the best solution.
> In this case regex gives 5 bytes shorter result (without .0/24 at the end).
True, but that's only relevant if you are really short on storage. >> This also works with IPv6 (one should use >> a different bit count for that, though). > Did someone receive a spam via IPv6 not from a real MTA? I heard of one case recently. With the rise of ipv6 we'll probably see more, but it's not a problem right. >> Or, don't greylist the whole world by default > The original poster wrote "selective" in Subject. Yes, in parenthesis. Greylisting gmail does not sound very selective to me, but depends on one's selection criteria, of course. >>> I attached excerpts from my config (including the whitelist) to >>> http://wiki.exim.org/DbLessGreyListingC >> What's the big advantage over using the builtin sqlite support for >> greylisting? > When I wrote that, I didn't know that sqlite is demonless. I run Exim Too bad. One should check the available options before reinventing the wheel :) > Please give a link to a sqlite greylisting implementation. http://plonk.de/sw/exim/greylist.txt has been out for quite a while. There's also one in the wiki: http://wiki.exim.org/SimpleGreylisting -- ## List details at http://lists.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/