similar to: 2.0.7 (a131a498731f): Core Dump on parsing Config

after aptitude upgrade it segfaults. syslog: Nov 30 15:42:05 serv dovecot: master: Dovecot v2.0.7 (a131a498731f) starting up (core dumps disabled) Nov 30 15:42:05 serv kernel: [ 50.920530] dovecot[1474]: segfault at 0 ip 0804fa9c sp bf87ba80 error 4 in dovecot[8048000+c000] Nov 30 15:42:05 serv kernel: [ 50.921140] dovecot[1475]: segfault at 0 ip 0804fa9c sp bf87bab0 error 4 in

Since updating to the latest HG these errors occur. Nothing else changed in the config: $ dovecot --version 2.2.beta1 (62a930eb22b5) ==> /var/log/dovecot/dovecot.log <== Feb 18 09:47:32 spectre dovecot: lmtp(14340): Connect from local Feb 18 09:47:32 spectre dovecot: lmtp(14340, tlx at leuxner.net): Error: mkdir_parents(/var/vmail/domains/leuxner.net/tlx/mdbox) failed: File exists Feb 18

Please find Backtrace for LMTP Core Dump below: [...] ==> /var/log/dovecot/dovecot.log <== Nov 1 11:16:14 spectre dovecot: lmtp(17245): Connect from local Nov 1 11:16:14 spectre dovecot: lmtp(17245): Fatal: master: service(lmtp): child 17245 killed with signal 11 (core dumped) ==> /var/log/mail.log <== Nov 1 11:16:14 spectre postfix/lmtp[17204]: 3Xsj4G11MrzNY: to=<tlx at

Latest Dovecot Auto-Build 2.1.rc1-0~auto+42 (056934abd2ef) fails to include global Sieve Scripts. Not sure this is specific to Stephan's Repository. Rolling back to older version restores functionality. ==> /var/log/dovecot/dovecot.log <== Dec 22 12:13:52 spectre dovecot: lmtp(32246): Connect from local Dec 22 12:13:52 spectre dovecot: lmtp(32246, tlx at leuxner.net): Error:

Dec 4 07:27:41 spectre dovecot: imap-login: Login: user=<tlx at leuxner.net>, method=PLAIN, rip=84.58.184.122, lip=1.2.3.4, mpid=30987, TLS Dec 4 07:27:42 spectre dovecot: imap-login: Login: user=<tlx at leuxner.net>, method=PLAIN, rip=84.58.184.122, lip=1.2.3.4, mpid=30990, TLS Dec 4 07:27:42 spectre dovecot: master: Error: service(imap): child 30990 killed with signal 11 (core

Latest HG dies upon client login. Rolling back to 2.0.rc2 (7dd7adba1c9e) restores functionality. Dump attached. Jul 17 07:31:04 spectre dovecot: master: Dovecot v2.0.rc2 (875598cd7e26) starting up [?] Jul 17 07:32:06 spectre dovecot: master: Error: service(imap): child 29169 killed with signal 11 (core dumped) GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+:

Hi, when trying to backup mailboxes I noticed some hiccups when the ACL plugin is enabled. It works fine with ACL disabled: $ doveadm -o plugin/quota= backup -u tlx at leuxner.net mdbox:/home/backups/tlx/mdbox However, enabled (and w/ a mailbox actually using ACLs) the following error occurs: $ doveadm -o plugin/quota= backup -u tlx at leuxner.net mdbox:/home/backups/tlx/mdbox dsync(tlx at

Hi, the latest HG of Dovecot 2.0 throws a warning when creating a new mailbox inside an INBOX with 'mdbox' format. It does however create the mailbox correctly. ==> /var/log/dovecot.log <== Apr 24 14:35:09 spectre dovecot: imap(tlx at leuxner.net): rename(/var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity, /var/vmail/leuxner.net/tlx/mdbox/dovecot-uidvalidity) failed: No such

* 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

With the latest HG Quota code cleanups there seem to be hicups with Sieve/LMTP. Please see excerpt below. Sieve processing fails, though quota is within limits: [...] sieve: info: started log at Apr 05 09:06:36. error: msgid=<20110405070128.315AF3173F0 at eul0300650.eu.verio.net>: failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full). [...] Apr 5

Hi, with 'changeset 10910' the Auth master process is running as 'default_internal_user' now (dovecot). This requires permissions tuning for 'passwd-files' at least, while other plugins would run in a different user context, 'vmail' in my setup. I see that this may be safer, just wondering how to streamline the config: [20:27] root spectre:/var/vmail/conf.d# l

Hi! I wrote a little something about how to prevent delivery to mailboxes over quota while still being in the SMTP dialogue: http://sys4.de/en/blog/2013/04/08/postfix-dovecot-mailbox-quota/ (Postfix/Dovecot-2.2) -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter,

I have Dovecot2 auth setup to run as user = doveauth group = dovecot configured in, vi conf.d/10-master.conf ... service auth { unix_listener /var/spool/postfix/private/auth { user = postfix group = postfix mode = 0660 } user = doveauth group = dovecot } service auth-worker { user = doveauth group = dovecot } ... When I start Dovecot, ls -al

Hi Timo, today I've started Dovecot v2.2.rc2 (976bf9e69367) for the first time. /var/log/mail.log: Mar 3 14:28:33 mail dovecot: master: Dovecot v2.2.rc2 (976bf9e69367) starting up Mar 3 14:28:38 mail dovecot: master: Error: service(tcpwrap): command startup failed, throttling for 2 secs Mar 3 14:28:38 mail dovecot: tcpwrap: Fatal: master: service(tcpwrap): child $PID killed with signal

On Mon, Nov 21, 2016 at 6:20 PM, Fred Turner <fred at c5consulting.net> wrote: > Yeah, I gradually figured out it wouldn't work yesterday when delving back > into this and testing. No separate quotas per namespaces until 2.1 or > something, I think? > > So, got any suggestions on getting it to work with v2.x? I found an old > thread from 2013 by Andreas (I think?) and

Hi Timo, some imap processes seems to have some problems. Regards, Pascal -------------- next part -------------- Core was generated by `dovecot/imap'. Program terminated with signal 6, Aborted. #0 0x00007fbf87b25475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt full #0 0x00007fbf87b25475 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1

Hi, I am a long-time dovecot user/admin for my family mail server, but I had ventured into configuring replication only recently and I am not sure about how it should work and what are the good practices. My intent for replication was to have another instance to switch to in a short time if something fails. I have daily backups, but it will take much more time to rebuild and restore than just to

Each time a mail message is delivered to a mailbox records like the following appear in /var/log/dovecot.warn: Jul 29 10:02:05 iris dovecot: lmtp(29320, jax at XXX.com): Error: file dict commit: file_dotlock_open(/var/vmail/XXX.com/jax/home/maildir/dovecot-quota) failed: No such file or directory Jul 29 10:02:05 iris dovecot: lmtp(29320, jax at XXX.com): Error: file dict commit:

Hi all! I am a long-time dovecot user/admin on my home server, but only recently tried to configure replication. Everything seems to work except sieve scripts replication. When I upload new one on the server A, it does not replicate to server B, even if it seemingly tries to, according to debug logs. The log antry says: Replication requested by 'sieve_storage_sync_transaction_begin',

Hi Thomas, thank you for your help. This is very strange that it wont work here. can you doveconf -n the relevant parts especially mail_plugins= and plugin { } i think i have misconfigured something :( Regards, Daniel