Thanks for the reply, if you refer to Dovecots wiki it states that there are some concerns with NFS caching when multiple devices are trying to access the same mailbox simultaneously. This is the reason for the question about dovecot director, from following the dovecot wiki I have most of the configuration done but seem unable to find where doveadm is located. Any further explanation of the issues with NFS caching and the location of doveadm would be appreciated.

I am not saying that it is not available, I am just asking where it is amongst the multiple .conf files for dovecot. I am either overlooking it or looking in the wrong spot making it difficult to locate.

Ok still trying to figure out this dovecot director the part I am stuck is where I suppose to enter or change the settings for doveadm. The following is from the wiki describing what needs to be done for doveadm:

Doveadm server
Use these settings for both director and backends:
service doveadm {
  inet_listener {
    # any port you want to use for this:
    port = 24245
  }
}

local 10.10.10.0/24 {
  # password to use for client authentication
  doveadm_password = secret
  # allow client to only use specified list of commands (default is all):
  #doveadm_allowed_commands =
}
The director also needs the following configuration:
# same port as doveadm's inet_listener
doveadm_proxy_port = 24245

protocol doveadm {
  auth_socket_path = director-userdb
}
Now you can run doveadm commands on the director, and it'll run them automatically on the correct backend server.