similar to: Question about Dovecot and NFS

Hi, I am using Dovecot 1.0 beta 7, moving to beta8 probably tomorrow. I am seeing a few RFC compliance issues with IMAP responses. I have an in-house IMAP client that caches IMAP data for a web mail system (it parses millions of IMAP interactions a day), and it reports whenever it gets a line that does not look RFC compliant. Unfortunately, users modify their mailboxes before I can get a copy

Hi, Mac mail (a horribly mis-behaved client, it seems), has a horribly hard time deleting/copying large blocks of messages from one folder to another. The basic symptom is: 1. Select a bunch of messages 2. Click on delete 3. Wait for a _very_ long time. It also seems very slow on copying, so it may be the "trash folder copy on delete" that is really slowing it down. Anybody else seen

How does Dovecot handle accounts when writes are denied, such as in situations when a user is over quota, or the filesystem is full? -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 Only a statue can be perfect, and even then it casts a shadow. - Merle Fossum

In the midst of evaluating Dovecot for use in solving some mbox locking issues (while also waiting for our eventual migration to maildir), I had an epiphany. It looks like Dovecot's auto-detection of mail formats would allow us to migrate from mbox to maildir on a user-by-user basis! I was thinking: 1. Let dovecot autodetect mail storage 2. Use some procmail trickery to detect which format

Hi, We are using Dovecot with maildir, and the mail client requests flags, internaldate, and uid for all messages on folder open, which on average takes 3 seconds, but for large folders is much longer. It seems like I want mail_cache_fields to include "flags", but which date corresponds to internaldate? date.received? Is UID always cached for messages, or does it have to read through

Hi, I am getting intermittent error messages in the log when my mail client tries to create/open a folder named ".imhoprefs". Some accounts seem to able to do it, but I have at least one that gives the log error: Feb 7 09:29:54 acad-cl1 dovecot: imap(tkay): close() failed with index file (in-memory index): Bad file descriptor I traced through the code, and it seems to be coming from

Hi, I think I already know the answer to this and I agree with it, but I have a question about "invalid" mailbox naming decisions in dovecot. Technically, RFC3501 (Section 5.1, pg. 18, client consideration 3) says that * and % are legal in mailbox names, though it implicitly discourages their use. We just migrated to dovecot, and unfortunately have a few users who used * in their

The configuration files has settings that seem to address the issues of using indexes on NFS (i.e. locking and mmap fixes), but we are using Dovecot on NFS, and when the load gets high we start to see a lot of NFS stale file handle errors, particularly with MS clients like Outlook. I see the discussion about these errors from last year. Any updates on the state of the code? Should we be using

Environment: Dovecot 1.0beta8 Host: 64 bit Red Hat AS4 Linux (2.6.9-34.0.1) Disks: NFS netapp In the case below, the two connections were going through two separate servers sharing disks via an NFS NetApp. Here is the sequence of operations: 1. Open a connection to a folder (say mail/Trash) 2. Open a connection to another folder (say Inbox) 3. Move messages from Inbox to Trash using this

If a mail folder contains quotes, the IMAP server may respond with a line like: 1 list "" "a/b/"X" Y Z" The specific example I saw had this exact form (it was in a nested folder, and one of the words was quoted). -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 Physics is like sex: sure,

There was a patch posted to fix dotfile folder names in this mail: http://www.dovecot.org/list/dovecot/2005-July/008127.html I have a web mail client (which stores preferences in a dot-file/folder through IMAP) and pine users (address book is a dot-folder in IMAP) that this affects. I can certainly hand-apply the patch, but I'd feel a lot more comfortable if this had some future in the real

I mis-read the line. -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 This isn't right. This isn't even wrong. Wolfgang Pauli

I've got some of our busiest users now using Dovecot instead of UW-IMAP with mbox-format mailboxes and predominantly Outlook Express as the client. Doing some perfomance monitoring (with Solaris 8 process accounting), it looks like Dovecot needing to read only 30-50% of the disk blocks needed by UW-IMAP, but I was hoping for better! What seems to happen, is that most of the connections

On Mon, 23 Jul 2018, Michael Wagner wrote: > here works a dovecot 2.2.27 on a raspberrypi and the behaviour is as > expected. > > doveadm -f tab fetch -u <user> "uid date.saved" mailbox Trash > uid date.saved > 314 2018-06-23 00:35:59 > 315 2018-06-23 12:39:10 > 316 2018-06-24 10:32:43 > ... > > And I have a cron script that

Hi, We are thinking of converting to Dovecot to lighten our I/O load. I have done some performace tests comparing UW-IMAP to Dovecot when using mbox format if anyone is interested. They primarily examine the I/O improvements that can be gained from using Dovecot over UW when staying with mbox format: http://whizzo.uoregon.edu/public/src/mailperf/results.html I had too much cached for this set

I'm still collecting user feedback after moving from uw-imap to dovecot development release 1.1.rc3. What said in the subject seems the obvious result of an improper configuration. Office emails are configured and accessed on multiple clients with the same automatic filters, and sometimes the filtered emails get duplicated on the destination folder. The fact is that this was perfectly

I am working on upgrading our current squirrelmail and replace uw-imap with dovecot.? I have what looks like a successful installation.? My current setup is: Centos 5.2 sendmail 8.13.8 dovecot 1.1.17 (imap) squirrelmail 1.4.17 I can send and receive email fine.? However when I try to delete an email in my Inbox, it doesn't get deleted.? It only sends a copy to the Trash folder.? But the

I've tried turning on mbox_very_dirty_syncs for myself (and a few other brave souls running 1.0-alpha3 rather than 1.0-stable) again to see what perfomance gain it gives (see thread http://www.dovecot.org/list/dovecot/2005-July/007956.html). Now we aren't running UW-IMAP at all, how safe is mbox_very_dirty_syncs assuming the only other process writing to mailboxes is our MTA (exim) which

Hi List, last time i did a lot of packaging and installing different versions of dovecot 1.0.x (rc not included ;) )and all was fine. Now a have a little problem. In this case it was an update from 1.0.13 to 1.1.1 Sometime it happens that 1 user out of x (more than 100) got this standardmessage for ~1 or ~2 thousend times in his mailbox (mbox) for example: >From MAILER_DAEMON Mon Sep 18

I have a question which others must have encountered. I switched from uw-imap to dovecot-imap a few months ago and moved my fairly large mail archive (~15 yrs) by simply mounting both accounts in a mail app and simply copying my folders over. This worked well, and all my mail is in order when I view it in evolution or thunderbird on any number of machines. However, since our company uses MS