From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] upas/fs still modifying gmail inbox after window closed
Date: Tue, 1 Feb 2011 12:52:03 -0500 [thread overview]
Message-ID: <92aafd1159da880f379241a98341c105@ladd.quanstro.net> (raw)
In-Reply-To: <20110201173127.GA27842@phoenix.inri.net>
On Tue Feb 1 12:32:34 EST 2011, stanley.lieber@gmail.com wrote:
> in plan 9: using upas/fs, i mounted my gmail inbox over imap, then
> started acme. at some point, the acme window disappeared. newly
> received messages in my gmail inbox continue to get marked as read
> shortly after they arrive. my assumption is that upas/fs is still
> accessing the mailbox. how can i prove (or disprove) this, and stop
> it from happening?
echo close mbox > /mail/fs/ctl
i don't know if nupas handles this correctly or not. but i
seem to recall that it does. it's a matter of issuing the right
imap command when you're fetching the message body for
internal use, rather than for viewing.
- erik
next prev parent reply other threads:[~2011-02-01 17:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-01 17:31 Stanley Lieber
2011-02-01 17:52 ` erik quanstrom [this message]
2011-02-01 18:29 ` Stanley Lieber
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=92aafd1159da880f379241a98341c105@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).