does aggregator honors defaultserver conf?

Andre Felipe Machado andremachado at techforce.com.br
Wed Aug 25 14:07:41 EDT 2010


Hello,
i am trying to setup a very simple cyrus aggregator / murder (2 backends, 1
mupdate master, 1 frontend with its mupdate slave) to work with a php webmail
app using experimental "hmh" cvs branch 2.3.16 debian packages [0] backported to
Lenny.
The 2.3.8 experimental package [1] is not recommended anymore. 
The "hmh" 2.3.16 branch is, as of today[2].

By reading imapd.conf man page, realized that in order to not "have to" specify
a backend (and partition?) to create mailboxes, will need "defaultserver" and
"serverlist" paremeters configured in imapd.conf.
This could achieve compatibility with php imap functions.
I configured these parameters at backends, mupdate master and even frontend, but
cyrus aggregator still creates mailboxes at the frontend (that could not be
moved as frontend is not a listed backend) when not given backendserver parameters.

Were they configured correctly? Did not find any related config errors at the
mailservers logs yet.
What did I miss?
Please, point to some documentation/list archive/wiki  url that could guide at
this issue.

Regards.
Andre Felipe Machado
http://www.techforce.com.br


[0] https://mail.incase.de/viewcvs/
[1] http://packages.debian.org/source/experimental/cyrus-imapd-2.3
[2]
http://lists.alioth.debian.org/pipermail/pkg-cyrus-imapd-debian-devel/2010-August/003417.html



#AFM 24ago2010 para evitar travar frontend ao criar mbox sem especificar onde
# Whitespace separated list of backend server names.  Used for find-
# ing server with the most available free space for proxying CREATE.
serverlist: debian192_168_56_107 debian192_168_56_108

#AFM 24ago2010 para evitar criar mbox no frontend
# The backend server name used by default for new mailboxes.  If not
# specified, the server with the most free space will  be  used  for
# new mailboxes.
defaultserver: debian192_168_56_107






More information about the Info-cyrus mailing list