imapd.conf settings, required and optional, for frontends vs. backends vs. mupdate masters?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Folks,
Finally getting around to bringing up my first production Murder environment and I have the feeling that I have more than I need in my frontend configs.  Here is what I currently have configured:

Frontend imapd.conf:
admins: cyrus cyradmin
configdirectory: /var/lib/imap
partition-default: /var/spool/imap
sievedir: /var/lib/imap/sieve
sendmail: /usr/sbin/sendmail
mboxname_lockpath: /var/run/cyrus/lock
proc_path: /var/run/cyrus/proc
duplicate_db_path: /var/run/cyrus/deliver.db
statuscache_db_path: /var/run/cyrus/statuscache.db
tlscache_db_path: /var/run/cyrus/tls_sessions.db
allowplaintext: yes
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN
sasl_minimum_layer: 0
sasl_auto_transition: no
servername: mail.example.com
lmtp_downcase_rcpt: true
username_tolower: true
lmtpsocket: /var/run/cyrus/socket/lmtp
idlesocket: /var/run/cyrus/socket/idle
notifysocket: /var/run/cyrus/socket/notify
syslog_prefix: cyrus
proxyservers: cyradmin
allowusermoves: true
idlemethod: idled
allowallsubscribe: true
altnamespace: true
defaultacl: anyone lrsip
createonpost: true
proxyd_disable_mailbox_referrals: true
mupdate_server: postman.example.com
mupdate_username: postman
mupdate_authname: postman
mupdate_password: ********
proxy_authname: murder
proxy_password: ********
force_sasl_client_mech: PLAIN
postman_mechs: PLAIN
mailbox_mechs: PLAIN
Backend imapd.conf:
admins: cyrus cyradmin
configdirectory: /var/lib/imap
partition-default: /var/spool/imap
sievedir: /var/lib/imap/sieve
sendmail: /usr/sbin/sendmail
mboxname_lockpath: /var/run/cyrus/lock
proc_path: /var/run/cyrus/proc
duplicate_db_path: /var/run/cyrus/deliver.db
statuscache_db_path: /var/run/cyrus/statuscache.db
tlscache_db_path: /var/run/cyrus/tls_sessions.db
allowplaintext: yes
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN
sasl_minimum_layer: 0
sasl_auto_transition: no
servername: mailbox.example.com
singleinstancestore: true
duplicatesuppression: true
expunge_mode: delayed
lmtp_downcase_rcpt: true
username_tolower: true
lmtpsocket: /var/run/cyrus/socket/lmtp
idlesocket: /var/run/cyrus/socket/idle
notifysocket: /var/run/cyrus/socket/notify
syslog_prefix: cyrus
proxyservers: cyradmin murder
allowusermoves: true
idlemethod: idled
allowallsubscribe: true
altnamespace: true
defaultacl: anyone lrsip
mupdate_server: postman.example.com
mupdate_username: postman
mupdate_authname: postman
mupdate_password: *********
force_sasl_client_mech: PLAIN
postman_mechs: PLAIN
Mupdate master imapd.conf:
admins: cyrus cyradmin postman
configdirectory: /var/lib/cyrus
defaultpartition: default
partition-default: /tmp
allowplaintext: yes
sasl_pwcheck_method: saslauthd
sasl_mech_list: PLAIN
sasl_minimum_layer: 0
sasl_auto_transition: no
servername: postman.example.com
allowallsubscribe: true
altnamespace: true
defaultacl: anyone lrsip
umask: 077
syslog_prefix: cyrus
I think it would be most useful if we had some sort of guide as to which directives are required versus optional or useless for each given mode of operation.  I do appreciate that some of the settings listed in imapd.conf.5 now list " - Cyrus Murder" after them (such as hostname_password) indicating they only apply in a murder, but knowing which are necessary or not for each mode would sure be handy.

If someone can provide quick notes, I'd be glad to make a Wiki entry.

Cheers,
    -nic
-- 
Nic Bernstein                             nic@xxxxxxxxxxx
Onlight, Inc.                             www.onlight.com
219 N. Milwaukee St., Suite 2a            v. 414.272.4477
Milwaukee, Wisconsin  53202
----
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/

[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux