On 02/25/14 20:42 +0100, Marcus Schopen wrote:
>Hi,
>
>as soon as a user is created in sasldb2 a imap login is possible even if
>a cyrus mailbox isn't available. Can I avoid this? I use sasldb
>authentication for another service (sendmail smtp_auth) on the same
>server and don't want to mix up smtp
Sorry, on holiday. Phone only.
Looks like you might have corruption at one end, try reconstructing both ends.
Also make sure you're not changing things on the replicas.
On Tue, Feb 25, 2014, at 10:39 PM, Willy Offermans wrote:
> Dear Friends,
>
>
> On Mon, Feb 24, 2014 at 01:17:30PM +0100, Wil
I'm running a very small murder setup using Simon Matter's RPM packages on
CentOS 6.x. Frequently, the tis_sessions.db file on the update master
becomes corrupt such that one or more of the nodes can no longer establish
a connection. Of course, this results in folders not reserved properly on
the
Hi,
as soon as a user is created in sasldb2 a imap login is possible even if
a cyrus mailbox isn't available. Can I avoid this? I use sasldb
authentication for another service (sendmail smtp_auth) on the same
server and don't want to mix up smtp and imap users. Separated sasldb
databases would be
I'm running a very small murder setup using Simon Matter's RPM packages on
CentOS 6.x. Frequently, the tis_sessions.db file on the update master
becomes corrupt such that one or more of the nodes can no longer establish
a connection. Of course, this results in folders not reserved properly on
the m
Dear Friends,
On Mon, Feb 24, 2014 at 01:17:30PM +0100, Willy Offermans wrote:
> Dear cyrus Friends,
>
> I'm testing the replication option of cyrus. I have rebooted the ``master''
> several times yesterday, but for reasons __not__ related to cyrus. Today I
> figured out that replication was not
