I'm convinced :) I'll probably add it with Ken while we're at CMU in a couple of weeks when we can test it together. This is precisely the kind of thing we love to see! Thanks. Bron. On Tue, Oct 7, 2014, at 10:23 PM, Michael Menge wrote: > Hi, > > as we have had an other crash of mupdate master last week, we used the > patch on our production system. > > After the patch was added the load on mupdate master was dropping form > about 10 to about 1. > > After one week of using it we have not found any problems. > As I have not received any other feedback, I added it to the > bugtracker. > > https://bugzilla.cyrusimap.org/show_bug.cgi?id=3866 > > Pleas consider adding it to 2.5 and 2.4.next > > Regards > > Michael > > > Quoting Michael Menge <michael.menge@xxxxxxxxxxxxxxxxxxxx>: > > > Hi, > > > > > > Quoting Michael Menge <michael.menge@xxxxxxxxxxxxxxxxxxxx>: > > > >> Quoting Michael Menge <michael.menge@xxxxxxxxxxxxxxxxxxxx>: > >> > >>> By thew way, the reason I was so surprised in the first place was, that > >>> I have been fooled by the documentation: > >>> Quoting https://cyrusimap.org/docs/cyrus-imapd/2.4.17/install-murder.php > >>> > >>>> Configuring the frontends > >>>> [...] > >>>> However, because the frontends only talk to the mupdate master > >>>> via a slave running on the local machine, you will also need > >>>> to set up a slave on the same machine, in the SERVICES section > >>>> of cyrus.conf, like so > >> > >> And an other misleading DOC ! > >> Quoting > >> http://www.cyrusimap.org/mediawiki/index.php/Cyrus_Murder_Mail_Delivery > >>> UMich patch > >>> > >>> Patch Patches are against 2.2 but are being moved to 2.3 > >>> Lmtpproxyd will now use the local mailboxes.db > >> > > > > Quoting Wesley Craig <wescraig@xxxxxxxxx>: > > > >> On 29 Sep 2014, at 10:08, Michael Menge > >> <michael.menge@xxxxxxxxxxxxxxxxxxxx> wrote: > >>> thanks for your mail. By any chance do you still have the patch? > >> > >> In fact, I don't. Dusting off my notes, I recall now that instead > >> of patching this (bogus) code, we instead decided to configure the > >> frontends as "unified", while leaving the backends "standard". The > >> only downside of this approach was that a naive admin could > >> potentially create a user's mailbox on a frontend. > >> > >> Sorry I said that we ported that code forward: in fact we simply > >> got the effect of consulting mailboxes.db without porting forward. > >> > >> :wes > > > > I have patched my lmtpd to use the local mailbox.db in all cases, > > unified Murder, and standalone cyrus already did this. > > I tested it with a few testmails on my test system, > > but as i don't have a unified setup or a standalone test system > > at the moment i didn't test these setups. > > > > I would appreciate a review. > > > > > > Regards, > > > > Michael Menge > > > > > > -------------------------------------------------------------------------------- > > M.Menge Tel.: (49) 7071/29-70316 > > Universität Tübingen Fax.: (49) 7071/29-5912 > > Zentrum für Datenverarbeitung mail: > > michael.menge@xxxxxxxxxxxxxxxxxxxx > > Wächterstraße 76 > > 72074 Tübingen > > > > > -------------------------------------------------------------------------------- > M.Menge Tel.: (49) 7071/29-70316 > Universität Tübingen Fax.: (49) 7071/29-5912 > Zentrum für Datenverarbeitung mail: > michael.menge@xxxxxxxxxxxxxxxxxxxx > Wächterstraße 76 > 72074 Tübingen > ---- > Cyrus Home Page: http://www.cyrusimap.org/ > List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ > To Unsubscribe: > https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus > Email had 1 attachment: > + smime.p7s > 7k (application/pkcs7-signature) -- Bron Gondwana brong@xxxxxxxxxxx ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
