search for: timeout_msecs

Aloha, again, Timo. Concerning the problem of copying within one folder... I'm still not sure it's not a problem I created myself, but I think it's caused by the use of the buffered IO routines in ostream-file.c ... you use io_add() to schedule write operations for later while simultanously reading new chunks from the very same file. This seems to confuse dovecot and make it write

Sometimes my redis connection times out, both for pop3, imap and lmtp. I have no idea why, when I do a "doveadm quota recalc -u" it works just fine? I'm thinking the connection is lost somehow and not retried? Apr 06 15:42:00 lmtp(xxx at xxx.com): Error: redis: Lookup timed out in 30.000 secs Apr 06 15:42:00 lmtp(xxx at xxx.com): Error: Internal quota calculation error Apr 06

...it's really bad, because the mail is actually >> saved correctly, but the error is reported back to the Director, >> causing the delivery to be retried by the MTA - so the mail actually >> lands *twice* in the user's inbox. > > 1) Shrink the timeout in Redis with timeout_msecs parameter. > http://wiki2.dovecot.org/Dictionary Yea, but why is it taking 30 seconds anyway? I'll try and lower it, but I suspect I'll just get 10.000 secs errors instead? > 2) Actually it looks like the timeout handling code doesn't work at > all. It simply keeps on loggin...

...0-862.2.3.el7.x86_64 x86_64 CentOS Linux release 7.5.1804 (Core) # Hostname: xxxx auth_mechanisms = plain login digest-md5 cram-md5 base_dir = /var/run/dovecot/ default_client_limit = 20000 default_login_user = dovecot default_process_limit = 10000 dict { quota = redis:host=127.0.0.1:prefix=user/:timeout_msecs=1000 } disable_plaintext_auth = no first_valid_gid = 90 first_valid_uid = 90 imapc_features = rfc822.size fetch-headers imapc_host = xxxx imapc_user = %u lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_greeting = xxxx. login_log_format_elements = user=<%u> method=%m rip=%r...

...; # Hostname: xxxx >> auth_mechanisms = plain login digest-md5 cram-md5 >> base_dir = /var/run/dovecot/ >> default_client_limit = 20000 >> default_login_user = dovecot >> default_process_limit = 10000 >> dict { >> ? quota = redis:host=127.0.0.1:prefix=user/:timeout_msecs=1000 >> } >> disable_plaintext_auth = no >> first_valid_gid = 90 >> first_valid_uid = 90 >> imapc_features = rfc822.size fetch-headers >> imapc_host = xxxx >> imapc_user = %u >> lda_mailbox_autocreate = yes >> lda_mailbox_autosubscribe = yes &gt...

...ase > 7.5.1804 (Core) > # Hostname: xxxx > auth_mechanisms = plain login digest-md5 cram-md5 > base_dir = /var/run/dovecot/ > default_client_limit = 20000 > default_login_user = dovecot > default_process_limit = 10000 > dict { > quota = redis:host=127.0.0.1:prefix=user/:timeout_msecs=1000 > } > disable_plaintext_auth = no > first_valid_gid = 90 > first_valid_uid = 90 > imapc_features = rfc822.size fetch-headers > imapc_host = xxxx > imapc_user = %u > lda_mailbox_autocreate = yes > lda_mailbox_autosubscribe = yes > login_greeting = xxxx. > login_...

Hi, I maintain Kodi[1] in RPMFusion[2] and the latest version of Kodi, 18.0, is crashing when trying to browse the SMB network. The previous version, 17.x, worked fine. The backtrace shows that Samba was not able to open /dev/urandom, which can't be true and must be masking another issue. The issue occurs on any Fedora 28 or 29 system (multiple user reports[3]). SELinux is disabled and

...gt; auth_mechanisms = plain login digest-md5 cram-md5 >>> base_dir = /var/run/dovecot/ >>> default_client_limit = 20000 >>> default_login_user = dovecot >>> default_process_limit = 10000 >>> dict { >>> ? quota = redis:host=127.0.0.1:prefix=user/:timeout_msecs=1000 >>> } >>> disable_plaintext_auth = no >>> first_valid_gid = 90 >>> first_valid_uid = 90 >>> imapc_features = rfc822.size fetch-headers >>> imapc_host = xxxx >>> imapc_user = %u >>> lda_mailbox_autocreate = yes >>>...

...out> #9 0x000055c930e9b423 in auth_request_proxy_host_lookup (callback=0x55c930e9cab0 <auth_request_handler_proxy_callback>, host=0x55c930eca584 "", request=0x55c932881628) at auth-request.c:2584 dns_set = {dns_client_socket_path = 0x55c930ec5eaf "dns-client", timeout_msecs = 10000, idle_timeout_msecs = 0, ioloop = 0x0, event_parent = 0x0} value = <optimized out> secs = 32551 #10 auth_request_proxy_finish (request=request at entry=0x55c932881628, callback=callback at entry=0x55c930e9cab0 <auth_request_handler_proxy_callback>) at auth-reques...

Hi, currently we deploying Dovecot as imap/pop3 proxy. Every few minutes some panic/assert occurred (we connect roughly 7k - 8k user at one imap proxy with a connection rate of 200/s). We activate core dumps. Concerning the sensitive information in the dump we would prefer to not share the dump (e.g. i found our ssl private key in the dump). Log/Stack trace: Mar 30 15:54:06 imap16 dovecot: