9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] UPAS, IMAP, and SMTP
Date: Tue, 10 Feb 2009 05:09:04 -0500	[thread overview]
Message-ID: <59b2b1b0213fcda32efe6b046cb14b95@quanstro.net> (raw)
In-Reply-To: <27127745fb2dfebbebc9c813667fe276@mail.nanosouffle.net>

> However,
> 	echo open '/imaps/imap.gmail.com/user@example.com/All Mail' > /mail/fs/ctl
> seems to create /mail/fs/Mail, but says it does not exist when I try
> to to access it.  Quite weird.  Is it just a naming problem with the
> space, or something different?

i think i mentioned this before.  this is a quirk of upas/nedmail —
there are a few cases where ned assumes that you don't
mean the already-open mailbox in /mail/fs and tries to
reopen the same in /mail/box/$user.  this can result in
doubly-opened mailboxes.  this is no big deal for small,
local mailboxes.  but with upas, it's a big pain if your
mailbox is big and doesn't work if your mailbox doesn't
live in /mail/box/$user

i didn't think this behavior was helpful, so i changed
ned to prefer already-open mailboxes:

	; useupas
	; echo open /mail/box/quanstro/t Mail > /mail/fs/ctl
	; upas/nedmail -f Mail
	!can't 'open Mail Mail': '/mail/box/quanstro/Mail' does not exist
	upas/nedmail: can't read
	; usenupas
	; echo open /mail/box/quanstro/x Mail >/mail/fs/ctl
	minooka; upas/nedmail -f Mail
	4 messages

acme Mail already does the right thing as
far as i can tell.

- erik



  reply	other threads:[~2009-02-10 10:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-10  6:50 Akshat Kumar
2009-02-10 10:09 ` erik quanstrom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-09  0:57 erik quanstrom
2009-02-09  0:35 Akshat Kumar
2009-02-09  8:29 ` Steve Simon
2009-02-09 12:12   ` Akshat Kumar
2009-02-09 12:30     ` Gabriel Díaz López de la Llave
2009-02-09 13:23       ` akumar
2009-02-09 13:40       ` erik quanstrom
2009-02-09 15:04     ` lucio
2009-02-10  3:44       ` Akshat Kumar
2009-02-10  3:46       ` Akshat Kumar
2009-02-10  3:48         ` erik quanstrom
2009-02-10  3:55         ` Tom Lieber
2009-02-10  4:07           ` Akshat Kumar
2009-02-10  9:46             ` erik quanstrom

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=59b2b1b0213fcda32efe6b046cb14b95@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).