similar to: No Dovecot 2.2.9 on OpenBSD 5.4 amd64

Hi I first let base_dir = with it's default value of /var/dovecot. I changed my mind and now I have doveconf -n # 2.1.17: /etc/dovecot/dovecot.conf # OS: OpenBSD 5.4 amd64 ffs base_dir = /var/run/dovecot/ After a few days, imap clients couldn't login. Here the problem Dec 04 17:03:16 imap-login: Fatal: Corrupted SSL parameters file: /var/dovecot/ssl-parameters.dat Dec 04 17:03:16

When I do a ./configure in dovecot (2.2.1) I get this notice (first line): configure: WARNING: you should use --build, --host, --target Then, much later on: checking sys/ucred.h presence... yes configure: WARNING: sys/ucred.h: present but cannot be compiled configure: WARNING: sys/ucred.h: check for missing prerequisite headers? configure: WARNING: sys/ucred.h: see the Autoconf

FreeBSD-12 Dovecot-2.3.5 I am having problems with one use Mar 25 21:30:12 imap(gau.mon at crownkenya.com)<91364><U7qCZO+ECfCaRh6E>: Fatal: master: service(imap): child 91364 killed with signal 6 (core dumped) Mar 25 21:30:14 imap(gau.mon at crownkenya.com)<2381><moHYZO+EDvCaRh6E>: Fatal: master: service(imap): child 2381 killed with signal 6 (core dumped) Mar 26 06:29:26

Le 13/02/2015 16:19, Casey Stone a ?crit : > On Feb 5, 2015, at 10:39 PM, Casey Stone <tcstone at caseystone.com> wrote: > >> Hello: >> >> I've been looking forward to getting my mail server up to Dovecot 2.2+ to be able to use the sync mechanism. I run my own mail server just for myself, with a few different accounts, and want to keep a master and backup server

