9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Steve Simon <steve@quintile.net>
To: 9front@9front.org
Subject: Re: [9front] nupas spf checker: outdated ip bans
Date: Sat, 11 Feb 2017 22:34:16 +0000	[thread overview]
Message-ID: <1EF86914-E2E8-4603-814E-DF6BC30B429A@quintile.net> (raw)
In-Reply-To: <20170211212334.GF18221@wopr>

hi,

i agree SPF is (sadly) no longer much use.

i still run a plan 9 mail server. my main source of spam is French virtual hosts which appear in distinct up blocks. i use ratfs(1) to block cidr ranges to keep them at bay.

i also added code to ratfs to add a reverse ip address database. this supports regex so i can easily block reverse address ranges - i use tho block mail from dialup and adsl addresses.

code available to the interested.

-Steve


> On 11 Feb 2017, at 21:23, Kurt H Maier <khm@sciops.net> wrote:
> 
>> On Sat, Feb 11, 2017 at 08:42:34PM +0100, Julius Schmidt wrote:
>> on second thought, the whole cidrokay() check should go away, i.e. i 
>> propose we replace cidrokay() with "return 1;"
> 
> I support this.
> 
>> - disallow any email from the ranges
> 
> Among other things, why is the SPF checker screwing around with IP
> ranges to start with?   I am assuming it was just a convenient place to
> put these tests, but regardless, the tests are dated and arguably
> useless anyway.
> 
> khm



  reply	other threads:[~2017-02-11 22:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-11 19:21 Julius Schmidt
2017-02-11 19:42 ` [9front] " Julius Schmidt
2017-02-11 21:23   ` Kurt H Maier
2017-02-11 22:34     ` Steve Simon [this message]
2017-02-12 19:44   ` sl
2017-02-12 20:27     ` Kurt H Maier

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=1EF86914-E2E8-4603-814E-DF6BC30B429A@quintile.net \
    --to=steve@quintile.net \
    --cc=9front@9front.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).