The problem is that I currently already use the symlink-way. But the
drawback of this solution is that whenever the (NFS) fileserver is
down, /home doesn't exist and one is unable to use Courier IMAP
(because the /home/$USER/Maildir->/mail/$USER/Maildir symlink does
NOT exist). :-S
I guess, the best solution (in the future) would be to simply give both
our mail & file server their own physical /home-directory.....
Brian Candler wrote:
On Wed, Jun 21, 2006 at 04:15:47PM +0200, Arno van Amersfoort wrote:
This is what I have:
- a fileserver which contains all user home-directories, which are
exported to our mail/ssh server via NFS;
- a mailserver running Courier-IMAP which has the home-directories of
the fileserver mounted under /home.
What I would like to do is have the Maildir's of all users locally
stored on the mailserver in ie. /mail. This is to increase Courier's
performance but also to allow the Mail-server to work even if the
fileserver is down.The latter is the most important goal because now
whenever the fileserver is down users are also unable to ie. read mail
eventhough the mailserver is still working.
I guess, it's currently not possible with Courier IMAP(?) but I'm hoping
that the developers may want to have a look at this and see whether they
can implement this.
It's certainly possible.
Option 1: stick the mail under /mail as you suggest. Make symlinks from
/home/user1/Maildir to /mail/u/s/user1/Maildir
Now, if you want users to have direct filesystem access to their maildir,
then you NFS-export /mail and mount it on the ssh server. If you don't, then
don't. In the latter case, the mail server doesn't need to mount the real
home directories; you can make a fake /home hierarchy which contains just
the Maildir symlinks and nothing else.
Option 2: put the mail user data in a separate database - e.g. userdb,
mysql, postgresql, or LDAP. In that case, you can point each user's homedir
to any location you like, e.g. /mail/user1, which is different from the
system homedir. Or you can set home=/home/user1 but mail=/mail/user1/Maildir
If your current user data is in the system password file, there's a utility
to convert it into userdb format automatically.
I'd lean towards option 2 if you want to build a mail 'appliance' where
users have only access via mail protocols (e.g. POP3, IMAP) to access their
mail. I'd lean towards option 1 if your users are tech-savvy and want full
filesystem access to their mail, .forward files and so on.
Regards,
Brian.
--
Ing. A.C.J. van Amersfoort (Arno)
Department Of Electronics (ELD, k1007)
Huygens Laboratory
Leiden University
P.O. Box 9504
Niels Bohrweg 2
2333 CA Leiden
The Netherlands
----------------------------------------------------------------
Phone : +31-(0)71-527.1894 Fax: +31-(0)71-527.5819
E-mail: [EMAIL PROTECTED]
----------------------------------------------------------------
Arno's (Linux firewall) homepage: http://rocky.eld.leidenuniv.nl
|
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
