Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>,
	starlink@lists.bufferbloat.net,
	 Make-Wifi-fast <make-wifi-fast@lists.bufferbloat.net>,
	 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>,
	 Cake List <cake@lists.bufferbloat.net>
Subject: [Cerowrt-devel] DMARC policy change fix for lists.bufferbloat.net
Date: Thu, 9 Jun 2022 18:37:04 -0700	[thread overview]
Message-ID: <CAA93jw4S5KZC=RF_S4aCPWterZqTMt9E4Zu61RtnaDiPR2B2nA@mail.gmail.com> (raw)

Over the past year or three the DMARC policy change to how mailing
lists were handled have been propagating across the net. I wasn't
paying attention. A lot of people have been auto-unsubscribed over the
last few months. I'm still working on improving the DMARC policy
here... and this is a test message of munging replies differently...

The bloat mailing list, which at its peak was above 550 people, is now
down to around 350, and for all I know the DMARC classifiers have been
tossing all the email that remains into your spam folders. If you've
been missing all the exciting, innovative debloating activity across
so many aspects of our project - the iab workshop last sept for
example, the new speedtest.net app, the improvements to wifi, news on
the latest broadband activities, etc, etc, our mailing list archives,
would be a good place to look to see when these problems really
started.

IF you have been missing emails from this domain, please contact me
privately so I can look over the logs. There's at least 3 different
behaviors happening - rejections, which is what I noticed, but 250
quarantine I had not, until today, and something that I cannot
describe, only curse at, as yet.

-- 
FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/
Dave Täht CEO, TekLibre, LLC

                 reply	other threads:[~2022-06-10  1:37 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw4S5KZC=RF_S4aCPWterZqTMt9E4Zu61RtnaDiPR2B2nA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=make-wifi-fast@lists.bufferbloat.net \
    --cc=starlink@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