From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: [PATCH 2/2] Add additional munged reply-to tests
Date: Fri, 14 Jul 2017 15:26:51 +0200 [thread overview]
Message-ID: <87shhz6tes.fsf@fifthhorseman.net> (raw)
In-Reply-To: <20170714130912.24777-2-dkg@fifthhorseman.net>
[-- Attachment #1: Type: text/plain, Size: 1915 bytes --]
On Fri 2017-07-14 15:09:12 +0200, Daniel Kahn Gillmor wrote:
> The reply-to munging code might behave differently whether there's an
> exact match on the strings or not, or whether the string is a raw
> addr-spec instead of an name-addr. These tests cover those
> variations.
This pair of patches should be safe and clean to apply. When they're
applied, though, the gmime 3.0 series no longer passes the test suite
due to these failures:
----------
T220-reply: Testing "notmuch reply" in several variations
PASS Basic reply
PASS Multiple recipients
PASS Reply with CC
PASS Reply from alternate address
PASS Reply from address in named group list
PASS Support for Reply-To
FAIL Un-munging Reply-To
--- T220-reply.7.expected 2017-07-14 13:24:32.203184911 +0000
+++ T220-reply.7.output 2017-07-14 13:24:32.203184911 +0000
@@ -6,3 +6,4 @@
On Tue, 05 Jan 2010 15:43:56 -0000, Sender <sender@example.com> wrote:
> Un-munging Reply-To
+failed
FAIL Un-munging Reply-To With Exact Match
--- T220-reply.8.expected 2017-07-14 13:24:32.243185095 +0000
+++ T220-reply.8.output 2017-07-14 13:24:32.243185095 +0000
@@ -6,3 +6,4 @@
On Tue, 05 Jan 2010 15:43:56 -0000, Sender <sender@example.com> wrote:
> Un-munging Reply-To
+failed
PASS Un-munging Reply-To With Raw addr-spec
PASS Message with header of exactly 200 bytes
PASS From guessing: Envelope-To
PASS From guessing: X-Original-To
PASS From guessing: Delivered-To
PASS Reply with RFC 2047-encoded headers
PASS Reply with RFC 2047-encoded headers (JSON)
PASS Reply to a message with multiple Cc headers
----------
I think this is due to "notmuch reply" crashing on those first two tests
with a segmentation fault.
i think this implicates the reply-to munging code, which i don't
understand, but would welcome help on debugging.
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2017-07-14 13:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-14 13:09 [PATCH 1/2] Ensure that "notmuch reply" succeeds during testing Daniel Kahn Gillmor
2017-07-14 13:09 ` [PATCH 2/2] Add additional munged reply-to tests Daniel Kahn Gillmor
2017-07-14 13:26 ` Daniel Kahn Gillmor [this message]
2017-07-14 14:42 ` [PATCH 1/2] Ensure that "notmuch reply" succeeds during testing David Bremner
2017-07-14 17:08 ` Daniel Kahn Gillmor
2017-07-14 18:04 ` David Bremner
2017-07-14 20:14 ` [PATCH v2 " Daniel Kahn Gillmor
2017-07-14 20:14 ` [PATCH v2 2/2] Add additional munged reply-to tests Daniel Kahn Gillmor
2017-07-14 22:03 ` [PATCH] Avoid crashes in "notmuch reply" with gmime 3.0 when reply-to == sender Daniel Kahn Gillmor
2017-07-14 22:13 ` Daniel Kahn Gillmor
2017-07-14 22:53 ` Daniel Kahn Gillmor
2017-07-15 11:47 ` David Bremner
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=87shhz6tes.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--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).