From: Michael Richardson <mcr@sandelman.ca>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] ipv6 now disabled for lists.bufferbloat.net
Date: Sun, 10 Nov 2019 10:18:25 +0800 [thread overview]
Message-ID: <dabf0bcc-16a1-f927-c45f-833b862f0486@sandelman.ca> (raw)
In-Reply-To: <CAA93jw67XdcJ0r_kvoH3y4py44FX4PFZAbBoVJ-QqQmywmBUkQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 953 bytes --]
On 2019-11-09 1:56 p.m., Dave Taht wrote:
> For no reason that I've been able to discern, for months and months
> now, nearly any use of ipv6 as an email transport has ended up getting
> the ipv6 address blocked in spamhaus's SBL listing, and thus a lot of
> email has been blocked. IPv4, seems ok, but for all I know
> whatever's triggering it only triggers when ipv6 is used. So I've
> given up on ipv6 and switched it over to ipv4 only.
I'm sorry to hear that. can we still send to you on v6?
Spamhaus is useless. Discourage it as widely as you can. They seem to
be on autopilot.
I have blackholed a few IPv6 for destinations that I can't live without,
and I've pushed ietf.org to whitelist me in to avoid their spamhaus
dependancy. The major problem is that the SBL listing uses a bunch of
other listings which nobody maintains and which have some bogus rules.
Like that SLAAC addresses as instantly suspicious.
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 2501 bytes --]
next prev parent reply other threads:[~2019-11-10 2:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 18:56 Dave Taht
2019-11-09 19:00 ` Dave Taht
2019-11-10 2:18 ` Michael Richardson [this message]
2019-11-10 18:38 ` Dave Taht
2019-11-10 21:50 ` Michael Richardson
2019-11-11 18:33 ` [Bloat] test: ipv6 re-enabled " Dave Taht
2019-11-11 18:38 ` Dave Taht
2019-11-11 18:46 ` Dave Taht
2019-11-13 19:47 ` James Cloos
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=dabf0bcc-16a1-f927-c45f-833b862f0486@sandelman.ca \
--to=mcr@sandelman.ca \
--cc=bloat@lists.bufferbloat.net \
/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