em_utils_reply_to_message(): Require a CamelMimeMessage.

No more fetching a message itself.  Oh, and stop unreffing the message.
Those kinds of insane semantics are what lead to crashes.

1 files changed, 0 insertions, 7 deletions

diff --git a/mail/e-mail-reader.c b/mail/e-mail-reader.c
index 315e6b91c1..673a5b206f 100644
--- a/mail/e-mail-reader.c
+++ b/mail/e-mail-reader.c
@@ -1122,9 +1122,6 @@ action_mail_reply_all_check (CamelFolder *folder,
 	if (!message)
 		return;
 
-	/* get_message_free () will unref the message, so we need to take an
-	   extra ref for e_mail_reader_reply_to_message () to own. */
-	g_object_ref (message);
 	to = camel_mime_message_get_recipients (message, CAMEL_RECIPIENT_TYPE_TO);
 	cc = camel_mime_message_get_recipients (message, CAMEL_RECIPIENT_TYPE_CC);
 
@@ -1291,10 +1288,6 @@ action_mail_reply_sender_check (CamelFolder *folder,
 
 	munged_list_message = em_utils_is_munged_list_message (message);
 
-	/* get_message_free () will unref the message, so we need to take an
-	   extra ref for e_mail_reader_reply_to_message () to own. */
-	g_object_ref (message);
-
 	/* Don't do the "Are you sure you want to reply in private?" pop-up if
 	   it's a Reply-To: munged list message... unless we're ignoring munging */
 	if (ask_ignore_list_reply_to || !munged_list_message) {