From: Benjamin LaHaise <ben@communityfibre.ca>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: linux-mm@kvack.org - limping on a backup
Date: Mon, 28 Jun 2021 09:53:52 -0400 [thread overview]
Message-ID: <20210628135352.GL4058@kvack.org> (raw)
In-Reply-To: <20210628134607.GA4604@ziepe.ca>
On Mon, Jun 28, 2021 at 10:46:07AM -0300, Jason Gunthorpe wrote:
> Well, the DKIM issue has been left unresolved for a long time.
> I saw on the bug conversation there seems to be no clear path to fix
> it?
Nobody had ever bothered to provide or figure out a test case. We have
one now and I'm working with Tucows to try to sort out a fix.
The fact of the matter is that the DKIM spec is broken and doesn't
properly address issues relating to transport of emails containing UTF-8
content over SMTP sessions which are limited to 7 bit transport due to
backwards compatibility assumptions.
-ben
--
"Thought is the essence of where you are now."
next prev parent reply other threads:[~2021-06-28 13:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 14:59 linux-mm@kvack.org - limping on a backup Benjamin LaHaise
2021-06-24 12:12 ` David Sterba
2021-06-25 17:00 ` James Bottomley
2021-06-25 17:12 ` Benjamin LaHaise
2021-06-25 19:21 ` James Bottomley
2021-06-25 19:26 ` Benjamin LaHaise
2021-06-25 21:52 ` James Bottomley
2021-06-28 13:46 ` Jason Gunthorpe
2021-06-28 13:53 ` Benjamin LaHaise [this message]
2021-06-28 14:26 ` Jason Gunthorpe
2021-06-28 14:40 ` Benjamin LaHaise
2021-06-28 16:20 ` Jason Gunthorpe
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=20210628135352.GL4058@kvack.org \
--to=ben@communityfibre.ca \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.