diff options
| author | Dan Winship <danw@src.gnome.org> | 2000-08-03 08:35:45 +0800 |
|---|---|---|
| committer | Dan Winship <danw@src.gnome.org> | 2000-08-03 08:35:45 +0800 |
| commit | 5a2a24af928e27bea1e54734b5bdf62a226300af (patch) | |
| tree | 1d6ce0db71bb7c0432ea7792d37dc38de05adf9b /camel/camel-mime-message.c | |
| parent | 83dbcbadc224f5add72a42b7a7c6c794093528f8 (diff) | |
| download | gsoc2013-evolution-5a2a24af928e27bea1e54734b5bdf62a226300af.tar.gz gsoc2013-evolution-5a2a24af928e27bea1e54734b5bdf62a226300af.tar.zst gsoc2013-evolution-5a2a24af928e27bea1e54734b5bdf62a226300af.zip | |
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
Diffstat (limited to 'camel/camel-mime-message.c')
| -rw-r--r-- | camel/camel-mime-message.c | 2 |
1 files changed, 1 insertions, 1 deletions
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); |