From: Alexander Kotelnikov <sacha@giotto.sj.ru>
Subject: Re: imap expiration trouble
Date: Sun, 17 Nov 2002 18:59:23 +0300 [thread overview]
Message-ID: <87vg2wchlw.fsf@pale.sj.ru> (raw)
In-Reply-To: <ilud6p4xkvl.fsf@latte.josefsson.org> (Simon Josefsson's message of "Sun, 17 Nov 2002 16:43:10 +0100")
>>>>> On Sun, 17 Nov 2002 16:43:10 +0100
>>>>> "SJ" == Simon Josefsson <jas@extundo.com> wrote:
SJ>
SJ> Alexander Kotelnikov <sacha@giotto.sj.ru> writes:
>> Hi.
>>
>> I've meved one nnimap group into total-expire mode and expiration doe
>> not work, since too many articles need to be expired (about 6000). I
>> get in my *imap-log*:
>>
>> 30 BAD Command line too long
SJ>
SJ> What was the commands before that? Wasn't the range of articles
SJ> compressed? Was it too long anyway?
It was. It was a list of numbers from 1 to ~6000
29 OK UID SEARCH completed
30 UID STORE 1,2,3,4,5,6
...
6102,6103,6104,6105,6106,6107,6108,6109,6110,6111,6112 +FLAGS (\Deleted)
30 BAD Command line too long
31 STATUS "IMAP/debian.devel" (unseen)
SJ>
>> 31 STATUS "IMAP/debian.devel" (unseen)
>> * NO CLIENT BUG DETECTED: STATUS on selected mailbox: IMAP/debian.devel
>> * STATUS IMAP/debian.devel (UNSEEN 0)
>> 31 OK STATUS completed
SJ>
SJ> nnimap.el should probably use SEARCH UNSEEN instead, but the usage
SJ> above is perfectly fine according to the standard. It is OK to ignore
SJ> this, unless the UNSEEN article count is wrong too. This is probably
SJ> not what is causing your problem.
Huh... the articles are not expired...
--
Alexander Kotelnikov
Saint-Petersburg, Russia
next prev parent reply other threads:[~2002-11-17 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-17 13:14 Alexander Kotelnikov
2002-11-17 15:43 ` Simon Josefsson
2002-11-17 15:59 ` Alexander Kotelnikov [this message]
2002-11-18 8:49 ` Simon Josefsson
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=87vg2wchlw.fsf@pale.sj.ru \
--to=sacha@giotto.sj.ru \
/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).