From 8e7eea0d261f38e22c72a9a394df6375247c8e59 Mon Sep 17 00:00:00 2001 From: Dan Winship Date: Tue, 3 Jul 2001 15:24:55 +0000 Subject: Doh. Don't remove things from the hash table while foreach'ing it. (And * providers/imap/camel-imap-message-cache.c (camel_imap_message_cache_clear): Doh. Don't remove things from the hash table while foreach'ing it. (And can't use foreach_remove either because we have to remove them in a weird order). Fixes #3618. * providers/imap/camel-imap-folder.c (imap_get_message): If the server returns OK from the FETCH BODY, but there's no parseable BODY response, it's probably because there's an UN-parseable BODY response, implying the message is badly formatted, MIMEwise. In that case, fall back to fetching the message as a single part. svn path=/trunk/; revision=10748 --- camel/ChangeLog | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'camel/ChangeLog') diff --git a/camel/ChangeLog b/camel/ChangeLog index 7b5a045284..5f9a0fdf1d 100644 --- a/camel/ChangeLog +++ b/camel/ChangeLog @@ -1,3 +1,17 @@ +2001-07-03 Dan Winship + + * providers/imap/camel-imap-message-cache.c + (camel_imap_message_cache_clear): Doh. Don't remove things from + the hash table while foreach'ing it. (And can't use foreach_remove + either because we have to remove them in a weird order). Fixes + #3618. + + * providers/imap/camel-imap-folder.c (imap_get_message): If the + server returns OK from the FETCH BODY, but there's no parseable + BODY response, it's probably because there's an UN-parseable BODY + response, implying the message is badly formatted, MIMEwise. In + that case, fall back to fetching the message as a single part. + 2001-07-02 Sam Creasey * providers/nntp/camel-nntp-folder.c: Implemented -- cgit v1.2.3