I was just about to write and say that spamdyke can't do that, but apparently it can. Using just "@pw" in your blacklist file should work. It will block any sender with an address that end in either "@pw" or ".pw". So, for example, it would block "spammer@pw", "[email protected]" and "[email protected]", but it won't block "[email protected]".
Sometimes I amaze even myself. :) -- Sam Clippinger On May 31, 2013, at 11:07 AM, Faris Raouf wrote: > Can someone point me in the right direction please? > > I want to block all email with a FROM: sender address ending in a particular > TLD (.pw) > Unfortunately I’m not sure exactly what the correct syntax is. > > In the docs, it says: > One form of wildcard address is supported. All usernames within a domain (and > its subdomains) may be blocked by a line starting with @. For example, if the > file contained the following entry: @example.com spamdyke will block mail to > [email protected], [email protected], [email protected], > etc. > > This sort of implies that using @ is the only way to wildcard a sender > address, and that possibly @pw might do the trick in in my sender_blacklist > file. > > But something tells me that I should use .pw rather than @pw given that > “.”-style wildcards are supported in other blacklist files and @pw somehow > feels wrong. > Or am I totally off-track? > > Thanks, > > Faris. > > _______________________________________________ > 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
