similar to: (message_parser_parse_next_block): assertion, failed: (ctx->input->eof)

I haven't seen this before 1.1b16, it happened to two users today while they were searching using fts. Feb 18 16:41:36 hill dovecot: IMAP(username): file buffer.c: line 288 (buffer_set_used_size): assertion failed: (used_size <= buf->alloc) Feb 18 16:41:36 hill dovecot: child 53560 (imap) killed with signal 6 I can probably narrow it down to an example mail if needed. GNU gdb 6.1.1

For quite some time I have seen dovecot imap exit with a sig11 without any other error message, but usually with the frequency of between once per week and once per day (per server). A few weeks ago I finally enabled core dumping with debug symbols and it seemed to happen less often. I finally caught a coredump that wasn't overwritten. I have no idea what on the client end may cause it,

Feb 23 20:40:36 postamt dovecot: IMAP(username): file message-parser.c: line 766 (message_parser_parse_next_block): assertion failed: (ctx->input->eof || ctx->input->closed || ctx->input->stream_errno != 0) Feb 23 20:40:36 postamt dovecot: IMAP(username): Raw backtrace: /usr/local/libexec/dovecot/imap [0x8009236d] -> /usr/local/libexec/dovecot/imap [0x80091ed8] ->

Hi all, ive seen a few segfaults in RC15. It's hard for me to reproduce but I was able to get a core when it happened with one of our customers. RC15 FreeBSD 4.10 X86 NFS/NetApp It's squirrelmail/webmail client. Can't reproduce it, cant turn on dovecot.rawlog because I dont know in advance which customer will hit this. See it about 5 times per hour, with thousands of logins per hour.

We have started seeing index corruption ever since we upgraded (we believe) our imap servers from SL6 to Centos 7. Mail/Indexes are stored on Netapps mounted via NFS. We have 2 lvs servers running surealived in dr/wlc, 2 directors and 6 backend imap/pop servers. Most of the core dumps I've looked at for different users are like "Backtrace 2" with some variations on folder path.

I have a situation where if a user is over quota and sending through postfix I get an error, now this error only happens if the user is over quota, otherwise it works with no problem. However if sending using /usr/local/libexec/dovecot/dovecot-lda it works every time even if overquota, any ideas? I just can't seem to figure this one out. TIA, Paul Using mail command Dec 21

Hi, I compressed a folder with the following script: ... for i in *.*.*; do file $i | grep bzip2 >/dev/null 2>&1 if [ $? -ne 0 ]; then echo "Compress: $i" cat "$i" | bzip2 -9 > ../tmp/$i if [ $? -eq 0 ]; then mv ../tmp/$i $i fi else

Version: 2.0.2 OS: Mac OS X 10.5.8 IMAP Client: Apple Mail.app on 10.5.8 Since upgrading to 2.0.2 I've noticed one user ends up with 4-5 imap processes all using as much CPU as they can get. I know of one other person who is seeing this on a FreeBSD server (that person moved back to dovecot 1.2 which 'solved' the problem there). I didn't notice anything in the list archive

Hello list, When trying to deliver a big message (which over-quota user limit), I always get segmentation faults. Others common delivers work fine. This only happens with messages, which over-quota user limit. Here is more details: /var/log/maillog: ... ** user at fakedomain.ua R=virtual_user T=dovecot_virtual_delivery: Child process of dovecot_virtual_delivery transport (running command

Hi, while a user is searching through his (1.2 GB, >150000) mails, I get a lot of these messages in the log, and the search (with Thunderbird) doesn't finish: Jun 19 14:35:45 stshamail1 dovecot: Panic: IMAP(username): file message-parser.c: line 620 (preparsed_parse_body_init): assertion failed: (offset >= ctx->input->v_offset) Jun 19 14:35:45 stshamail1 dovecot:

Hi I seem to be getting an error when quotas are enabled. Also I noticed that the quota_ rule settings don't actually get used, the only settings that are used are on the sql.conf file. Maybe I'm not understanding what the quota_rule does but should I be specifying the storage/messages values on there even though they are being read/used are on the sql.conf file only. dict {

Hi Timo and all others! The current Dovecot 2.0.rc4 did really well with Mutt 1.5.20 and Thunderbird 3.1.2, but a user with Alpine 2.00 crashed it immediately. I'm running Fedora 13 (Linux) and compiled Dovecot 2.0.rc4 manually like I did before with Dovecot 1.2.13. When switching from 1.2 to 2.0 I removed all those ".imap" folders with internal cache data (didn't know for sure

Hello, I recently upgraded to dovecot 2.0.2 (on gentoo ~amd64) and now fts_squat's index building seems to hang for some of my mailboxes. The imap process gets stuck at 100% cpu usage and dovecot.index.search is never touched. I traced the problem to a message (attached) for one of the problematic mailboxes. Also attached are a full backtrace and the output of dovecot -n. The problem

Hi I have a dovecot installed on debian 10 using solr to have a better search speed in emails. I am observing after an upgrade of the debian dovecot package the error below: Aug 25 00:33:45 server01 dovecot: imap(username at example.com)<24104><hyaFXqutnqUAAAAAAAAAAAAAAAAAAAAB>: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b) [0x7f0faeaeb62b] ->

Hi, I am migrating from 0.99.14 to 1.1.rc10 and from mbox to maildir. During the conversion, via convert plugin, I get this assertion failure: 2008-06-13 14:12:51 Error: IMAP(username): Next message unexpectedly lost from 4700 2008-06-13 14:12:51 Error: IMAP(username): Next message unexpectedly lost from 4700 2008-06-13 14:12:51 Panic: IMAP(username): file istream-crlf.c: line 49

You should be able to workaround this by enabling fts. Aki > On 04/11/2020 09:22 Andreas Piper <piper at hrz.uni-marburg.de> wrote: > > > Hello, > > on my dovecot-replicator-backend I see lots of panic-messages "assertion > failed: (ctx->nested_parts_count > 0)", produced from a single user. I > assume that this is correlated with >

Hello, on my dovecot-replicator-backend I see lots of panic-messages "assertion failed: (ctx->nested_parts_count > 0)", produced from a single user. I assume that this is correlated with https://github.com/dovecot/core/commit/a668d767a710ca18ab6e7177d8e8be22a6b024fb How can I identify the incorrect formatted message in the user's mailbox? I want to remove it, as the

Hi, i'm getting a coredump on a specific msg, i've attached the gdb. file on disk i noticed W=<vsize> is missing. 1571209735.M744550P1608.rwvirtual65,S=15886:2,S Best regards, mail.log Oct 18 14:41:39 rwvirtual10 dovecot: imap(johndoe at company.nl)<15868><qjTFpy6VPsMKAAok>: Error: Mailbox INBOX.Debug: UID=1041: read(/data/mail/

Hi, I have a couple of people bumping into an issue with their imap process crashing - from the users perspective, their mail client (thunderbird) just stops recieving new mail. It still seems to be possible for them to read their mail using squirell mail. When it crashes, it leaves behind a log message like this on the server: Aug 12 15:52:25 fury dovecot: imap-login: Login:

Hi folks, with the brandnew release Dovecot 1.1.2, the daemon killed itself with signal 6 (SIGABRT) when trying to save a mail from the INBOX to another folder. The mail client is PINE 4.64. After reconnecting to the IMAP server, the mail was actually copied to the destination folder, but the original mail was still in the INBOX and not flagged as "deleted". This is the panic: Jul 25