Please pardon me if this question is in a doc somewhere. I have
searched through the source tarball, the www site, and the mailing
list archives and have yet to find an answer to my question despite
that it seems to be something that would be asked about often.
The problem:
I have some users who would like to be able to check their mail
through a web-based IMAP interface sometimes but use
mutt/pine/elm/etc. in non-IMAP mode at other times.
The solution(?):
My first inclination is to provide the users some way of configuring
where IMAP will look for mail for their account. For instance, the
default may be /var/spool/mail/<username>. Perhaps through a ~/.imaprc
they could change that to ~Mail/ or something else that suits
them. This solves the problem of being able to use mutt/pine/etc. in
non-IMAP mode and also allows people to keep their procmail
recipes, however, I don't yet know if Cyrus imapd will play nicely
with that setup. My chief concerns are:
1) How do I make Cyrus use something other than its /var/spool/imap
database and how do I make it configurable on a per-user basis?
2) Will Cyrus be able to handle manipulating mail in mbox format? My
understanding is that Cyrus stores mail in a much different format in
order to reduce load on the machine acting as the imap server.
I know that WU will use /var/spool/mail and do mbox format. That puts
me a little closer to my goal, but I *really* don't want to use WU
given its history of security problems.
Any idea how I can solve the problem with Cyrus?
--
---
Nathan Valentine - [EMAIL PROTECTED]
University of Kentucky Lab for Advanced Networking
Jabber: NRVesKY AIM: NRVesKY ICQ: 39023424
PGP signature