Hello, I though this bug should be reported, although there is workaround already made and in use. Dovecot 2.2.10 crashes into out of memory error when there is defined system users (userdb+passdb) and own virtual users (userdb+passdb). Removing either one solves the issue and Dovecot is working as it should. When memory leak (I replaced pw_init and gr_init with the version that is found

Hello: I've been looking forward to getting my mail server up to Dovecot 2.2+ to be able to use the sync mechanism. I run my own mail server just for myself, with a few different accounts, and want to keep a master and backup server in sync. I'm running the Ubuntu server 14.04.1 mail stack which features Dovecot 2.2.9 (and Postfix). My setup is to use system users (userdb passwd /

Hi, we run Dovecot 2.2.13 on Debian Wheezy with a couple thousand mailboxes. We have two users that repeatedly trigger an OOM condition with IMAP. Jun 23 12:53:21 lxmhs74 dovecot: imap(USER): Fatal: pool_system_realloc(268435456): Out of memory Jun 23 12:53:21 lxmhs74 dovecot: imap(USER): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x6c15f) [0x7f11766cc15f] ->

Le 16/02/2015 20:40, Casey Stone a ?crit : > On Feb 13, 2015, at 3:42 PM, FUSTE Emmanuel <emmanuel.fuste at thalesgroup.com> wrote: > >> Le 13/02/2015 16:19, Casey Stone a ?crit : >>> On Feb 5, 2015, at 10:39 PM, Casey Stone <tcstone at caseystone.com> wrote: >>> >>>> Hello: >>>> >>>> I've been looking forward to

Do these errors indicate a memory leak? I see them in the logs a few times per day on each of our servers, running CVS dovecot-20060924... Oct 8 22:21:30 mail38b dovecot: auth(default): block_alloc(): Out of memory Oct 8 22:21:30 mail38b dovecot: child 6391 (auth) returned error 83 (Out of memory) Oct 9 20:05:05 mail38b dovecot: auth(default): pool_system_realloc(): Out of memory Oct 9

Hello, I have here a problem with managesieve. With the login about webmail (roundcube) comes here in the log: --snip dovecot: managesieve-login: Fatal: pool_system_realloc(4294967296): Out of memory dovecot: managesieve-login: Fatal: master: service(managesieve-login): child 10157 returned error 83 (Out of memory (service managesieve-login { vsz_limit=1024 MB }, you may need to increase it))

Hello! I have used Dovecot for more than a year without problems, but today it just crashed with this message: dovecot: Apr 09 21:23:38 Panic: file mempool-system.c: line 104 (pool_system_realloc): assertion failed: (old_size == (size_t)-1 || mem == NULL || old_size <= malloc_usable_size(mem)) dovecot: Apr 09 21:23:38 Error: Raw backtrace: /usr/local/sbin/dovecot [0x805757c] ->

We're running 2.2.24 with fts_lucene and I wonder why indexer-working can be out-of-memory even with vsz_limit=750 MB ?! Peer May 15 12:14:51 dobby4 dovecot: indexer-worker(user at example.com): Fatal: pool_system_realloc(134217728): Out of memory May 15 12:14:51 dobby4 dovecot: indexer-worker(user at example.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xaa4b7)

I thought I had cleared out the corruption I had before - perhaps I was mistaken. What steps should I take to help locate these issues? Currently using 2.1rc1. I see the following errors in my logs, including out of memory and message size issues (at 15:30): Jan 4 05:17:17 bubba dovecot: indexer-worker(user1 at domain.com): Error: Raw backtrace:

Hello, I've upgraded our servers and now dovecot seems to be running out of memory when accessing my own mailbox (and only mine, which is in a way pretty fortunate): dovecot: imap(abelard-a): Error: mmap() failed with file /vmail/a/b/abelard-a/dovecot.index.cache: Cannot allocate memory imap(abelard-a): Fatal: pool_system_realloc(131072): Out of memory

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 23 Jun 2014, Bernhard Schmidt wrote: > > we run Dovecot 2.2.13 on Debian Wheezy with a couple thousand mailboxes. > We have two users that repeatedly trigger an OOM condition with IMAP. Do those users have mailboxes extra ordinary large or is one message of them extra ordinary large? Jun 23 12:53:21 lxmhs74 dovecot: imap(USER):

I encountered this error on FreeBSD 9.3 with dovecot2-2.2.13_3 Short version; vsz_limit is 18,447 PB and it ran out of RAM. Suggestions for change? Sep 6 03:39:32 mailjail dovecot: imap(dan): Panic: file imap-fetch.c: line 556 (imap_fetch_more): assertion failed: (ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock == cmd) Sep 6 03:39:32 mailjail dovecot:

Dovecot-2.3.5, FreeBSD-12 (amd64), I will wait to see coredumps after setting up things to allow it. Mar 24 20:56:08 imap(john.doe at crownkenya.com)<82746><wg80zdqEy+eaTXHr>: Panic: file mempool-system.c: line 137 (pool_system_realloc): assertion failed: (old_size == (size_t)-1 || mem == NULL || old_size <= malloc_usable_size(mem)) Mar 24 20:56:08 imap(john.doe at

On Sun, Sep 27, 2015 at 12:40:40PM -0600, The Doctor wrote: > Timo, > > I have to test something on one of the BSD, namely related to src/lib/net.c . > FYI make sys/ucred.h reads #ifndef _SYS_UCRED_H_ #define _SYS_UCRED_H_ /* * Credentials. */ struct ucred { u_int cr_ref; /* reference count */ uid_t cr_uid; /* effective

New nbdkit_peer_pid, nbdkit_peer_uid and nbdkit_peer_gid calls can be used on Linux (only) to read the peer PID, UID and GID from clients connected over a Unix domain socket. This can be used in the preconnect phase to add additional filtering. One use for this is to add an extra layer of authentication for local connections. A subsequent commit will enhance the now misnamed nbdkit-ip-filter to

hi, Solaris doesn't have getpeereid() or SO_PEERCRED. However, getpeerucred() is perfectly usable for that; and it's in Solaris 10 and OpenSolaris. So, ssh-agent(1) security there so far depends only on permissions of the socket directory and with this patch it checks peer's credentials, too. I patched following files using a snapshot from 20060921: openssh/config.h.in