Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: Oort 0.10 doesn't delete auto-expired mail in IMAP
Date: Tue, 18 Feb 2003 23:52:49 +0100	[thread overview]
Message-ID: <ilufzql42wu.fsf@latte.josefsson.org> (raw)
In-Reply-To: <7wzadgtutza.fsf@dlsun92.us.oracle.com>

Nimar Arora <nospam_nimar_arora@yahoo.com> writes:

> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> So it's the is-this-article-old computation that fails.  Can you find
>> the function that does this?  Position point inside it and do M-x
>> edebug-defun RET, then invoke expiry.  Emacs should show you the code
>> and allow you to single-step with SPC.  Do that and watch it
>> compute.  Can you see where it fails?
>
> OK, it appears that the function gnus-summary-expire-articles creates a
> list of expirable articles and then a sublist of articles which
> shouldn't be expired. The two list always end up being the same in my
> case and thats why articles never get expired. I turned on imap-log and
> found the following error. 
>
> 2733 UID SEARCH UID 5739,5776,5794,5870,5873,5895,5930,5947:5952,5954:5957,5959,5961:5964,5966:6057,6059:6095,6097:6136,6138:6176,6178,6180:6248,6250:6465,6467:6521,6523:6617,6619,6621:6629,6631,6633:6651,6653:6670,6672:6688,6690:6741,6743,6745:6764,6766:6775,6777:6781,6783:6785,6787,6789:6801,6803:6818,6820:6932,6934:6970,6972:7018,7020:7051,7053:7071,7074:7088,7090:7118,7120:7133,7135:7158,7160:7243,7245:7261,7263:7270,7273:7287,7289:7316,7318,7320:7359,7361:7411,7413:7415,7417:7420,7422:7423,7426:7486,7489:7491,7493:7494,7496:7521,7524:7533 NOT SINCE 11-Feb-2003
> 2733 NO UID SEARCH failed: Search Failed. Err=6502

Interesting.  Maybe you could report this to the server
administrators?  Which server is it?  It seems to be a server problem.
Perhaps shortening the command line helps.  Maybe you could try
issuing the same command via telnet (or similar) but with less UIDs to
see if the server starts to respond at some point.


      reply	other threads:[~2003-02-18 22:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7wz3cmscccg.fsf@dlsun92.us.oracle.com>
     [not found] ` <841y2b1c28.fsf@lucy.is.informatik.uni-duisburg.de>
2003-02-14 20:52   ` Nimar Arora
     [not found]     ` <84vfzlvoii.fsf@lucy.is.informatik.uni-duisburg.de>
     [not found]       ` <7wz8yweflyp.fsf@dlsun92.us.oracle.com>
     [not found]         ` <848yweuk8w.fsf@lucy.is.informatik.uni-duisburg.de>
2003-02-18 22:03           ` Nimar Arora
2003-02-18 22:52             ` Simon Josefsson [this message]

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=ilufzql42wu.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    /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).