similar to: dovecot: ssl-params

Hello, after switching from version 2.2.7 to 2.2.7 I miss the loglines which say: ssl-params: Generating SSL parameters ssl-params: SSL parameters regeneration completed The configuration has not been changed and reads: | # 2.2.7: /usr/local/dovecot/etc/dovecot/dovecot.conf | # OS: Linux 2.6.35.14-106.fc14.i686.PAE i686 Fedora release 14 (Laughlin) ext3 | auth_mechanisms = plain login |

Hello all, I've squirrelmail-webmail-1.4.22, dovecot 2.1.1, dovecot-2.1-pigeonhole-0.3.0 installed and working. But I've problems to get the avelsieve plugin for squirrelmail working with dovecot. The "Message Filters" show up in "Options" of squirrelmail, but "Could not log on to timsieved daemon on your IMAP server ........." dovecot log shows: Mar 6

Hi *, running dovecot 1.2.alpha1 I find the following messages in the log: Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): fchown(/home/Mail/steffen/subscriptions.lock) failed: Operation not permitted Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): file_dotlock_open() failed with subscription file /home/Mail/steffen/subscriptions: Operation not permitted Sep 10

Hi all, I want to use maildir++ quota with dovecot but when starting I get: > service dovecot start Starting IMAP-Service (dovecot 1.1.7) ILoading modules from directory: /usr/dovecot/lib/dovecot/imap IModule loaded: /usr/dovecot/lib/dovecot/imap/lib10_quota_plugin.so IModule loaded: /usr/dovecot/lib/dovecot/imap/lib11_imap_quota_plugin.so IModule loaded:

Hello *, strange happening yesterday. See this logfile lines: Sep 10 20:45:52 seymour ntpd[9104]: synchronized to 192.53.103.108, stratum 1 Sep 10 20:58:07 seymour ntpd[9104]: synchronized to 134.34.3.18, stratum 1 Sep 10 21:21:02 seymour dovecot: dovecot: Fatal: Time just moved backwards by 434 seconds. [ ... ] Sep 10 21:26:36 seymour ntpd[9104]: no servers reachable Sep 10 21:42:56 seymour

Hallo experts, what is the meaning of the "<" sign in config files as in ssl_key = </etc/pki/tls/private/dovecot.key ^ | ? --Frank Elsner

Based on the recent found weaknesses in DH key exchange, http://weakdh.org/ I increased ssl_dh_parameters_length to 2048 bits, and found waited for 5+ minutes for dovecot to come back online after a restart. Unless you got a fast machine, the initialization of DH parameters can exceed your patience. Regeneration may not be a problem (if ssl_parameters_regenerate=0 or if Dovecot uses old

On Tue, 12 Nov 2019 09:22:56 +0200 Aki Tuomi via dovecot wrote: > Hi! > > Can you try follow this guide to get a core dump > > https://www.dovecot.org/bugreport-mail > > then provide > > > gdb /usr/lib/dovecot/auth /path/to/core > > bt full Sorry, I'm not familiar with gdb and can only provide this # gdb /usr/local/dovecot//libexec/dovecot/auth GNU

On Tue, 12 Nov 2019 00:17:28 +0100 Frank Elsner via dovecot wrote: > On Mon, 11 Nov 2019 23:47:27 +0100 Frank Elsner via dovecot wrote: [ ... ] > I narrowed the probelem down to the warnings > > Warning: service auth { client_limit=128 } is lower than required under max. load (768) > Warning: service anvil { client_limit=256 } is lower than required under max. load (643) These

Hi! Can you try follow this guide to get a core dump https://www.dovecot.org/bugreport-mail then provide gdb /usr/lib/dovecot/auth /path/to/core bt full on it. Would help narrowing down that bug. Also doveconf -n could be useful. Aki On 12.11.2019 9.19, Frank Elsner wrote: > On Tue, 12 Nov 2019 00:17:28 +0100 Frank Elsner via dovecot wrote: >> On Mon, 11 Nov 2019 23:47:27

On 05/27/2015 09:55 AM, Rick Romero wrote: > Quoting Gedalya <gedalya at gedalya.net>: > >> On 05/26/2015 10:37 AM, Ron Leach wrote: >>> https://weakdh.org/sysadmin.html >>> >>> includes altering DH parameters length to 2048, and re-specifying the >>> allowable cipher suites - they give their suggestion. >> >> It looks like there

Quoting Gedalya <gedalya at gedalya.net>: > On 05/27/2015 09:55 AM, Rick Romero wrote: >> Quoting Gedalya <gedalya at gedalya.net>: >> >>> On 05/26/2015 10:37 AM, Ron Leach wrote: >>>> https://weakdh.org/sysadmin.html >>>> >>>> includes altering DH parameters length to 2048, and re-specifying the >>>> allowable

Quoting Gedalya <gedalya at gedalya.net>: > On 05/26/2015 10:37 AM, Ron Leach wrote: >> https://weakdh.org/sysadmin.html >> >> includes altering DH parameters length to 2048, and re-specifying the >> allowable cipher suites - they give their suggestion. > > It looks like there is an error on this page regarding regeneration. In > current dovecots

Hello, the dovecot-example.conf states: # Authentication cache size in kilobytes. 0 means it's disabled. # Note that bsdauth, PAM and vpopmail require cache_key to be set for caching # to be used. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds the cached # record is no longer used, *except* if the main database lookup returns # internal failure. We

I went from a nightly of about 20051117 or so (about alpha4 generation) to 1.0beta1 yesterday, and dovecot is now spinning the CPU furiously apparently every ~10 minutes per: Jan 18 13:04:36 server dovecot: SSL parameters regeneration completed Jan 18 13:14:14 server dovecot: SSL parameters regeneration completed Jan 18 13:24:00 server dovecot: SSL parameters regeneration completed Jan 18

Hello, dovecot-1.0.3 on Fedora 6 works perfect in general but sometimes the system becomes unresponsive and the log file shows tons of messages like this: ... imap-login: Disconnected: Shutting down: 127.0.0.1, secured ... pop3-login: Disconnected: Shutting down: aa.bb.cc.dd Restarting dovecot helps, but what's behind? What can I do to prevent this? dovecot -n output: #

Hello *, I've the following problem with dovecot 1.0.7: /var/log/messages shows | Dec 13 13:48:27 mailbox kernel: possible SYN flooding on port 143. Sending cookies. and /var/log/maillog shows (Please note: nearly the same time): | Dec 13 13:48:28 mailbox dovecot: pipe() failed: Too many open files This leads to an unresponsive mail service and requires a dovecot restart. What

Hello, I have a linux system (Ubuntu 7.04 server edition) running Postfix 2.3.8 Today i installed Dovecot through apt-get (got version 1.0.rc17 installed) and configured it to do sasl auth only, (i already have other pop3,smtp and imap servers running) following the howto's at dovecot.org The thing is that if i try to start dovecot or run dovecot -n i get this message: Error: Can't use

Hello *, I'm running dovecot 1.0.10 on a Fedora 6 with this configuration # 1.0.10: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /usr/local/dovecot/etc/mailbox.pem ssl_key_file: /usr/local/dovecot/etc/mailbox.key disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default):

On 27/05/2015 05:22, Gedalya wrote: > It looks like there is an error on this page regarding regeneration. > In current dovecots ssl_parameters_regenerate defaults to zero, and > this means regeneration is disabled. The old default was 168 hours (1 > week). > The language on http://wiki2.dovecot.org/SSL/DovecotConfiguration is > confusing and could be understood to mean that the