On 23.08.2012, at 22:01, Timo Sirainen wrote:
On 19.8.2012, at 12.51, Michael Grimm wrote:
1) I see a lot of error messages whenever replicator is in action like
(although everything is being synced correctly):
| mail.err mail dovecot: dsync-local(test): Error: remote:
On 19.8.2012, at 12.51, Michael Grimm wrote:
1) I see a lot of error messages whenever replicator is in action like
(although everything is being synced correctly):
| mail.err mail dovecot: dsync-local(test): Error: remote:
dsync-remote(test): Info: save: box=INBOX, uid=27,
On 08.03.2012, at 12:35, Timo Sirainen wrote:
On Thu, 2012-03-08 at 11:26 +0100, Michael Grimm wrote:
Now some observations regarding replicator:
1) I see a lot of error messages whenever replicator is in action like
(although everything is being synced correctly):
| mail.err mail
Hi --
On 04.03.2012 11:44, Timo Sirainen wrote:
In dovecot-2.1 hg you can now test dsync-based replication.
Everything isn't finished yet, but it appears to work and I've
enabled
it for my @dovecot.fi mails.
I did give it a try starting some days ago, and I can confirm that you
are right,
On Thu, 2012-03-08 at 11:26 +0100, Michael Grimm wrote:
Let me start with replicator's configuration ...
Below is a configuration for virtual user setup.
[...]
service doveadm {
# if you're using a single virtual user, set this to
# start ssh as vmail (not root)
user = vmail
Hi --
On 08.03.2012 12:35, Timo Sirainen wrote:
On Thu, 2012-03-08 at 11:26 +0100, Michael Grimm wrote:
You can do for example:
service config {
unix_listener config {
user = vmail
}
}
I will try that later.
It seems to me, that whenever a larger number of mails arrive on
both
On Sun, Mar 04, 2012 at 01:38:14PM +0200, Timo Sirainen wrote:
Great news. I would love to test it, if I will be able to run this on a
test
account, only. All other users should become synced the old way for the
time
being.
Would that be possible with the current
On 5.3.2012, at 9.25, Attila Nagy wrote:
On 03/04/12 11:44, Timo Sirainen wrote:
In dovecot-2.1 hg you can now test dsync-based replication. Everything isn't
finished yet, but it appears to work and I've enabled it for my @dovecot.fi
mails. Some issues:
Do you plan to make it more
On 5.3.2012, at 10.35, Jan-Frode Myklebust wrote:
1) Replicator syncs all users at startup. If you can change your userdb
iteration to return only one test user for replicator that avoids it. (You
may be able to do protocol replicator { userdb {..} } and protocol
!replicator { .. })
On 03/05/12 11:08, Timo Sirainen wrote:
On 5.3.2012, at 9.25, Attila Nagy wrote:
On 03/04/12 11:44, Timo Sirainen wrote:
In dovecot-2.1 hg you can now test dsync-based replication. Everything isn't
finished yet, but it appears to work and I've enabled it for my @dovecot.fi
mails. Some
On Mon, Mar 05, 2012 at 12:45:26PM +0200, Timo Sirainen wrote:
So, ideally (for us), dovecot should keep a log over which accounts are
active (has received or checked mail), and only sync users that has been
active for the last $timeperiode on startup.
Well, all of this could be done
On 5.3.2012, at 14.15, Attila Nagy wrote:
On 03/04/12 11:44, Timo Sirainen wrote:
In dovecot-2.1 hg you can now test dsync-based replication. Everything
isn't finished yet, but it appears to work and I've enabled it for my
@dovecot.fi mails. Some issues:
Do you plan to make it more
On 03/05/12 13:48, Timo Sirainen wrote:
On 5.3.2012, at 14.15, Attila Nagy wrote:
On 03/04/12 11:44, Timo Sirainen wrote:
In dovecot-2.1 hg you can now test dsync-based replication. Everything isn't
finished yet, but it appears to work and I've enabled it for my @dovecot.fi
mails. Some
On 5.3.2012, at 15.11, Attila Nagy wrote:
dsync doesn't currently take enough advantage of modseqs and send only the
changed data.
Hm. What is your estimate about the performance capability of the current
best replication scheme available in Dovecot?
I know it's hard to tell, because there
On 5.3.2012, at 14.35, Jan-Frode Myklebust wrote:
On Mon, Mar 05, 2012 at 12:45:26PM +0200, Timo Sirainen wrote:
So, ideally (for us), dovecot should keep a log over which accounts are
active (has received or checked mail), and only sync users that has been
active for the last $timeperiode
In dovecot-2.1 hg you can now test dsync-based replication. Everything
isn't finished yet, but it appears to work and I've enabled it for my
@dovecot.fi mails. Some issues:
- public namespace isn't replicated at all
- shared namespace is replicated, but not private mail flags
- I've only
Hi --
On 04.03.2012, at 11:44, Timo Sirainen wrote:
In dovecot-2.1 hg you can now test dsync-based replication.
Great news. I would love to test it, if I will be able to run this on a test
account, only. All other users should become synced the old way for the time
being.
Would that be
On 4.3.2012, at 13.34, Michael Grimm wrote:
On 04.03.2012, at 11:44, Timo Sirainen wrote:
In dovecot-2.1 hg you can now test dsync-based replication.
Great news. I would love to test it, if I will be able to run this on a test
account, only. All other users should become synced the old
Hi --
On 04.03.2012, at 12:38, Timo Sirainen wrote:
On 4.3.2012, at 13.34, Michael Grimm wrote:
On 04.03.2012, at 11:44, Timo Sirainen wrote:
In dovecot-2.1 hg you can now test dsync-based replication.
Great news. I would love to test it, if I will be able to run this on a test
account,
On 4.3.2012, at 23.39, Michael Grimm wrote:
Anyway, replicator simply runs doveadm, so there's not much that can go
wrong. So
you could even ignore 1) and just let it sync everyone at startup.
Does that mean that the new functionality (queue) does only run dsync
replication
the usual
Hi,
On 03/04/12 11:44, Timo Sirainen wrote:
In dovecot-2.1 hg you can now test dsync-based replication. Everything
isn't finished yet, but it appears to work and I've enabled it for my
@dovecot.fi mails. Some issues:
- public namespace isn't replicated at all
- shared namespace is
21 matches
Mail list logo
