Gnus development mailing list
 help / color / mirror / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Cc: ding@gnus.org
Subject: Re: [nnimap] Deleted messages don't go away
Date: Wed, 29 Mar 2006 08:55:23 -0800	[thread overview]
Message-ID: <ubqvpw5qc.fsf@boost-consulting.com> (raw)
In-Reply-To: <smupsk51aqj.fsf@linuxpal.mit.edu> (gdt@work.lexort.com's message of "Wed, 29 Mar 2006 11:23:00 -0500")

gdt@work.lexort.com writes:

> David Abrahams <dave@boost-consulting.com> writes:
>
>> gdt@work.lexort.com writes:
>>
>>> David Abrahams <dave@boost-consulting.com> writes:
>>>
>>>> I keep seeing some messages in my NNIMAP groups even long after I've
>>>> removed them using a different mail client.  Is there some way to get
>>>> Gnus to forget what it thinks it knows so the record can be accurate
>>>> again?
>>>
>>> I had this problem too, and turned off the agent.  Then gnus seems to
>>> no longer remember the stale messages.
>>
>> Yeah, but once you turn it back on, they come back, right?  I can't
>> even get them to go away by removing the group from the agent.
>
> I didn't try this, but I'd expect them to come back.  Since the agent
> seems broken with nnimap (if messages are deleted by other imap
> clients), I just disabled the agent for the entire nnimap server.

But of course I want offline access to my IMAP messages.  And (of
course) my IMAP server is slow so having a local cache is valuable.

> It would be nice to have the agent work, and be able to use cached
> copies of messages and at mail offline.  It seems that some other uses
> of the agent want articles only in the agent (but not on the server)
> to appear.  So perhaps this should be a per-group or per-server
> property, defaulting to "sync with server" for nnimap.

That would sure be nice.  I wish I could do it myself, but I've given
up trying to modify the Gnus system (or even really understand it --
I'm sometimes amazed I can use it at all, but it's still the most
productive client I can find).

-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com



      reply	other threads:[~2006-03-29 16:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-26 15:40 David Abrahams
2006-03-27 23:57 ` gdt
2006-03-28  3:33   ` Dave Goldberg
2006-03-28  9:21     ` Reiner Steib
2006-03-28 16:34     ` Steven E. Harris
2006-03-31  3:39       ` Dave Goldberg
2006-04-04 13:04     ` moved messages don't go away neither (was: Deleted messages don't go away) Uwe Brauer
2006-04-04 13:38       ` moved messages don't go away neither Simon Josefsson
2006-04-04 14:09         ` Uwe Brauer
2006-04-04 22:09       ` Dave Goldberg
2006-04-05  1:17         ` Wolfram Fenske
2006-04-05 11:29           ` Uwe Brauer
2006-04-05 14:44             ` Wolfram Fenske
2006-04-05 16:28               ` Uwe Brauer
2006-04-05 17:50                 ` Wolfram Fenske
2006-04-05 18:35                   ` Uwe Brauer
2006-04-05 18:41                   ` Uwe Brauer
2006-04-05 19:14                     ` Wolfram Fenske
2006-03-28 13:30   ` Deleted messages don't go away Wolfram Fenske
2006-03-29 16:03   ` [nnimap] " David Abrahams
2006-03-29 16:23     ` gdt
2006-03-29 16:55       ` David Abrahams [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=ubqvpw5qc.fsf@boost-consulting.com \
    --to=dave@boost-consulting.com \
    --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).