Hi Gary, I think that is the correct way, so for blacklist_senders, use:
@ru not: .ru (which might feel the intuitive right choice first) At least that is how I interpret this Spamdyke documentation: "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." Please note: @ru blocks *MAIL FROM domains ending in .ru*, for example: [email protected] [email protected] It does *not* block by IP geolocation, rDNS country, message body, or visible From: header if the SMTP envelope sender uses some other domain. Best, Peter On Wed, Jun 10, 2026 at 3:10 PM Gary Bowling <[email protected]> wrote: > > I have recently started blocking some top level domains to help control > spam. What I'm doing right now is putting them in the spamdyke > blacklist_senders file, adding a line like this. > > @ru > > Which would block anything coming from and .ru domain or subdomain. > > > Is this the right way to do this? Maybe there is a better or more > appropriate way to block TLDs. > > > Thanks, > > -- > ____________________ > Gary Bowling > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
