similar to: Dovecot 2.0.3

Hi, we are in migration progress from Communigate Pro 5.0.x to Dovecot 2.0.15 with mdbox. We still migrated about 25.000 IMAP accounts from CGP to Dovecot. Also there were still added about 2000 new POP3 Accounts on Dovecot. Now we must migrate about 10.000 POP3 accounts from CGP to Dovecot. At the beginning of our migration we didn't set the "pop3_reuse_xuidl" configuration

Hello, So ive spent the last 45 minutes or so searching the list for dbox stuff, but Im not seeing anything real definitive. My question is basically whether the dbox format is ready for production environment, is sdbox or mdbox more stable/ready than the other or does it matter? What are people's experience/review with running this format (and if you reply can you tell me which one

It's apparent I have some level of corruption in my mailboxes - something to do with the combination of mdbox, sis, and zlib. I should note that I know I have a mix of compressed and raw messages - if that makes any difference in identifying the problems. I think I need to somehow regenerate the mailboxes with issues. Is there a suggestion for how to accomplish this? Should I perhaps use

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 =

I have a problem to convert mdbox to MailDir. Log from that process looks like: /bin/dsync -Dv -u user at domian.com mirror maildir:/tmp/destination/mailboxes/user at domian.com Debug: Loading modules from directory: /lib/dovecot Debug: Module loaded: /lib/dovecot/lib01_acl_plugin.so Debug: Loading modules from directory: /lib/dovecot/doveadm Debug: Module loaded:

Hello, I'm using 2.2.13 on Debian stable, and I perform regular dsync backups. Typically if there is an error, dsync can recover from it the next time it is run, but I've been encountering a new error that doesn't seem to self-heal: # /usr/bin/dsync -u gae backup ssh -i /root/.ssh/id_rsa backmaildir at internal.example /usr/bin/dsync -u micah dsync-remote(micah): Error:

we have some replication issues. From time to time a doveadm-server process takes 100% cpu in the state recv_mailbox_tree_deletes on the replica. The process runs forever until it is manually killed. Strace on this process doesn't show anything. Sometimes we have several doveadm-server processes in this state, all for the same account, all with 100% CPU Load. The logfile on the master says:

Hello all-- I'm in a bind trying to reset an older Nether DSL modem. I did a manual reset on it. It was set up as "pass thru" by me and I want to "undo" that. When I boot now, the joys of Network Manager!, I can not just enter the modem manager IP address because I keep getting "network not accessible" . HELP! _______________________ Sent from MzK's phone.

I just setup a new server for a client and everything is running well. I added and setup all the users from the cli just because that's how I'm used to doing it. I tried using the samba gui that comes with CentOS 4.03 and I tried Webmin but nether one will add the user proberly to the tdbsam database. They add the user fine to the /etc/passwd file but samba does not get updated

Hi Tim, > Do you have any new insights on the problem with reappearing mail using dovecot replication + pop3? > > It's driving me mad. I'm running dovecot 2.2.34 (874deae) on OpenBSD and it looks like I have the same problem as you have. unfortunately there has been no response, I'm stuck with 2.2.33.2 for the time being. I can only suspect it has something to do with

Hi, I'm currently trying to setup remote backups of my emails but i'm running into issues (mdbox format, indexes and storage in the same folder hierarchy). Local backup command: dsync -u "my_user" backup /backups/my_user (1) Recently, I noticed that the local backup takes up twice the size as the original mail location (8gb vs. 4gb). I purged alot of emails from the original

Hi guys, I'm running dovecot/postfix on my Debian Jessie maschine: # dovecot --version 2.2.13 doveconf -n output: http://p.bastelfreak.de/HsVwS/ today I migrated from maildir(located at /var/vmail) to mdbox with these commands: rsync -av -f"+ */" -f"- *" /var/vmail/ /home/vmail/ rm /home/vmail/*/*/Maildir -rf for i in $(doveadm user \*); do u=$(echo $i | cut -d@ -f1);

I upgraded today to Dovecot 2.0.2 and Pigeonhole-0.2.0 based on debian lenny. Looked not to bad, but when I activated sieve in the lda section the following error appeared for each delivery Sep 11 18:13:11 lda: Error: dlopen(/usr/local/lib/dovecot/lda/lib90_sieve_plugin.so) failed: /usr/local/lib/dovecot/lda/lib90_sieve_plugin.so: undefined symbol: tried_default_save Sep 11 18:13:11 lda:

I've completed my mailbox rebuild - theoretically I should be free of corruption. I used dsync to export from mdbox to maildir (so should be clean) then used a virtual machine with Dovecot to import back to mdbox in another location. So...theoretically I should be free of all corruption now... Running an fts update - "doveadm search text -u user at domain.com xyzzyx" works on

Hi Guys, I've been desperately trying to find some comparative performance information about the different mailbox formats supported by Dovecot in order to make an assessment on which format is right for our environment. This is a brand new build, with customer mailboxes to be migrated in over the course of 3-4 months. Some details on our new environment: * Approximately 1.6M+

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz.sig A lot of dsync fixes. I think I've fixed now all of the bugs ever reported about dsync and I'm hopeful that it's now stable. All the rest of Dovecot looks pretty good too. Maybe v2.0.0 will be out next week. Changes since rc2: * Single-dbox is now called

http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz http://dovecot.org/releases/2.0/rc/dovecot-2.0.rc3.tar.gz.sig A lot of dsync fixes. I think I've fixed now all of the bugs ever reported about dsync and I'm hopeful that it's now stable. All the rest of Dovecot looks pretty good too. Maybe v2.0.0 will be out next week. Changes since rc2: * Single-dbox is now called

Hi Looking for some insight into mdbox index file management and recovery from corruptions. I have a two node cluster on NFS with proxy director in front for user stickness. One node (a nominated master) bidirectionally replicates to a 3rd node on a DR site. We periodically get index file corruptions resulting in rebuilds. However the user experience is poor as messages read/deleted from

Hi, A couple of months ago I had a problem with Single Attachment Storage after infrastructure migration; All mailboxes were rsynced to another filesystem, and that may have broken Single Attachment Storage. Many, many (if not all) mailboxes show the below logs on dovecot: imap(foo at bar.com): Error: read(attachments-connector(zlib(/dovecotdir/mail/