similar to: 'doveadm who' behind nginx mail proxy

Hello, I have this strange situation on nested mailboxes (directories) # dovecot --version 2.2.36 (1f10bfa63) # doveconf -n # 2.2.36 (1f10bfa63): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.24 (124e06aa) # OS: Linux 3.10.0-693.21.1.el7.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) mail_access_groups = vmail mail_location = maildir:%h mail_plugins = quota stats quota_clone

> btw, what is the reasong for NGINX proxy anyway? Since dovecot proxy can do this for you too. I want to do authentication using the IP that the IMAP client used to connect to the IMAP server. That is, I have 50 IPs, one for each state my users live in, so the users can only connect to the IMAP server using the domain name where their account is hosted (e.g., va.example.com

I?m trying to understand how the nginx mail proxy and dovecot work. As a I understand it, nginx can listen on a IP:port for IMAP connections. NGINX then can invoke a PHP script to do authorization and backend server selection. Does NGINX than proxy to the backend dovecot IMAP server all subsequent IMAP commands that the user?s mail client requests? Does the backend dovecot IMAP server do its

Changes with nginx 0.7.66 07 Jun 2010 *) Security: now nginx/Windows ignores default file stream name. Thanks to Jose Antonio Vazquez Gonzalez. *) Change: now the charset filter runs before the SSI filter. *) Change: now no message is written in an error log if a variable is not found by $r->variable() method. *) Change:

Changes with nginx 0.8.33 01 Feb 2010 *) Security: now nginx/Windows ignores trailing spaces in URI. Thanks to Dan Crowley, Core Security Technologies. *) Security: now nginx/Windows ignores short files names. Thanks to Dan Crowley, Core Security Technologies. *) Change: now keepalive connections after POST requests are not

It appears that using dovecot to proxy to nginx imap proxy doesn't work. >From tcpdump and browsing the source it appears dovecot sends, C CAPABILITY\r\nL LOGIN <user> <pass>\r\n and nginx only responds to the CAPABILITY command. Is this a problem with dovecot sending the two commands without waiting for the first to complete or is it nginx's trouble with not handling it

Changes with nginx 1.2.7 12 Feb 2013 *) Change: now if the "include" directive with mask is used on Unix systems, included files are sorted in alphabetical order. *) Change: the "add_header" directive adds headers to 201 responses. *) Feature: the "geo" directive now supports IPv6 addresses in CIDR

Changes with nginx 1.3.10 25 Dec 2012 *) Change: domain names specified in configuration file are now resolved to IPv6 addresses as well as IPv4 ones. *) Change: now if the "include" directive with mask is used on Unix systems, included files are sorted in alphabetical order. *) Change: the "add_header"

I''m using a cluster of mongrels behind an apache 1.3 proxy pass. I''ve been passing the request to pen, which in turn balances the cluster of mongrels. Now, I''d like to be able to use a different server to send the static files created by the rails application, so I tried to replace pen with nginx. Everything seems to work fine except the environment variable REMOTE_ADDR.

Hi, we have configured userdb and passdb in the director and try to iterate all users and pass the "purge" command via doveadm proxy to port 19000 on the correct director backend host. A single purge -u username at example.org via doveadm-proxy works correctly, but iterating over some users with -A fails. Note: users/domains have been anonymized in output:

Hello, after rebooting my dovecot server quotas are no longer working. # dovecot --version 2.2.10 CentOS Linux release 7.0.1406 It is strange that restarting dovecot did not reveal this problem, but rebooting whole server did. Before reboot it was like this: # doveadm -D quota get -u test1 at testdomain1.tld doveadm(root): Debug: Loading modules from directory: /usr/lib64/dovecot

Hi, I switched from dovecot 1.2.* to 2.0.* for a mail proxy. I try to play with the new cool utility doveadm, but I don't manage to get results from it. # /usr/local/dovecot-2.0.15/bin/doveadm proxy list username proto src ip dest ip port # As 'proxy list'

Changes with nginx 0.8.29 30 Nov 2009 *) Change: now the "009" status code is written to an access log for proxied HTTP/0.9 responses. *) Feature: the "addition_types", "charset_types", "gzip_types", "ssi_types", "sub_filter_types", and "xslt_types" directives

On 21 Jan 2019, at 07:38, Edgaras Luko?evi?ius <edgaras.lukosevicius at gmail.com> wrote: > > # doveadm mailbox status -u name at domain.com -t all INBOX.* You?re doing better than I, whenever I try to use * I get # doveadm mailbox status -u kremels at kreme.com -t all * messages=0 recent=0 unseen=0 vsize=0 # doveadm mailbox list -u kremels at kreme.com Archive Drafts Junk dovecot

Hi, I''m serving the puppetmaster application with its config.ru through unicorn - proxied by nginx. I''m using unix sockets, 4 workers, and 2048 backlog. The clients - after their typical "puppet run" - send back a report to the master in YAML. Some clients whose reports tend to be large (close to 2mb) get a 502 bad gateway error and error out. nginx log: 2010/10/22

By the way, my quotas are configured to use SQL: user_query = SELECT CONCAT('/home/vmail/', maildir) AS home, 997 AS uid, 996 AS gid, CONCAT('*:bytes=', quota) AS quota_rule, CONCAT('maildir:storage=', quota) AS quota FROM mailbox WHERE username = LOWER('%u') AND active = '1' AND suspended = ?0' And when I run command "doveadm -D quota get -u test1

Hi, We are running Dovecot 2.1.10 I want configure dovecot to do execute doveadm commands on the proxy server. We have 1 proxy with director and 2 mail servers. we use LDAP when I try to do doveadm quota get -u user it works fine. The problem is when I try to do doveadm quota get -A ON PROXY I have this result: doveadm(first_user): Error: Proxy is missing destination host doveadm: Error: Failed

# 2.1.10: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-44-server x86_64 Ubuntu 10.04.4 LTS doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A shows the following message in the log when iterating the 49th user: Oct 17 00:47:17 10.129.3.233 dovecot: doveadm: Error: purge: invalid option -- 'e' Oct 17 00:47:17 10.129.3.233 dovecot: doveadm(someuser at example-ll.org):

Hi, I'm configuring a proxy host to connect to backend servers. As proxy is done based on an LDAP attribute of the user, I'm not using director. In the proxy server I have configured: doveadm_port = 24245 doveadm_password = secret And in the backend: service doveadm { inet_listener { port = 24245 } } local <mynetwork> { doveadm_password = secret }

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"