Starting NFS will consume more cpu on system-A, but you will free a lot more CPU cycles by serving half of the IMAP clients directly on system-B. Another option is to use an imap proxy on system-B.
On Mon, May 16, 2016 at 1:18 PM, Divakar BM <bmdiva...@gmail.com> wrote: > Thanks for suggestion. Starting NFS would consume more cpu on Server-A as > I need to start mountd, nfsd (couple more) and also sync from nfs client > would further degrade system performance. Is there way of telling dovecot > on system-B that *Maildir* is located on server-A and map it to home dir > attribute... > > > On Mon, May 16, 2016 at 2:44 PM Adrian M <adrian.mi...@gmail.com> wrote: > >> mount the /mail/vmail/**/ on server-B via nfs. >> >> On Mon, May 16, 2016 at 11:54 AM, Divakar BM <bmdiva...@gmail.com> wrote: >> >>> Hi, >>> I've my mail solution configured on Server-A with webmail, Dovecot and >>> Postfix. I'm trying to deploy only Dovecot and postfix on Server-B to >>> reduce IMAP/POP3/SMTP load on server-A. Please note server-B does not >>> mailboxes. It should be mapped to mailboxes on server-A. While the LDAP >>> query from Server-B to Server-A is going successfully, the imap service >>> on >>> Server-B is throwing the below error. >>> >>> imap(u...@example.com): Debug: Home dir not found: /mail/vmail/**/ >>> >>> I guess imap is looking for *home dir* in server-B. How do I tel the imap >> >> >>> that home dir is on server-A and not server-B. >>> >>> Please let me know if there exists a configuration parameter for the >>> above.. >>> >>> Thanks >>> Divakar >>> >>
