Cyrus 2.2.12 Murder: Frontend/Backend on same Host?

AdNovum Mailinglist User listuser at adnovum.ch
Thu Nov 16 05:42:05 EST 2006


Hello Peter,

> I'm not sure about the version number, but even without "unified"
> murder but a friend over here had frontend, backend and even mupdate
> on the same box, using several interfaces (with seperate ip adresses)
> and lines like this in cyrus conf -- using e.g. Fimap (for frontend
> services, aka proxyd) and Bimap (for backend services) with seperate
> config-files, listening on seperate interfaces. 10.0.0.100 is an
> example for the public backend interface, 10.0.0.200 for the frontend.
> note that none of this is my idea, I'm not even sure this works
> without local patches.
> 
> START {
>   Frecover cmd="/usr/local/cyrus/bin/ctl_cyrusdb -C/etc/imapd-frontend.conf -r"
>   mupdatepush cmd="ctl_mboxlist -C/etc/imapd-backend.conf -m" 
>   Brecover cmd="/usr/local/cyrus/bin/ctl_cyrusdb -C/etc/imapd-backend.conf -r"
> }
> 
> SERVICES {
>   # backend
>   Bimap   cmd="/usr/local/cyrus/bin/imapd -C /etc/imapd-backend.conf" listen="10.0.0.100:imap"  prefork=2
>   Bpop3   cmd="/usr/local/cyrus/bin/pop3d -C /etc/imapd-backend.conf" listen="10.0.0.100:pop3"  prefork=2
>   Blmtp   cmd="/usr/local/cyrus/bin/lmtpd -C /etc/imapd-backend.conf" listen="10.0.0.100:lmtp"  prefork=2
>   Bsieve  cmd="/usr/local/cyrus/bin/timsieved -C /etc/imapd-backend.conf"  listen="10.0.0.100:sieve" prefork=0
>   # frontend
>   mupdate cmd="/usr/local/cyrus/bin/mupdate -m -C /etc/imapd-frontend.conf" listen="10.0.0.200:3905" prefork=1
>   Fimap   cmd="/usr/local/cyrus/bin/proxyd -C /etc/imapd-frontend.conf" listen="10.0.0.200:imap" prefork=2
>   Fimaps  cmd="/usr/local/cyrus/bin/proxyd -s -C /etc/imapd-frontend.conf" listen="10.0.0.200:imaps" prefork=1
>   Fpop3   cmd="/usr/local/cyrus/bin/pop3proxyd -C /etc/imapd-frontend.conf" listen="10.0.0.200:pop3" prefork=2
>   Fpop3s  cmd="/usr/local/cyrus/bin/pop3proxyd -s -C /etc/imapd-frontend.conf" listen="10.0.0.200:pop3s" prefork=0
>   Flmtp   cmd="/usr/local/cyrus/bin/lmtpproxyd -C /etc/imapd-frontend.conf" listen="10.0.0.200:lmtp" prefork=2
>   Fsieve  cmd="timsieved -C /etc/imapd-frontend.conf" listen="10.0.0.200:sieve" prefork=0
> }
> 
> EVENTS {
>   delprune     cmd="/usr/local/cyrus/bin/ctl_deliver -C /etc/imapd-backend.conf -E 3" at=0400
>   checkpoint   cmd="/usr/local/cyrus/bin/ctl_cyrusdb -c -C /etc/imapd-backend.conf" period=5
> }
> 
>> The intention for this construct is: We have two locations in
>> different countries, connected with VPN. I would like to have one
>> Cyrus frontend/backend on each location and move the user mailboxes
>> to that locations where they are working. Some users are moving from
>> one location to another so I would like to give a transparent view
>> to the shared folders.
> 
> just take my above example as a hint, that this could be possible,
> wheather it is a good idea or a good solution to the actual problem
> you're trying to solve I don't know.
> note that we did this with a 2.2.12 cyrus. also note that I had
> trouble including even a 2.1.18 (the last of the 2.1 series; from
> debian stable) into a test setup with three other 2.2.13 cyri --
> replacing it with 2.2.13 (from source) immediately fixed the problem,
> so I didn't care to look into this more closely.

Thanks. I expected it to work something like that. I made a typo in the
version number, we're using Cyrus 2.2.12.

Regards,
Bernd




More information about the Info-cyrus mailing list