similar to: Using director but stick user to a fixed backend

On 2019-03-20 16:40, Sami Ketola via dovecot wrote: >> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot <dovecot at dovecot.org> >> wrote: >> >> I realize quota-service on Director is not supported, which is a >> shame. >> >> As a workaround I'm thinking of setting up quota-service on one of my >> backend nodes, and have all my

I realize quota-service on Director is not supported, which is a shame. As a workaround I'm thinking of setting up quota-service on one of my backend nodes, and have all my Postfix services ask this one node for the quota status. This sort of defeats the purpose of the Director (having per-user assigned hot nodes), since now this one node running the quota-service will access all

On 2019-03-21 10:28, Sami Ketola via dovecot wrote: >> On 20 Mar 2019, at 18.17, Tom Sommer via dovecot <dovecot at dovecot.org> >> wrote: >> >> >> On 2019-03-20 16:40, Sami Ketola via dovecot wrote: >> >>>> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot >>>> <dovecot at dovecot.org> wrote: >>>> I realize

> On 15 Feb 2018, at 22.16, Travis Dolan <travis.dolan at gmail.com> wrote: > > It would look as though the changes have now negatively affected a "normal" user from logging in. > > > telnet host 143 > > a login username password > > > a NO [AUTHENTICATIONFAILED] Authentication failed. > > > telnet host 143 > > 1 login

Hi, We have recently started using the director in some tests. We are using the static passdb setup (proxy=y nopassword=y) for now, where authentication is done on the downstream IMAP servers. "dovecot director status" shows a breakdown of proxied connections per backend, but there does not seem to be a similar breakdown of user connections per director. The output of

Hello everyone, I'm on a small dovecot director -> dovecot mailbox setup and I try to get doveadm command proxying to work. Though I don't get the expected output. My directors do not forward the doveadm commands to the expected backend host. Doveadm is working as expected on the backend hosts, the director hosts just dont log anything about the proxying that should happen or

Hi guys, I tried to use a global sieve skript to sort spam mails into a subfolder of INBOX. I?m using mdbox. The log shows that the script is called and executed but it is not able to find or create the mailbox: Sep 4 15:18:55 mercury dovecot: lmtp(6237, mail at steulerfliesen.de): Debug: Namespace : Permission lookup failed from /var/mail/steulerfliesen.de/mail/mdbox/mailboxes/Spamverdacht

Hello, I am currently running 2.2.31. I have a cluster of dovecot instances running in AWS. - Two instances running Director/Proxy - Two instances running Dovecot. -- Storage for the Dovecot instances is EFS. My setup works, requests for 143 hit my Director cluster and are proxied to an appropriate dovecot backend. My question is how often if at all the Director service looks up the addresses

Hi everyone, some days ago I had trouble with my NFS-Server (high delays) which caused dovecot lmtp to deliver the same message several times (up to 10x). I recognized some old/unused .nfsXXXX files in the maildirs which seemed to be index files. I deleted them and everything was fine again. However, there are still 2-3 mailboxen where mails (old and new ones) are delivered multiple times. All

On Thu, Feb 23, 2017 at 3:45 PM, Zhang Huangbin <zhb at iredmail.org> wrote: > > > On Feb 24, 2017, at 6:08 AM, Mark Moseley <moseleymark at gmail.com> wrote: > > > > * Do you use the perl poolmon script or something else? The perl script > was > > being weird for me, so I rewrote it in python but it basically does the > > exact same things. >

Awesome, thanks for the advice. Using the following now works... passdb { driver = static args = proxy=y password=doesnotmatter } Cheers. On Feb 15 2018, at 2:40 pm, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > On 15 February 2018 at 20:22 Travis Dolan <travis.dolan at gmail.com> wrote: > > > Hello, > > I have Director setup to proxy

Fair enough but the command snippet I posted was taken directly from your earlier post dated Mon Jul 27 23:11:06 EEST 2020 and it does say ?production1??I just double-checked as well... FWIW?the server order in the command you just pasted is the exact reverse from the Jul 27th post I mentioned above? Here you appear to be exec?ing the command on prod2 and trying to pull from the remote of prod

Hi all, I just recognized a lot of log entries like this on my proxy: Dec 03 13:50:54 imap-login: Info: proxy(mail at example.com): disconnecting 1.2.3.4 (Disconnected by server): user=<mail at example.com>, method=PLAIN, rip=1.2.3.4, lip=2.4.6.8, TLS, session=<qk02v6DsJwBTlUQX> There are no similar entries on the backends. What does this mean? Something I have to worry about?

Well that option set still doesn?t look correct? Here is the doveadm option set from my 2.2.2 server which is several weeks\months before 2.2.36? [Jul-27 @ 15:25:09 ] > dovecot --version 2.2.2 [Jul-27 @ 15:26:53 ] > ls -l /usr/local/bin/doveadm -rwxr-xr-x 1 root root 1379203 May 22 2013 /usr/local/bin/doveadm [Jul-27 @ 15:25:12 ] > doveadm usage: doveadm [-Dv] [-f

I have setup director and a backend dovecot service on the same machine using different ports. The backend service is listening on the default 24, 110 and 143 for lmtp, pop3 and imap respectively. Director is listening on 10024, 10110 and 10143 for the same respective services. I can get this setup to work if I have one backend server on a different IP listening on 10024, it seems director

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

Not sure if this matters but the prompt when attempting the ?doveadm backup? command shows it to be a ?production" server? [root at production1 <https://dovecot.org/mailman/listinfo/dovecot> test.org.com]# doveadm backup -R -u kishore at test.org.com <https://dovecot.org/mailman/listinfo/dovecot> remote:vmail at production2.baplc.com

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

In data venerd? 7 settembre 2018 09:39:23 CEST, Aki Tuomi ha scritto: > Do you see anything else in logs? > Just the usual proxy messages, like these: Sep 6 14:45:41 imap-front13 dovecot: imap-login: proxy(alessandro at soldinicarrelli.it): disconnecting 5.169.233.224 (Disconnected by server(0s idle, in=451, out=3556)): user=<alessandro at soldinicarrelli.it>, method=PLAIN,

Timo Sirainen <tss at iki.fi> (Di 13 Okt 2015 21:02:59 CEST): > > the IP address the director connects to. > > Right. The hostnames are lost immediately at director startup. I've never really thought about needing this functionality for director, since they're usually in the same trusted network with backends.. > Ooo. What if director_mail_servers =