Trim trailing space from the subject. I've now seen replies from two

	* camel-mime-message.c (camel_mime_message_set_subject): Trim
	trailing space from the subject. I've now seen replies from two
	different people that tricked the threading code by (a) not having
	References/In-Reply-To, and (b) adding an extra space to the end
	of the subject line so the subject-based threading fails too. Who
	writes these broken mailers anyway?

svn path=/trunk/; revision=4495

2 files changed, 10 insertions, 1 deletions

diff --git a/camel/ChangeLog b/camel/ChangeLog
index ace0859687..2998aae007 100644
--- a/camel/ChangeLog
+++ b/camel/ChangeLog
@@ -1,3 +1,12 @@
+2000-08-02  Dan Winship  <danw@helixcode.com>
+
+	* camel-mime-message.c (camel_mime_message_set_subject): Trim
+	trailing space from the subject. I've now seen replies from two
+	different people that tricked the threading code by (a) not having
+	References/In-Reply-To, and (b) adding an extra space to the end
+	of the subject line so the subject-based threading fails too. Who
+	writes these broken mailers anyway?
+
 2000-08-01  Jeffrey Stedfast  <fejj@helixcode.com>
 
 	* providers/smtp/camel-smtp-transport.c (smtp_helo): When forced
diff --git a/camel/camel-mime-message.c b/camel/camel-mime-message.c
index e511fece7a..f0b3ea4a70 100644
--- a/camel/camel-mime-message.c
+++ b/camel/camel-mime-message.c
@@ -256,7 +256,7 @@ camel_mime_message_set_subject (CamelMimeMessage *mime_message,
 	g_assert (mime_message);
 
 	g_free(mime_message->subject);
-	mime_message->subject = g_strdup(subject);
+	mime_message->subject = g_strchomp(g_strdup(subject));
 	text = header_encode_string(subject);
 	CAMEL_MEDIUM_CLASS(parent_class)->set_header((CamelMedium *)mime_message, "Subject", text);
 	g_free(text);