Yes, starting a line with "@" is the only available wildcard. I thought about doing more, just like you're asking about, but I got hung up on the complexities.
Email addresses allow so many characters that it's hard to find a good way to indicate a wildcard. I was also afraid that no matter what I tried to implement, it wouldn't work for all situations -- the best solution would be to just use full regular expressions. Then I became concerned that using regular expressions would cause problems if someone just filled the file with email addresses and they wound up being matched as regexps. That's where my thinking ended and I went with the current solution. What do you think? I'm open to suggestions. -- Sam Clippinger Marc Van Houwelingen wrote: > Thanks for adding the "recipient-whitelist-file" feature. I have a quick > question: Is starting a line with "@" the only wildcard ability? > > What I would like to do is have something like this: > > #--recipient-blacklist-file:--- > @mydomain.com > #------------------------------ > > #--recipient-whitelist-file:--- > [EMAIL PROTECTED] > #------------------------------ > > The intention is for spamdyke to block all email coming in for that domain, > except anything matching "[EMAIL PROTECTED]" (eg [EMAIL PROTECTED], > [EMAIL PROTECTED], etc) > > Is this possible now, or perhaps in future versions? > > > _______________________________________________ > spamdyke-users mailing list > spamdyke-users@spamdyke.org > http://www.spamdyke.org/mailman/listinfo/spamdyke-users _______________________________________________ spamdyke-users mailing list spamdyke-users@spamdyke.org http://www.spamdyke.org/mailman/listinfo/spamdyke-users
