Gnus development mailing list
 help / color / mirror / Atom feed
From: Vladimir Volovich <vvv@vsu.ru>
Subject: Re: nnimap: updating article list for a group
Date: Tue, 19 Jul 2005 18:34:59 +0400	[thread overview]
Message-ID: <873bqalv8s.fsf@vsu.ru> (raw)
In-Reply-To: <m3d60azxyi.fsf@vvv.vsu.ru>

Hi!

"VV" == Vladimir Volovich writes:

 VV> I read my IMAP folders via gnus from several
 VV> computers. Sometimes, e.g. in the following scenario: I have
 VV> opened some IMAP group in gnus, then went to another computer,
 VV> and went there to the same IMAP group, and (re)moved some of the
 VV> messages from that group. Then I return to the first computer
 VV> again, and now gnus still thinks that these articles exist, and
 VV> lists them in when i open this group. But when I try to view
 VV> them, it shows an error:

 VV> No such article (may have expired or been canceled)

this behavior is still present with current gnus from CVS... :(

 VV> The question: how do I "update article list for a group", so that
 VV> gnus somehow "synchronizes" with the de-facto present articles,
 VV> i.e. how to force gnus to re-scan the article list from server?

Also, i experience another bad nnimap behavior: when i move some
message(s) using "B m" from one folder to another (on the same imap
server), it is usually that nnimap does not delete the message from
the first folder, i.e. after moving the message(s), i quit from the
folder, and then i can see these messages still there if i re-enter
this folder... :(

Best,
v.

P.S. I would appreciate a CC of your reply to me.





      parent reply	other threads:[~2005-07-19 14:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-25  6:04 Q: " Vladimir Volovich
2004-09-25 11:53 ` Simon Josefsson
2005-07-19 14:34 ` Vladimir Volovich [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=873bqalv8s.fsf@vsu.ru \
    --to=vvv@vsu.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).