From: "Dave Täht" <dave@taht.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] bufferbloat email list server upgrade going slow and badly
Date: Mon, 4 Jan 2016 16:30:10 -0800 [thread overview]
Message-ID: <568B0E92.3060200@taht.net> (raw)
In-Reply-To: <20160104161025.3861dbc5@xeon-e3>
On 1/4/16 4:10 PM, Stephen Hemminger wrote:
> Talk to davem, maybe kernel.org would be safer/better more robust?
Damned if I know - vger is one of my problems that I'd wanted to solve
with this move 1) my old anti-spam setup made him crazy - now fixed -
and 2) vger doesn't use starttls. I'd so hoped that after 10+ years of
availability it was basically on universally, and in the post CISA world
we could put at least this portion of the middle finger up.
for now, for accepting email, (and while I sort out
other stuff) I have postfix being strict about what it accepts, and
liberal about what it sends.
smtp_tls_security_level=may
smtpd_tls_security_level=encrypt
Only 38 out of 532 email addresses on the bloat list are refusing
starttls. The instant anti-spam improvement of making tls mandatory for
email was pretty amazing...
The ongoing mailman subscribe attack looks to have been going on for
months and must be targetted at a metric ton of mailman servers.
It's only hitting three users at google, but
whoever+somerandomnumber is something I need to teach mailman to sort
out. These are the users getting the subscribe spam.
kemo.mart+67292312@gmail.com
kezukaya+93690766@gmail.com
touma3108+42493211@gmail.com
On my more paranoid days I'd think this was an attempt at a known
plaintext attack...
and, alas, poor linode: http://status.linode.com
prev parent reply other threads:[~2016-01-05 0:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-04 23:38 Dave Täht
2016-01-05 0:10 ` Stephen Hemminger
2016-01-05 0:30 ` Dave Täht [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=568B0E92.3060200@taht.net \
--to=dave@taht.net \
--cc=bloat@lists.bufferbloat.net \
--cc=stephen@networkplumber.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