similar to: mail_location in LDAP and variables

Hi, I'm doing the final tests before I migrate my 10000 users from RHEL 4 + dovecot 1.1.20 to RHEL5 + dovecot 1.2.11, and I'm having some serious problems with outlook 2007 clients disconnecting very often. In dovecot's log I see lot of connects and disconnects from these clients (as oposed to my kmail, that just connects once when I come in and disconnects when I shut it off).

Hi, in http://wiki2.dovecot.org/Quota/Configuration, the example script that sends an email to the user uses the -o option to dovecot-lda that doesn't exists. HTH -- Joseba Torre. Vicegerencia de TICs, ?rea de Explotaci?n

Hi, yesterday I migrated and old version with sendmail + courier to a virtual machine (vmware) with postfix and dovecot 2.0.9. Everything worked fine, but with a more or less default setup for both dovecot and postfix, lmtp performance was pretty bad: a message was written to an inbox every 2 or 3 seconds. With that rate and a 5000+ and growing mail queue mail delivery was really slow.

Hi, I'm trying to setup a system with dovecot to remove the old courier one, and everything (pop3, imap, lmtp, quotas) but managesieve is working fine. It seems like it's a problem with each user having a separate uid, because I have a working similar setup with a single uid working without problems. In this system when I try to connect to the managesieve port using telnet I get no

Hi! Two days ago I upgraded to 1.2.15, and again I the warning "Warning: fd limit 1024 is lower than what Dovecot can use under full load" reappeared. It's a bit weird, because my actual limits are higher. From /etc/security/limits.conf * soft nofile 4096 * hard nofile 8192 root soft nofile 4096 root

Hi, we have a medium setup (8000 pop and imap users using almost every available client, 800GB of stored mails using maildir on a Celerra NFS server, with index files on local disks, and procmail for local delivery), being served by a Dell PowerEdge 2850 (2GB RAM and dual P4 Xeon 3,2GHz). Our current not-so-high availability setup is based on a similar server with the same setup and a easy

Hi, Before some major changes in our infrastructure, I was interested in the performance impact of moving indexes to our NAS (Emc Celerra v5.5). So I downloaded both dovecot-1.1.19 and dovecot-1.2.6, compiled them and wrote 2 confs for each of them, one with local indexes and another with indexes in the NAS. Then I created 19 pam users, and tested system performance this way: - uninstall

I suppose this was for the list... -- Joseba Torre. Vicegerencia de TICs, ?rea de Explotaci?n -------------- next part -------------- An embedded message was scrubbed... From: Stewart Dean <sdean at bard.edu> Subject: Re: [Dovecot] Dovecot and SATA Backend Date: Tue, 17 Nov 2009 09:07:31 -0500 Size: 2870 URL:

I supposse this was directed to the list -- Joseba Torre. Vicegerencia de TICs, ?rea de Explotaci?n -------------- next part -------------- An embedded message was scrubbed... From: "Voytek Eymont" <voytek at sbt.net.au> Subject: Re: [Dovecot] Dovecot Solutions company Date: Fri, 13 May 2011 23:41:02 +1100 Size: 3011 URL:

Hi all, in the last days, probably since I upgraded to 2.2.7, I'm seeing lots of deleted messages reappearing in my folders. This is after this error in the log: Nov 13 14:55:16 buzones2 dovecot: imap-login: Login: user=<username>, method=PLAIN, rip=source_ip, lip=dest_ip, mpid=15510, TLS, session=<2bmiUA/rZACe4wQZ> Nov 13 14:55:16 buzones2 dovecot: imap(username): Error: mdbox

Hi, I've almost finished my new director based setup, but in the first test I discovered that imap and lmtp connections were not always being proxied to the same server. After some research now I think that the main problem is that in imap connections users connect as 'username' while lmtp connections are as 'username at mailserver'. In my current setup I receive mail via

mail_location setting has started becoming a bit bloaty. I'm not actually even sure why I've kept adding more parameters to it rather than just adding new settings. It's also caused confusion, because people try things like: mail_location = mbox:/var/mail/%u mail_location = mbox:INBOX=/var/mail/%u Although the first one has been giving ok enough error message for a long time now and

I recently created Dovecot Solutions Oy (Ltd) company with two other guys. We sell Dovecot support, development, etc. I was planning on announcing this only after we get an actual web site, but since I already told about it in Linuxtag today, I might as well tell everyone. The upcoming web site should have some more details, but if you already know you want to buy something, let me know. :)

I recently created Dovecot Solutions Oy (Ltd) company with two other guys. We sell Dovecot support, development, etc. I was planning on announcing this only after we get an actual web site, but since I already told about it in Linuxtag today, I might as well tell everyone. The upcoming web site should have some more details, but if you already know you want to buy something, let me know. :)

Hi all, I've installed rc23 in a new testing machine, and i've had some permission problems related to dovecot-master.conf. As I have my master passwords in that file, I don't want it to be world readable. dovecot -n shows that auth_user is nobody, so setting the permissions to nobody.whatever 640 solves the problem. Anyway, I've tried to change the auth_user setting with no

Hi All, Sorry if this is a dumb questions, but what methods are available for retrieving mail for a system user i.e www-data. Basically my setup is just a normal Dovecot-IMAP which is working fine for shell users, but I want to be able to read mail for system users via IMAP. Is this doable? Cheers

Hi, I have already set up DOVECOT + POSTFIX mail server and I can send and receive mails outside my Domain. The problem however is that LOCAL Mail is not working. When I send LOCAL mails, it leaves my system without error messages but it is not received by the recipient. How do I make LOCAL mails work? Regards Alexander

Is there any way to still be able to login/delete email via dovecot-imap when the user's filesystem quota is exceeded? We just moved from courier where this was still possible but now a user over quota can login but cannot get a list of messages and the logs show this: May 27 10:24:45 pop1.gwtc.net dovecot: POP3(cody at howaboutnow.net) [64.251.165.209]:

I get dovecot to work and answer when telnet to 110 both local and from another computer. But it shows nothing in the log files except it's running. Here's the log and other info: /var/log/maillog: Jan 25 16:49:32 widgeteye dovecot: master: Dovecot v2.0.9 starting up (core dumps disabled) dovecot --version 2.0.9 dovecot -n output # 2.0.9: /usr/local/etc/dovecot/dovecot.conf #

We're using roundcube as a method of access to a read-only email archive served via imap/dovecot. I was thinking of disabling outgoing mails by fiddling with the roundcube code, but thought it might be possible to disable the outgoing functionality from dovecot? /Per Jessen, Z?rich