I didn't know about .netrc, will check it out.
I can see a whole bunch of empty directories being a waste, but
.mh_sequences does need to be stored somewhere. Perhaps there should
just be a $HOME/[Mail/].imap-mh_sequences that has all of them?
Your syntax idea is a good one, in fact, an URI based scheme would be
quite intuitive for people (i.e.
imap://[username:password@]mailhost/foldername). It would make for long
args after +, but only if you hadn't specified the credentials and
mailhost beforehand. We could support a shorthand 'i:', so my IMAP
inbox would be "scan +i:INBOX"
re,
N
Joel Reicher wrote:
I want to do IMAP too. I have an idea for design:
1. a .rc file with credentials (i.e. username, password and IMAP server)
2. All mh folders as normal, except if a directory has a ".imaprc" (or
similar) file in it, then it has no real files -- it is a reference
to an IMAP folder
Is it really necessary to have all this extra filesystem stuff? The IMAP
credentials could go in the same file as the current POP mechanism, which
I think is .netrc, and the syntax +foldername could be augmented with
a special character to indicate an IMAP folder instead of a local one.
The special character could even be incorporated into a special syntax
that specifies username and hostname, optionally. Something akin to
the scp remote file location syntax.
AFAICT, this covers everything you'd want from IMAP functionality, and
if the special characters are special enough, is unlikely to interfere
with any user's existing folder names.
Cheers,
- Joel
_______________________________________________
Nmh-workers mailing list
Nmh-workers@nongnu.org
http://lists.nongnu.org/mailman/listinfo/nmh-workers