From: Jason Gunthorpe <jgg@ziepe.ca>
To: Benjamin LaHaise <bcrl@kvack.org>
Cc: Matthew Wilcox <willy@infradead.org>,
Jann Horn <jannh@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org
Subject: Re: Emails from kvack.org going into spam
Date: Fri, 16 Oct 2020 12:10:29 -0300 [thread overview]
Message-ID: <20201016151029.GD36674@ziepe.ca> (raw)
In-Reply-To: <20201016141349.GK30228@kvack.org>
On Fri, Oct 16, 2020 at 10:13:49AM -0400, Benjamin LaHaise wrote:
> On Fri, Oct 16, 2020 at 02:57:33PM +0100, Matthew Wilcox wrote:
> > On Fri, Oct 16, 2020 at 10:54:51AM -0300, Jason Gunthorpe wrote:
> > > Does anyone know who is the admin for kvack.org?
> >
> > That's Ben. Adding cc.
>
> Without suggestions for how to fix the issue, there's not much I can do.
> majordomo doesn't modify the message body - that was changed years ago to
> deal with the first round of DKIM breakage.
First round? I looked some more and it is not just Google senders, but
Facebook and others. This is a bug chunk of the major kernel
contributing companies effected :(
> Postfix must be mangling things, but I have no idea how to prevent
> that.
If so, it is probably the hand off from majordomo to postfix is not
8bit clean? Weitse had some guidance on how that works:
http://postfix.1071664.n5.nabble.com/On-DKIM-and-Content-Transfer-Encoding-td68767.html
Seems he confirms that indeed postfix auto downgrades if it is not all
done correctly.
The big hammer is to try this:
disable_mime_output_conversion (default: no)
Disable the conversion of 8BITMIME format to 7BIT format. Mime output conversion is needed when the destination does not advertise 8BITMIME support.
This feature is available in Postfix 2.0 and later.
In 2020 I bet you can safely set that to yes. Lots of internet hits
related to that config and DKIM breakage with Postfix.
But probably this is an issue with integrating majordomo with postfix,
ie it doesn't set the -B8BITMIME when calling sendmail or something?
Postfix is sensitive to this, other mailers like exim are not.
> I wish people wouldn't keep coming up with new ways to break
> mailing lists.
Running mailing lists has always been hard :(
Jason
next prev parent reply other threads:[~2020-10-16 15:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 13:54 Jason Gunthorpe
2020-10-16 13:57 ` Matthew Wilcox
2020-10-16 14:13 ` Benjamin LaHaise
2020-10-16 15:10 ` Jason Gunthorpe [this message]
2020-10-16 15:17 ` Jann Horn
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=20201016151029.GD36674@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=akpm@linux-foundation.org \
--cc=bcrl@kvack.org \
--cc=jannh@google.com \
--cc=linux-mm@kvack.org \
--cc=willy@infradead.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