similar to: dbox support state

When a user enable vacation in sieve deliver die and the mail lost. I am using 1.0.3 Thanks ------------------------------------------------------------------------------------------------------------------------------------------- in syslog postfix/pipe[16060]: 8E33017D4: to=<vivi at abc.com.hk>, relay=dovecot, delay=0.17, delays=0.13/0.01/0/0.03, dsn=5.3.0, status=bounced (Command

Hello, today I checked out a new copy of Dovecot (and LDA) from CVS: File: ChangeLog Status: Up-to-date Working revision: 1.2765 Repository revision: 1.2765 /home/cvs/dovecot/ChangeLog,v I could compile them, but my findings follow: - the problem: I copied dovecot-lda below CVS_ROOT/dovecot, the first make attempt failed with this fatal error: make[3]: Entering directory

Hello, I'm trying to install dovecot as LDA, IMAP server and Sieve functions, all of this with a Postfix, Spamassassin and a MySQL Auth. When I use a Sieve script, it 's loaded but actions are not respect with this logs : Mar 18 10:31:19 localhost dovecot: lda(info at info.xx.com): Debug: sieve: using sieve path for user's script: /vmail/sieve/info.xx.com/info.sieve Mar 18

I set up system copying all mails to a backup system. This used to work without a hitch - now in the last few days mails would pile up in the Postfix Queue, waiting to be delivered using the lmtp transport into dovecot. So dovecot was being slow, but why? After all, nothing changed. After reading some articles on stackoverflow I found a way of finding out which file gets the most IO: % sysdig

Now that I have a working kvm setup, I thought I'd finally try how Zimbra works. This is mainly some microbenchmarking, so it may not have much to do with actual performance in real life. Setup: - 1GB memory given to kvm (from host's 2GB) - Intel Core 2 6600 (kvm uses only one CPU) - CentOS 5 - 15GB qcow2 image on XFS filesystem - Zimbra 5.0 RC2 RHEL5 x86_64 - Dovecot latest hg,

Hi, I originally picked mdbox because I had the impression from reading about it on the mailing list that it was more performant and that it would conserve disc space. But lately i found mailboxes have nearly double the storage as reported. I mean, IMAP QUOTA reports around 900MB for one account that has over 2GB when I inspect the mail location of the user using the linux command `du`

I am migrating our mail server from Courier-IMAP to Dovecot. We currently use maildir storage format. What are the advantages and disadvantages of Dovecot's dbox format over maildir? Does anyone have any performance benchmarks for both? What do people use to test performance? We are running on a Mac OS X box (10.5.7) using Postfix 2.6. Thanks, James.

Does anyone know of a script to compress old mails stored in a maildir format by carrying out the steps described at http://wiki.dovecot.org/Plugins/Zlib thanks, John

Hello, is possible in some way use on each ip address different certificate (for imap, for pop3). There are options like (but that is not enough for me): protocol imap { listen = *:10143 ssl_listen = *:10943 .. } protocol pop3 { listen = *:10100 .. } I have server for 4 domains (each has own ip address), so i need bind one ip address to one domain to one certificate(each certificate

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha4.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha4.tar.gz.sig Lots of fixes since alpha3. Also includes the dbox rewrite. Currently dbox works properly only in one-message-per-file mode. I'm not actually even sure how good idea it would be to use it with multiple-messages-per-file mode. But I guess it won't hurt to

Mail seems to be delivered to INBOX without reading what is in .dovecot.sieve # cat /home/vmail/user at example.com/.dovecot.sieve if exists "From" { discard; stop; } # ls -alh /home/vmail/user at example.com/.dovecot.sieve -rw-r--r-- 1 vmail vmail 41B Oct 29 01:26 .dovecot.sieve # tail /var/log/dovecot-deliver.log deliver(user at example.com): Oct 29 01:33:14 Info:

Hello, As per wiki instructions, I tried to enable zlib compression of mails by adding/modifying the following snippets of configuration: plugin { zlib_save_level = 6 zlib_save = gz } and protocol imap { mail_plugins = fts fts_squat autocreate zlib imap_zlib imap_id_log = * } I am using dbox format and delivering the mails via dovecot deliver, however mails don't seem

Hello I have read carefully about dbox (/http://wiki2.dovecot.org/MailboxFormat/dbox/) and I have some questions: - One of the main advantages (speed wise) of dbox over maildir is that index files are the only storage for message flags and keywords. What happens when we want to recover some messages from backup? With maildir we can rebuild message indexes, but I am not sure about

It has been my wish to move to dbox for a long time hoping to reduce the number of writes which is really killing us. Now I wonder what may be the best way of doing so. I'm considering some sort of intermediate migration where the existing Maildir users are changed to single-dbox and then later upgraded to 2.0 and changed to multi-dbox when it becomes stable. But is this a reasonable task

I'd like to give the dbox format a try, but I could not find any information on how to enable it. There's information on how to set mail_location for the Maildir and mbox formats in the wiki and also in the commented configuration file, but how to set it for dbox is strangely missing. I took a guess with 'mail_location = dbox:~/dbox', but that didn't work, so it's probably

Hello, I'm upgrading my mail server from UW to Dovecot and I'd like to convert from mbox to maildir. I've successfully convert myself and a few other users with the mb2md script. All is well. My question is, I have somewhere around 500 users and about 122gb of mail folders to convert (this does not include the inbox at /var/mail). mb2md needs to be run as each user to convert.

I wasted too much time today doing this, but they do show a few interesting things: 1) mmap_disable=yes is faster than mmap_disable=no. I didn't expect this. I'm not yet sure why this is, but possibly because then it updates the mail index by reading the changes from dovecot.index.log, instead of reopening and re-mmaping dovecot.index. At least that's the biggest difference between

Hi, I am contemplating migrating from maildir to dbox. However, I wonder about the maturity of the dbox code, as it appears to not be widely used. Does anybody have some success stories? My primary driver is to have non-changing file names, and thus smaller backup deltas. Are there other advantages that I should pursue? I read in the wiki that the migration is straightforward, but I did not

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

Hi Timo, I've just setup Dovecot v1.2.rc5 and switched the mailbox format of one account to dbox. Therefor I've created an empty directory, called dbox, with access mode 0700, like the user's home directory. After the IMAP login with Thunderbird some dboxes was created. All permissions were set fine (0700 / 0600), except the permissions for the files: *