similar to: v1.1.rc13 released

To some users happens this assertion failure while deleting a message. dovecot: Mar 10 08:40:44 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists (&ibox->recent_flags, uid)) dovecot: Mar 10 08:40:44 Error: IMAP(user): Raw backtrace: [see bleow] dovecot: Mar 10 08:40:44 Error: child 17683 (imap) killed with signal 6 And the

I have just upgraded to dovecot 1.1.2 and am seeing lots of the following panic messages filling up the error logs: dovecot: Aug 29 09:34:32 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Aug 29 09:34:32 Error: IMAP(user): Raw backtrace: imap [0x483888] -> imap [0x484293] -> imap

Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit Intel. Pretty sure NFS was not used. Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: seq_range_exists(&ibox->recent_flags, uid) The backtrace is: 0 libSystem.B.dylib 0x00007fff85025166 __kill + 10 1 libSystem.B.dylib 0x00007fff850a80e0

I recently upgraded dovecot from 1.0.15 to 1.1.2 and since then I am getting the following types of things in the logs: Aug 21 17:23:13 mail1 dovecot: imap-login: Login: user=<myuser>, method=PLAIN, rip=172.16.78.20, lip=172.16.78.22 Aug 21 17:24:01 mail1 dovecot: Panic: IMAP(myuser): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed:

Hello, I upgraded dovecot to 1.1.2 this weekend and i get those errors: grep dovecot /var/log/net/maillog |grep Panic | cut -d " " -f 11-100| sort | uniq -c | sort -rn 7547 file index-sync.c: line 39: assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) 89 file index-mail.c: line 1091: assertion failed: (! mail->data.destroying_stream) 18 file

We just came across a mailbox today that, when accessed via POP3 or IMAP, crashes Dovecot. It seems to be another index-related corruption issue (as removing "dovecot.index" for INBOX fixed it); Using POP3: dovecot: Apr 09 10:28:14 Warning: POP3(USERNAME): Maildir /mail/USERNAME/Maildir: UIDVALIDITY changed (1145576765 -> 1207677483) dovecot: Apr 09 10:28:14 Panic:

Hi, with dovecot-1.2.17 (yes i know it's old) i'm getting the folowing error after doing a system upgrade. May 7 22:04:26 mail dovecot: deliver(elon): Panic: file index-sync.c: line 25 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) May 7 22:04:27 mail kernel: pid 79989 (deliver), uid 4873: exited on signal 6 (core dumped) this

Hi folks, with Dovecot 1.1.1, I've had two "crashes" (SIGABRT) recently. Dovecot 1.1.1 has been compiled from source and is running on Fedora 8 Linux 32 Bit (all patches) with custom OpenSSL 0.9.8h. [ output of "dovecot -n" ] # 1.1.1: /usr/local/dovecot/etc/dovecot.conf ssl_cert_file: /usr/local/dovecot/etc/dovecot.crt ssl_key_file: /usr/local/dovecot/etc/dovecot.key

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sent an e-mail off as was detailed here: http://wiki.dovecot.org/MboxProblems for crashes but I also wanted to see if any of you folks had insight into the issue. Dovecot is crashing on a certain user inbox which is in mbox format as well as one of the users other mbox files. The crash doesn't exactly match what is listed in the aforementioned

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just switched over to dovecot 1.1.2 on our live system last night. I'm seeing the following errors in the logs: Aug 19 10:01:03 goku dovecot: [ID 107833 mail.crit] Panic: IMAP(elevin): file in dex-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range _exists(&ibox->recent_flags, uid)) I did apply the assertion fix

http://dovecot.org/releases/dovecot-1.0.rc13.tar.gz http://dovecot.org/releases/dovecot-1.0.rc13.tar.gz.sig I'll just keep on making new releases now whenever something important is fixed. Hopefully there shouldn't be many left anymore. Most of the bugs fixed in this release were found by stress testing with my imaptest tool (http://dovecot.org/tools/imaptest.c). If you're interested

http://dovecot.org/releases/dovecot-1.0.rc13.tar.gz http://dovecot.org/releases/dovecot-1.0.rc13.tar.gz.sig I'll just keep on making new releases now whenever something important is fixed. Hopefully there shouldn't be many left anymore. Most of the bugs fixed in this release were found by stress testing with my imaptest tool (http://dovecot.org/tools/imaptest.c). If you're interested

Hi, another imap crash with latest dovecot. segmentation fault in fetch_bodystructure src/imap/imap-fetch.c static int fetch_bodystructure(struct imap_fetch_context *ctx, struct mail *mail, void *context ATTR_UNUSED) { const char *bodystructure; if (mail_get_special(mail, MAIL_FETCH_IMAP_BODYSTRUCTURE,

Hello, I've installed dovecot-1.0.rc13 on FreeBSD-6.1 with LDA support. But I didn't found the /var/run/dovecot/auth-master file on my system. I need this file for the protocol lda { ... auth_socket_path = /var/run/dovecot-auth-master ... } settings in the /usr/local/etc/dovecot.conf. Does anyone has an idea? PS: On a older installation (dovecot-1.0.rc7) the file exists and

Dear R developers: I am trying to fit a PPO model using vglm from the library VGAM, and get an error while executing the code. Here is the data, code, and error: Data: first row is the column names. a = age, and 1,2,3, 4 and 5 are condition grades. a 1 2 3 4 5 1 1 0 0 0 0 2 84 2 7 10 2 3 16 0 6 6 2 4 13 0 3 4 0 5 0 0 0 1 0 Library(VGAM)

I think I'll just start making new releases whenever I've fixed something important. You'll have a while to report more bugs and then I'll make rc13 release, maybe in about 5 hours or maybe tomorrow. I updated already the nightly snapshot if you want to test the upcoming rc13. Changes so far: + deliver: If we're executing as a normal system user, get the HOME environment

As promised, here it is finally. v1.0 is getting nearer and I want people to start looking at Dovecot's sources. Getting some more help with development would be nice, but I'd also like to hear if there are any hidden bugs in the code. So, one week from now I'll start offering 1000 EUR for the first person to point out a remotely exploitable security hole in Dovecot. See

Hello, For those interested, I have released the NHW v0.3.0-rc13 new version. I am still continuing to fine-tune the nhw_kernel weights.This new version has then more precision and a better visual quality. More at: http://nhwcodec.blogspot.com/ Cheers, Raphael -------------- next part -------------- An HTML attachment was scrubbed... URL:

Hi, I am stuck at rc13 because rc14 and rc15 have both failed to keep up with imap connections on my (slow old) system. I have the problem where if a lot of people check their email at once (like at the top of the hour) then my load goes way up and things slow to a crawl. My setup: Solaris 10 on an E220R, mbox format, imap and imaps only. I also use "login_process_per_connection =

I upgraded from rc12 to rc14 last night... sifting through the logs I noticed the following. I point this out since it appears dovecot is in high gear bug-fix mode. This issue is not big for me; I rarely stop dovecot. My init.d script for dovecot is basically stop) killall dovecot imap-login I am guessing there might be a more graceful way to stop dovecot? Or rc14 fixed this? I see in