similar to: dbox on CIFS

I have just upgraded to 1.1.8, hoping to fix these types of errors: Jan 20 10:39:27 laura deliver(xxxxxx at example.net): Broken file /srv/storage/mail/store/net/example/xx/xxxxxx/Maildir/dovecot-uidlist line 156: Invalid data: Jan 20 10:41:19 laura dovecot: POP3(yy.yy at example.at): Broken file /srv/storage/mail/store/at/example/yy.yy/Maildir/dovecot-uidlist line 2: Invalid data:

http://hg.dovecot.org/dovecot-dbox-redesign/ Looks like multi-dbox scales pretty nicely. Even after 100k messages the peak saved msgs/sec is the same as the initial saved msgs/sec, even if the average slows down somewhat. I tested this by first deleting mailbox, then running "imaptest" for a second to get saving to start writing several fields to dovecot.index.cache file. Then ran

I tried Squat indexing on my very small home system and when I did a body search in Thunderbird, I got a TON, and I mean TON, of these messages in my log file: Mar 6 06:13:31 apple dovecot: child 14142 (imap) killed with signal 6 Mar 6 06:13:31 apple dovecot: IMAP(jeff): file file-lock.c: line 112: unreached Mar 6 06:13:31 apple dovecot: IMAP(jeff): Raw backtrace: imap [0x482771] ->

Hi, I'll try to keep short. My primary question is what, in people's experience, are the best configuration settings for to avoid potential NFS cache locking issues in an interesting heterogeneous environment? We appear to have a workaround for some locking issues we have seen, which is turning off IDLE. Upgrading our version of dovecot from 1.1.4 is likely to address some core

Hi. Trying to upgrade from Dovecot 1.1.11 to 1.1.13 but having a problem with imap process segfaulting. Backtrace is below. I presume it's related to these MAILBOXDIR changes but the only documentation is the single line in the news for changing to ":MAILBOXDIR=mailboxes" when using dbox. Current configuration is "mail_location = dbox:~/Mail" so what exactly should be

Hi, there! Well, I am new to dovecot, so please be patient with me: I have a virtual server and want to setup simple mail delivery. postfix, saslauthd and dovecot basically work fine. The only open issue is, that (I guess) dovecot doesn't remove the mail when it's retrieved via pop3 from the server. It keeps sending me the same emails again and again. (The mail client (Thunderbird) is

What options are available for remote storage, i.e. storage devices directly mounted on the machine running Dovecot? I've seen discussions of NFS usage - but my experiences with NFS in times past have been poor. CIFS has worked well for me for non-mail use - would this be suitable? Or is there another method I've not considered? -- Daniel

Dovecot 1.2.10 in Debian, using Dovecot sieve. I have a sieve script, generated by Ingo, that's supposed to mark spam messages as "Seen" and file them into the Junk folder. In part it reads: require ["regex", "body", "imapflags", "fileinto"]; if exists "X-Spam-Flag" { addflag "\\Seen"; fileinto

Hello list, we continue our tests using Dovecot on a RHEL 6.1 Cluster Backend with GFS2, also we are using dovecot as a Director for user node persistence, everything was ok until we started stress testing the solution with imaptest, we had many deadlocks, cluster filesystems corruptions and hangs, specially in index filesystem, we have configured the backend as if they were on a NFS like setup

Hello, I cannot run FTS SOLR engine. OS is debian lenny. I re-compiled debian package (from backports) with --with-solr option. Dovecot loads fts_solr plugin. I know that it loads plugin because if I remove lib21_fts_solr_plugin.so, dovecot does not start. But it does not attempt to communicate with SOLR. Simple check: stop solr tomcat, and open 8080 port in netcat: $nc -l -p 8080 dovecot

Hi, i have a big problem with dovecot... PAM auth problem i guess, but don't know how to sort it out... Down the log and the dovecot.conf. Please soemone can tell me what's broken there? Thanks a lot ************************* HERE log ************************* Jun 9 14:49:46 vps dovecot: pop3-login: Can't connect to auth server at default: Resource temporarily unavailable Jun 9

Ok - I gave up on trying to get CIFS to work - there's obviously stuff going on I don't understand. So - instead of trying to get a virtual server to work, I next tried a chroot. That worked...but imapsync error'ed out trying to handle one of my large mailboxes. I was trying to setup a "new" server, migrate all my mail over, verify everything worked - maybe even leave the

We are setting up a Dovecot over a pair of NFS which mirrored with DRBD +Heartbeat, under Debian Etch AMD64 with Kernel 2.6.22-5. The problem was slow header downloading rate. We had tried to use postal to inject 500 emails which are under 5KB each, but when ever we start up Mail.app, Thunderbird or even OE6, the header download rate is terrible slow. Its look like a few sec for just 1

Hello all. We start to use Dovecot at our email production but it runs not such fast as we expect. We use Dell 2950 with 4GbRAM at FreeBSD-7.0-p9 - load avarage never upper a 0.5 We have about 500 clients most of it use Outlook 2007 via IMAP. We run in this problems: 1) Sync of imap folder is really slow(I think it is Outlook problem) 2) Time after time we got Sync error from outlook 3) Time

Hello all, I'm setting up a Dovecot environment here, version 1.2.15 on Debian 6.0.2 "squeeze". This is actually a complete revamp of the previous setup we have in-place here, built from the ground up with updated versions of all involved software. The operators have told me that they use some scripts hacked up by a previous sysadmin to give a single "admin" account full

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

Hello everybody, We are updating our old dovecot 1.1 servers to 2.0. We have a farm os servers, with users in nfs filesystems and indexes in local fs. Mail is stored in maildir format. We don't warrant that a user is always directed to the same server, although our load balancer sends all request from one IP to the same server (during a session time with a inactivity timeout). This is

I'm bringing up a system with dovecot that has been running for years with uw-imap. In making the switch, I put a tail on the log file, made the switch, and sent a test mail and received it. I was able to receive mail with no apparent difficulties, but the log file was disconcerting. A number of users connected during the few minutes I had it running, and for each of them there was an

Hello Timo, I'm running a single instance of dovecot-2.1.15 on a single host running 8.3-RELEASE-p3 FreeBSD amd64 mailboxes (Maildir), control files and indexes are on NFS (v3,tcp) mail_nfs_storage = yes lock_method = fcntl [didn't touch the following] # Mail index files also exist in NFS. Setting this to yes requires # mmap_disable=yes and

I see the following history in my log during message delivery: Mar 1 13:35:09 mailserver postfix/pickup[21464]: 5FAFC2A002: uid=0 from=<root> Mar 1 13:35:09 mailserver postfix/cleanup[21526]: 5FAFC2A002: message-id=<20090301213509.5FAFC2A002 at mailserver.amfeslan.local> Mar 1 13:35:09 mailserver postfix/qmgr[21429]: 5FAFC2A002: from=<root at mailserver.amfeslan.local>,