similar to: Upgrade Dovecot from 2.1.17 to 2.2.13 lmtp child killed with signal 6

I do always get a panic on service lmtp, while receiving a mail by postfix through always_bcc, containing an attachment. If the bcc recipient would be supplied by a small delay, I would say that the panic wouldn't occur, but I don't know how to verify this. dovecot is configured with 'mail_attachment_dir' and the public namespace location is sdbox dovecot log: Aug 6 14:18:02

Hello, a colleague found some strange messages in the logs: Oct 27 13:08:43 mail postfix/qmgr[1618]: E83C8180F56: from=<user1 at domain.de>, size=298937, nrcpt=2 (queue active) Oct 27 13:08:43 mail dovecot: lmtp(6740): Connect from local Oct 27 13:08:43 mail dovecot: lmtp(user2 at domain.de): gYFbBEdpL1ZUGgAA0nA0dQ: message-id=<035901d110b0$3929bc20$ab7d3460$@domain.de>: saved mail

Hey guys, overall I have an working dovecot replication between 2 servers running on amazon cloud. Sadly I had some messages that my server ran out of memory. After investigating a little bit further I realized that some mails didn't got replicated, but I'm not sure if this was related to the memory exhaust. I was expecting that the full-sync would catch them up but sadly it's not.

Hi, I'm currently trying the 3.2 version of winbindd (pam + nss + winbindd). I would like to loging with the userPrincipalName on ? Win 2k3 but I can't. Winbindd retrun NT_STATUS_INVALID_PARAMETER_MIX (PAM: 4) Any idea winbindd --version output : Version 3.2.0pre2-GIT--e 85eec1d-test My smb.conf file : [global] security = ads realm =

Gents, I've just upgraded to the latest build of dovecot , now lmtp delivery process panics for just one user Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev at bgoperator.com): Panic: file str.c: line 22 (str_new_const): assertion failed: (str[len] == '\0') Nov 10 15:36:49 mx10 dovecot: lmtp(oleg.vasilyev at bgoperator.com): Panic: file str.c: line 22 (str_new_const):

root at mx10:~# doveadm force-resync -u oleg.vasilyev at bgoperator.com noreply-05-08-2015 doveadm(oleg.vasilyev at bgoperator.com): Warning: fscking index file /srv/vmail/current/bgoperator.com/oleg.vasilyev/storage/dovecot.map.index doveadm(oleg.vasilyev at bgoperator.com): Warning: mdbox /srv/vmail/current/bgoperator.com/oleg.vasilyev/storage: rebuilding indexes doveadm(oleg.vasilyev at

On 13/04/16 06:41, Timo Sirainen wrote: > On 09 Apr 2016, at 21:48, Hugh Bragg <hughbragg at dodo.com.au> wrote: >> I'm repeatedly getting this error: >> >> Apr 07 04:37:27 imap(mymail at address): Panic: file mail-search.c: line 84 (mail_search_arg_init): assertion failed: (arg->initialized.keywords == NULL) >> Apr 07 04:37:27 imap(mymail at address):

Mar 19 16:54:37 lmtp(xxxx at xxx.xxx): Panic: file file-lock.c: line 269: unreached Mar 19 16:54:37 lmtp(xxxx at xxx.xxx): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x35f647e07a] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f647e0e6] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f647d4ac] -> /usr/lib/dovecot/libdovecot.so.0 [0x35f6481edf] ->

2.2.25 (also happens on 2.2.24). Happens every time I try to make deliver and only for this user: Jul 14 09:52:02 mbox dovecot: lmtp(25601): Connect from local Jul 14 09:52:02 mbox dovecot: lmtp(powiadomienia): session=<CRU2EaJEh1cBZAAALZVUYQ>, Error: Index /var/mail/powiadomienia/dovecot.index: Lost log for seq=1009 offset=40: Missing middle file seq=1009 (between 1009..4294967295) Jul 14

