Ubuntu
evolution package

Evolution is not reading the datestamps on incoming messages.

Asked by Neil Woolford

I've just changed my subscription to the ubuntu-users mailing list so that it is directed via my isp's mailserver rather than via my domain. So I have simply moved it from one POP server to another. (I'm trying to reduce the volume of traffic on my domain and in my non-hacking computers' mailboxes.)

Since the move, Evolution shows a '?' instead of the message date and time in the message listings. This means that the incoming messages are no longer sortable by date. The messages from the Ubuntu list (digest format) still have what appear to be sensible and valid dates when I open them; it is just that Evolution doesn't seem to be able to use them for display or sorting.

Googling gets me a lot about evolution, the hypothesis or heresy, depending on your understanding of science...

I'd really like to continue to easily sort the messages by date. Is there any known issue with date headers that could be at play here? If so, what can I do about it?

Neil

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu evolution Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Dave Meikle (dmk-uk) said : 		#1

If you push Ctrl-U to view the messages source, what does the Date header say?

Regards,
Dave

Revision history for this message
Neil Woolford (neil-neilwoolford) said : 		#2

Well, to the naked eye there is no difference in the message headers (viewed by Ctrl-U or by ticking 'show full headers') between the messages that display with a valid date and those that don't. Evolution shows a perfectly valid date in the message headers when reading all of the messages, including the ones where the date is replaced by a '?' in the list view. So the date is there in a format that Evolution can parse...

I'd happily post examples, but by some kind of random magic, the dates have started to show in the listings again since last night.

Although this isn't a resolution in the sense of 'problem fixed, we know what it was', I'm going to close the query as I don't think it struck a chord with other users having similar problems.

Neil