similar to: Bug Report: Failure delay config is ignored

Since upgrding to Debian squeeze, the web mail system (Imp4/Horde3) suffers delays every time a new IMAP connection is needed. Tracing the authentication conversation, we find: 08:45:55.270609: 00000000 AUTHENTICATE GSSAPI 08:45:55.271277: + 08:45:55.271761: * 08:45:55.271782: 00000000 BAD Authentication aborted by client. 08:45:55.271815: 00000001 AUTHENTICATE PLAIN 08:46:00.271008: + and the

Hello, I am having trouble getting the curlPerform function to authenticate using the .netrc file. From the documentation I've read it certainly seems as though this function should be able to authenticate via the .netrc file. The example I am using here comes from the "R as a Web Client- the RCurl package" paper and demonstrates using the .netrc file to access the

The scenario: This is all done SIP with a VOIP provider (have to register to single IP) We have two inbound DID numbers / Accounts. We have to register each individually with the VOIP provider. I'd like inbound from each registered account (DID) to be able to come into a unique PEER or dialplan context. What matters is that the inbound call lands in the context of my choice. I've been

This time the problem is that the ssh server only sets TCP_NODELAY for interactive (tty) sessions or if X11 forwarding is enabled. Neither of which are true for the use of the sftp subsystem. This hurts upload performance for sftp/sshfs. I'm not sure why this hasn't cropped up earlier. Were there any TCP_NODELAY related changes in the sshd code recently? Is there a reason not to

I have a distributed/replicated setup with Glusterfs 3.0.2, that I'm testing on 4 servers, each with access to /mnt/gluster (which consists of all directories /mnt/data01 - data24) on each server. I'm using configs I built from volgen, but every time I access a file (via an 'ls -l') for the first time, I get all of these messages in my logs on each server: [2010-05-04 10:50:30] W

Hello again! Since there was some resistance against adding TCP_NODELAY uncontionally, I've made another patch. The new patch contains the following: * Added a NoDelay yes/no (default no) config option to ssh and sshd * Added -oNoDelay=yes to the ssh command line for sftp. * Changed the sshd subsystem config option syntax from Subsystem name path to Subsystem name options path

There are two rather clear issues with the state of authentication failure delays. First, the delay length isn't what was (presumably) intended. Second, there is a new way of doing failure delays in Dovecot 2 which was added *in addition to* the old method, rather than replacing it. As a result delays may not be the expected length and settings don't have the expected effect. First, the

Dear List Somehow I don't understand the intended work flow to have new mailboxes auto created. On login of a new user with no mailbox, I get 2014-01-09 12:53:06 imap(tester): Error: user tester: Initialization failed: Namespace '': mkdir(/var/mail/tester) failed: Permission denied (euid=1016(tester) egid=1016(tester) missing +w perm: /var/mail, we're not in group 8(mail), dir

Hi list, hi devs, On 26.11.18 16:26, Patrick Cernko wrote: > Hi list, > > I think, I found a bug in the replication setup, that drops (custom) > flags like Thunderbird labels. I have set up a simple 2 node setup to > reproduce and explain it: > > Host adove.mpi-klsb.mpg.de and bdove.mpi-klsb.mpg.de (doveconf -n > attached) have dovecot-imapd (from repo.dovecot.org)

Hi! We are pleased to release v2.3.14 of Dovecot. IMPORTANT NOTE: We have removed some components from the software, please review changelogs carefully prior upgrading. Please find source tarballs at https://dovecot.org/releases/2.3/dovecot-2.3.14.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.14.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in

Hi! We are pleased to release v2.3.14 of Dovecot. IMPORTANT NOTE: We have removed some components from the software, please review changelogs carefully prior upgrading. Please find source tarballs at https://dovecot.org/releases/2.3/dovecot-2.3.14.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.14.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images in

Hi all, I have observed with my Dovecot setup that unique failed logins cause legitimate correct logins to be slowed. I am running two servers, each with two Dovecot instances, a Proxy with Director, and a backend Dovecot. I suspect that the backend instance is throttling connections from the same IP, and because I am running a Proxy, the backend will only see either of the two server IPs. I

Hi there, Im running glusterfs version 3.1.0. The client crashed after sometime with below stack. 2011-01-13 08:33:49.230976] I [afr-common.c:2568:afr_notify] replicate-1: Subvolume 'distribute-1' came back up; going online. [2011-01-13 08:33:49.499909] I [afr-open.c:393:afr_openfd_sh] replicate-1: data self-heal triggered. path: /streaming/set3/work/reduce.12.1294902171.dplog.temp,

Hello all, this patch add APOP authentication mechanism to dovecot 1.0-test23. Please take a look. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke at donpac.ru | PGP key: wwwkeys.pgp.net -------------- next part -------------- diff -udrpN -X /usr/share/dontdiff -x Makefile dovecot-1.0-test23.vanilla/src/auth/Makefile.am dovecot-1.0-test23/src/auth/Makefile.am ---

Currently Dovecot works like this when authentication fails: - the delay is always at least auth_failure_delay seconds (default: 2s) - each failed attempt doubles the delay for that specific imap/pop3 connection (no such delays for e.g. smtp) - the delay's upper limit is 3 minutes For v2.0 I was planning on making dovecot-auth process do these checks and keeping the state in anvil

> On 23/06/2020 12:19 Joe Wong <joewong99 at gmail.com> wrote: > > > > > On Tue, Jun 23, 2020 at 5:17 PM Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > > > On 23/06/2020 12:15 Joe Wong <joewong99 at gmail.com> wrote: > > > > > > > > > Hello, I have added 'y' as nodelay in my passdb query and I

Hi list, I think, I found a bug in the replication setup, that drops (custom) flags like Thunderbird labels. I have set up a simple 2 node setup to reproduce and explain it: Host adove.mpi-klsb.mpg.de and bdove.mpi-klsb.mpg.de (doveconf -n attached) have dovecot-imapd (from repo.dovecot.org) installed on an ext4 filesystem. They only have one account "test" via /etc/dovecot/userdb

We are pleased to release first release candidate for v2.3.14. We have done changes to packaging so please give us any feedback on how it works. https://dovecot.org/releases/2.3/rc/dovecot-2.3.14.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.14.rc1.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images are not available for this release candidate. Kind regards, Aki

We are pleased to release first release candidate for v2.3.14. We have done changes to packaging so please give us any feedback on how it works. https://dovecot.org/releases/2.3/rc/dovecot-2.3.14.rc1.tar.gz https://dovecot.org/releases/2.3/rc/dovecot-2.3.14.rc1.tar.gz.sig Binary packages in https://repo.dovecot.org/ Docker images are not available for this release candidate. Kind regards, Aki

In order to test my overlapping request path for sftp on another ssh server, I downloaded ssh2 version 3.1.0 from ssh.com. Having downloaded it, I decided to study the use of TCP_NODELAY in that implementation. Here's what I found: * Both ssh2 and sshd2 has a NoDelay config option which is false by default. * The ssh2 client does not enable or disable NoDelay because of a channel