From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] Smtpd spam prevention
Date: Fri, 20 Nov 2020 11:41:34 -0500 [thread overview]
Message-ID: <719D2C5E-FE79-48C8-AFC0-5E5D34CA02EF@stanleylieber.com> (raw)
In-Reply-To: <d87d5a63-524a-44ed-b39b-feeeb863351f@sirjofri.de>
On November 20, 2020 10:53:35 AM EST, sirjofri <sirjofri+ml-9front@sirjofri.de> wrote:
>Hello all,
>
>my smtpd server runs fine, but I recently got some spam mails.
>Currently
>my server doesn't filter anything and does nothing to prevent spam.
>
>There are two options to smtpd, according to the man:
>
>> -D sleeps for 15 seconds usually at the start of the SMTP
>> dialogue; this deters some spammers. Connections from
>> Class A networks frequented by spammers will incur a
>> longer delay.
>
>> -g turns on grey/white list processing. All mail is
>> rejected (with a retry code) unless the sender's IP
>> address is on the whitelist, /mail/grey/whitelist, an
>> append only file. Addresses can be added to the whitel-
>> ist by the administrator. However, the usual way for
>> addresses to be added is by smtpd itself. ... (Greylisting)
>
>Both options make sense to me. -g might work out of the box, is there
>anything I need to know before enabling it?
>
>-D is new to me. I never heard about this extra delay when handling
>mail.
>Can I safely enable that?
>
>What configurations do you use?
>
>I don't want to dive into ratfs for now. My mail traffic is low
>anyways.
>
>sirjofri
never used -g or -D.
I ran ratfs for a while. i inadvertently blocked a lot of legit mail as well. I got tired of maintaining it.
I update /mail/lib/spamhaus every night via cron.
I do manually block some repeat offender class c blocks with -k.
sl
next prev parent reply other threads:[~2020-11-20 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 15:53 sirjofri
2020-11-20 16:41 ` Stanley Lieber [this message]
2020-11-20 16:44 ` [9front] " ori
2020-11-20 17:04 ` 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=719D2C5E-FE79-48C8-AFC0-5E5D34CA02EF@stanleylieber.com \
--to=sl@stanleylieber.com \
--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).