this fix, detailed below, has indeed solved our problem with folder
creation on our new 2.4.17 frontends.
many thanks
On Tue, 10 Jun 2014, Andrew Morgan wrote:
> On Tue, 10 Jun 2014, gavin.g...@ed.ac.uk wrote:
>
>> Hi Wes,
>>
>> It looks like the whole mupdate thing is working perfectly well.
On Tue, 10 Jun 2014, gavin.g...@ed.ac.uk wrote:
> Hi Wes,
>
> It looks like the whole mupdate thing is working perfectly well.
> If I create a folder while connected to my 2.4.17 frontend then the logs show
> the backend issuing the cmd_set and then a bunch of cmd_find going out
> including to t
Hi Wes,
It looks like the whole mupdate thing is working perfectly well.
If I create a folder while connected to my 2.4.17 frontend then the logs
show the backend issuing the cmd_set and then a bunch of cmd_find going
out including to the frontend in question. Furthermore the new folder
really
I've switched to debug logging now on our mupdate master,
thanks
On Mon, 9 Jun 2014, Wesley Craig wrote:
> On 09 Jun 2014, at 07:14, gavin.g...@ed.ac.uk wrote:
>> Actually we get very little logged on our mupdate master, just logins,
>> checkpointing notices etc, nothing about the work done t
sorry I should've been more explicit, we also have the same thing in our
backend's imapd.conf
On Tue, 10 Jun 2014, Michael Menge wrote:
Hi,
Quoting gavin.g...@ed.ac.uk:
yes we have
allowallsubscribe: yes
in our frontend imapd.conf
the man page mentions backend servers
thanks
On Tue,
Hi,
Quoting gavin.g...@ed.ac.uk:
yes we have
allowallsubscribe: yes
in our frontend imapd.conf
the man page mentions backend servers
thanks
On Tue, 10 Jun 2014, Michael Menge wrote:
Hi,
did you use allowallsubscribe in your imapd.conf?
copied from imapd.conf manpage
allowallsubscri
yes we have
allowallsubscribe: yes
in our frontend imapd.conf
thanks
On Tue, 10 Jun 2014, Michael Menge wrote:
Hi,
did you use allowallsubscribe in your imapd.conf?
copied from imapd.conf manpage
allowallsubscribe: 0
Allow subscription to nonexistent mailboxes. This option is typic
