Make EMailPartList thread-safe.

Exposing data members in the public struct is unwise, especially when
EMailPartList is used from multiple threads.  Instead keep the members
private and provide a set of thread-safe functions to manipulate them.

1 files changed, 4 insertions, 2 deletions

diff --git a/mail/e-http-request.c b/mail/e-http-request.c
index 4b77950a4c..5c4b638ac8 100644
--- a/mail/e-http-request.c
+++ b/mail/e-http-request.c
@@ -291,12 +291,14 @@ handle_http_request (GSimpleAsyncResult *res,
 			EShell *shell;
 			ESourceRegistry *registry;
 			CamelInternetAddress *addr;
+			CamelMimeMessage *message;
 
 			shell = e_shell_get_default ();
 			registry = e_shell_get_registry (shell);
-			addr = camel_mime_message_get_from (part_list->message);
+			message = e_mail_part_list_get_message (part_list);
+			addr = camel_mime_message_get_from (message);
 			force_load_images = em_utils_in_addressbook (
-					registry, addr, FALSE, cancellable);
+				registry, addr, FALSE, cancellable);
 
 			g_object_unref (part_list);
 		}