similar to: doveadm backup, question

Hi, I'm experiencing serious issues when using doveadm sync not working at all or do not properly sync. I wanted to use this for migrating external mailboxes to my server (in order to overcome the time when some servers/clients still use the old server and some already the my server). I tried to find a few steps in order to replicate this: For testing purposes I simulate both the remote and

Hi I migrated my dovecot server from Maildir to mdbox with saving attachments to external files and enabled SIS a few days ago. Everything works fine except one issue. I have both virtual and system users. Dovecot saves attachments with mode 0600. So I catch such errors for system users: dovecot: lda(wasya): Error: fs-sis: Couldn't read hash file

I have old dovecot server: (# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.14.15-3.el7xen.x86_64 x86_64 CentOS Linux release 7.4.1708 (Core) and new dovecot server: # 2.3.1 (c5a5c0c82): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.devel (61b47828) # OS: Linux 4.14.47-5.el7xen.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) I try

Hi, I replaced HDDs in my home server and reinstalled the OS (Ubuntu 17.04). Since I had some time I reviewed my Dovecot configuration and changed a couple of things, including mailbox format. Now I would like to migrate e-mail (about 20G -- I use this server as an e-mail archive). The Maildir is available on the (old) hard disk. The new dovecot is running. What should I use? Would mbsync work?

Hello, First of all, happy new year! I?ve recently configured my mail server and was using a simple sieve rule in order to store all my ?user+pattern at example.com? ingoing email to be stored in the INBOX/pattern folder. This setup worked very well. I restarted my server this morning (don?t know if it?s related?) and since Dovecot keep storing my emails in INBOX with following errors: root at

Debian Wheezy amd64 plus Stefan's stable-auto/dovecot2.2 repository 2:2.2.2-0~auto+57 = 16495:d447dcc6b611 Crash goes away when I disable mail_attachment_dir, happens with a fresh home as well # 2.2.2 (d447dcc6b611): /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.0 disable_plaintext_auth = no first_valid_uid = 100 mail_attachment_dir = /home/studext/attachment mail_gid

Silly question? Which is preferred? MailDir or Mbox? (directory vs flat file) How would you do this when migrating from an old server to a new one? Thx -Mike > On May 2, 2017, at 1:58 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > Assuming your maildir path is /path/to/mail/Maildir You could do it like this: > > mail_home=/path/to/mail >

mbox is not recommended for new setups unless you have very good reason to do so. Use maildir or sdbox. Aki > On May 2, 2017 at 5:09 PM Michael Segel <dovecot_mjs at hotmail.com> wrote: > > > Silly question? > Which is preferred? MailDir or Mbox? (directory vs flat file) > > How would you do this when migrating from an old server to a new one? > > Thx

Hi list, it's been 2 months now since my initial posting (s.b.). I wonder if I could get at least a "still working on it" statement from the devs or something like that? On 22.02.2018 16:42, Patrick Cernko wrote: > Hi list, > > this question was already posted a few years ago > (https://www.dovecot.org/list/dovecot/2014-November/098585.html). I > already asked the

I need to run a mail-migration from a Dovecot with mail_attachment_dir / single instance storage enabled. As mailboxes and mail_attachment_dir are rsynced I would normally run a doveadm backup -u <user> -R -d dbox:<path to rsynced mailbox>/dbox How can I tell it the mail_attachment_dir the rsynced source / (reverse) destination uses? Or do I have to start a Dovecot process and use

Dear Dovecot Team, We would like to use the LDAP iterate for dovecot replication, but I got this error: dovecot: auth-worker(10149): Error: ldap(*): ldap_search(base=ou=mail,o=asd,c=TLD filter=(objectClass=inetMailUser) failed: Size limit exceeded dovecot: replicator: Error: User listing returned failure dovecot: replicator: Error: listing users failed, can't replicate existing data When I

Dear Dovecot Team, We would like to use the LDAP iterate for dovecot replication, but I got this error: dovecot: auth-worker(10149): Error: ldap(*): ldap_search(base=ou=mail,o=asd,c=TLD filter=(objectClass=inetMailUser) failed: Size limit exceeded dovecot: replicator: Error: User listing returned failure dovecot: replicator: Error: listing users failed, can't replicate existing data When I

We will be deploying a replacement Dovecot server soon, and we are planning to use maildir for the primary storage, but with an archive namespace using mdbox (or perhaps sdbox), and SIS. Our backup servers and (luke)warm spare server need to obtain full copies of the mail store. For the maildirs I know I can simply use rsync (we already use it here). I'm a little wary of using rsync with

Hi Guys, I have a quite interesting problem. I have two servers that replicate to each-other. Suddenly one of the accounts is starting to eat a very large amount of disk space on, what basically is the replica for this account. doveadm-server seems to hang and keeps on filling the disk. I came across this message in the logs: Dec 8 07:36:40 <server> dovecot:

Hi, we have a problem. Command "doveadm mailbox cryptokey" does not work: # doveadm mailbox cryptokey usage: doveadm [-Dv] [-f <formatter>] mailbox <command> [<args>] create [-u <user>|-A] [-S <socket_path>] [-s] [-g <guid>] <mailbox> [...] delete [-u <user>|-A] [-S <socket_path>] [-e] [-r] [-s] [-Z] <mailbox>

Hi list, this question was already posted a few years ago (https://www.dovecot.org/list/dovecot/2014-November/098585.html). I already asked the original queriest and he told me, that he never got an solution or workaround but it was not important enough for him. When using replication in conjunction with sieve vacations, the .dovecot.lda-dupes file is not synced with the other server. So when

Thanks Jack. That's good to know. It is definitely something to consider. In a distributed storage scenario we might build a dedicated pool for that and tune the pool as more capacity or performance is needed. Regards, Webert Lima DevOps Engineer at MAV Tecnologia *Belo Horizonte - Brasil* *IRC NICK - WebertRLZ* On Wed, May 16, 2018 at 4:45 PM Jack <ceph at jack.fr.eu.org> wrote:

Assuming your maildir path is /path/to/mail/Maildir You could do it like this: mail_home=/path/to/mail mail_location=mdbox:~/Mail Then run doveadm import -A -s maildir:~/Maildir "" ALL mdbox should end up in /path/to/mail/Mail Please try it with doveadm import -u username first and keep backups, naturally. Aki On 2017-05-02 09:51, Tamas Papp wrote: > Hi, > > I replaced

I do always get a panic on service lmtp, while receiving a mail by postfix through always_bcc, containing an attachment. If the bcc recipient would be supplied by a small delay, I would say that the panic wouldn't occur, but I don't know how to verify this. dovecot is configured with 'mail_attachment_dir' and the public namespace location is sdbox dovecot log: Aug 6 14:18:02

The wiki says that doveadm backup supports the -A option for all users, but when I specify a file-system destination (like /tmp, or an NFS mounted folder), it just rewrites each user backup to the same location overwriting the previous user's content. You end up with just the content for the last user processed. I tried the typical %u substitution but that just created folder named