similar to: configuring dovecot-lda takes forever...

Hi, One of my users can't read message of his Inbox, he can view subject of message with Thunderbird or Squirrelmail and IMAP but when he click on a message in order to read it he has thess messages with Thunderbird : The current command did not succeed. Invalidmessageset: 1181461470:-1181461446. ou 1181461444:* ou 1181461444:-1181461445 with Squirrelmail : SquirrelMail: ERREUR ERREUR: Le

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

Hi everyone, i am using dovecot 1.0 as IMAP and i am facing the following problem: when a user is overquota he is unable to access his account and thus he can't delete emails ! Is there any workaround for this problem ? thanks for any help. ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page.

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, 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'm doing in-site migration of accounts from /etc/passwd to an LDAP directory. The migration should be progressive (not all users at the same time). I'm already able to check mail for accounts in /etc/passwd and accounts in LDAP. The problem is with mail delivery. I'm using Postfix + Dovecot-LDA. This is the error I get with every delivery -- dovecot: Oct 03 00:16:09 Info:

Hello, I'm setting up a new mail server using freebsd 6.2, postfix, dovecot with SASL and, eventually, squirrelmail. I've gone through http://wiki.dovecot.org/TestPop3Installation the program is running, plain works over telnet from local host or from a remote machine. I can do stat and retr commands. however, when I try to use the login method (that is what the command 1 login

I can set up and access a dovecot pop3 account using outlook express fine. I can telnet into it fine. However, GFI FaxMaker is failing to log in. I assisted a client in switching his web site, including email from one server (FreeBSD) which was using Cyrus to a Redhat 4.0 server using dovecot version 0.99.11 Here's the listing of dovecot -n: dovecot -n Usage: dovecot [-F] [-c <config

Hello list, I'm using Dovecot 1.0.0 on FreeBSD 6.2-RELEASE and applied the latest MANAGESIEVE patch v3 [1] which seems to have worked smoothly, i.e. all hunks succeeded and no compilation problems. Now this may be stupid question with an obvious answer, but I am at a loss at how to start the daemon? What's the binary called that starts the sieve server? Is there a special way to

Hi all, storing e-mails (using postfix) via dovecot-lda fails and I assume this is related with a auth_socket configuration problem. But I am at a dead end, so perhaps anybody has got a hint for me: This is dovecot-2.0.8 on Solaris 10: 10-auth.conf and its include: ----------------------------- ... userdb { driver = static args = uid=104 gid=104 home=/some/path/%u } Relevant parts of

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

Tere. I'm using Debian, postfix & dovecot, with system quotas and settings in dovecot.conf: default_mail_env = maildir:%h/Maildir:INDEX=/var/spool/dovecot/index/%u:CONTROL=/var/spool/dovecot/control/%u But if system quota is full, users won't get new messages but won't get also any kind information, and also in mail.log is nothing. Is this normal? Should I use dovecot -s own

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, On a freshly installed RedHat RHEL 5.1 x86 with quota-3.13-1.2.3.2.el5.rpm I can't compile neither dovecot 1.0.7 nor 1.1beta8 : $ ./configure --with-linux-quota && make [...] gcc -DHAVE_CONFIG_H -I. -I. -I../../.. -I../../../src/lib -I../../../src/lib-dict -I../../../src/lib-index -I../../../src/lib-mail -I../../../src/lib-storage -I../../../src/lib-storage/index

Hi, I'm using dovecot for some time now. Previously I was using Courier and I've migrated this setup to dovecot which went pretty fine. Now I'm experiencing some strange behaviour when using some newer mail clients. Some of my Folders, like "spam", are vanished. The strange point is that it only happens in some clients, like Thunderbird 2.x+ or KMail 3.5.x. In others,

Hi, I've been trying some benchmarks to compare 1.0 vs 1.1 -this is the easiest way to explain the move to my boss-, so I've compiled dovecot 1.1 and imaptest-20080627 in my secondary machine running RHEL4, with homes in NFS, indeces in local files and control files also in NFS. Then I've created 100 new users imaptest001-imaptest100, and set the password paquitoelchocolatero to

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. :)

I think the most common Dovecot newbie problems are: - Not looking at the (correct) logs for errors - Authentication problems - Mail location problems - Mail permission problems Below are some of my ideas how I could stop people from asking these questions with future Dovecot (v1.1+) releases. Suggestions welcome. Distribution people especially should say if they're against some change.

Hi all, I'm in my final steps with my testing server using rc23 in a x86 RHEL4 machine. Everything is working quite well, but still are some LDAP related issues I'd like to clarify: - I'm using auth_bind and auth_bind_userdn. So pass_filter isn't used, and pass_attrs are never searched. Is this true or am I missing something? - Is there a choice for the userdb bind/queries