[In a message on Thu, 25 Jul 2002 16:33:58 CDT,
the pithy ruminations of "chewie(_at_)wookimus(_dot_)net" were:]
Hmmm.. I think we want to stay away from changing the syntax of
folders.
In a way that makes sense. In another, it "guarentees" that you won't
accidently clobber a local folder. On the other hand, if you use the
folder directory as a cache, it makes it easy to have a consistent
cache location.
Rather, let the agent handle the caching of folders through
an alias of some kind. I.e. Let's say I connect to two differnet IMAP
servers; one connection I've aliased as "bob", and one as "alice".
The agent would hold the imap://user(_at_)password:host:port information
for each server and bind it to the "bob" and "alice" folders. Folder
access could simply be "+bob/inbox" and "+alice/inbox". The agent
would have to figure out a way to store cached info w/o clobbering
info from another agent. Perhaps the cached mail folder is actually
~/Mail/.nmh-agent_hostnameforbob/ and
~/Mail/.nmh-agent_hostnameforalice/.
Hmm. I could also see using something like .xmhcheck, where you can
specify locations to inc from. Perhaps a ~/Mail/folder.adjuct, which
allows you to specify folders on the IMAP server? You specify a
folder name to "logically" appear under some directory, like so:
bob imap:BobMail imap:server_bob
bob2 imap:BobAuxMail imap:server_bob
alice imap:AliceMail imap:server_alice
Then have a a imap config file with the server settings:
bob imap://user:password(_at_)host:port
Further, if you're going to have an agent, why not have a single agent
for all servers, thus alleviating the entire caching issue?
Perl, huh? We all have our own skeletons, I guess. ;-)
Yeah, somewhere around here i have some TECO macros. . .
Sean