From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: [9front] Ratify questions
Date: Mon, 11 Apr 2022 16:32:33 +0000 (UTC) [thread overview]
Message-ID: <8271b320-83fc-479f-be34-d14aaad73ab6@sirjofri.de> (raw)
Hello all,
After I received lots of spam mails in my standard inbox I tried using
ratfs on my mail server. It seems to work according to the man page.
However, I have some wildcard blocks for certain domains configured and
noticed that mails from these domains still come through. My
configuration lines look like this:
*block example.com!*
*block *.example.com!*
Why? What could possibly go wrong?
The other question is more general. Managing block domains manually is
tedious and doesn't save you from all sources. Integrating spamhaus (for
example) would be a great addition. Has somebody tried that?
sirjofri
next reply other threads:[~2022-04-11 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 16:32 sirjofri [this message]
2022-04-11 17:25 ` Stanley Lieber
2022-04-11 20:54 ` sirjofri
2022-04-11 21:31 ` Stanley Lieber
2022-04-11 17:52 ` Steve Simon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8271b320-83fc-479f-be34-d14aaad73ab6@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--cc=9front@9front.org \
--subject='Re: [9front] Ratify questions' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).