From: erik quanstrom <quanstro@quanstro.net>
To: akumar@mail.nanosouffle.net, 9fans@9fans.net
Subject: Re: [9fans] UPAS, IMAP, and SMTP
Date: Sun, 8 Feb 2009 19:57:35 -0500 [thread overview]
Message-ID: <21f15de8b3a797760938ffb7b64886fd@quanstro.net> (raw)
> Using upas/fs -f /imaps/imap.gmail.com I can access my GMail
> Inbox. The mail structure is posted in /mail/fs/mbox
> However, there may be local mail as well as other labels (i.e., folders)
> in GMail that I would want to access -- it seems that specifying
> a new folder at GMail, i.e.,
> upas -f /imaps/imap.gmail.com/user@mail.example.com/label
> replaces the /mail/fs/mbox structure with the mail at this new place.
> Is there any way to have these co-exist -- i.e., /mail/fs/mbox for
> the original, and /mail/fs/label for subsequent labels/folders I want
> to access?
yes. you can have as many mailboxes open as you wish.
once upas/fs is running, you can
u = user@mail.example.com
l = label
echo open /imaps/imap.gmail.com/$u/$l $l>/mail/fs/ctl
in fact if labels is a list you could
for(i in $labels)
echo open /imaps/imap.gmail.com/$u/$i $i>/mail/fs/ctl
side note:
upas/nedmail's rules for when to open an already
open folder confused me a little bit. i changed the
nupas version to prefer an already-open folder over
one in /mail/box/$user to ease using a secondary
imap mailbox.
- erik
next reply other threads:[~2009-02-09 0:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 0:57 erik quanstrom [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-10 6:50 Akshat Kumar
2009-02-10 10:09 ` 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=21f15de8b3a797760938ffb7b64886fd@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=akumar@mail.nanosouffle.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).