On Tue, 2020-03-31 at 09:06 +0300, Aki Tuomi wrote: > > > > On 30/03/2020 22:11 Ben Mulvihill <ben.mulvihill at gmail.com> wrote: > > > > ? > > I am trying to backup a gmail account (not the one I am writing > > from) > > to dovecot, using doveadm-backup and imapc, but am having ssl > > connection problems. > > > > ted at

Do you have a huge >4GB dovecot.index.cache file? > On 17 Nov 2015, at 13:04, Sergey Schwartz <sergey.schwartz at bgoperator.com> wrote: > > Gentlemen, > > imap hits the same problem > > Nov 17 14:02:06 mx10 dovecot: imap(oleg.vasilyev at bgoperator.com): Panic: file mail-index-util.c: line 37 (mail_index_uint32_to_offset): assertion failed: (offset <

Hello, I'm trying to figure out if this is a configuration issue or an actual bug. Dovecot does start, but if anybody tries to log in or if you run sievec you get an assertion fail and a coredump. --- sievec(root): Panic: file mail-namespace.c: line 709 (mail_namespace_find): assertion failed: (ns != NULL) sievec(root): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9c3a2)

Thanks. Assuming that the IMAP mail directory for the account affected is under /home/xyz/mail, are you talking about the contents of the index directory, excluding the log file therein? On Wed, Nov 28, 2018 at 2:29 PM Thomas Durand <tom at rezoo.org> wrote: > Hi, > > I had the similar messages after an upgrade then downgrade. I was able to > fix by removing all indexes files.

And can you provide dovecot --version too, please. Aki > On 25 July 2018 at 09:18 Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > Hi! > > Which debian release is this? > > Aki > > > On 25 July 2018 at 05:18 Jakobus Sch?rz <jakobus.schuerz at ebcont.com> wrote: > > > > > > Hi There! > > > > I run into this problem

This happening when my Thunderbird client is trying to establish a connection with a Dovecot server. Some background first: 1) I am running Thunderbird 6.20.1 from a Linux client. 2) Other clients (e.g. Maildroid in my Android phone) do not have any issues. 3) The Dovecot software is version 2.2.9, running in a Linux server. 4) This may be the root of the problem: at some point, the

I have the following in my log: Mar 21 14:46:59 bubba dovecot: replicator: Panic: data stack: Out of memory when allocating 1073741864 bytes Mar 21 14:46:59 bubba dovecot: replicator: Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x97c90) [0x7f4638a7cc90] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x97d6e) [0x7f4638a7cd6e] ->

Hello, I am running dovecot 2.2.34 (874deae), on Debian stable, from backports. I just tried the master account, and although everything worked in the email client, I had logs in the error logs: > imap(mirina): Panic: file mail-index-sync.c: line 413 > (mail_index_sync_begin_to2): assertion failed: (!index->syncing) > Nov 08 22:06:24 osaka dovecot[1450]: imap(mirina): Error: Raw

Hello Dovecot users, Last time I had a few stupid problems in the releases, so I'll follow Timo's example and I release an RC first. The highlights include the implementation of the index and metadata extensions. Quite a few bugs are fixed as well. Changelog v0.4.7: * editheader extension: Made protection against addition and deletion of headers configurable separately. Also, the

Hello Dovecot users, Last time I had a few stupid problems in the releases, so I'll follow Timo's example and I release an RC first. The highlights include the implementation of the index and metadata extensions. Quite a few bugs are fixed as well. Changelog v0.4.7: * editheader extension: Made protection against addition and deletion of headers configurable separately. Also, the

Hi There! I run into this problem with virtual Mailboxes on release-2.3.2 (and also in master and in older versions of dovecot) I added the core-file. Jul 25 04:11:29 aldebaran dovecot[10573]: imap(jakob)<11292><rg2GZclxHaPAqADc>: Panic: Leaked view for index /var/lib/dovecot/db/indexes/Maildir/jakob/&ANY-BB/dovecot.index: Opened in index-storage.c:338 Jul 25 04:11:29