similar to: Dovecot 2.2. proxy_maybe and twice SSL connections

Hello. With dovecot ver. from 20130211 I have a segfault on doveadm when sync. There are messages from server: 2013-02-14T12:42:35.508031+04:00 imap1 kernel: [870542.927083] doveadm-server[9483]: segfault at 4 ip 00000074b228bc24 sp 000003f30b8e61b0 error 4 in doveadm-server[74b226b000+3a000] or 2013-02-14T12:47:39.850942+04:00 imap1 kernel: [870847.279513] doveadm[9513]: segfault at 4 ip

Hello. Used 2.2.rc3. Try LDAP search: # ldapsearch -LLL -D "uid=dovecot,ou=Services,o=m" -b "ou=C,o=m" -w 1 -s subtree "(objectClass=mailUser)" mail dn: uid=test,dc=m.u,ou=C,o=m mail: test at m.u dn: uid=basov,dc=m.u,ou=C,o=m mail: basov at m.u mail: wow at m.u dn: uid=postmaster,dc=m.u,ou=C,o=m mail: postmaster at m.u dn: uid=ogo,dc=rest.com,ou=C,o=m mail: ogo

I've got a basic dovecot master-master replication setup between two servers (imap1 and imap2). Actions such as deleting messages or moving them between folders are replicated correctly and quickly. However, when new mail is delivered by postfix, replication does not occur until something else triggers it, such as one of the delete/move actions mentioned earlier. A search suggested this

On 26/10/2020 19:25, John Fawcett wrote: > On 25/10/2020 17:19, jayare~dcml at videocoding.org wrote: >> I've got a basic dovecot master-master replication setup between two >> servers (imap1 and imap2). Actions such as deleting messages or moving >> them between folders are replicated correctly and quickly. >> >> However, when new mail is delivered by postfix,

When using proxy_maybe CRAM-MD5 authentication fails when the connection is proxied. Is this expected behavior? Is proxy_maybe too simplified for this case? We're using SQL so I could rewrite the query with IFs to fake proxy_maybe and return the password as NULL and nologin as Y, but if it works that way couldn't it work with proxy_maybe? This works: password_query = \ SELECT NULL AS

Hi Folks, I spent quite some time yesterday understanding how proxy works along with the director. I came to the conclusion that proxy_maybe and director cannot be used together, but this isn?t a true incompatibility so much as caused by the way things are handled and the order they are processed in. The way proxy_maybe works is that it is processed by the auth provider once it gets the

hi, we are using the dovecot-rc1 version, and we are testing the director service, as there is little documentation on this service, a pair of questions.. if i'm not wrong, the proxy_maybe it's not implemented, yet? will be soon? this limitation does not allow use the same two directors servers like mail backend servers? the fairlure of one director server it's automatically

Hello, I'm using proxy_maybe and auth_default_realm. It seems that when a user logs in without the domain name, relying on auth_default_realm, and the "host" field points to the local server, I get the Proxying loops to itself error. It does work as expected - log on to the local server without proxying, if the user does include the domain name in the login. (IP's and

Does anyone know if dovecot support regex lookups for proxy/proxy_maybe, rather than mysql/ldap etc? I've been comparing it with perdition to see which one might be better for us to do layer7 username switching. Perdition supports the ability to not have any auth/db looks, but rather just a regex file that parses the usernames as they come in and forwards to the particular machine on the

Hi help is preciated, PROBLEM The dovecot-ldap.conf of "proxy server A" is working when the "host" attribute is the FQDN of other server: pass_attrs = uid=user,userPassword={SSHA}password,\ =proxy_maybe=,maildrop=host,=port=143,=destuser=%u,=starttls=any-cert pass_filter = (&(objectClass=posixAccount)(uid=%u)) CASES When the "host" attribute is the

Hello everybody and Timo. I have the next problem. With LDAP tree like ou=mail | - dc=example1.com,ou=Mail | - mail=box1 at example1.com,dc=example1.com,ou=Mail | - mail=box2 at example1.com,dc=example1.com,ou=Mail ? | - dc=example2.com,ou=Mail | - mail=box1 at example2.com,dc=example2.com,ou=Mail | - mail=box2 at example2.com,dc=example2.com,ou=Mail ? and settings in dovecot

hi, mutt -f imap://max at test.local@127.0.0.1 Could not connect to 127.0.0.1 (Connection refused). lsof -i dovecot 20200 root 5u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20204 dovecot 0u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20205 dovecot 0u IPv4 233361 TCP localhost:imap2 (LISTEN) imap-logi 20206 dovecot 0u IPv4 233361 TCP

Hello. I have this settings of imapc: # doveconf -a | grep imapc imapc_features = imapc_host = imapc_list_prefix = imapc_master_user = imapc_max_idle_time = 29 mins imapc_password = imapc_port = 143 imapc_rawlog_dir = imapc_ssl = no imapc_ssl_ca_dir = imapc_ssl_verify = yes imapc_user = %u and try to sync mailbox on old server and new one: $ dsync -o imapc_user="user at example.org"

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

Hi, first of all, many thanks for a great piece of software. Today I updated one of our 2 IMAP/POP3 proxies from version 2.2.15.17-1 to 2.2.23.1-1 (both are enterprise editions). After the update I now see randomly the following errors in the log file on my first proxy: ... Apr 15 10:28:54 imap1 dovecot: pop3-login: Error: SSL: Stacked error: error:1408F119:SSL

Hi, I would like to have two seperate imap listeners, with different authentication settings, but the mailstore and userbase etc will be identical. I know I can do this: > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imap2 { > port = 144 > } > } But I'm unsure how to configure imap/143 with "driver =

Hi, Using dovecot 1.1.2 on a dual-stack server, with the 'proxy_maybe' attribute to forward some clients to another server, it seems that only clients connecting with the same protocol version as the one used by address in the 'host' attribute in the password db are recognized as local. If an IPv4 address is specified as 'host', a dovecot proxy is created for clients

I'm getting lots of errors like this (possibly on every message delivery): imap2 dovecot: lmtp(rlaager at wiktel.com): Error: OU02K+gQmFhUAwAAVtfydQ : sieve: binary save: failed to create temporary file: open(/var/lib/dovecot/sieve/junk-mail.svbin.ima p2.852.) failed: Permission denied (euid=500(vmail) egid=500(vmail) missing +w perm: /var/lib/dovecot/ sieve, dir owned by 0:0 mode=0755)

Hello. Used next version of dovecot: # dovecot --version 20130205 (03a0af22100d+) Quota configuration: plugin { quota = dict:Domain quota:%d:redis:host=127.0.0.1:prefix=domain/ quota_rule = *:storage=0 quota_rule2 = Trash:storage=+5%% quota2 = dict:User quota::redis:host=127.0.0.1:prefix=user/ quota2_rule = *:storage=0 quota2_rule2 = Trash:storage=+5%% } Problem:

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