similar to: Connection queue full on my directors

We upgraded our two dovecot directors from v2.0.14 to dovecot-ee 2.1.10.3 this week, and after that mail seems to be flowing a lot slower than before. The backend mailstores are untouched, on v2.0.14 still. After the upgrade we've been hitting process_limit for lmtp a lot, and we're struggeling with large queues in the incoming mailservers that are using LMTP virtual transport towards our

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

One of our backend pop/imap-server running dovecot v1.2.16 experienced some problems yesterday. It suddenly couldn't authenticate users anymore, flooding the logs with: pop3-login: Disconnected (auth failed, 1 attempts): user=<user1 at example.com>, method=PLAIN, rip=192.168.42.15, lip=192.168.42.28 The problem seemed to start with this log entry: Mar 29 18:57:21 popimap1 dovecot:

Hi, For the past day, I have been researching about making dovecot to support mailfront (http://untroubled.org/mailfront/) imapfront-auth natively and able to use mailfront imapfront-auth with dovecot imap v1.2.16 without starting any dovecot related services and no /etc/dovecot.conf file is required. More information about this can be read at:

Hi, I am reinstalling my server and i have encoutered a strange problem, both dovecot 2.0.13 and 1.2.16 are reporting me a problem with fd_send Invalid argument on imap login. I am running dragonfly bsd 2.10.1., compiled dovecot from pkgsrc. Can someone help me out or at least point me in some direction, i am a bit lost... :( Aug 15 10:01:00 master: Info: Dovecot v2.0.13 starting up Aug 15

I just configured postfix' virtual_transport to point at my dovecot director, but am seeing occational problems like this: Aug 31 11:50:06 smtpgw postfix/lmtp[5339]: 69E2F5410D: to=<email at example.net>, relay=loadbalancers.example.net[192.168.42.17]:24, delay=0.15, delays=0.14/0.01/0/0, dsn=5.5.4, status=bounced (host loadbalancers.example.net[192.168.42.17] said: 501 5.5.4 Invalid

What are the major differences between Versions 1.x and 2.0? I am beginning to set up a new mail server for a small group of users (~20 accounts). Options are the "0.99" version pre- packaged with RHEL-4, or building v1.2.16 or v2.0.7. Just wondering what the list recommends for a new installation. Thanks, - Don

It's long over due, but now I finally plan on upgrading from v1.0.15 to v1.2.16 on our servers. Would appreciate any comments! We have 7 servers, all running of the same GPFS filesystem. Both maildirs and indexes are stored here. We use dovecot for POP/IMAP and deliver. Currently we're using mysql as authentication source, but want to move to using ldap instead. Can we upgrade one server

I plan on putting two dovecot directors in front of our backend dovecot pop/imap servers, instead of our current haproxy loadbalancing of the connections -- but how do we handle SSL in such a setup. Will all SSL be terminated on the directors automatically, and then proxyed plain text, or is there any configuration needed to achieve this ? Does it matter that the directors are v2.0 while the

(dovecot v1.2.16) I've notice the log notices about increasing /proc/sys/fs/inotify/max_user_instances on my servers, and started wondering if inotify works for network/cluster filesystems.. I found this: http://www.ibm.com/developerworks/forums/thread.jspa?threadID=311194 which says that there's no mechanism for one node to tell another node that a directory changed for GPFS.. And I

http://dovecot.org/releases/1.2/dovecot-1.2.17.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.17.tar.gz.sig The important changes since v1.2.16: - Fixed potential crashes and other problems when parsing header names that contained NUL characters. - IMAP: Fixed a memory leak with ESEARCH command handling - Quota warnings could have been executed at incorrect

http://dovecot.org/releases/1.2/dovecot-1.2.17.tar.gz http://dovecot.org/releases/1.2/dovecot-1.2.17.tar.gz.sig The important changes since v1.2.16: - Fixed potential crashes and other problems when parsing header names that contained NUL characters. - IMAP: Fixed a memory leak with ESEARCH command handling - Quota warnings could have been executed at incorrect

Hello kind people, Any help on this would be appreciated. Dovecot v1.2.16. Freshly installed today. Comes up with this during service startup (CentOS 5.5 -> "service dovecot start" <ENTER> : --------------------------- Restarting DovecotFatal: ssl_listen: Can't resolve address required: Name or service not known --------------------------- Here's "dovecot

Hello , Went to /etc/dovecot/dovecot.conf, hunted down "ssl_listen =" which I had set it up to "ssl_listen = required" and commented it out. Tried "service dovecot start" and it started. The USD2,000,000 question being : what does this do (I know , I know, I cannot remember, I documented all this for v1.2.14) and will I need it in the future ? THank you people,

We have quite a few frontend mail gateways that deliver incoming email trough our dovecot director (lmtp proxy) to the backend lmtp servers, and are seeing this logged on the frontend mail gateways: Sep 5 10:51:56 mailgw1 postfix/lmtp[23443]: 0E2F41C01A: to=<me at example.com>, relay=loadbalancers.example.com[192.168.42.15]:24, delay=61, delays=0.02/0.3/31/30, dsn=4.4.0, status=deferred

On 13 Oct 2015, at 22:31, Heiko Schlittermann <hs at schlittermann.de> wrote: > > Hi, > > still using 2.2.9, I've two directors, and these directors > use both IPv4/IPv6 addresses. > > `host directors.<domain>` returns one A and AAA for each > of the two directors: > > directors.<domain> has address 149.x.y.96 (director1)

I'm preparing to set up a new set of directors on dovecot-ee-2.1.10.3-1, but would prefer to do this a bit gradually. Will it be OK to set up a ring of directors with 2x dovecot-ee-2.1.10.3-1 and 2x dovecot-2.0.14 ? -jf

We have an Asterisk v1.2.16 box registering with an ITSP using SIP. The registration succeeds, and is confirmed with SIP SHOW REGISTER. However, we frequently (every few minutes) see this on our console: REGISTER attempt 1 to 999@pbx.itsp.com REGISTER attempt 2 to 999@pbx.itsp.com Any ideas what is going on? In particular 1. What causes the two register attempt messages above? 2. Why

Hi, still using 2.2.9, I've two directors, and these directors use both IPv4/IPv6 addresses. `host directors.<domain>` returns one A and AAA for each of the two directors: directors.<domain> has address 149.x.y.96 (director1) directors.<domain> has address 149.x.y.97 (director2) directors.<domain> has IPv6 address

I am having an issue with the quota display not showing up in e.g. Roundcube. There are multiple Dovecot servers and three directors. A load balancer also does it's thing. The quota plug-in is enabled everywhere, except on the directors. Do those also need it enabled? -- Kristijan Savic -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc