From: Jani Nikula <jani@nikula.org>
To: Jani Nikula <jani@nikula.org>, notmuch@notmuchmail.org
Cc: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Subject: [RFC PATCH 4/6] cli/reply: pass internet address list to munge detect
Date: Sun, 19 Jun 2016 23:15:32 +0300 [thread overview]
Message-ID: <723de0c9331d8c96be4ea4b16fdb85095c9defd1.1466366738.git.jani@nikula.org> (raw)
In-Reply-To: <cover.1466366737.git.jani@nikula.org>
In-Reply-To: <cover.1466366737.git.jani@nikula.org>
---
notmuch-reply.c | 20 ++++++++++++--------
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/notmuch-reply.c b/notmuch-reply.c
index 98034485c546..cf4248bd6794 100644
--- a/notmuch-reply.c
+++ b/notmuch-reply.c
@@ -231,19 +231,18 @@ scan_address_list (InternetAddressList *list,
* in either the 'To' or 'Cc' header of the message?
*/
static int
-reply_to_header_is_redundant (notmuch_message_t *message, const char *reply_to)
+reply_to_header_is_redundant (notmuch_message_t *message,
+ InternetAddressList *reply_to_list)
{
const char *to, *cc, *addr;
- InternetAddressList *list;
InternetAddress *address;
InternetAddressMailbox *mailbox;
- list = internet_address_list_parse_string (reply_to);
-
- if (internet_address_list_length (list) != 1)
+ if (reply_to_list == NULL ||
+ internet_address_list_length (reply_to_list) != 1)
return 0;
- address = internet_address_list_get_address (list, 0);
+ address = internet_address_list_get_address (reply_to_list, 0);
if (INTERNET_ADDRESS_IS_GROUP (address))
return 0;
@@ -269,6 +268,8 @@ static InternetAddressList *get_sender(notmuch_message_t *message,
reply_to = g_mime_message_get_reply_to (mime_message);
if (reply_to && *reply_to) {
+ InternetAddressList *reply_to_list;
+
/*
* Some mailing lists munge the Reply-To header despite it
* being A Bad Thing, see
@@ -282,8 +283,11 @@ static InternetAddressList *get_sender(notmuch_message_t *message,
* to the list. Note that the address in the Reply-To header
* will always appear in the reply if reply_all is true.
*/
- if (! reply_to_header_is_redundant (message, reply_to))
- return internet_address_list_parse_string (reply_to);
+ reply_to_list = internet_address_list_parse_string (reply_to);
+ if (! reply_to_header_is_redundant (message, reply_to_list))
+ return reply_to_list;
+
+ g_object_unref (G_OBJECT (reply_to_list));
}
return internet_address_list_parse_string (
--
2.1.4
next prev parent reply other threads:[~2016-06-19 20:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-18 21:31 [PATCH 0/7] cli/reply: refactoring Jani Nikula
2016-06-18 21:31 ` [PATCH 1/7] cli/reply: push notmuch reply format abstraction lower in the stack Jani Nikula
2016-06-18 21:31 ` [PATCH 2/7] cli/reply: reuse show_reply_headers() in headers-only format Jani Nikula
2016-06-18 21:31 ` [PATCH 3/7] cli/reply: unify reply format functions Jani Nikula
2016-06-18 21:31 ` [PATCH 4/7] cli/reply: reorganize create_reply_message() Jani Nikula
2016-06-18 21:31 ` [PATCH 5/7] cli/reply: make references header creation easier to follow Jani Nikula
2016-06-18 21:31 ` [PATCH 6/7] cli/reply: reuse create_reply_message() also for headers-only format Jani Nikula
2016-06-18 21:31 ` [PATCH 7/7] cli/reply: reduce the reply format abstractions Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 0/6] cli/reply: refactoring part 2 Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 1/6] cli/reply: use dedicated functions for reply to mapping Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 2/6] cli/reply: check for NULL list first in scan_address_list() Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 3/6] cli/reply: return internet address list from get header funcs Jani Nikula
2016-06-19 20:15 ` Jani Nikula [this message]
2016-06-19 20:15 ` [RFC PATCH 5/6] cli/reply: pass gmime message to munge detection Jani Nikula
2016-06-19 20:15 ` [RFC PATCH 6/6] cli/reply: only pass gmime message to add recipients to reply message Jani Nikula
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=723de0c9331d8c96be4ea4b16fdb85095c9defd1.1466366738.git.jani@nikula.org \
--to=jani@nikula.org \
--cc=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).