Duncan posted on Sun, 15 Sep 2013 13:03:34 +0000 as excerpted:
> I can't be sure, but I'd have guessed the problem would have been
> reported /long/ before now if it was the full gmime 2.6 series, so I'm
> guessing it was 2.6.15 (March installation here) or later, very possibly
> only 2.6.17, which I built and installed on August 22 according to the
> date on my binpkg. You started this thread on August 19, it appears, so
> it's just possible you had just updated to 2.6.17 yourself at that
> point. I hadn't seen the problem yet then, but I had a complaint a few
> days later, and if I updated on the 22nd and it only happens on long
> threads where the references header is long enough to wrap, that could
> very well be it.
Hmm... checked the upstream gnome bugzilla, and while my bug-search
skills aren't always the greatest, there's a limited number of bugs for
the 2.6 series and I couldn't find a match at all.
But I did find a changelog entry that's a good candidate:
2013-04-05 Jeffrey Stedfast <f...@gnome.org>
* gmime/gmime-utils.c (header_fold_tokens): New internal function
that replaces the older header_fold() function. This new one uses
the rfc2047 tokenizer so that we share the same rfc2047 workaround
logic in the tokenizer.
Fixes bug #697407
The mentioned bug is:
header folding logic doesn't use the same rfc2047 workarounds as the
decoder
https://bugzilla.gnome.org/show_bug.cgi?id=697407
That log entry was post-2.6.15 but should have been in 2.6.16, released
the end of June.
Meanwhile, threading for that post was off too. =:^( (I'm using pan to
read/reply via gmane.)
But =:^) also, as it looks like we have a reproducer right in this thread
now. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
_______________________________________________
Pan-users mailing list
Pan-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/pan-users
