similar to: dovecot-lda crash after upgrade to 2.2.28

Hi, I've been trying to get a Public Folder namespace working, so far without any luck. I've tried in my home folder, outside my home folder, with and without acl. I can see the namespace (PUBLIC) in Roundcube, but that's as far as I get. I've put a .FirstFolder under the location, but it never appears. I've added dirs cur, new, and tmp but no difference. No hints from

I have been reading up on TLS and Dovecot and came across this URL: https://www.weakdh.org/sysadmin.html which recommended these settings for Dovecot. I would like to know if they are correct? Some much documentation on the web is pure garbage. Dovecot These changes should be made in /etc/dovecot.conf Cipher Suites

There is no error in the server logs. I checked those particular folders on the server and they don?t seems to have anything special about them, like permission or etc. Yes, calling STATUS on those particular folders returns the status. The folders can be opened and they have emails in them so nothing special about those folders. # 2.3.5 (513208660): /etc/dovecot/dovecot.conf # OS: Linux

my ERROR.log show: [2020-06-28 07:54:24] INFO main/main.c Icecast 2.4.4 server started [2020-06-28 07:54:24] DBUG yp/yp.c Updating YP configuration [2020-06-28 07:54:24] INFO yp/yp.c YP update thread started [2020-06-28 07:54:24] INFO connection/connection.c SSL certificate found at icecast.pem [2020-06-28 07:54:24] INFO connection/connection.c SSL using ciphers

You probably need to increase ulimit -n Aki On 23.08.2017 14:10, Patrick Westenberg wrote: > Hi @all, > > after re-installing one of my two frontends/proxy-servers I get the > following error messages after some time (sometimes after 1h, sometimes > after 24h): > > > 11:23:55 imap-login: Error: socketpair() failed: Too many open files > 11:23:55 imap-login: Error:

Hello, are you using systemd? May be you have to edit unit-file for dovecotservice and increase filelimit LimitNOFILE=infinity Hajo Am 23.08.2017 um 14:21 schrieb Patrick Westenberg: > I haven't done this on the old, working machine. > > So there must be a difference between Debian 7 and 9 how open files are > handled? > > Regards > Patrick > > > > Aki

On Sat, 2018-12-08 at 11:03 +0100, Marco Fioretti wrote: > Greetings, > I have had to reinstall my email server on another Linux (centos 7.6) > VPS, with a newer version of dovecot, other software and a brand new > letsencrypt certificate just for email withpostfix and dovecot (that > certificate works fine with postfix). Output of dovecot --version and > dovecot -n on the new

On 10 Jun 2020, at 23:19, @lbutlr <kremels at kreme.com> wrote: > On 10 Jun 2020, at 23:18, @lbutlr <kremels at kreme.com> wrote: >> IF it?s not permissions you need to provide doveconf -n output. Bloglines for any fall, panic, or error level events at a minimum. > > Apologies, I did not see the attachments. Will look on a real screen later. Looks like your main

Am 11.06.20 um 18:08 schrieb @lbutlr: > On 10 Jun 2020, at 23:19, @lbutlr <kremels at kreme.com> wrote: >> On 10 Jun 2020, at 23:18, @lbutlr <kremels at kreme.com> wrote: >>> IF it?s not permissions you need to provide doveconf -n output. Bloglines for any fall, panic, or error level events at a minimum. >> >> Apologies, I did not see the attachments. Will

I haven't doveadm logs in /var/log/. Are they default in another place or maybe should I turn on something? My config (default passdb block and auth_mechanisms, nothing more changed): root at vps342401:/etc/dovecot# doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-100-generic x86_64 Ubuntu 14.04.5 LTS auth_mechanisms = plain login listen = *,[::] log_timestamp = "%Y-%m-%d

Hi all; I've upgraded a ring of dovecot directors from 2.2.15 to 2.2.36. After the upgrade I've got some instability: a few time per day per server, seemly at random, the auth process stop responding and the clients cannot authenticate any more: Sep 6 14:45:51 imap-front13 dovecot: pop3-login: Warning: Auth process not responding, delayed sending initial response (greeting):

> On April 27, 2017 at 8:12 AM Poliman - Serwis <serwis at poliman.pl> wrote: > > > Hi, > To default dovecot.conf file I added (based on found documentation): > ssl = required > disable_plaintext_auth = yes #change default 'no' to 'yes' > ssl_prefer_server_ciphers = yes > ssl_options = no_compression > ssl_dh_parameters_length = 2048 >

> For more clarity I also attach the content of > "/etc/dovecot/conf.d/15-mailboxes.conf" > > > # mailbox Junk { > # special_use = \Junk > # } > # mailbox Trash { > # special_use = \Trash > # } > mailbox INBOX/Junk { > auto = subscribe > special_use = \Junk > } > mailbox INBOX/Trash { > auto = subscribe >

I'm trying to setup our first director server. Trying to keep the initial config simple really as just maybe a proof of concept and its got me pulling my hair out today. Initially I just tried to convert one of my already running IMAP servers to be a director just to see if I could do it. I modified the configs as it appeared they needed based on: https://wiki2.dovecot.org/Director

Hello! I run dovecot for many years now, but today it ran into a bug I've never seen before. Searching the archives, this bug seems to occur very seldom. The current server installation & configuration is running since mid 2015, uptime of the server today is more than two months. It is a virtual machine in a data center, debian 7 / reiserfs, 'dovecot -n' output below. Just

Jan Vejvalka <jan.vejvalka at lfmotol.cuni.cz> writes: >> Mine are below and they work just fine: >> >> ssl_cipher_list = >>

On Thu, Mar 10, 2016 at 12:30 PM, Osiris <dovecot at flut.demon.nl> wrote: > On 09-03-16 13:14, djk wrote: >> On 09/03/16 10:44, Florent B wrote: >>> Hi, >>> >>> I don't see any SSL configuration option in Dovecot to disable >>> "Client-initiated secure renegotiation". >>> >>> It is advised to disable it as it can

Hey all, I'm experiencing a weird and annoying issue with my 2-node dovecot replication setup. The setup is based on virtual users in a pgsql database, which is replicated from the master to a slave node. For the mails I rely on the dovecot builtin replication which has been working great for me thus far. However I noticed something was off when looking through my journal yesterday:

Thanks for your reply; I used the defaults, both before and after the upgrade, cf. https://wiki2.dovecot.org/Upgrading/2.3 -> Setting default changes. The new defaults broke the connection. Jan > what are your settings? > > Mine are below and they work just fine: > > ssl_cipher_list = >

On 24.04.2018 00:40, Grant Keller wrote: > Hello, > > I have a new director ring I am setting up on centos 7 with dovecot > 2.3.1. I haven't been able to replecate this in testing, but as soon as > I start pushing production traffic to the new ring I see dozens of these in the > logs: > Apr 18 00:34:00 d.director.imapd.sonic.net kernel: imap-login[163107]: segfault at 10