similar to: Dovecot 2.0.7 (8793036f6de8) seems to miss some defaults for vsz_limit

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:

Hello, I would like to ask on suggested vsz_limit values. Is there any way of calculating such values? How should we determine them? I don't want to risk wrong values (and possible errors) on a production system, if I upgrade to 2.0.16 where vsz_limit values are enforced (I read release notes)! If there is no standard way of calculation, could someone please check the following info and

Hi, Lately I've seen a few examples of users hitting the vsz_limit (usually trying to "delete" mails i Spam/Junk by moving them to Trash with a large dovecot.index.cache - which resulted in mails left/leaked in the tmp directory of Trash. Sometimes it seems the client gets into a state were it repeatedly tried to sync the client and server state so it does it again and again,

Hi all, when hardening dovecot against the POODLE vulnerability, we followed the advise to disable SSL2 and SSL3 but this is giving problems with some email clients (claws-mail). ssl_protocols = !SSLv2 !SSLv3 results in the following error: dovecot: pop3-login: Disconnected (no auth attempts in 1 secs): user=<>, rip=XXX, lip=XXX, TLS handshaking: SSL_accept() failed: error:1408A0C1:SSL

You could also add it as setting for the fts_xapian plugin parameters? Aki > On 04/11/2020 08:42 Joan Moreau <jom at grosjo.net> wrote: > > > For machines with low memory, I would like to detect how much ram remains available before starting indexing a mail, so I can commit everything on disk before the ram is exhausted (and break the process) > I tried to put a

Duh... src/lib/restrict-process-size.h Should be in the installed include files as well, /usr/include/dovecot/restrict-process-size.h Aki > On 06/11/2020 15:56 Joan Moreau <jom at grosjo.net> wrote: > > > Hello > I can't find "src/lib/restrict.h" . Is it in dovecot source ? > > > On 2020-11-06 13:20, Aki Tuomi wrote: > > Seems I had

> On 04/11/2020 05:19 Joan Moreau <jom at grosjo.net> wrote: > > > Hello > I am looking for help around memory management > 1 - How to get the current value of "vsz_limit" from inside a plugin (namely https://github.com/grosjo/fts-xapian/ ) , especially for indexer-worker > 2 - Is there a macro or function in dovecot to get the remaining free memory from this

Seems I had forgotten that you can use src/lib/restrict.h, in particular, restrict_get_process_size() to figure out the limit. You can combine this with getrusage to find out current usage. Aki > On 06/11/2020 13:26 Joan Moreau <jom at grosjo.net> wrote: > > > yes, will do so. > It would be nice however to be able to access the actual dovecot config from the plugin side

How about you try moving the mail into another folder on daily basis, this way the INBOX would stay nice and empty. doveadm move -u archive at company.com Archive MAILBOX INBOX SENTBEFORE todays-date Aki On 16.02.2018 06:19, Terence Lau wrote: > > Bump. > > ? > > Any advice would be most appreciated. > > ? > > Thanks. > > ? > > *From:*Terence Lau >

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)

Hi, We've been getting these types or errors for quite a while now ... Fatal: master: service(lmtp): child 63477 returned error 83 (Out of memory (service lmtp { vsz_limit=4096 MB }, you may need to increase it) ... and these errors have been decreasing in occurrence as we increased the default_vsz_limit. Which is good but I would like to get some advice on how I could possibly eliminate

http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz.sig So it's time for the first alpha version of Dovecot v2.1. There are no huge intrusive changes, so I expect v2.1.0 to be released this year (maybe even in a few months?) The biggest changes are related to full text search handling. I'll probably still make

http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz http://dovecot.org/releases/2.1/alpha/dovecot-2.1.alpha1.tar.gz.sig So it's time for the first alpha version of Dovecot v2.1. There are no huge intrusive changes, so I expect v2.1.0 to be released this year (maybe even in a few months?) The biggest changes are related to full text search handling. I'll probably still make

Hello Timo and dovecot teamwork, We have dovecot 2.0.10 installed with this configuration: # dovecot -n # 2.0.10: /usr/local/dovecot/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-92.1.18.el5 x86_64 Scientific Linux SL release 5.2 (Boron) auth_cache_size = 500 k auth_cache_ttl = 1000 secs disable_plaintext_auth = no first_valid_uid = 501 lock_method = dotlock mail_fsync = always mail_gid = vmail

I have noticed a difference in the behavior of ACLs. When used in a MUA the following global ACL works fine and has the desired effect - new mailboxes can be created by a user being part of the 'PublicMailboxAdmins' group: [ global-acl: ] INBOX owner lrwstiekxap Public/* group=PublicMailboxAdmins lrwsipk Public/* anyone lr Public/* authenticated lrws Creating the same mailbox via

* Timo Sirainen <tss at iki.fi> 2015.09.08 12:20: > How does the PublicMailboxAdmins group get set? Looks to me like the problem is that it's not getting set to doveadm. Here's an easy way to check if that's the problem or something else: http://hg.dovecot.org/dovecot-2.2/rev/500e8dd7a389 > > If that doesn't help: Show your full doveconf -n, set auth_debug=yes and

# 2.2.devel (c73322f): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.devel (fac92b5) # OS: Linux 3.16.0-4-amd64 x86_64 Debian 8.6 ==> /var/log/dovecot/dovecot.log <== Oct 15 09:50:15 nihlus dovecot: lmtp(11447): Connect from local Oct 15 09:50:15 nihlus dovecot: lmtp(tlx at leuxner.net): Panic: file lda-sieve-plugin.c: line 447 (lda_sieve_execute_scripts): assertion failed: (script !=

Let me say this is a rather cosmetic issue, but it appears with the latest commits (around 2.2.5 release) the scheme of 'Received' headers has changed for LMTP: 1) Inet socket: Return-Path: <dfn-adv-bounces at dfn-cert.de> Delivered-To: <tlx at leuxner.net> Received: from spectre.leuxner.net ([188.138.0.199]) by spectre.leuxner.net (Dovecot) with LMTP id

Hi, not sure what is wrong with the mail, but the Dovecot LMTP won't accept it. This is actually the first ever occurrence, so I'm attaching the evidence for further diagnosis: [?] Nov 26 18:01:49 spectre dkim-filter[1723]: A7BEA4086: no signature data Nov 26 18:01:49 spectre postfix/qmgr[6175]: A7BEA4086: from=<bounce-1841919-268661 at news.juno.co.uk>, size=131577, nrcpt=1

Hi, converted my personal mailbox from 'maildir' to 'mdbox' for testing today: # dsync convert -u user at domain mdbox:~/mdbox Set mail location to mdbox in 'mail.conf' and restarted server: mail_location = mdbox:~/mdbox Dovecot panicked instantly upon login with different clients. Tried to disable several plugins to no avail: Feb 28 14:43:02 spectre dovecot: