Just to verify, I also read somewhere in the wiki where you can add your
own domain to the blacklist_senders file to prevent spoofed email from
your own domain.
But I believe you also have to have your web service set up to
authenticate when sending email. I use roundcube and discovered that in
my haste to install that some time ago, I did not set that up. I believe
the way to set that up is to configure these in the
/etc/roundcube/config.inc.php file.
$config['smtp_server'] = 'tls://<YOURDOMAIN>';
$config['smtp_user'] = '%u';
$config['smtp_pass'] = '%p';
$config['smtp_port'] = 587;
After you do that, it is also my understanding that you can remove the
localhost line from your tcp.smtp file, so remove this line
127.:allow,RELAYCLIENT="",QMAILQUEUE="/var/qmail/bin/simscan",,NOP0FCHECK="1"
Let me know if that is correct, as I'm a bit nervous about doing this
one. I'll have to find a slow time I can quickly do it, test it all out,
and be prepared to move it back if I have problems. I have quite a few
users who exclusively use the web interface.
Thanks, g
On 6/15/2026 8:33 AM, Gary Bowling wrote:
Thanks Jaime, be sure to put it in as @ru and not @.ru! One TLD per
line like this.
@ru
@cn
At least it works for me and that's also what the spamdyke
documentation says.
Gary
On 6/15/2026 7:54 AM, Jaime Lerner wrote:
Hey Gary,
Thank you so much for the extra info! I swear I tried blocking
something like .ru in the past, and it didn’t work to just put @ru in
the senders blacklist. I’ll try again!
I use Fail2ban and it blocks a lot of things also for sure. I have a
ton of jail configs.
Blocking spam definitely takes a village! :)
Jaime
*From: *Gary Bowling <[email protected]>
*Organization: *GBCO
*Reply-To: *<[email protected]>
*Date: *Friday, June 12, 2026 at 7:38 PM
*To: *Qmail <[email protected]>, <[email protected]>
*Subject: *Re: [qmailtoaster] Blocking TLDs
Thanks for all the replies.
Finn, I do use Fail2ban, so that's another option of ways to deal with
these things. I'll read up on how to do that. I have a system using
fail2ban that I put in a long time ago. It was a recipe for how to block
attacks where if someone tries an attack it first blocks them for a
week, if it persists it adds them to a month, if it still persists it
adds them for a year, and if it still persists is blocks them
permanently. That works great, so something that looks at spam might be
worthwhile as well. I have had limited success blocking full TLDs with
spamassassin, at least the way I have it set up.
Jaime, I have now tested using @ru for a few days and it does indeed
work. You do not need to put in the full domain like @spammer.ru, it
will work on everything if you just put in @ru
Here's an example of that from my logs. In my blacklist_senders, I have
a line like this @living and that's the only reference in any of my
config files to the word "living" and here's a line from my maillog
Jun 12 18:13:18 mail spamdyke[162474]: DENIED_SENDER_BLACKLISTED from:
[email protected] to: .....
So far, putting things in the blacklist_senders seems to be working
fairly well. Now my only concern is how it reacts to having many entries
as I've already got 82 lines in my blacklist_senders file and that's
likely to grow a lot as I add more entries.
I do also want to check into Finn's suggestion of fail2ban to block
country codes.
Thanks as the war on spam continues!
On 6/12/2026 10:38 AM, Qmail wrote:
Hi again,
I remember there was some kind of plugin to Spamassassin to check
location - how it works I don't know or if it exists anymore...
/Finn
Den 10.06.2026 kl. 14.10 skrev Gary Bowling:
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,
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
