similar to: Does Director only work with dovecot proxy?

Hi all, I have some IMAP servers fronted with separate perdition processes, and it would be ideal if I could collapse this down to having dovecot do both the IMAP proxying and the IMAP serving at the same time on the same IP addresses. One of the fields in my LDAP entries contains the canonical name of the server that hosts their mailbox, and if I follow the manual at

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

Hello, I've just finished transiting our proxies from perdition to dovecot (2.1.7-7 Debian). Yesterday 12 messages (all within the same second) like this caught my attention: --- Apr 25 17:19:09 pp11 dovecot: auth: Warning: proxy(redacted at gol.com,xx.xx.xx.xx,<26hUEivbfQBlMrMS>): DNS lookup for mb04.dentaku.gol.com took 5.002 s --- Now this machine at that time was handling a load

Before I spend some time experimenting with what might be impossible, maybe someone can just tell me (either "how" or that it's impossible). I'd like to get perdition out of my environment (mainly to have one less moving part in my architecture). I'm looking at dovecot's built-in proxying. In my setup, I don't have dedicated front-end machines. A user can connect

The wiki <http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy> page says this: "The connections created to the destination server can't be TLS/SSL encrypted.". Hrmm. Right now, with perdition, I'm forcing the use of STARTTLS on the internal connections. I'd just as soon get rid of perdition (to have one less moving part in my architecture), but I need the

I'm a database noob, and it really seems like it would be overkill for my setup: I just want to proxy all connections from my DMZ to my internal mail server -- same internal server for all users. I used to use perdition for this set up, but am having issues getting it to play nicely with my new servers. Can I bypass all of the SQL stuff and just have dovecot forward all POP/IMAP

Hi, I setup a rather large POP3/IMAP configuration and want to use dovecot proxying feature. I have noted that the capability announce when connecting via the proxies are not the same before you are authenticated and after. Before you are authenticated the proxy announce is own capability and after it announce the final server capability. The problem is that some (most ? all ?) mail client ask

I'm trying to follow the instructions for configuring Dovecot LMTP with postfix for virtual domains but whenever mail arrives, in /var/log/maillog, I see Sep 23 16:01:20 mybox postfix/pipe[572]: 999C83206C6: to=< user at mytest.domain.com>, relay=dovecot, delay=0.08, delays=0.04/0.01/0/0.03, dsn=4.3.0, status=deferred (temporary failure. Command output: pipe: fatal: pipe_command: execvp

Hi, I have two load-balanced dovecot servers using a single NFS mount. The version is 1.2.11. I chose this so that if one server goes down the other will take up the load, and if my load is too much for one server I just have to add more identical servers. It works, but I wish to move to SAN storage because the NFS server is exhibiting irregular performance. (I spent a lot of time with tcpdump to

I'm trying to configure my proxy/director server, which proxies imap/pop/managesieve correctly already, to proxy LMTP to my backend message store server (dovecot+postfix already configured there) This is what I have so far: 10-auth.conf using auth-static.conf.ext instead of auth-ldap.conf.ext (switching to this made proxying imap/pop/managesieve work) 10-director.conf protocol lmtp {

Hello, I've searched the documentation for IMAP/POP3 server with proxy feature, but wiki says that this is not fully implemented yet, but wiki page hasnt been updated for a while. So is there any change since then? Because we are looking for a solution to replace the perdition POP3/IMAP proxy in front of the current UW-IMAP servers and we would really appreciate this feature, since the

We have a few dovecot servers all pointing to the same mail location (an NFS mount on a NAS drive). This could lead to a possible bottleneck eventually and we were wondering if it's possible to have dovecot direct x number of users to one message store location while others get their mail on a different mount?

Is it possible to use Dovecot frontends in front of UWash backends? I need a proxy pool ASAP. There is not sufficient time to migrate the backends for 40,000+ users so they have to stay UW for now. I have been looking at Perdition but concerned about performance under load. Dovecot looks really promising with it's non-forking mode. I need simple dumb frontends no local mail. Other

We are currently evaluating the migration from a proprietary, legacy mail server onto Dovecot for 20,000+ virtual domains. This is a big job and we intend to do it by initially proxying connections through to the legacy server, and moving customers over in batches by turning off the proxy feature for them. In the manual it states "This model is still a bit unfinished in current code"

I have successfully set up the master user on the destination server (2.0.11) and tests have worked. now I'm working on the proxy Before I had the proxy just forward everything to the backend and had the destination server do the authentication. My authentication is done via LDAP but not really sure how to append the master user and password to the users credentials after authentication is

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

First off, just want to say Dovecot is great! We have been using it for several months now in a fairly large installation with only a few problems. We are running 1.0.rc28 on three servers with 3 Horde/IMP boxes talking to Dovecot. The user's home dirs are located on an NFS server and the indexes are stored in their Maildirs. I have mmap_disable=yes and lock_method=dotlock in dovecot.conf.

Hi, I have a setup with several dovecot-servers (2.2.35) and I use dovecot proxy. I upgraded one server to 2.3.1 and got the configs fixed so far that it started again. But when I tried to add it into the proxying again with "doveadm director add" I see the following in the logfiles: May 6 07:19:30 host dovecot: director: Warning: Director xxx.xxx.xxx.176:9090/out disconnected us with

I have a folder created in dovecot entered by the user as "??o??" On the file system it appears as "&APEA8Q-o&AOkA6Q-" (mUTF7) When creating a sieve rule, to file into the folder ??o??, I am converting the name from UTF8 into UTF7, the rule becomes require ["fileinto"]; if header :contains ["From"] "user at domain.com" { fileinto

Hi! I am about to migrate a perdition-based IMAP/POP3 proxy to Dovecot. Unfortunately some users are behind a firewall/NAT setup which throws away seemingly idle TCP connections sooner than the established default of 24 hours (more likely after 30 minutes ...) resulting in all kinds of weird client behavior. And unfortunately? this firewall/NAT setup is outside of my control and I have no means