similar to: assertion failed in 1.0-stable

Hi list, Today i tried upgrading my dovecot server from 0.99.14 to 1.0alpha3. Unfortunately the new version does not work. The log file says: Oct 2 20:40:02 knut dovecot: imap-login: Login: user=<arved>, method=PLAIN, rip=213.225.30.218, lip=213.9.70.XXX, TLS Oct 2 20:40:02 knut dovecot: imap(arved): file istream-raw-mbox.c: line 450 (istream_raw_mbox_get_body_size): assertion failed:

Yesterday, I upgraded my debian packages from 0.99.14 to 0.99.20050712-2. IMAP service has not been reliable since, and I was seeing crashes with one user. I tried deleting the user's .subscriptions and .imap folders, and forcing the client (Mac OS X's Mail.app) to redownload everything, but that resulted in an empty inbox. Here's what I have: # dpkg -l dovecot*

Hello, When moving a message from my inbox to an existing mailbox folder I get: dovecot: Mar 21 12:52:48 Error: IMAP(paulj): file istream-raw-mbox.c: line 383 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) dovecot: Mar 21 12:52:48 Error: child 10265 (imap) killed with signal 6 This after moving from 0.99 to 1.0 stable on 5.3-RELEASE-p5 Client is

Hi We run dovecot 1.2.10 on Solaris 10 and had a few days ago this error message in the logs: Mar 6 21:48:55 dovecot: [ID 583609 mail.crit] IMAP(username): Panic: file istream-raw-mbox.c: line 583 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) Mar 6 21:48:55 dovecot: [ID 583609 mail.error] IMAP(username): Raw backtrace: 0xb1064 -> 0xb0aa0 ->

Hello Timo, I've upgraded from dovecot-0.99 to dovecot-1.0-stable (the 2005-05-09 version) on FreeBSD 5.4 and encountered the following problems (problem #4 (assertion failed) made me downgrade back to dovecot-0.99...) : 1. mbox sync: UID inserted in the middle of mailbox /var/mail/gopauld (5230 > 4407) --> OK, that's documented on the Wiki, not a real problem 2. imap(cxxx):

Hello, It seems that mbox format mailboxes holding \r\n (CR + LF) character sequences (instead of \n only) still cause assertion failures when moving messages from one folder to another. -- dovecot: Jul 19 17:14:52 Error: IMAP(dovetest): file istream-raw-mbox.c: line 38 3 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != ( uoff_t)-1) -- I seems to work in -test78

One of my users is causing dovecot to exit with signal 6 and generate a core file. Seems to be in the mbox code. Dovecot configuration: # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-STABLE amd64 protocols: imap imaps pop3s listen(default): localhost:143 listen(imap): localhost:143 listen(pop3): * ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995

Dovecot is crashing occasionally for me. Today it crashed six times in quick succession, as I fired up a computer (Mac) I hadn't used in a while, and my mail application (Apple Mail) tried to synchronize many large mailboxes. The log entries look like this: Aug 26 10:26:15 computer dovecot: dovecot: child 23223 (imap) killed with signal 6 (core dumped) Aug 26 10:26:30 computer dovecot:

Hi, We switched from dovecot 0.99.something to 1.0-stable (on FreeBSD 4.10) a few days ago and have been seeing many errors and one corrupted mailbox so far. Almost everyone uses mbox format, and most users primarily use SquirrelMail; I use Apple Mail and Thunderbird, as well as accessing the mailboxes locally with Mutt, and have not noted any visible problems. There have been several of

Hi, thank You for a reply, compiling with Solaris Studio 12.5 solved this case. Martin Preen <preen at informatik.uni-freiburg.de> ra??: > Hello, > I don't have problems building 2.2.27 on Solaris 10 > (using Sun Workshop compiler 5.11). > > The configuration is the same as your. > Maybe a compiler/version problem on your system ? > > Regards, > Martin >

Hi, Would anyone know what these errors mean? Running DoveCot RC15 on RedHat ES 4 Dec 1 17:30:53 serv-01 dovecot: pop3-login: file client.c: line 423 (client_unref): assertion failed: (client->destroyed) Dec 1 17:31:21 serv-01 dovecot: pop3-login: file client.c: line 423 (client_unref): assertion failed: (client->destroyed) Dec 1 17:31:25 serv-01 dovecot: pop3-login: file client.c:

Hello, I just found this message in our dovecot logfiles: "Disconnected: BUG: Unknown internal error" Should I worry about this ? There are no complaints yet (although it is not limited to one user). It seems to occur with different clients (Apple/MacOS mail, Windows/Thunderbird, Pine). We're running dovecot 1.0.10 on Solaris 10 with mboxes (NFS) and local index storage. There are

Hello! I was able to overcome the earlier-reported problems (of dovecot treating the standard mailboxes in /var/mail/ as directories) by specifying mail_location (continuing to use the 0.99-era dovecot.conf did not work). Then I started seeing assertion-failures like: file istream-raw-mbox.c: line 499 (istream_raw_mbox_get_body_size): assertion failed: (rstream->mail_size != (uoff_t)-1)

Greetings all, I (nor anyone else) am suddely unable to read mail. Dovecot dumps the following in it's log: # BEGIN LOG ENTRIES # dovecot: Jan 07 18:15:52 Info: imap-login: Login: user=<username>, method=PLAIN, rip=::1, lip=::1, TLS dovecot: Jan 07 18:15:52 Error: IMAP(username): file istream-raw-mbox.c: line 499 (istream_raw_mbox_get_body_size): assertion failed:

Hi. As some of you may remember, I reported a problem a while back where dovecot 1.1.beta14 (as well as dovecot 1.0) would corrupt mbox-style mailboxes by ignoring the Content-Length header and breaking up messages with embededed "From<space>" lines. I recently downloaded Dovecot 1.1.5 and noted to my pleasure that this bug now has been fixed. That's great! This fix

Hello, with some mbox folders I got this error: Mar 18 14:48:12 imap2 dovecot: [ID 107833 mail.crit] Panic: IMAP(xyz): file charset-iconv.c: line 122: unreached I assume that this is related to the folder contents (and not the configration). What does that mean to me ? Martin --------------------------------------------------------------- Martin Preen, Universit?t Freiburg, Institut f?r

Hello, I have a question about the way Dovecot limits file system access. Currently we're using Dovecot 1.0.5 (Solaris 10). In some cases users have a symbolic link like "z: -> /" in their mail directory. As a result there are log entries like Jan 25 13:30:31 imap1 dovecot: [ID 107833 mail.error] IMAP(xyz):

Hello, a few days ago I switched out UW-server installation to dovecot 0.99.14 (Solaris 9). There were a few client issues, but mostly the migration was ok. But I have still some questions/problems: +) dovecot-auth: ... PAM: pipe() failed: Too many open files I increased the max. number of open files. Is this normal behaviour, that more than 512 open files are needed ? +) we're using mbox

Hello, I'm currently testing dovecot/imap (Version 0.99.13). I found this in the log: imap(xxxxx): [ID 265587 mail.crit] file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) dovecot: [ID 684838 mail.error] child 7376 (imap) killed with signal 6 The user tried to setup a new folder (with Thunderbird)

Hello, I'm testing version 1.1.12 and occasionally there is Mar 18 14:40:44 imap2 dovecot: [ID 107833 mail.error] IMAP(xyz): nfs_flush_file_handle_cache_dir: rmdir(/home/xyz) failed: Device busy It seems that it is related to a crash of the previous imap process of that user. And it doesn't seem to cause any problems. So can it safely be ignored ? It is on Solaris 10. Index storage