thread-based email index, search, and tagging https://git.notmuchmail.org/git/notmuch/atom?h=0.24 2016-09-17T11:41:29Z 2016-09-17T11:41:29Z Jani Nikula jani@nikula.org 2016-09-13T17:14:09Z urn:sha1:36416c74e09d07fe3dfff79900171f15c4671412 As Daniel Kahn Gillmor <dkg@fifthhorseman.net> reports in id:87d1ngv95p.fsf@alice.fifthhorseman.net, notmuch show combines multiple Cc: fields into one, while notmuch reply does not. While such messages are in violation of RFC 5322, it would be reasonable to expect notmuch to be consistent. Add a known broken test to document this expectation. This also starts a new "broken" corpus for messages which are broken. Details: The original message is formatted using the message printing in notmuch-show.c. For Cc:, it uses g_mime_message_get_recipients(), which apparently combines all Cc: fields into one internally. The addresses in the reply headers, OTOH, are based on headers queried through libnotmuch. It boils down to g_mime_object_get_header() in lib/message-file.c, which returns only the first occurence of header.