for the synch ;)
Best regards,
Andrei
Hi --
On 2013-02-21 Michescu Andrei wrote:
Can you post to the list your working configurations for dovecot?
(This is based on
http://dovecot.org/list/dovecot/2012-March/064513.html)
My design:
single user vmail to run dsync over ssh
Hello Michael,
Can you post to the list your working configurations for dovecot?
I've been fighting with the dsync replication a while ago and was super
buggy so I've put that project on ice.
If now it finally works I would like to get it moving again.
Best,
Andrei
On 21.02.2013, at 21:17,
Hello Spyros,
As best practice you never have the OS and the data/logs/user homes on
the same partition or set of disks.
If this is the case then your life is pretty easy:
-simply create the new set of partitions
-mount the new ones in a temporary location
-rsync (or copy everything from old
Hello Spyros,
Oupss... the DL360 G4 has only 2 bays and no external SCSI/SATA
connector... so the solution below does not really apply to you :(
Andrei
Hello Spyros,
As best practice you never have the OS and the data/logs/user homes on
the same partition or set of disks.
If this is the
Hello Alexander,
But the replication between points of presence (5 big datacenters, one
per continent, won't be good topology) will be painful and we easily
face split-brain situation, whichever replication scheme I can imagine.
The split-brain is indeed the biggest problem of common
Hello Timo,
And there is actually some (any!) way this could be avoided?... One server
dies, another continues sending the mail?
I have had some thoughts about transferring idling Dovecot connections
between processes / servers so that clients wouldn't notice it, but I
haven't even thought
Hello,
If disk space and bandwidth are affordable (and from your setup it seems
that they are affordable as you have everything locally) I would split the
mail storage completely and use replication in between n-master servers
(n=2 for your case).
The replication is not yet fully tested, but
Hello,
I agree, in practice this is not an issue compared to the unavailability
of the service, but on longer IMAP sessions (e.g. transferring a big
file) the connection loss is noticeable.
It is noticeable for somebody that really waits for a large email. For the
standard user there is
hello Timo,
Thank you very much for keeping dovecot such an active project. ;)
Do you happen to have any updates on the progress of dsync redesign?
best wishes,
Andrei
On Tue, 2012-05-29 at 22:24 +0300, Timo Sirainen wrote:
http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz
Hello Reuben,
I'm having a very similar setup. The 2 main differences: all my users are
virtual and the 2nd server is on a different continent (high latency
sync).
Unfortunately the dsync is not working for the moment. Timo is in the
process of redesigning it. So once it is release will know
Oh, and looks like I got accepted as a speaker to LinuxTag 2012. The plan
is to talk about some new things in Dovecot and dsync replication (looks
like I have to hurry up with the dsync rewrite).
Hey Timo,
Thank you very much for your hard work ;)
Please let us know if there is anything that
Hello Timo,
Thank you very much for planning a redesign of the dsycn and for opening
this discussion.
As I can see from the replies that came until now everybody misses the
main point of IMAP: IMAP has been designed to work as a disconnected,
high-latency data store.
To make this more clear:
Hello,
As log as example.com resolves to 192.0.43.10 (which I suppose it is a
host that you don't own) this will not work.
dsync seems to be resolving example.com and trying to connect there via
ssh using the current user.
It is better to test on domains that you own, on on domains that don't
Hello Jitendra,
I'm trying to do the same thing but I hit a wall as the sync seems to be
doubling some emails in my case. My issues is still open with Timo (I
HOPE!)
As you seem to be stuck in an earlier stage here are my advices:
1) add the id_rsa to the .ssh folder to the user that runs the
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
-worker {
user = vpopmail
}
user = vpopmail
}
service auth {
user = vpopmail
}
service imap-login {
user = vpopmail
}
service pop3-login {
user = vpopmail
}
ssl = no
userdb {
driver = vpopmail
}
Thank you,
Andrei
On 15.3.2012, at 19.49, Michescu Andrei wrote:
Can you get
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
in the
previous email in the listings the email files contained the hostname
mx1.a and mx2.a)
Thank you,
Andrei
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
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 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
, 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
Inbox_3e3ff3g3gb3bb3b22).
This is kind
, 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 the local dsync
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
24 matches
Mail list logo
