From: cinap_lenrek@felloff.net
To: 9front@9front.org
Subject: Re: [9front] upasfs and IMAP: opening nested mailboxes
Date: Thu, 3 Oct 2019 12:11:54 +0200 [thread overview]
Message-ID: <1D1234FC2EDDE680C16D236D8812C132@felloff.net> (raw)
In-Reply-To: 20191003072831.5jajstonuumyvhgi@BlackBox
> open /imaps/imap.fastmail.com/personal@sgregoratto.me/Dev/9front
> open /imaps/imap.fastmail.com/personal@sgregoratto.me/Dev.9front
i'm not an imap expert but reading the code this should have worked.
how does it fail? is there a error message? how do you expect this to work?
maybe enable some debug printing with -l and -d flag.
you can pass a 3rd argument to open with the local name (in case you
dont want to have the mailbox directory appear as /mail/fs/9front/
or /mail/fs/Dev.9front/).
in any case, there should be a directory showing up in /mail/fs/
named as the part after the last slash in the path or the explicit
name.
--
cinap
next reply other threads:[~2019-10-03 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 10:11 cinap_lenrek [this message]
2019-10-03 12:05 ` Stephen Gregoratto
-- strict thread matches above, loose matches on Subject: below --
2019-10-04 4:30 kokamoto
2019-10-03 7:28 Stephen Gregoratto
2019-10-03 9:42 ` [9front] " Ethan Gardener
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=1D1234FC2EDDE680C16D236D8812C132@felloff.net \
--to=cinap_lenrek@felloff.net \
--cc=9front@9front.org \
/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).