On Thu, Jun 29, 2006 at 09:20:12AM +0200, Arno van Amersfoort wrote: > 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.....
Exactly - and it need only contain the symlinks, nothing else. Alternatively, the mail server can have its own password file, where the home directories point to /mail/user instead of /home/user. But then you might as well go with a different authentication database, e.g. userdb. Or, if you don't mind the potential confusion, you could have a completely separate /home hierarchy on the mailserver, and deliver to /home/user/Maildir as normal. Then you could mount mailserver:/home on /mail on the ssh server to give direct access to it. Regards, Brian. 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
