On 2012-03-14 5:51 PM, Michael Grimm trash...@odo.in-berlin.de wrote:
You misunderstood. I was referring to system cronjob's mail reports
from cron.daily jobs like security reports et al. Those reports
normally run at identical times.
But are these really 'duplicate' mails? It sounds to me
Hi --
On 15.03.2012 12:21, Charles Marcus wrote:
On 2012-03-14 5:51 PM, Michael Grimm trash...@odo.in-berlin.de
wrote:
You misunderstood. I was referring to system cronjob's mail reports
from cron.daily jobs like security reports et al. Those reports
normally run at identical times.
But
On 2012-03-15 9:46 AM, Michael Grimm trash...@odo.in-berlin.de wrote:
Thus, at 3:01 one report from mx1 will be delivered at mx1 into mailfolder
REPORTS and at 3:01 one report from mx2 will be delivered at mx2 into the
mailfolder REPORTS. Important: both mails are different but they arrive
in
Hi --
On 15.03.2012 15:04, Charles Marcus wrote:
On 2012-03-15 9:46 AM, Michael Grimm trash...@odo.in-berlin.de
wrote:
Thus, at 3:01 one report from mx1 will be delivered at mx1 into
mailfolder
REPORTS and at 3:01 one report from mx2 will be delivered at mx2
into the
mailfolder REPORTS.
The day I switched to the new replicator/dsync technique, those
duplicates
are history, but I'm still able to produce duplicates (and multiples)
if
Hello,
Can you get a little bit more in details about this replicator/dsync
techique? As my main problem is that EVERYTHING (that gets created
On 15.3.2012, at 19.49, Michescu Andrei wrote:
Can you get a little bit more in details about this replicator/dsync
techique? As my main problem is that EVERYTHING (that gets created on
different servers in the same time) gets duplicated.
I only do replication using the doveadm sync
Hi --
On 15.03.2012, at 18:49, Michescu Andrei wrote:
Can you get a little bit more in details about this replicator/dsync
techique?
http://blog.dovecot.org/2012/02/dovecot-clustering-with-dsync-based.html
and
http://www.dovecot.org/img/dsync-director-replication-ssh.png
helped me a lot
Hello Timo,
I have update the repository with hg pull -u, recompiled and redeployed
and somehow the dovecot -n still shows 2.1.1... :(
I ran exactly the same test: starting for 1 clean user1, I create 2
emails, one on mx1.a and one on mx2.a and I sync them with doveadm.
The output is exactly as
hello,
So I upgraded to 2.1.2 (not from repository because that one still says
2.1.1, but from the release).
I ran exactly the same test with exactly the same behaviour. (new account,
synced successfully on 2 servers, deliver 1 email to each server, run
doveadm sync)...
Please find below the
On Wed, 2012-03-14 at 01:25 -0400, Michescu Andrei wrote:
Now, as long as I touch the mailbox of user1 only on mx1.a doveadm sync
keeps them in sync (cron job every 5 minutes).
The problem comes when I start using the master-master model: emails
starts getting duplicate with different ids.
Hello,
Nope dsync was not running during the email delivery on that account. I've
simulated in a controlled environment.
Servers are having different priorities, but this was a basic scenario to
test the master-master synchronization.
Think that for incoming SMTP I can even restrict which
On 14.3.2012, at 18.45, Michescu Andrei wrote:
Nope dsync was not running during the email delivery on that account. I've
simulated in a controlled environment.
How? You mean simply deliver mail to server A and to server B and run dsync and
it duplicates it? I can't reproduce it that way,
On 14.3.2012, at 18.45, Michescu Andrei wrote:
Nope dsync was not running during the email delivery on that account.
I've
simulated in a controlled environment.
How? You mean simply deliver mail to server A and to server B and run
dsync and it duplicates it? I can't reproduce it that way,
Hi --
On 14.03.2012, at 15:09, Timo Sirainen wrote:
On Wed, 2012-03-14 at 01:25 -0400, Michescu Andrei wrote:
The problem comes when I start using the master-master model: emails
starts getting duplicate with different ids.
I was testing this a bit, and I guess in your tests dsync was
On 14.3.2012, at 22.36, Michael Grimm wrote:
And spammers don't care about mx priorities at all :-(
But spams go to spam mailbox where duplicates don't really matter. :)
Hi -
On 14.03.2012, at 22:14, Timo Sirainen wrote:
On 14.3.2012, at 22.36, Michael Grimm wrote:
And spammers don't care about mx priorities at all :-(
But spams go to spam mailbox where duplicates don't really matter. :)
True ;-) But spam mails might interfere with syncing of legitimate
Hi --
On 14.03.2012, at 22:26, Michael Grimm wrote:
But spam mails might interfere with syncing of legitimate
mail arriving at the same time.
Forget about that part, I was wrong because duplicates are
produced in corresponding mailboxes, only.
Sorry for the noise,
Michael
On 14.3.2012, at 22.36, Michael Grimm wrote:
And spammers don't care about mx priorities at all :-(
But spams go to spam mailbox where duplicates don't really matter. :)
In an ideal world yes... or no.
In our deployment spam is simply header tagged and left in INBOX. Each
user can decide
Hi --
On 14.03.2012, at 15:09, Timo Sirainen wrote:
On Wed, 2012-03-14 at 01:25 -0400, Michescu Andrei wrote:
The problem comes when I start using the master-master model: emails
starts getting duplicate with different ids.
I was testing this a bit, and I guess in your tests dsync was
Hi --
On 14.03.2012, at 21:58, Michescu Andrei wrote:
Sometimes croncobs are running on both servers at the same time
producing locally delivered mails simultaneously, though. Ok, one
can modify run times accordingly ...
Why do you run the crontab on all the servers? You can run a
On 13.3.2012, at 7.41, Michescu Andrei wrote:
Initially I synchronize mx1.a with mx2.a using rsync. I check that I can
login using dovecot.
..
The only thing that happens is that the on each machine the folders get
doubled with some random extension (eg. Inbox becomes
Hello,
Thank you for your reply.
I'm attaching you the output for the 2nd bug. All the folders that you see
in there does not exists in user1@b but they belong to first_user@a (which
is NOT involved in this sync), BUT a is the default domain.
Also for the first suggestion:
1) how do you sync
On 13.3.2012, at 20.22, Michescu Andrei wrote:
I'm attaching you the output for the 2nd bug. All the folders that you see
in there does not exists in user1@b but they belong to first_user@a (which
is NOT involved in this sync), BUT a is the default domain.
The output showed debug output from
Hello,
Thank you very much... Using the nightly build and a combination of
mailbox status + rsync + dsync made it happen.
So the *full* procedure was:
for every domain dom
for every user u in dom
doveadm mailbox status -u user@domain guid '*'
rsync /home/vpopmail/domains/$dom/$u
Hello,
I'm using dovecot 2.1.1 with vpopmail 5.4.30 with multiples domains and I
have problems setting up synchronization in between multiple computers.
All act like master (my clients can connect to any of the them and read
their emails either via POP3 either via IMAP, inbound email gets on any
25 matches
Mail list logo
