similar to: Load average on machine 400+

Hi all, Please correct me if I'm going about this the wrong way. We currently have a 3 system Mail server set up - two machines are the load balanced frontends running Dovecot and Postfix, and the third machine is our NFS. Over the past 4 months or so, I've tweaked and optimized our mail servers, and we receive roughly 3 million emails a day combined through this setup. Sometimes,

Hi, Some words about my Dovecot setup: - 10 dovecot servers - each server has some local mailboxes - each server has proxying enabled to seamlessly connect to another host if the mailbox is not local Running Dovecot 1.1.1 on FreeBSD 6.3-RELEASE-p3. First of all, local mailbox access is fine. Proxying works also as expected. Now for the actual problem: Shortly after startup, Dovecot starts

I'm using 1.2.6 with the managesieve patch and maildir++ quotas (via the maildirsite file). Again, I found that the quota warning is not bering triggered. Testing via: smtp-source -4 -f sender at charite.de -t recipient at charite.de -m 1 -l 1000000 -C 1 mail.charite.de:submission recipient at charite.de being a mailbox with a 10.0 MB limit. I attached dovecot -n and the quota warn script.

What is this ? dovecot: Apr 24 13:03:29 Error: IMAP(tina.burdujan): file maildir-sync.c: line 1075 (maildir_sync_index): assertion failed: (uid >prev_uid) dovecot: Apr 24 13:03:29 Error: IMAP(tina.burdujan): Raw backtrace: /usr/libexec/dovecot/imap [0x80b8741] -> /usr/libexec/dovecot/imap [0x80b819c] -> /usr/libexec/dovecot/imap(maildir_sync_index+0x898) [0x80695f8] ->

I'm getting "imap-login: Disconnected: Connection queue full:" messages like these: May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=160.45.172.202, lip=141.42.4.250 May 16 12:17:26 postamt dovecot: imap-login: Disconnected: Connection queue full: rip=141.42.165.160, lip=141.42.4.250, TLS May 16 12:18:23 postamt dovecot: imap-login: Disconnected:

At noon, I often get "dovecot: Maximum number of mail processes exceeded" I'm at my wits end, which parameter needs to be increased further? # 1.1.3: /usr/local/etc/dovecot.conf protocols: imap imaps pop3s ssl_cert_file: /etc/ssl/certs/postamt.pem ssl_key_file: /etc/ssl/private/postamt.key disable_plaintext_auth: no version_ignore: yes login_dir: /usr/local/var/run/dovecot/login

Hi all! First of all, I want ti thank the whole Dovecot community (developers for developing and fast responses, users for populating and responses too). Dovecot is a really good and fast IMAP server - it serves near 3000 in our installation. Now I have a problem and request community's help its resolving;) Dovecot version: 1.0.13, compiled with vpopmail support. I have an account spam at

Hello, I installed 1.2.3 and we are seeing a few messages in the log files such as: --- Aug 4 16:40:24 xyz dovecot: IMAP(john): fchown() failed with file /home/john/.imap/INBOX/dovecot.index.log.newlock: Operation not permitted Aug 4 16:40:24 xyz dovecot: IMAP(john): fchown() failed with file /home/john/.imap/INBOX/dovecot.index.tmp: Operation not permitted --- dovecot -n: # 1.2.3:

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, 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

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

Is there a way to configure dovecot to register in syslog the debug messages enabled by mail_debug=yes as a debug not as information? I need this because I want to send this kind of information only to a remote server. I've configured rsyslog to do this, but dovecot is registering those debug messages as information not as debug (as I expected). This is my rsyslog config: mail.info;\

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

Two of my users are reporting that their quota is not being recalculated ALTHOUGH they deleted lots and lots of mails. I'm using today's hg checkout of 1.2 beta 4 -- Ralf Hildebrandt Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.computerbeschimpfung.de Wen du nicht mit K?nnen beeindrucken kannst, den verwirre mit Schwachsinn! -------------- next

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

I'm getting constantly high numbers of page reclaims & involuntary context switches for dovecot/auth. page reclaims = minor faults = cpu switching back to system-mode, But why is the auth process doing that so excessively? Same for the large number of involuntary context switches... Attached is my "dovecot -n" output. Date: Sun, 07 Nov 2010 20:40:34 +0100 type real

dovecot version 1.1.6 >dovecot -n # 1.1.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-gentoo-r1 i686 Gentoo Base System release 2.0.0 xfs base_dir: /var/run/dovecot/ protocols: imap pop3 listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login

This is with respect to an error that I am facing in dovecot. The error is that is seen in logs is "Feb 23 00:04:46 mailblade1 dovecot: IMAP(USERNAME): /indexes/USERNAME/.INBOX/dovecot-uidlist: Duplicate file entry at line 7: 1234776125.M559298P3988.s2o.qlc.co.in,S=13111,W=13470:2, (uid 94277 -> 97805)" This error is seen for multiple users. Once this error occurs for a user, the

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