similar to: Dovecot Proxy - auth on proxy

Hi all, I am interested in running a Dovecot Proxy(with Director) on the same server as the main Dovecot IMAP/POP3 service. I have a basic Proxy/Director configuration working, however I am struggling with getting the Proxy and IMAP/POP3 service to coexist on the same server. I plan to use three IMAP/POP3 servers with a NFS/maildir backend, and I am playing with Dovecot 2.1.5 at the moment. I

We are looking at deploying several pop/imap servers to house the mail for 15,000 or more mailbox accounts. We are contemplating on the design and are looking at using MySQL auth (we already have a MySQL environment in place for our user auth to live) and proxy_maybe so each server can proxy for all the others and we just have a network load balancer distribute the incoming connections to all of

On 15 May 2018, at 12.06, Timo Sirainen <tss at iki.fi> wrote: > > If you look at .176's error log, do you see an error about "director_consistent_hashing settings differ between directors"? Have you set director_consistent_hashing=yes in the old directors? That is needed now, because the old non-consistent-hashing method is obsoleted. Unfortunately there's no easy

Hi, I'm relatively new to Dovecot and I did a bit of search but couldn't find a possible solution for the particular setup I'm working on. Basically I have an SMTP/POP/IMAP proxy setup running Postfix & Dovecot. IMAP/POP authentication is done using the password proxy feature, where the login credentials are passed to the backend server after a db lookup, which does the actual

This patch allows the dovecot proxy processes to lookup the destination host by name instead of IP address. Tested agains 1.2.10, expected to work against 1.2.11. The patch is pretty straightforward, it's making it work within the restrictions of the login process that's more interesting. I have made some changes to the wiki (pending approval) to - enhance the discussion of proxy

Hello, I would like to know if it possible to have a dovecot IMAP proxy frontend where CRAM-MD5 can be used as auth mechanism (assuming I would be using a master user/password on the dovecot IMAP backend/mailbox)? I have read a few times the following http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy page but somehow it is still unclear to me if the IMAP proxy then needs to have all the

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

Hi all, I have been struggling trying to understand the syntax to configure dovecot as a proxy against an LDAP server. As a single server dovecot works great. Now I want to add the "mailHost" attribute which, if present, should indicate the DNS name of the host that contains the person's mailbox. If the mailHost matches the local hostname, the mailbox should be served locally as it

NOTE: LMTP/doveadm proxying doesn't support SSL/TLS currently - any ssl/starttls extra field is ignored https://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy Am 23. November 2017 09:31:41 MEZ schrieb Tobi <tobisworld at gmail.com>: >Hi > >I got dovecot 2.2.26 on a Centos7 with latest updates. Dovecot is >configured to act as director and delivers to my two backend

Hi All I follwed the steps in the below url to configure a dovecot proxy instance. http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy I created a new file '95-test.conf' in /etc/dovecot/conf.d/ location. and put the below lines in that file. proxy=yes host=**** port=143 nopassword=yes However I am getting the following when starting the serice. I tried 'proxy' and

Quick follow-up: updated the proxies to 2.2.28, but I still couldn't find a way to limit the inbound IMAP connections per IP & username. I know "mail_max_userip_connections" limit works for the mail stores, but it doesn't seem to have any effect on the proxies. I'm using a mix of Dovecot & Courier-IMAP servers as backends. Basically I need to find a way to enforce

Dear list, First of all, I am French so excuse my bad english. I am currently using dovecot proxy feature, using sql backend. I "proxy" the imap/pop requests to another server, let's say server2. On server2, I use a script to keep up to date a "pop before smtp auth" database. I used mail_executable = /path/to/this/script.sh ... My problem is: the $IP environment

Good morning dovecot users I read in http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy that dovecot need ip address in host field and then "This field is required. Note that currently it's required to use an IP address since no DNS resolving is done.". I use a qmail cluster and Courier IMAP. In this system used the ldap field mailhost for proxy functionality

Thanks, I thought this might be the case. Is there any solution to enforce this on the proxy? If not, will a feature request be considered anytime soon? I see the proxies as the first line of defense against IMAP "abuse" and I think it's consistent having the same configurable option available on both backends and the proxies. --- Adi Pircalabu On 14-03-2017 20:17, Sami Ketola

Hi, I'm trying to use dovecot as a proxy as described on http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy but without much success. The problem is that when I send a IMAP login command dovecot is responding with "BYE Internal login failure. Refer to server log for more information." Can anyone help me shed light on this problem? Here's the log (Username,

Hi thanks for the link. Read that page before but somehow missed the comment about ssl+lmtp proxy :-) Are there any plans to implement that to dovecot in future? Regards tobi Am 23.11.2017 um 18:38 schrieb Carsten Rosenberg: > NOTE: LMTP/doveadm proxying doesn't support SSL/TLS currently - any ssl/starttls extra field is ignored > >

On 11 Oct 2015, at 20:04, Heiko Schlittermann <hs at schlittermann.de> wrote: > > Hello, > > I'm using a dovecot as proxy, connecting to one or more backends. > The backends use X.509 certificates. > > The proxy's passdb returns > > extra fields: > user=foo > proxy > host=backend1.<domain> > ssl=yes > nopassword=y

Op 25/06/2018 om 21:42 schreef Stephan Bosch: > > > > Op 14/06/2018 om 22:24 schreef grupo correo: >> Hi, >> I need to use lmtp server proxy, to proxy a remote smtp server, the >> documentation says "It's possible to use Dovecot LMTP server as a >> proxy to remote LMTP or SMTP servers", but i do not find how to >> configure. Can anybody

I am doing some research on Dovecots IMAP-Proxy features mentioned in <http://wiki.dovecot.org/HowTo/ImapProxy> and <http://wiki.dovecot.org/PasswordDatabase/ExtraFields/Proxy>. The docs only mention SQL as backend to hold required data. Is it also possible to use LDAP? TIA, p at rick -- state of mind Agentur f?r Kommunikation, Design und Softwareentwicklung Patrick Koetter

Hi, mail_max_userip_connections is only enforced at the backend level. The setting has no effect on proxy. If you want to force the limit then you can only do it in the backend. Sami > On 9 Mar 2017, at 12.05, Adi Pircalabu <adi at ddns.com.au> wrote: > > Quick follow-up: updated the proxies to 2.2.28, but I still couldn't find a way to limit the inbound IMAP connections per