From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] Ratify questions
Date: Mon, 11 Apr 2022 20:54:44 +0000 (UTC) [thread overview]
Message-ID: <1225a12a-1f7d-409a-8a87-7b604c47c6c9@sirjofri.de> (raw)
In-Reply-To: <D246755A-CFB2-4BDC-9BDA-F425F6A0D319@stanleylieber.com>
Hello Stanley,
11.04.2022 19:25:10 Stanley Lieber <sl@stanleylieber.com>:
> validatesender checks /mail/lib/spamhaus, i update it via cron.
My mail server setup is quite old (or a little corrupt), I don't have a
validatesender in my /mail/lib at all. I'll have to look where I can get
that.
> i still receive tons of spam.
That's unfortunate. I hoped this would be better. On the other hand, I
assume your mail address is published more often than mine?
sirjofri
next prev parent reply other threads:[~2022-04-11 20:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 16:32 sirjofri
2022-04-11 17:25 ` Stanley Lieber
2022-04-11 20:54 ` sirjofri [this message]
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=1225a12a-1f7d-409a-8a87-7b604c47c6c9@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).