Hi,
> I bet if you look at the Date headers of the problem emails, you'll find
> that they're not RFC compliant.
>
> The cyrus date parser is very strict, and if the header isn't RFC
> compliant, you'll get a bad value, and bad sorting.
>
> Looking at the RFC
>
> http://www.faqs.org/rfcs/rfc525
Robert Mueller (web) wrote:
> I bet if you look at the Date headers of the problem emails, you'll find
> that they're not RFC compliant.
These are the date headers from the offending emails.
Date: Sun, 29 Mar 2009 01:48:19 -0700
Date: Sun 17 Feb 2008 20:05:01 -0500
Date: Sun 27 Jan 2008 20:15:18
I bet if you look at the Date headers of the problem emails, you'll find
that they're not RFC compliant.
The cyrus date parser is very strict, and if the header isn't RFC
compliant, you'll get a bad value, and bad sorting.
Looking at the RFC
http://www.faqs.org/rfcs/rfc5256.html
If the sent
Hi,
> I am running cyrus imapd 2.2.13 on NetBSD, as installed from pkgsrc.
I've also got a cyrus + roundcube installation and I see the same
problem. I've got cyrus 2.2.13-10 on Debian etch.
The out of order messages in my INBOX just happen to be spam and some
have weird character sets.
The d
I have been running cyrus imapd for several years now. I recently
installed roundcube, to provide access to email on those occasions when
a proper IMAP client isn't available.
Unlike Thunderbird, roundcube relies on IMAP SORT. When sorting by date,
some emails from the past are presented as new
