similar to: Multiple Patitions with with mdbox

Hello, i have to backup (tape library) a mailsystem with about 300.000 Mailboxes on 2 backends. Summary of all mailboxes are 2 TByte. The mailstore is mdbox. Is it save to do a simple filesystem backup (full and incremental) with backupsoftware? What is the prefered strategy to do a backup for desaster recovery (mailsystem crash) and restoring single usermailboxes? Regards, Claus

Will dsync also use zlib-compression when copying mails from one side to another? Wouldn't this be a good way to compress existing mails? http://wiki2.dovecot.org/Plugins/Zlib says, there's no way to do that. But dsync should respect the zlib-Plugin... Peer -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel:

Hi, I have > 11 TB hard used Mailstorage, saved als maildir in ext3 on HP EVA. I always wanted to make some mesurements about several influences to the performance (switch to ext4, switch to mdbox), but I never had enough time to do that. At the moment I *need* more speed, we have too much waitI/O on the system and I already used all other performance and tuning-tricks (separated cache,

We're running Dovecot 2.1.17 on Debian: # 2.1.17 (9efbc0731929): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-042stab078.27.debug i686 Debian 7.1 simfs and we're having this namespace configuration: mail_location = mdbox:/var/mail/%Ld/%Ln/mdbox namespace inbox { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = prefix = separator = .

Hi, I have a complicated SQL backend with stored procedures to generate passdb/userdb queries. This result have the proxy-attribute set and it's very complicated to change that procedures. On one system I tried to override/delete the proxy attribute: passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext override_fields = proxy=n } Looks like that doesn't work.

Hi, I have a server with Dovecot 2.1.x and I'm trying to convert mbox-storages to mdbox-storages. # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.7 mail_location = mbox:~/mail During the first run everything's okay, but if I run the migration a second time, the later migration is broken: root at mailstore1:/srv/vmail/cklein# rm -R mdbox/ root at

After a filesystem crash dovecot isn't able to repair some of the m-Files. That's okay in general -- but I wonder why he's complaining about "wrong dsync version" if I execute "doveadm force-resync" locally: doveadm(user at mailbox.org): Warning: mdbox /mail-mailbox/mailbox.org/1846405//mdbox/storage: rebuilding indexes doveadm(user at mailbox.org): Error:

Having dsync to make backups from existing mail-spaces, it would be nice to make dsync syncing the sieve-dirs too. -Otherweise backups aren't complete... Peer -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030 / 40 50 51 - 0 Fax: 030 / 40 50 51 - 19 Zwangsangaben lt. ?35a GmbHG: HRB 93818 B / Amtsgericht

We're running Dovecot 2.2.21 from Stephan Bosch's build service on Dovecot 7.x. Everything's up2date. # 2.2.devel (7ab22fc): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.11 (71e908a) # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.9 root at mailimap01:/etc/dovecot/conf.d # apt-show-versions | grep dovecot debian-dovecot-auto-keyring/oldstable-auto uptodate 2010.01.30

I'm using Dovecot 2.0 rc5, installed by using the deb.packes from xi.rename-it.nl/debian/dists/stable-auto/. When sieve is enabled (see attached config) my imap-process crashs: Aug 12 13:25:11 mail-archiv dovecot: imap: Debug: Loading modules from directory: /usr/lib/doot/modules Aug 12 13:25:11 mail-archiv dovecot: imap: Error: dlopen(/usr/lib/dovecot/modules/lib90_sieveugin.so)

Hi all. We've just migrated our back-end NFS mailstore from FC1 systems to CentOS4 and are experiencing problems/delays with vpopmail and user Maildirs. IMAP is fine, it's just POP access that causes us problems. Now, NFS mounts successfully, the clients can see /home/vpopmail and serve content as we would expect. IMAP works perfectly and sees new messages as soon as they're

The mdbox-format with the altstorage-feature is quite nice and important. But we're having much more then >> 30 TB of maildata and doing an fsck on huge partitions takes too much (down-) time for our mailsystem. It would be much easier, if Dovecot would be able to use at least THREE storage-paths for his m-Files (and not just TWO like now). Having an altstorage1 and altstorage2, we

We're running a huge imapc-Migration from an old Courier-IMAP to Dovecot. Courier always uses "INBOX."-prefix for his folders, so we set namespace inbox { [...] separator = . prefix = INBOX. [...] } on our new Dovecot 2.2.20 system. And also we added: imapc_list_prefix=INBOX to avoid the dublication of the INBOX prefix. At the end, doveadm/dsync/imapc see

Hi, in seldom cirumstances it's possible that the imap-process is crashing without write something usefule into the logfile. a) User foo exists, is happy and everything's alright b) He had a shared folder given from bar c) In our setup we have mailforwarding adresses without a valid $home in LDAP c) if user bar is changed from a user with into a mailforwarding adress, the user foo

I have a strange behavior on a customer's server and I don't understand that: User "bar" has some folders and one shared folder from "foo" if I use the "LIST"-command, which should list AFAIK *all* folders: # telnet localhost 143 a login bar xxxx a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES

Hi! Since our mails aren't saved correctly since we updated to 2.xx I'd really appreciate some help. What's going wrong? My mistake? Bug? Peer ---------- Weitergeleitete Nachricht ---------- Betreff: [Dovecot] Saving mails to +detail failed: Namespace error Datum: Dienstag, 3. Mai 2011, 12:50:20 Von: Peer Heinlein <p.heinlein at heinlein-support.de> An: dovecot at

Hi, the default: listen = *, :: should work and should open port 143 on IPv4 and IPv6. In my setup it looks broken: root at mail-archiv:/etc/dovecot# doveconf | grep ^listen listen = *, :: root at mail-archiv:/etc/dovecot# /etc/init.d/dovecot restart Restarting mail server: dovecotError: service(imap-login): listen(::, 143) failed: Address already in use Fatal: Failed to start listeners

Hi, somebody from the kolab groupware project recently explained me that the Bus- Factor[1] of around 1 would be one of their primary reasons not to use Dovecot and stick with Cyrus. What do you think about that? Is the bus factor much higher then 1? [1] http://en.wikipedia.org/wiki/Bus_factor Somehow related: Since the free software world[2] slowly converges towards GIT as the "one and

I'm using roundcube webmail managesieve plugin. Webmail can login managesieve to a specific mailstore successfully without proxying. Because I have mutiple mailstores, I have to use proxying to redirect the correct mailstores just as imap/pop3. ???? Stephan Bosch ????? 2016-04-03 22:50 ???? Hawk Chen; dovecot ??? Re: ??: Re: managesieve proxying not working Op 3-4-2016 om 16:32 schreef

Hi! I'm using static results in LDAP-lookups: uris = ldap://127.0.0.1 dn = xxxxxxxxxxxxx dnpass = xxxxxxxxxxxx tls = no ldap_version = 3 base = xxxxxxxxxxxxxxxxx user_attrs = =home=/mail/%d/%n,=uid=10000,=gid=10000,jpberlinMailQuota=quota_rule=*:storage=%$B user_filter = (email=%u) pass_attrs = userPassword=password pass_filter = (email=%u) default_pass_scheme = PLAIN Unfortunately, LMTP