FYI - bug updated and fix pushed. It will be in 2.4.13. Shiny!
Bron.
On Thu, Dec 29, 2011 at 11:43:14AM +0100, Bron Gondwana wrote:
> I will have a look through the code and update everything to be protected by
> the right configuration checks!
>
> Bron.
>
> On Wed, Dec 28, 2011, at 10:35 PM,
I will have a look through the code and update everything to be protected by
the right configuration checks!
Bron.
On Wed, Dec 28, 2011, at 10:35 PM, Wesley Craig wrote:
> The short answer is that "kick_mupdate()" makes no sense on a backend in the
> configuration you're talking about. The long
The short answer is that "kick_mupdate()" makes no sense on a backend in the
configuration you're talking about. The long answer is that calls to
kick_mupdate() are liberally sprinkled through the code, primarily involving
calls that manipulate mailboxes or acls (xfer does both, naturally). So
