9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] upas/fs to imap: removed messages sometimes regenerate
Date: Sun,  2 Mar 2008 08:01:37 -0500	[thread overview]
Message-ID: <ef23690e0f2aeea45f1d2e9e245447c6@quanstro.net> (raw)
In-Reply-To: <509071940803012136y334eaaafu3b78d102fbf81cdf@mail.gmail.com>

> I'm seeing some odd (wrong) behavior with Plan 9's upas/fs and was
> wondering of others have seen it, before I start digging further. I
> use upas/fs to talk to a local mailbox and two IMAP servers. The local
> store and one of the IMAP servers work reliably correctly. On the
> other IMAP server, upas/fs will *sometimes* get into a state where
> when I remove a message, it'll re-insert itself into the tree with a
> higher message number. For example, with the IMAP server dalet:
>
> :; cd /mail/fs/dalet
> :; ls
> 1
> 2
> ctl
> :; rm 1 2 ; ls
> 3
> 4
> ctl
>
> Messages 3&4 are the same as 1&2; nothing new's actually come in.
> Other IMAP clients I've used behave properly with this server. I've
> not yet identified the pattern which causes it, but it's not random.
> Anyone else seen this or similar?

i've seen this before.  the problem was the client and server had lost
uid sync.  if you know a situation that always produces the behavior
it would be interesting to telnet directly to the server and snoop on
the uids.
	1 login $user $password
	2 select inbox
	3 status inbox (messages uidvalidity)
	4 uid fetch 1:* uid
<delete messages the normal way.  upas/fs uses "uid store %uld +flags (\Deleted)"
and then "expunge">
	5 uid fetch 1:* uid
will list all the available messages.  if you list the uids, delete messages
in a way that causes a problem, then you can list the uids again and
see if upas/fs or the server is at fault.

- erik


      reply	other threads:[~2008-03-02 13:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-02  5:36 Anthony Sorace
2008-03-02 13:01 ` erik quanstrom [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=ef23690e0f2aeea45f1d2e9e245447c6@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    /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).