Displaying 20 results from an estimated 11000 matches similar to: "2.2.14rc1 - dsync in backup mode still changes source permissions"
2014 May 27
1
dsync changing source permission to "root" in backup mode
Hi,
We have dsync failing once in a while when running in "backup" mode.
What's strange is that the result is that the file permissions on the
*source* machine ends up with the wrong permissions (set to uid 0).
Even though the dsync manual clearly says:
"Backup mails from default mail location to location2 (or vice versa, if
-R parameter is given). No changes are ever done
2012 Jun 22
2
dsync error: "Mailboxes don't have unique GUIDs"
I'm getting an error backing up mailboxes. I'm using the mirror
command:
dsync -fvo mail_home=/home/users/bob mirror ssh vmail at 10.1.4.1 dsync -o
mail_home=/home/.incoming_mail_migrations/users/bob
dsync-remote(vmail): Error: Mailboxes don't have unique GUIDs:
1ef6ee37c694894d783100000581a675 is shared by INBOX and INBOX
dsync-remote(vmail): Error: command BOX-LIST failed
2019 Sep 03
3
dsync and altpath on shared storage.
On 9/2/19 3:03 PM, Sami Ketola wrote:
>> On 2 Sep 2019, at 15.25, Peter Mogensen via dovecot <dovecot at dovecot.org> wrote:
...
>> Is there anyway for dsync to avoid moving Gigabytes of data for could
>> just be "moved" by moving the mount?
>
>
> Not tested but you can probably do something like this in the target server:
>
> doveadm backup -u
2019 Sep 02
2
dsync and altpath on shared storage.
Hi,
I was wondering...
If one had mdbox ALT path set to a shared storage mount (say, on NFS)
and one wanted to move a mailbox to a different host... I guess it in
principle wouldn't be necessary to copy all the ALT storage through
dsync, when the volume could just be mounted on the new host.
Is there anyway for dsync to avoid moving Gigabytes of data for could
just be "moved" by
2012 Feb 09
1
POP3 UIDLs with virtual INBOX and migration from maildir->mdbox
Hi,
Considering the scenario, where you have some old account with a
different POP3 UIDL format and you migrate them to dovecot.
So these old UIDLs would be saved to dovecot-uidlist.
At some later time you want to introduce a virtual POP3 INBOX like
described on:
http://wiki.dovecot.org/Plugins/Virtual
So you decide to make the new UIDL format "%f" - to make them unique
across
2017 Mar 05
5
Transitioning away from mail_location = maildir:~
Hi,
I have been using this setup for years:
mail_home = /var/mail/vhosts/%d/%n
mail_location = maildir:~
I have since learned that mail_home and mail_location should be
different. I plan to use this:
mail_home = /var/mail/vhosts/%d/%n
mail_location = maildir:~/mail
I would like the transition to be transparent for my email clients. I
don't want mail/directories/sieve_scripts to
2013 Jul 26
3
Expunged message reappeared, giving a new UID
I am running dovecot 2.2.2 with tcp based replication, and experiencing
some duplicated emails. `doveconf -n` output is below.
I have narrowed it down to the following scenario:
An email arrives, and is successfully replicated to both nodes. It is in
INBOX/new/ at this point on both servers.
Connect with a mail client, and delete the message - without delayed
expunge. So, for example, mutt
2019 Sep 04
1
dsync and altpath on shared storage.
So... I've done some testing.
One method which seemed to work - at least for primitive cases - was to:
* Mount the ALT storage on the destination.
* Run "doveadm force-resync \*" on the destination.
(putting all the mails in ALT storage into the dovecot.map.index)
* Run dsync from source to destination.
Of course... if there was some way to avoid step 2...
/Peter
2018 Nov 12
1
Panic: file dsync-brain-mailbox-tree.c: line 448: unreached
Hi all,
To backup our imap folders I've a cronjob running in the night:
/usr/bin/doveadm -o stats_writer_socket_path= backup -R -A -N
tcp:xxx.yyy.zzz:4191
This ran successful when I set it up and didn't look at it anymore.
Recently I noticed errors:
dsync-local(administration)<uO/qHjXS6FteLAAA3i05xw>: Panic: file
dsync-mailbox-tree-sync.c: line 1253 (sync_create_mailboxes):
2018 Aug 05
1
dsync not replicating ".dovecot.sieve -> .sieve/managesieve.sieve"
Hi,
Currently using dovecot 2.3.2.1 and pigeonhole 0.5.2 on two identical
hosts. I recently noticed ".dovecot.sieve" and
".sieve/managesieve.sieve" are not replicating from one host to the
other in either direction. Mail is having no trouble replicating on both
hosts with dsync, it is only sieve files that are not replicating for
unclear reasons.
# doveconf -n
host 1:
2012 Apr 23
2
dsync on large mailbox "fails"
I've been trying to convert an existing set of mbox mail to maildir
using dsync, but it seems to fail when it gets to the large boxes.
$ dsync -Dv mirror maildir:~/Maildir
Everything seems to work reasonably well until the first of the large
boxes hits:
dsync(jeff): Warning: Maildir /home/jeff/Maildir/.cron.2010-07-10:
Synchronization took 1210 seconds (102289 new msgs, 0 flag change
2012 Jul 14
1
Migrating with dsync and INBOX.INBOX namespace issue
I'm working on migrating IMAP users from Mirapoint Message Servers to Dovecot servers. The Mirapoint IMAP server uses INBOX as a namespace for private mailboxes. I created the same namespace in Dovecot, but when I migrate mailboxes dsync seems to ignore/miss the namespace on Mirapoint and I end up with all mailboxes under a INBOX.INBOX hierarchy.
Mirapoint Source Server
2018 Nov 23
2
doveadm dsync-server doesn't use user parameter?
Hi,
I tried to migrate my dovecot 2.2 to a new server with a other storage
configuration and dovecot 2.3.
New (and old) Server uses mysql for user information
I use the following storage settings
mail_home = /storage1/vmail/%{userdb:path}
mail_location =
2012 Feb 13
1
dsync, hard-links and refcounts
Hi,
when creating a copy of a mail, dovecot provides a feature that will
store its contents only once. In maildir, this is done by means of hard
links, while mdbox has some special refcounting mechanism.
My question is, how can we convert mails from maildir to mdbox without
duplicating these copies? It seems that dsync does not detect the hard
links. Even if the hard-linked mails have the
2019 Apr 04
4
Solr connection timeout hardwired to 60s
Hi,
What's the recommended way to handling timeouts on large mailboxes given
the hardwired request timeout of 60s in solr-connection.c:
http_set.request_timeout_msecs = 60*1000;
/Peter
2013 May 14
2
[Bug 1993] ssh tries to add keys to ~/.ssh/known_hosts though StrictHostKeyChecking yes is set
https://bugzilla.mindrot.org/show_bug.cgi?id=1993
alex at testcore.net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alex at testcore.net
Version|5.9p1 |6.2p1
--- Comment #1 from alex at testcore.net ---
Also
2013 Jun 03
1
Bad exit status from dsync
I just tried to migrate one of my users from maildir to mdbox using
dsync. My conversion script is checking the dsync exit code to know if
the conversion goes fine or not, and surprisingly dsync returned "0" at
the same time as it gave the error:
Error: Failed to sync mailbox .ta\ vare\ p? ...
(sorry, lost the rest of the error message)
Changing the folder name to mUTF7 manually
2010 Aug 28
2
dsync mirror duplicates problem
Im trying to sync 2 mailserver with dsync mirror functionality.
Problem occurs when mails arrive in the same folder on both sides then
dsync sometimes runs into problems
and duplicates that entrys on both side(2mails then with same
content). After running again
the same happens again(now 4 mails with same content on every side).
And then duplicates this mails on
both sides on every run :(
2019 May 22
1
Converting user mailboxes from maildir to sdbox
Hello,
I've got a Postfix/Dovecot server setup. Currently Dovecot is version
2.3.6, and it's using Maildir storage. The mailbox is:
mail_home = /home/vmail/mailboxes/%d/%n
mail_location = maildir:~/mail:LAYOUT=fs
I'm wanting to convert from Maildir to sdbox. I looked at:
https://wiki2.dovecot.org/MailboxFormat
I was initially thinking mdbox but that's multiple messages per
2012 Feb 18
3
Failing: doveadm sync <--remote host--> dsync mirror
Hi --
I'm used to dsync my two mailservers running 2.0.16.
Today, I did upgrade one server to 2.1, and doveadm sync is throwing to following error:
mail> doveadm sync -f -u test ssh vmail at remote-host.tld dsync -v -f -u test
doveadm(test): Fatal: All your namespaces have a location setting. It should be empty (default mail_location) in the namespace to be converted.
Same error with