If the goal is to reject invalid recipients, I'm not sure I can think of a better way at this point. I'm planning to add recipient validation in version 4.1, so you should get this feature for free... someday.
The only concern with this configuration is keeping the list of valid users up-to-date. If a new account is created, especially by a domain administrator (i.e. not you), they're going to expect it to be able to receive email immediately. You'll need to explain that there will be a delay before the file is recreated. -- Sam Clippinger Venks Izod wrote: > The white-list and black-list are sledgehammers - they overrule all filters. > So I want a "partial" sledgehammer. First get the low-lying fruit with > RBL and RDNS etc, then use the sledgehammer to only accept mail to > valid users. > > The way I run the second spamdyke is with a recipient-whitelist (containing > all addresses that I want to receive email on) and a recipient-blacklist > (which > is wildcard everything else). > > As of 3.1.8 I don't think this is possible in one invocation. So I have to > daisy-chain two invocations. The question was "What is a good way > to do this?". Hope this explanation helps. > > - V > > On Tue, May 27, 2008 at 1:14 PM, nightduke <[EMAIL PROTECTED]> wrote: > >> Why you have two lines with spamdyke? >> >> It's necesary only one line spamdyke -f /etc/spamdyke/spamdyke.conf... >> >> Nightduke >> >> >> 2008/5/27, Venks Izod <[EMAIL PROTECTED]>: >> >>> I had originally added a whitelist-recipient-file and a >>> blacklist-recipient-file. The whitelist had the explicit names of >>> everyone (and aliases in the company). The blacklist was just >>> @xxxyy.com. But since whitelists are all-overpowering, the valid >>> users still got a bunch of spam through. >>> >>> I now use RBLs and RDNS and all the bells and whistles on one >>> spamdyke. But I see that I still let some spam through to weird >>> addresses. >>> >>> I thought that one way of doing this (without changing spamdyke code), >>> would be to run one spamdyke inside another. The first one uses >>> RBLs and no-RDNS and all the fancy stuff. >>> >>> The second one just uses recipient whitelist to accept emails and >>> recipient blacklist to reject them. >>> >>> I think it would require some magic more than just a changed >>> smtpd.conf for xinetd. For example: >>> >>> server_args = /usr/local/bin/spamdyke -f /etc/spamdyke-outer.conf \ >>> /usr/local/bin/spamdyke -f /etc/spamdyke-inner.conf \ >>> /var/qmail/bin/qmail-smtpd >>> >>> >>> Any ideas/experience/comments? >>> >>> - Venkat >>> _______________________________________________ >>> 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 >> >> >> >> >> > _______________________________________________ > 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
