search for: proxy_nopipelining

...>> a fully featured IMAP server. > Does the dumb server advertize pipelining? > Exactly how does an IMAP server advertise pipelining other than it says it's an IMAP server? :) There is no such capability, extension etc. It's in RFC3501, which defines IMAP v4r1. Dovecot has a proxy_nopipelining setting for its IMAP proxy, I just want to use that (ie: no pipelining) with imapc too. Whether it's dynamically configurable, even with the existing proxy_nopipelining, or with an imapc_features flag, it doesn't matter for me. Of course, setting this per user would be nicer.

...ttls=any-cert? if the port matches the sieve-port. It works as expected in that it returns the correct values and proxies to the correct backend. However it seems that TLS is no longer working and I get timeouts from the backends. Debug: client passdb out: OK 1 user=someuser at example.com proxy proxy_nopipelining=y host=backend1.example.com nodelay=y nologin starttls=no ssl=any-cert hostip=so.me.i.p pass=<hidden> results in: Sep 17 11:08:47 imapproxy1 dovecot: imap-login: Error: proxy(someuser at example.com): Login for so.me.i.p:993 timed out in state=/none (after 30 secs, local=lo.cal.i.p:60524): u...

...: js = { 'password': '', 'nopassword': '', 'host':'imap_backend', 'port':1430, 'driver':'imap', 'proxy_nopipelining':'y', 'userdb_user':qdata['Auth-User'], 'userdb_imapc_user':qdata['Auth-User'], 'userdb_imapc_password':qdata['Auth-Pass'], 'destuser':qdata['Auth-User...

...isco. (Probably can't get much done this week in Tokyo.) In the mean time here's v2.2.11 with some new features. + acl plugin: Added an alternative global ACL file that can contain mailbox patterns. See http://wiki2.dovecot.org/ACL for details. + imap proxy: Added proxy_nopipelining passdb setting to work around other IMAP servers' bugs (MS Exchange 2013 especially). + Added %{auth_user}, %{auth_username} and %{auth_domain} variables. See http://wiki2.dovecot.org/Variables for details. + Added support for LZ4 compression. + stats...

...isco. (Probably can't get much done this week in Tokyo.) In the mean time here's v2.2.11 with some new features. + acl plugin: Added an alternative global ACL file that can contain mailbox patterns. See http://wiki2.dovecot.org/ACL for details. + imap proxy: Added proxy_nopipelining passdb setting to work around other IMAP servers' bugs (MS Exchange 2013 especially). + Added %{auth_user}, %{auth_username} and %{auth_domain} variables. See http://wiki2.dovecot.org/Variables for details. + Added support for LZ4 compression. + stats...

...servers) could be easy... >> >> ... except I can see no place to do this in imapc (only in pop3c and >> imap proxy, which I guess doesn't apply here). >> >> If I'm right, may I ask for a knob for such dumb servers? >> >> Thanks, > For proxy, use proxy_nopipelining > Are you sure it works with imapc? I've tried it, and dovecot still does the above.

Hi, I've a broken IMAP server, which doesn't support pipelining and fails on dovecot's attempt to do this ([C] is dovecot's imapc, [S] is the IMAP server): [C] 24 LOGIN "user" "pass" [S] 23 OK [C] 25 SELECT "INBOX" [C] 23 UID FETCH 2 (INTERNALDATE) [S] 25 OK [S] 23 BAD No mailbox selected Sadly, fixing the server would be a hard task, turning off

...t; 'password': '', > 'nopassword': '', > 'host':'imap_backend', > 'port':1430, > 'driver':'imap', > 'proxy_nopipelining':'y', > 'userdb_user':qdata['Auth-User'], > 'userdb_imapc_user':qdata['Auth-User'], > 'userdb_imapc_password':qdata['Auth-Pass'], > 'destuser':qdat...

On 09/11/2017 12:12 PM, Aki Tuomi wrote: > Is there some reason you can't use normal proxy instead of imap backend? > That is,return proxy, host=imap_backend, port=1430? There seems to be no > pipeline setting currently for imapc in v2.2. > Yes, because it's a dumb IMAP server, which doesn't implement a lot of things, like SEARCH, FETCH BODYSTRUCTURE and similar. Dovecot

...e port matches the sieve-port. It works as expected in that it returns the correct values and proxies to the correct backend. > > However it seems that TLS is no longer working and I get timeouts from the backends. > > Debug: client passdb out: OK 1 user=someuser at example.com proxy proxy_nopipelining=y host=backend1.example.com nodelay=y nologin starttls=no ssl=any-cert hostip=so.me.i.p pass=<hidden> > > results in: > Sep 17 11:08:47 imapproxy1 dovecot: imap-login: Error: proxy(someuser at example.com): Login for so.me.i.p:993 timed out in state=/none (after 30 secs, local=lo.ca...

On 09/11/2017 10:42 AM, Sami Ketola wrote: >> On 11 Sep 2017, at 11.24, Nagy, Attila <bra at fsn.hu> wrote: >> I use dovecot with a broken IMAP server (which doesn't properly implement command pipelining amongst others) as an imapc backend. >> Dovecot issues the above command sequence (SELECT and UID FETCH pipelined), which doesn't work with this server. >>

...y workarounds for > different servers) could be easy... > > ... except I can see no place to do this in imapc (only in pop3c and > imap proxy, which I guess doesn't apply here). > > If I'm right, may I ask for a knob for such dumb servers? > > Thanks, For proxy, use proxy_nopipelining Aki

...gt;> >>> ... except I can see no place to do this in imapc (only in pop3c and >>> imap proxy, which I guess doesn't apply here). >>> >>> If I'm right, may I ask for a knob for such dumb servers? >>> >>> Thanks, >> For proxy, use proxy_nopipelining >> > Are you sure it works with imapc? I've tried it, and dovecot still > does the above. So what are you exactly doing? Aki

...'t get much done this week in Tokyo.) In the mean time here's v2.2.11 with some new features. > > + acl plugin: Added an alternative global ACL file that can contain > mailbox patterns. See http://wiki2.dovecot.org/ACL for details. > + imap proxy: Added proxy_nopipelining passdb setting to work around > other IMAP servers' bugs (MS Exchange 2013 especially). > + Added %{auth_user}, %{auth_username} and %{auth_domain} variables. > See http://wiki2.dovecot.org/Variables for details. > + Added support for LZ4 compress...

we have setup a two level proxy configuration for our zimbra server: [ dovecot 2.2.12 (imap proxy mode) ] V [ nginx (imap proxy mode) ] V [ zimbra imap server] and it does not work ... after tying a login, the connection just hangs and ends after 30 seconds with a timeout. - if I try again rightaway in the same dovecot connection, the login goes though without trouble.

...except I can see no place to do this in imapc (only in pop3c and >>>> imap proxy, which I guess doesn't apply here). >>>> >>>> If I'm right, may I ask for a knob for such dumb servers? >>>> >>>> Thanks, >>> For proxy, use proxy_nopipelining >>> >> Are you sure it works with imapc? I've tried it, and dovecot still >> does the above. > So what are you exactly doing? > > I use dovecot with a broken IMAP server (which doesn't properly implement command pipelining amongst others) as an imapc backend....

...local/etc/dovecot/mailserverpro.pem userdb { driver = prefetch } My MYSQL connection config: password_query = SELECT NULL AS password, NULL as user, NULL AS destuser, host, 'Y' AS nologin, 'Y' as nodelay, 'Y' AS nopassword, 'Y' AS proxy, 'Y' as proxy_nopipelining, 120 AS proxy_timeout FROM dovecot_domains WHERE domain = '%d' Anybody can help? Best Regards, Cleber

Hi Philon, now, it's time for "Mahlzeit" ;-) Sorry, that I read the wiki1 instead of wiki2. I thought the 1 means that it is server one of ... my fault. Also not reading the first line above the menu. My focus was really on the content. ;-) Also my problem with the doc of Dovecot2 proxy is, that the document https://doc.dovecot.org/configuration_manual/authentication/proxies/