On 06/05/2015 07:42 PM, Andrew Morgan wrote:
> On Fri, 5 Jun 2015, Major Csaba wrote:
>
>> There is one more small question: why the proxied LMTP needs to have
>> "admins" permission on the backend? I thought the proxyservers
>> setting is for this, but LMTP doesn't work without adding my proxy
On 06/05/15 16:44 +0200, Major Csaba wrote:
>Hi,
>
>Thanks for the quick answer.
>I managed to get further as I realized I missed a small piece from the
>documentation. My fronted server and master update server is on the
>same machine and I didn't configure the "mupdate_*" parameter. But as
>I
On Fri, 5 Jun 2015, Major Csaba wrote:
> There is one more small question: why the proxied LMTP needs to have "admins"
> permission on the backend? I thought the proxyservers setting is for this,
> but LMTP doesn't work without adding my proxy user in the "admins"...
Play around with lmtp_admin
Hi,
Thanks for the quick answer.
I managed to get further as I realized I missed a small piece from the
documentation. My fronted server and master update server is on the same
machine and I didn't configure the "mupdate_*" parameter. But as I can
see, the proxy still has to speak to mupdate w
On 06/05/15 14:38 +0200, Major Csaba wrote:
>Hi,
>
>I'm rying to build a cyrus server with murder frontend/backend. The
>topology is quiet simple at the moment: there is one frontend +
>mupdate master, and there is one backend server.
>(Cyrus version: 2.4.17)
>
>Almost everything is working fine
Hi,
I'm rying to build a cyrus server with murder frontend/backend. The
topology is quiet simple at the moment: there is one frontend + mupdate
master, and there is one backend server.
(Cyrus version: 2.4.17)
Almost everything is working fine:
* The backend populates the folder changes to
