GNOME Bugzilla – Bug 604028
When I connect to my Exchange 2007 account, about half the subject are missing from my summary buffer
Last modified: 2009-12-08 05:21:21 UTC
I've verified this happens on both the latest GIT trees for both the gnome-2.28 branch and for the master git branch. My Exchange 2007 inbox has about 1100 emails in it, dating back over two years or so. When I create an Exchange MAPI account in Evo for this, I see all my emails BUT about half of them have no subject shown in the summary window. If I select these emails then the "Subject" shows up in the mail preview window of course (but it still does not appear in the Subject column of the summary window). There is no obvious pattern to which emails have subjects and which don't: there will be a group with subjects, then one without, then a few scattered with subjects, then a large group without, then a large group with, etc. Probably there IS some pattern but as I say, it's not obvious. New emails I receive, after I create the account, seem to have the right subject shown. I have a debuging/debuggable version of Evo and all its backends, etc. so I'm happy to provide more debug information on this if you can give guidance.
Here's something weird: I visited my Exchange Deleted folder, and in this folder (which has about 2 months of deleted email, for about 5400 emails total), almost all of the Subject lines are present (there are a group missing here or there but only about 25-50 emails total) in the summary. However, about half the From addresses are missing in this summary!! There's just a blank space where they should show up. Bizarre.
If you think the Importance is just "Major" then please bump the Priority to "Urgent".
looks like a duplicate of bug 573725
I think you're right. I did search for bugs with what I hoped were relevant keywords but I guess I got it wrong: was looking for empty subjects in the summary window and the other bug reported empty subjects in the "message list". Sigh. The other bug doesn't mention the empty "From" fields though. *** This bug has been marked as a duplicate of bug 573725 ***