From: Rasmus <rasmus@gmx.us>
To: ding@gnus.org
Subject: Re: Wrong articles on RET
Date: Fri, 20 Jul 2012 08:26:51 +0100 [thread overview]
Message-ID: <87liie7v0k.fsf@pank.lan> (raw)
In-Reply-To: <87liifz888.fsf@dancingfrog.co.uk>
Matt,
> For whatever reason (copying, resyncing, internal server craziness)
> message sequence can be drastically re-ordered.
>
> I suspect its something to do with IMAP UIDs and Messages sequence
> numbers: http://tools.ietf.org/html/rfc3501#section-2.3.1
This was what I thought of last night as well. I will check whether
this is in fact the case later.
Out of curiosity, did you also get to this state using offlineimap?
> The only way to see the last date sixty is to load everything and
> sort by date AFAIK. If anyone knows different or how one might
> "reindex" the IMAP server based on date then please let me know!
IF it's based on IMAP UIDs it may be possible to use of these wonderful
Python libraries (e.g. imapclient or imaplib) [there's also a Perl
imapclient].
For my part it could also be that Dovecot is the source of the problem.
I'm really not sure. . .
–Rasmus
--
A clever person solves a problem. A wise person avoids it
next prev parent reply other threads:[~2012-07-20 7:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-19 19:41 Rasmus
2012-07-19 22:09 ` Rasmus
2012-07-19 22:39 ` Matt Ford
2012-07-20 7:26 ` Rasmus [this message]
2012-07-20 7:52 ` Matt Ford
2012-07-20 9:24 ` Rasmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87liie7v0k.fsf@pank.lan \
--to=rasmus@gmx.us \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).