similar to: dovecot director terminate ssl ?

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

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

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 {

It seems we have a few email addresses that are not RFC 5322 compliant, and now that we've started using sieve these are failing. The problem is that we have a few addresses with leading, trailing or double dots in the local part: jan..frode at tanso.net .janfrode at tanso.net janfrode. at tanso.net I believe these has been working fine with everything else in dovecot (lda, lmtp, imap,

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 now have "mail_home = /srv/mailstore/%256RHu/%d/%n". Is there any way of asking dovecot where a user's home directory is? It's not in "doveadm user": $ doveadm user -f home janfrode at lyse.net $ doveadm user janfrode at tanso.net userdb: janfrode at tanso.net mail : mdbox:~/mdbox quota_rule: *:storage=1048576 Alternatively, is there an easy way

Guess I don't quite get namespaces, but we have the following namespace configured: $ doveconf namespace namespace { hidden = no inbox = yes list = yes location = prefix = INBOX. separator = subscriptions = yes type = private } But when I try running dsync it complains: $ sudo -u atmail dsync -u janfrode at tanso.net mirror mdbox:/tmp/janfrodeboks

Hi All, I can't get directory proxying of pop3 and imap working.? The director stuff appears to be OK - see below.?? The ldap authentication is working on the backend mail server.? I just get connection refused when I telnet to the proxy on the pop3 and imap ports.? Nothing appears to be running on the pop3 and imap ports despite the lines in the config below.? I am not sure what to do from

On 11/12/13, Jan-Frode Myklebust <janfrode at tanso.net> wrote: > My installation is only serving 1/10 of your size, but long time ago we > migrated off mysql for userdatabase, and over to LDAP. The MySQL data > source had issues (not dovecot related), and didn't seem like the right > tool for the job. A database is a database, a master is a master, and a slave is a slave

I'd like to get the IP-address of the webmail-klient logged in my maillog (for being compliant with coming data retention policies). I've noticed that with login_trusted_networks pointing at my dovecot directors, we get rip=client-ip logged on the backends. How is the proxy providing this to the dovecot backends? Anybody know what magic we need to implement in our webmail-solution to be

We have a Dovecot installation of several nodes that share an NFS mount for the user data. We are trying to configure Dovecot Proxy with Director in order to have Director select the appropriate IMAP server for a given user on behave of Dovecot Proxy. So far all examples I've seen on the dovecot site require the proxy to know the exact mail server to pass the user to by way of an LDAP

The sample Director configuration (10-director.conf) says that director_servers and director_mail_servers can be lists of either IPs or hostnames: # List of IPs or hostnames to all director servers, including ourself. # Ports can be specified as ip:port. The default port is the same as # what director service's inet_listener is using. #director_servers = # List of IPs or hostnames to all

I'm in the processes of running our first dsync backup of all users (from maildir to mdbox on remote server), and one problem I'm hitting that dsync will work fine on first run for some users, and then reliably fail whenever I try a new run: $ sudo dsync -u janfrode at example.net backup ssh -q mailbackup at repo1.example.net dsync -u janfrode at example.net $ sudo dsync -u janfrode

Hi This is my first post here so i will be as precise as i can I'm trying to setup a quota system using dovecot postfix and procmail dovecot version 1.2.9 postfix version 2.7.0 I have succesfully modified dovecot config to use fs quota system (so far imap and pop3) It reports correct quotas to imap and pop3 clients (both user and group) What im tryin to do now is to modify

We've been collecting some stats to see what kind of benefits UP/SquirrelMail's IMAP Proxy in for our SOGo webmail users. Dovecot is running in High-performance mode http://wiki2.dovecot.org/LoginProcess with authentication caching http://wiki2.dovecot.org/Authentication/Caching During the weekend two servers (webmail3 and webmail4) has been running with local imapproxy and two servers

Hi, I've been running dovecot for many years, but now i've hit a strange problem. when retrieving imap there is sometimes in 1 of 4 imap requests a 4sec latency. * notes: - connected directly to the backends this latency disappears - removing a director from the loadbalancer(lvs) so i'm the only connected to the director this latency disappears too I would appreciate some feedback

Today I will try Dovecot Director for a setup using a Cluster Backend with GFS2 on rhel5, my question is if is Director stable for use in production for large sites, I know is mainly designed for NFS but I believe it will do the job also for a cluster filesystem like GFS2 and should solve the mail persistence problem with a node and locking issues. I plan to add a layer behind a load balancer to

Hi everyone, short version: Is there no built in failover mechanism for the director service to handle a backend failure? Long version: I have a frontend server running the director service and two backends. Due to maintenance I had to shut down one of the backends which caused connection errors for the users being directed to this backend. I was very surprised as I expected the director to

I noticed 2 minor things with the director. 1) if I start 2 directors, but in 1 of them I dont add the other as a director_servers, they both start spamming the logfiles really really fast. It seems there is no backoff mechanism in the protocol between directors. 2) user mail server ip expire time cor 194.109.26.171 2010-09-02 14:32:13

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"