From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: "Rollins\, Jameson" <jrollins@caltech.edu>,
Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Safe and useful handling of "Mixed Up" mangled messages
Date: Thu, 30 May 2019 13:30:41 -0400 [thread overview]
Message-ID: <87pnnzj1dq.fsf@fifthhorseman.net> (raw)
In-Reply-To: <87d0k0znqr.fsf@caltech.edu>
[-- Attachment #1: Type: text/plain, Size: 374 bytes --]
On Thu 2019-05-30 02:21:02 +0000, Rollins, Jameson wrote:
> The way he handles the repair seems reasonable to me (modulo
> a couple minor comments in reply).
I've responded to jamie's review here with v2 of this series, which can
be found at id:20190530172707.10378-1-dkg@fifthhorseman.net.
If anyone else wants to review, please review that revision.
Regards,
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
prev parent reply other threads:[~2019-05-30 20:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 22:54 Safe and useful handling of "Mixed Up" mangled messages Daniel Kahn Gillmor
2019-05-28 22:54 ` [PATCH 1/4] test: add test for "Mixed-Up Mime" message mangling Daniel Kahn Gillmor
2019-05-28 22:54 ` [PATCH 2/4] util/crypto: identify and repair "Mixed Up" mangled messages Daniel Kahn Gillmor
2019-05-30 2:18 ` Rollins, Jameson
2019-05-30 16:46 ` Daniel Kahn Gillmor
2019-05-30 17:01 ` Rollins, Jameson
2019-05-28 22:54 ` [PATCH 3/4] index: repair "Mixed Up" messages before indexing Daniel Kahn Gillmor
2019-05-28 22:54 ` [PATCH 4/4] cli/show: show repaired form of "Mixed Up" mangled messages Daniel Kahn Gillmor
2019-05-30 2:08 ` Rollins, Jameson
2019-05-30 2:09 ` Rollins, Jameson
2019-05-30 16:47 ` Daniel Kahn Gillmor
2019-05-30 17:06 ` Rollins, Jameson
2019-05-28 22:58 ` Safe and useful handling " Daniel Kahn Gillmor
2019-05-29 19:37 ` Daniel Kahn Gillmor
2019-05-30 2:21 ` Rollins, Jameson
2019-05-30 17:30 ` Daniel Kahn Gillmor [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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnnzj1dq.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=jrollins@caltech.edu \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).