On 08 Sep 2015, at 11:20, Sergey Schwartz
wrote:
>
> I use mdbox and probably have similar issue, but in my case only shared
> mailboxes were affected.
Yes, shared mailboxes don't work nicely with replication. Replication is
locking only the original user, so for shared mailboxes multiple dsy
On 08 Sep 2015, at 01:16, Gedalya wrote:
>
> On 02/17/2013 03:21 AM, Timo Sirainen wrote:
>> Although there's still some mail
>> duplication problem with maildir that doesn't log any errors about it.
>> I'm not sure why that happens.
>
> While you're around, Timo :-)
>
> I've had such an issue
On 02/17/2013 03:21 AM, Timo Sirainen wrote:
Although there's still some mail
duplication problem with maildir that doesn't log any errors about it.
I'm not sure why that happens.
While you're around, Timo :-)
I've had such an issue recently with 2.2.18, using Maildir, where emails
were being
On 16.4.2014, at 10.26, Nikolaos Milas wrote:
> I decided I should create a new one dedicated on it because that thread
> includes other issues as well, and the issue in question still remains
> unresolved although it is an important one (and I am hoping to attract Timo's
> attention on it, to
Hello,
Although this issue has been raised in another thread:
https://www.mail-archive.com/dovecot@dovecot.org/msg57281.html
I decided I should create a new one dedicated on it because that thread
includes other issues as well, and the issue in question still remains
unresolved although it
On 04/07/2014 12:22 PM, Simon Fraser wrote:
> Thank you. Is it still only the changes that are synced each way, or
> the entire mailbox? I'm trying to gauge the performance hit for enabling
> this on larger mailboxes. (I could, of course, run some tests, but
> someone may already have done that)
C
On Fri, 2014-04-04 at 15:41 +0300, Teemu Huovila wrote:
> Hi
>
> On 04/04/2014 03:38 PM, Simon Fraser wrote:
> > It does help, thank you. Do you also know what the '-f' option does?
> According to the dsync-man page it:
>
> Makes dsync run in "full sync" mode rather than "fast sync" mode. In fas
Hi
On 04/04/2014 03:38 PM, Simon Fraser wrote:
> It does help, thank you. Do you also know what the '-f' option does?
According to the dsync-man page it:
Makes dsync run in "full sync" mode rather than "fast sync" mode. In fast sync
mode dsync might skip syncing a mailbox, if both
locations had
On Fri, 2014-04-04 at 15:34 +0300, Teemu Huovila wrote:
> -d Use a default location for the replica. As far as I can tell this is
> obtained from userdb variable mail_replica.
> -N Sync all (visible?) namespaces (only makes sense when syncing with a
> remote host, with potentially different name
On 04/04/2014 12:42 PM, Nikolaos Milas wrote:
> Anyone please?
>
> How can we determine whether we need to configure
> "replication_dsync_parameters = -d -N -l 30 -U" as indicated on the wiki2 (or
> some variation thereof) or not?
I am definitely not Timo, but I will try a short answer based on
On 4/4/2014 1:17 μμ, Alan McGinlay wrote:
It does appear to be completely undocumented,
We would appreciate if Timo can kindly provide us with -at least- some
details!
I tried looking in the source code but just ended up going in circles
(i'm not familiar with it at all).
I faced the sa
On 2014-04-04 11:42, Nikolaos Milas wrote:
On 31/3/2014 12:03 μμ, Simon Fraser wrote:
On Fri, 2014-03-28 at 11:58 +0200, Nikolaos Milas wrote:
>Question 2a: What do options "-d -N -l 30 -U" signify in
>"replication_dsync_parameters = -d -N -l 30 -U"?
I'd also be interested to know the answer to
On 31/3/2014 12:03 μμ, Simon Fraser wrote:
On Fri, 2014-03-28 at 11:58 +0200, Nikolaos Milas wrote:
>Question 2a: What do options "-d -N -l 30 -U" signify in
>"replication_dsync_parameters = -d -N -l 30 -U"?
I'd also be interested to know the answer to this part. I found mention
of the '-f' o
On Fri, 2014-03-28 at 11:58 +0200, Nikolaos Milas wrote:
> Question 2a: What do options "-d -N -l 30 -U" signify in
> "replication_dsync_parameters = -d -N -l 30 -U"?
I'd also be interested to know the answer to this part. I found mention
of the '-f' option, and adding '-f' to that list appears
On 28/3/2014 10:40 μμ, Nikolaos Milas wrote:
When I started the server (vmail.example.com), mirroring started and
completed fine (after a few hours).
However, since then, I am not seeing a continued mirroring between the
two. I would expect changes to one of the masters to be propagated in
r
On 28/3/2014 11:58 πμ, Nikolaos Milas wrote:
When I started the server (vmail.example.com), mirroring started and
completed fine (after a few hours).
However, since then, I am not seeing a continued mirroring between the
two. I would expect changes to one of the masters to be propagated in
r
I am running two servers with Dovecot v2.2.12 on CentOS x86_64 (5.10 and
6.5 respectively) and users are virtual over ldap.
I have setup our main internal server (vmail.example.com) with dsync
replication according to the first part of
http://wiki2.dovecot.org/Replication. The second one
(vma
Hello,
I have working dovecot configuration with LDAP based authentication in
Active Directory.
I'd like to use dsync replication but dovecot can't do user lookups.
Is it possible to configure replication in such architecture?
doveadm user '*'
Returns only one local dovecot user.
dovecot --ver
On Mon, 8 Apr 2013 15:14:18 +0300
Timo Sirainen wrote:
> > ok, thanks for the clarification. Using two different tables does
> > the trick. I'll probably also have to disable the quota-warning
> > scripts on one of the servers. Currently, both servers run the
> > script when a account goes overqu
On 8.4.2013, at 14.56, Oli Schacher wrote:
> On Mon, 8 Apr 2013 13:15:54 +0300
> Timo Sirainen wrote:
>
>
>> There's no way to make quota work reliably that way. You need to use
>> different quota backends. Either two mysql databases (or tables), or
>> the other Dovecot could simply be using a
On Mon, 8 Apr 2013 13:15:54 +0300
Timo Sirainen wrote:
> There's no way to make quota work reliably that way. You need to use
> different quota backends. Either two mysql databases (or tables), or
> the other Dovecot could simply be using a dict file quota.
>
ok, thanks for the clarification.
On 8.4.2013, at 13.05, Oli Schacher wrote:
> I enabled quota + warnings in my replication test setup and now
> whenever a mail gets delivered the quota is counted twice (probably due
> to both servers using the same mysql quota backend)
Yes. Dovecot doesn't know that they are the same quota back
Hi
I enabled quota + warnings in my replication test setup and now
whenever a mail gets delivered the quota is counted twice (probably due
to both servers using the same mysql quota backend) and quota warnings
are fired too early. After a doveadm quota recalc -u the
quota is correct again. How do
On 25.3.2013, at 9.31, Oli Schacher wrote:
> current hg (33e78edac8f5)
>
> Mar 25 07:47:27 fumailsynctest2 dovecot: dsync-remote(): Panic: file
> dsync-ibc-stream.c: line 527 (dsync_ibc_stream_input_next): assertion failed:
> (ibc->value_input == NULL)
Fixed: http://hg.dovecot.org/dovecot-2.2
current hg (33e78edac8f5)
Mar 25 07:47:27 fumailsynctest2 dovecot: dsync-remote(): Panic: file
dsync-ibc-stream.c: line 527 (dsync_ibc_stream_input_next): assertion failed:
(ibc->value_input == NULL)
Mar 25 07:47:27 fumailsynctest2 dovecot: dsync-remote(): Error: Raw
backtrace: /usr/lib64/dovec
On 19.2.2013, at 13.48, Charles Marcus wrote:
> On 2013-02-18 10:39 PM, Timo Sirainen wrote:
>> On 18.2.2013, at 23.50, Michael Grimm wrote:
>>> With "doveconf -H dovecot%9d" I do end in tons of reported collisions like
>>> ...
>>> | doveconf: Error: Duplicate host hashes: dovecot1368344 and d
On 2013-02-18 10:39 PM, Timo Sirainen wrote:
On 18.2.2013, at 23.50, Michael Grimm wrote:
With "doveconf -H dovecot%9d" I do end in tons of reported collisions like ...
| doveconf: Error: Duplicate host hashes: dovecot1368344 and dovecot2055005
| doveconf: Error: Duplicate host hashes: dovecot
On 18.2.2013, at 23.50, Michael Grimm wrote:
>> % doveconf -H dovecot%2d
>> No duplicate host hashes in dovecot0 .. dovecot99
>
> With "doveconf -H dovecot%9d" I do end in tons of reported collisions like ...
> | doveconf: Error: Duplicate host hashes: dovecot1368344 and dovecot2055005
> | dovec
On 18.02.2013, at 07:07, Timo Sirainen wrote:
> On 17.2.2013, at 22.04, Michael Grimm wrote:
>> First of all: whenever you referred to "hostname" in this thread you have
>> been using it as a synonym for the local part [1] of a FQDN, right?
>
> I mean what gethostname() function returns, which
On 18.02.2013, at 07:49, Timo Sirainen wrote:
> On Sun, 2013-02-17 at 12:30 +0200, Timo Sirainen wrote:
>> (So yeah, ideally there should be checks for detecting hostname hash
>> collisions..)
>
> Added to v2.2 hg:
>
> % doveconf -H dovecot%2d
> No duplicate host hashes in dovecot0 .. dovecot9
On Sun, 2013-02-17 at 12:30 +0200, Timo Sirainen wrote:
> (So yeah, ideally there should be checks for detecting hostname hash
> collisions..)
Added to v2.2 hg:
% doveconf -H dovecot%d
No duplicate host hashes in dovecot0 .. dovecot9
% doveconf -H dovecot%2d
No duplicate host hashes in dovecot0
On 17.2.2013, at 22.04, Michael Grimm wrote:
> On 17.02.2013, at 11:08, Timo Sirainen wrote:
>
>> There may be some other features that require unique hostnames in
>> future. Anything where multiple Dovecot servers need to communicate
>> between each others.
>
> I'd like to come back to that i
On 17.02.2013, at 21:04, Michael Grimm wrote:
> BTW: I had had defined "hostname=" in dovecot.conf identically using
> completely different *but* identical FQDNs "mail.my-domain.tld" because of:
s/using completely different/using completely different to locally reported by
resolver/g
Regards
Am 17.02.2013 21:04, schrieb Michael Grimm:
> On 17.02.2013, at 11:08, Timo Sirainen wrote:
>
>> There may be some other features that require unique hostnames in
>> future. Anything where multiple Dovecot servers need to communicate
>> between each others.
>
> I'd like to come back to that is
On 17.02.2013, at 11:08, Timo Sirainen wrote:
> There may be some other features that require unique hostnames in
> future. Anything where multiple Dovecot servers need to communicate
> between each others.
I'd like to come back to that issue in order to understand your statement cited
below.
Am 17.02.2013 11:08, schrieb Timo Sirainen:
>> What parts of Dovecot would be involved? I'm curious because my production
>> mailservers use identical hostnames in their jails ever since running
>> Dovecot (starting 1.x).
>
> Mainly that maildir filenames are used as GUIDs. If two have the sam
On 17.2.2013, at 12.19, Michael Grimm wrote:
> On 17.02.2013, at 11:08, Timo Sirainen wrote:
>> On Sun, 2013-02-17 at 10:44 +0100, Michael Grimm wrote:
>
Although even if it does, other parts of Dovecot still use only the
hostname part to guarantee global uniqueness of things. So bet
On 17.02.2013, at 11:08, Timo Sirainen wrote:
> On Sun, 2013-02-17 at 10:44 +0100, Michael Grimm wrote:
>>> Although even if it does, other parts of Dovecot still use only the
>>> hostname part to guarantee global uniqueness of things. So better to have
>>> unique hostnames.
>>
>> What parts o
On Sun, 2013-02-17 at 10:44 +0100, Michael Grimm wrote:
> > Although even if it does, other parts of Dovecot still use only the
> > hostname part to guarantee global uniqueness of things. So better to have
> > unique hostnames.
>
> What parts of Dovecot would be involved? I'm curious because my
On 17.02.2013, at 06:23, Timo Sirainen wrote:
> On 17.2.2013, at 7.06, Timo Sirainen wrote:
>> On 17.2.2013, at 0.12, Michael Grimm wrote:
>>> Hmm. Both jails run at distinct servers. ssh replication uses different
>>> domains, though. But, both jails are named identically "test", and both
>>
On Sat, 2013-02-16 at 19:32 +0100, Oli Schacher wrote:
> There seems to be an issue left when expunging a large amount of
> messages from the Trash. I managed to get it twice so far by expunging
> ~3k messages. I'll try to create a reproducible test script for this
> scenario. I can currently only
On 17.2.2013, at 7.06, Timo Sirainen wrote:
> On 17.2.2013, at 0.12, Michael Grimm wrote:
>
>> Hmm. Both jails run at distinct servers. ssh replication uses different
>> domains, though. But, both jails are named identically "test", and both
>> jails resolve to identical hostnames "test" if u
On 17.2.2013, at 0.12, Michael Grimm wrote:
>>> I might add that both servers run inside FreeBSD jails (if that might make
>>> the difference to your test setup.
>>
>> Inside jail Dovecot sees two different hostnames (same as "hostname"
>> command)?
>
> Hmm. Both jails run at distinct servers.
On 16.02.2013, at 20:09, Timo Sirainen wrote:
> On 16.2.2013, at 20.26, Michael Grimm wrote:
>> Sorry to say, but I am still able to break replicator with v2.2.beta1
>> (35194cf0693e) under the conditions outlined below.
>
> I wonder if locking is working correctly in your setup. Your users hav
On 16.2.2013, at 20.26, Michael Grimm wrote:
> Timo Sirainen wrote:
>
>> I did a bunch of dsync fixes today in hg. With the new locking
>> behavior (and other fixes) you shouldn't be able to break it anymore.
>
> Sorry to say, but I am still able to break replicator with v2.2.beta1
> (35194cf0
On Sat, 16 Feb 2013 17:20:22 +0200
Timo Sirainen wrote:
> I did a bunch of dsync fixes today in hg. With the new locking
> behavior (and other fixes) you shouldn't be able to break it anymore.
>
Thanks for the fixes, Timo!
I can confirm I'm no longer able to break anything
with the tests I've
Timo Sirainen wrote:
> I did a bunch of dsync fixes today in hg. With the new locking
> behavior (and other fixes) you shouldn't be able to break it anymore.
Sorry to say, but I am still able to break replicator with v2.2.beta1
(35194cf0693e) under the conditions outlined below.
> On 2013-02-01
I did a bunch of dsync fixes today in hg. With the new locking behavior
(and other fixes) you shouldn't be able to break it anymore.
On Fri, 2013-02-01 at 21:53 +0100, Michael Grimm wrote:
> [Sorry Oli for my previous mail to your address, only. Resent here]
>
> Oli Schacher wrote:
>
> > There
[Sorry Oli for my previous mail to your address, only. Resent here]
Oli Schacher wrote:
> There still seems to be a problem when changes to both mailboxes at
> the same time are involved
I can confirm your observation, although triggered by a different test
scenario, similar to the one I did us
On Thu, 31 Jan 2013 22:17:28 +0200
Timo Sirainen wrote:
> On Thu, 2013-01-31 at 21:51 +0200, Timo Sirainen wrote:
> > On 31.1.2013, at 19.41, Oli Schacher wrote:
> >
> > >>> Jan 31 17:13:11 doco1 dovecot: dsync-local(user1): Error:
> > >>> Mailbox INBOX: Remote didn't send mail
> > >>> GUID=33d
On Thu, 2013-01-31 at 21:51 +0200, Timo Sirainen wrote:
> On 31.1.2013, at 19.41, Oli Schacher wrote:
>
> >>> Jan 31 17:13:11 doco1 dovecot: dsync-local(user1): Error: Mailbox
> >>> INBOX: Remote didn't send mail GUID=33dabe0f11980a51200c960042f4
> >>> (UID=104)
>
> I guess there's some bug
On 31.1.2013, at 19.41, Oli Schacher wrote:
>>> Jan 31 17:13:11 doco1 dovecot: dsync-local(user1): Error: Mailbox
>>> INBOX: Remote didn't send mail GUID=33dabe0f11980a51200c960042f4
>>> (UID=104)
I guess there's some bug that causes this to happen in some situations.. But
the reason for ma
On Thu, 31 Jan 2013 18:49:18 +0200
Timo Sirainen wrote:
>
> http://hg.dovecot.org/dovecot-2.2/rev/86629f621fe4 should fix this
> crash.
>
> The duplication happens because maildir somehow messes up itself. I
> guess I should look into it.
>
thanks, much appreciated!
> > test 3: mdbox again,
On 31.1.2013, at 18.37, Oli Schacher wrote:
> I updated to the latest hg, including the "remote cmd exit wait" update.
>
> It looks better now, but I still manage to break things :-)
>
> #
> test 2: append only 100 messages, but use maildir again instead of
> mdbox.
> still produces
On Thu, 31 Jan 2013 17:09:20 +0200
Timo Sirainen wrote:
>
> See if http://hg.dovecot.org/dovecot-2.2/rev/1d88f01ba2aa helps?
>
I updated to the latest hg, including the "remote cmd exit wait" update.
It looks better now, but I still manage to break things :-)
#
test 1: append 10
On 31.1.2013, at 15.36, Oli Schacher wrote:
> On Thu, 31 Jan 2013 15:24:06 +0200
> Timo Sirainen wrote:
>
>> On 31.1.2013, at 15.10, Oli Schacher wrote:
>>
>>> connect thunderbird to account user1 on server1
>>> result: login ok, mdbox visible on disk, 0 messages
>>>
>>> in thunderbird copy
On Thu, 31 Jan 2013 15:24:06 +0200
Timo Sirainen wrote:
> On 31.1.2013, at 15.10, Oli Schacher wrote:
>
> > connect thunderbird to account user1 on server1
> > result: login ok, mdbox visible on disk, 0 messages
> >
> > in thunderbird copy exactly 100 messages from a spambox to user1's
> > in
On 31.1.2013, at 15.10, Oli Schacher wrote:
> connect thunderbird to account user1 on server1
> result: login ok, mdbox visible on disk, 0 messages
>
> in thunderbird copy exactly 100 messages from a spambox to user1's
> inbox on server1
spambox not being in server1? So not IMAP COPY command,
> > I tried with mdbox now.. same problem, although I don't see
> > "Expunged message reappeared" anymore , but still tons of these:
> >
> > Server1:
> > Jan 31 13:38:05 doco1 dovecot: doveadm: Error: dsync-remote(user1):
> > Error: Mailbox INBOX: Remote didn't send mail
> > GUID=caec8e2a84650a51
On 31.1.2013, at 14.46, Oli Schacher wrote:
> On Thu, 31 Jan 2013 14:27:08 +0200
> Timo Sirainen wrote:
>
>> Oh. But it's still beta1. There are several fixes done to dsync since
>> beta1, including a fix for these maildir errors. I should release
>> beta2 or maybe rc1 soon.
>>
>
> hmm.. actu
On Thu, 31 Jan 2013 14:27:08 +0200
Timo Sirainen wrote:
> Oh. But it's still beta1. There are several fixes done to dsync since
> beta1, including a fix for these maildir errors. I should release
> beta2 or maybe rc1 soon.
>
hmm.. actually I think I built it from the latest hg (but I must admit
On 31.1.2013, at 14.06, Oli Schacher wrote:
>> b) Switch to v2.2 (latest hg version). It has a rewritte dsync that
>> works better.
>
> the testsetup is already on 2.2 hg
Oh. But it's still beta1. There are several fixes done to dsync since beta1,
including a fix for these maildir errors. I sh
> a) Use mdbox format instead of maildir. It works better with dsync.
ok, I'll try that
(although I was hoping I could avoid migrating all boxes on the server
I was planning to use this feature)
>
> b) Switch to v2.2 (latest hg version). It has a rewritte dsync that
> works better.
the test
On 31.1.2013, at 12.27, Oli Schacher wrote:
> I'm trying to build a cluster of two servers with dsync replication
> (based on http://wiki2.dovecot.org/Replication). My test setup works
> fine for very simple tests, I can log in to both servers, copy a
> message to one of the servers and it succes
Hi
I'm trying to build a cluster of two servers with dsync replication
(based on http://wiki2.dovecot.org/Replication). My test setup works
fine for very simple tests, I can log in to both servers, copy a
message to one of the servers and it successfully apperars in the other
account. But, if I tr
On 25.8.2012, at 19.09, Michael Grimm wrote:
>> Not enable mail_log for doveadm:
>>
>> protocol !doveadm {
>> mail_plugins = $mail_plugins = mail_log
>> }
>
> JFTR: That didn't work.
This would omit it from the local dsync.
>> or alternatively override it only for the dsync command with dovead
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 dovecot: dsync-local(test): Error: remote:
dsync
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 dovecot: dsync-local(test): Error: remote:
>>> dsync-remote(test): Info: save: box=INBOX, uid=27,
>>> m
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):
>>
>>| mai
On 18.7.2012, at 19.24, l...@airstreamcomm.net wrote:
>> Anyway, in my small installation I'm using it in active-active mode and it
>> works well enough. I've even configured my clients intentionally so that
>> they use different servers.
>
> Does dsync replication only work between two hosts?
l...@airstreamcomm.net wrote:
> On 7/6/12 9:56 PM, Timo Sirainen wrote:
> >On 6.7.2012, at 23.28, l...@airstreamcomm.net wrote:
> >
> >>Thanks, that certainly helps identify the configuration options. However I
> >>am more concerned about the experiences of others who have actually used
> >>the rep
On 7/6/12 9:56 PM, Timo Sirainen wrote:
On 6.7.2012, at 23.28, l...@airstreamcomm.net wrote:
Thanks, that certainly helps identify the configuration options. However I am more
concerned about the experiences of others who have actually used the replication.
What is the rate of change on your
On 6.7.2012, at 23.28, l...@airstreamcomm.net wrote:
> Thanks, that certainly helps identify the configuration options. However I am
> more concerned about the experiences of others who have actually used the
> replication. What is the rate of change on your mail cluster, how many
> concurrent
...@dovecot.org] On
Behalf Of l...@airstreamcomm.net
Sent: Friday, July 06, 2012 3:28 AM
To: dovecot@dovecot.org
Subject: [Dovecot] Dsync replication
I have been loosely following discussions dsync replication, but I am
wondering if this tool still in a testing phase or has it been committed
as a
: Friday, July 06, 2012 3:28 AM
To: dovecot@dovecot.org
Subject: [Dovecot] Dsync replication
I have been loosely following discussions dsync replication, but I am
wondering if this tool still in a testing phase or has it been committed
as a production part of Dovecot? I would like to do some testing
I have been loosely following discussions dsync replication, but I am
wondering if this tool still in a testing phase or has it been committed
as a production part of Dovecot? I would like to do some testing with
the protocol to see if it's capable of handling the change rate our mail
service
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
s
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)
> > use
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 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 $
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, becau
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 issue
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
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
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 issues
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 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 mo
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 cu
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 replicate
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
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
>
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
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 p
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 tes
94 matches
Mail list logo
