similar to: lmtp-proxying in 2.1 slower than in 2.0.14 ?

I finally upgraded to v1.2.16 on my backend servers, with ldap instead of previously mysql, and put a couple of dovecot v2.0.8 directors in front of them (used haproxy previously). It seemed to work OK initially, but after a few hours we got bit by "Connection queue full" problems on the directors. So I now set default_process_limit=512 and also: service anvil {

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

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

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

I'm trying to configure a doveadm service that will proxy trough our directors, following the recipie at: http://wiki2.dovecot.org/Director#Doveadm_server So on the backends I have: service doveadm { inet_listener { port = 24245 address = * } } doveadm_proxy_port = 24245 local 192.168.42.0/24 { doveadm_password = suPerSeecret } I assume the "local"

http://dovecot.org/releases/2.0/dovecot-2.0.15.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.15.tar.gz.sig + doveadm altmove: Added -r parameter to move mails back to primary storage. - v2.0.14: Index reading could have eaten a lot of memory in some situations - doveadm index no longer affects future caching decisions - mbox: Fixed crash during mail delivery when mailbox didn't

http://dovecot.org/releases/2.0/dovecot-2.0.15.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.15.tar.gz.sig + doveadm altmove: Added -r parameter to move mails back to primary storage. - v2.0.14: Index reading could have eaten a lot of memory in some situations - doveadm index no longer affects future caching decisions - mbox: Fixed crash during mail delivery when mailbox didn't

Hi, running dovecot-2.0.14 under Fedora 14 with kernel 2.6.35.14-103.fc14.i686.PA I've found a strange error in log which I've nerver observed before when startung dovecot: auth-worker: Error: dlopen(/usr/local/dovecot/lib/dovecot/auth/libauthdb_imap.so) failed: /usr/local/dovecot/lib/dovecot/auth/libauthdb_imap.so: undefined symbol: o_stream_switch_ioloop Dovecot seems to work normal

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Is it possible to use the instant messaging feature of Polycom phones in Asterisk? At the moment I'm seeing this in the SIP messaging when I try to send one from a Polycom 450. <--- SIP read from UDP:<CENSORED POLYCOM IP>:5060 ---> INVITE sip:0100@<CENSORED>:5060;user=phone SIP/2.0 Via: SIP/2.0/UDP <CENSORED POLYCOM

>> New subscriber here. I noticed that the FTS index is not used in compound searches. >> Is this expected? Tested in 2.0.0 and 2.0.8: > >Yep. It's been in TODO for a while. I know this thread is quite old, but we have the same issue with v2.0.14 and squat. Would this issue also affect the Solr FTS backend? Thanks, Nikolai.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 So here is my problem: I'm unable to remove an interface on CentOS 5.4 (/etc/init.d/network restart keeps enabling it again) Background: The system had several interfaces set (eth0 eth0.6 eth0.7 eth0.8) 1.) I added a test interface...eth0.9 2.) but later deleted the /etc/sysconfig/network-scripts/ifcfg-eth0.9 file (since i no longer needed it)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Currently, if you have BitCode that does not specify a target, it gets a default architecture. This is especially odd if you are doing llvm-ld -native but it first applies optimizations for a target other than what it is currently compiling for. Ideally, target-specific optimizations wouldn't be applied until a target was given. This would allow

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey All, Is there someone here on the list that has experience building RPM install files? I've never done it before. I'm looking for someone who is willing to do a little hand holding. I just built Musescore from source. I hope to build an install RPM from the resulting files. - -- _ ?v? /(_)\ ^ ^ Mark LaPierre Registered

http://dovecot.org/releases/2.0/dovecot-2.0.14.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.14.tar.gz.sig It's been a while since the previous release.. I've been a bit busy with my newly created Dovecot support company, but it was also summer and I wasted some time doing nothing useful. :) Most of my recent time has gone to adding new features to v2.1 branch. I'm planning on

http://dovecot.org/releases/2.0/dovecot-2.0.14.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.14.tar.gz.sig It's been a while since the previous release.. I've been a bit busy with my newly created Dovecot support company, but it was also summer and I wasted some time doing nothing useful. :) Most of my recent time has gone to adding new features to v2.1 branch. I'm planning on

One of our dovecot-servers (v2.0.14) got a bit too busy last evening: Sep 13 20:39:18 popimap1 dovecot: master: Warning: service(pop3-login): process_limit reached, client connections are being dropped then logged a few: Sep 13 20:39:20 popimap1 dovecot: pop3(XXXXXXXXX at YYYYY.YY): Warning: I/O leak: 0x3829233d20 (10) Sep 13 20:39:20 popimap1 dovecot: pop3(XXXXXXXXX at YYYYY.YY): Warning:

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:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The recent anti-social content on the list including threats and support of harassment needs to stop immediately. The CentOS Board will work with the list admins to enforce moderation and if needed removal and bans from the list should people continue this behaviour. This is a large, diverse, and respected community and none of us should need to

HI. www.centos.org is down. I can ping it, put connection is refused is for telnet on port 80 Several others also reported this. I and at least 1 other are from Europe. -- Ljubomir Ljubojevic (Love is in the Air) PL Computers Serbia, Europe StarOS, Mikrotik and CentOS/RHEL/Linux consultant

Hello, I think I've encountered a bug in Dovecot 2.0.9 (as provided on CentOS 6). According to the doveadm-search-query(7) manual page, a "mailbox" specification can only come at the beginning of a search query. However, if I put a mailbox specification in the middle of a query, not only do I not get an error message, I get surprising results: $ doveadm search mailbox A |wc -l