It's very difficult to say without more information. If you're trying to block whole TLDs, for example *.review, an entry like this in your sender-blacklist-file should do the trick: @review In that file, starting a line with a dot is not a wildcard, so a line that only contains ".review" won't block a domain at all -- it'll try to block a sender address that exactly matches ".review", which wouldn't be allowed anyway because it doesn't have a domain name (no "@" symbol).
If your sender blacklist file seems to be correct, could you provide some examples of what isn't getting blocked? Log messages from spamdyke and message headers would be especially helpful, as would your spamdyke config file. -- Sam Clippinger On Jul 31, 2015, at 9:58 AM, Ronnie Tartar via spamdyke-users <email@example.com> wrote: > I cannot seem to block .review .date .xxxx .xxxx TLD's. > > here is my blacklist_senders file. > > Any help? Thanks in advance > > @email.bwz.net > @pataripus.in > @space > .space > @top > .top > .us > @us > .science > @science > .cricket > @cricket > .ninja > @ninja > .work > @work > .link > @link > @review > .review > .uno > @uno > .party > @.party > .co > @co > .date > @date > .click > @click > > _______________________________________________ > spamdyke-users mailing list > firstname.lastname@example.org > http://www.spamdyke.org/mailman/listinfo/spamdyke-users
_______________________________________________ spamdyke-users mailing list email@example.com http://www.spamdyke.org/mailman/listinfo/spamdyke-users