similar to: director with multiple instances

This is with dovecot-ee 2.2.18.2 on RHEL6.... To handle backend and frontend on same machine, I'm using the following hack, as previously outlined here: [in director instance config] passdb { # See thread ending in: # http://dovecot.org/pipermail/dovecot/2012-June/083817.html # for why this has to be sql instead of 'static' driver = sql args = /etc/dovecot/dovecot-sql.conf

I have setup director and a backend dovecot service on the same machine using different ports. The backend service is listening on the default 24, 110 and 143 for lmtp, pop3 and imap respectively. Director is listening on 10024, 10110 and 10143 for the same respective services. I can get this setup to work if I have one backend server on a different IP listening on 10024, it seems director

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

I have four front end servers with two backend servers. Each front end server has three instances for different mail hosts (individual SSL certs, etc). I'm looking at adding a fourth instance on each front end server for the director process. Currently we just return the backend server ip via SQL and use the old master username/password to proxy the inbound POP/IMAP sessions to the correct

Hi all We experience some unexpected behavior with dovecot. It happens that emails marked as read get marked as unread (MUA is Thunderbird on port 143). Unfortunately this happens randomly, reproducing this issue is difficult. We could not find any pattern, it happens rarely. We are running dovecot version 2.2.24 on Debian Jessie (backports repository). /root at dovecot01:~# dovecot --version//

I just noticed this error in my logs: director: Error: doveadm not compatible with this server (mixed old and new binaries?) director: Error: director(10.161.192.28:541/right): Wrong protocol in socket (director-doveadm vs director) The first error I removed by changing director_doveadm_port = 541 to director_doveadm_port = 542 Not really sure why that fixed it. The second error I

Hi, I want to change ports that Dovecot uses to listen for connections. I have listen = [::] in global section and listen = 0.0.0.0:10143 and listen = 0.0.0.0:10110 in protocol imap and protocol pop3 sections. The problem is that it doesn't seem to work for SSL ports of the two protocols and I get following error when I try to start the service: Fatal: listen(993) failed: Address already in

Hi All, Does anyone know how to disable the Director service. In our current running Dovecot 2.2.4, if the director configuration is commented out and Dovecot has no errors nor warnings. But the version 2.2.12 I'm testing with gives out fatal errors. We have dedicated Dovecot Director servers that serve the public frontend and separate dedicated imap/pop3 servers on the backend

Hello, Following Jan-Frode's advise I am trying this configuration: {postfix} ---lmtp---> {director} ---lmtp---> {dovecot} so I have two dovecot instances for director/proxy and lmtp delivery on ports 1024 and 24 respectively. whilst for imap connections I can specify a pool of imap backend servers via 'director_mail_servers' it seems is not possible with lmtp. Sep 12

Hello, I'm trying to configure the dovecot-antispam plugin. Now I've run into a problem: whenever I try to move/copy a message in/from the spam mailbox, Thunderbird (and also Sylpheed, haven't tried anything else) says: The current command did not succeed. The mail server responded: Failed to read mail beginning. and in the logs I get: dovecot: Aug 07 10:41:23 Error:

HI I use dovecot-1.0.r17 on FreeBSD scat.setcom 6.2-RELEASE. Recently authentification stop working. May 10 02:56:02 scat dovecot: auth(default): passwd(test,127.0.0.1): unknown user May 10 02:56:02 scat dovecot: auth(default): client out: OK 1 user=test User= &:/home/test:/tmp/email/bin/nonexistance= May 10 02:56:02 scat dovecot: auth(default): master in: REQUEST 23 43856 1

Hi, I'm wondering, whether it's possible, to define an ACL on the mailbox itself. We use Dovecot 1.2.15 (included in Debian 6) and maildir filesystem layout: /home/mail01/user1/Maildir/new \ /home/mail01/user1/Maildir/cur Inbox /home/mail01/user1/Maildir/tmp / /home/mail01/user1/Maildir/.folder1/new \ /home/mail01/user1/Maildir/.folder1/cur folder1

Hi, I've upgraded from 1.0.7 to 1.1.3. When I did this, my Thunderbird lost its brain and did not show some subscribed folders. squirrelmail also seemed to have issues. Applemail and mutt were fine. The configuration output is below. Hopefully this is just me and just random bizarreness. There wasn't a problem in 1.0.7 but I could have been caught in mid-upgrade. Thunderbird did not

Emailed about this with 1.1rc3 and didn't get a reply. Tried upgrading to 1.1rc4 and got the same crashing: Centos 5 (in openvz container) 2.6.18-53.1.4.el5.028stab053.4 #1 SMP Fri Jan 18 12:29:44 MSK 2008 x86_64 x86_64 x86_64 GNU/Linux /usr/local/dovecot/sbin/dovecot -n # 1.1.rc4: /usr/local/dovecot/etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap imaps pop3 pop3s

Hi all, I have a setup of some nodes running Dovecot 2.0.13 and Postfix 2.5.6 with storage in NFS and authentication happening with PAM. Poking around in the wiki, I tried out different possibilities but now I am stuck -- and are hoping for your (enlightening) comments and tips. My planned setup for IMAP and LMTP is like this: IMAP ==== 1. A loadbalancer directs new sessions to a

Hello, I have installed the dovecot-2.0.2 and dovecot-2.0-pigeonhole-0.2.0 but if I try to use sieve I get this error. I can't find any help in documentation. Any ideas? thanks ----------------------- /usr/local/sbin/dovecot start doveadm(root): Error: dlopen(/usr/local/lib/dovecot /lib90_sieve_plugin.so) failed: /usr/local/lib/dovecot/libdovecot-sieve.so.0: undefined symbol:

Hello all, today I got this crash from dovecot (2.0.14) Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3f9aa)? [0x7f18f10299aa] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3f9f6)

I've got a weird split setup where POP3 is currently handled by Courier (courier-imap-3.0.2 distribution), and IMAP is currently handled by the RHEL 5 version of Dovecot (1.0.7) I'm trying to figure out a way to convert the POP3 UIDLs (in cases where the courierpop3dsizelist is newer than dovecot-uidlist, at least) to something that Dovecot will read, or to configure Dovecot's pop3 to

Hi I got this error when configured imapc proxy (http://wiki2.dovecot.org/HowTo/ImapcProxy) and moved indexes to memory (mail_location = imapc:~/imapc:INDEX=MEMORY), with indexes on disk this error does not occurred. Jul 16 17:06:31 imap-login: Info: Login: user=<user87>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=21703, secured, session=<iwFgMU/+lwB/AAAB> Jul 16 17:06:31

CentOS Errata and Security Advisory 2014:0328 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2014-0328.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 5c28b49df7bbb5265494e1d86bf1b78376712659a97759c10575a92d9c5e8596 kernel-2.6.32-431.11.2.el6.i686.rpm