imap expiration trouble

imap expiration trouble

[Alexander Kotelnikov]

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
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
32 EXPUNGE
32 OK No messages deleted, so no update needed

This hurts :(
-- 
Alexander Kotelnikov
Saint-Petersburg, Russia

Re: imap expiration trouble

[Simon Josefsson]

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

What was the commands before that?  Wasn't the range of articles
compressed?  Was it too long anyway?

> 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

nnimap.el should probably use SEARCH UNSEEN instead, but the usage
above is perfectly fine according to the standard.  It is OK to ignore
this, unless the UNSEEN article count is wrong too.  This is probably
not what is causing your problem.

Re: imap expiration trouble

[Alexander Kotelnikov]

>>>>> 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

Re: imap expiration trouble

[Simon Josefsson]

Alexander Kotelnikov <sacha@giotto.sj.ru> writes:

>>>>>> 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)

Ouch.  Should be fixed in CVS now.

> 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...

I meant that the latter part of your log didn't cause the problem
(even though the error message from the server might have suggested
that), the problem with the long line did.