similar to: CR LF in stable

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):

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 everybody, I get the following assertion error with dovecot 1.0-stable when accessing a large folder: file istream-raw-mbox.c: line 383 (istream_raw_mbox_get_body_size): assertion failed: (rstream->body_offset != (uoff_t)-1) There is no error when using dovecot 0.99.14. Any ideas ? Martin ----------------------------------------------------------------- Martin Preen, Universitaet

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 ->

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

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:

Hello, I've been trying to figure out what's wrong with authentication against an ldap pass/user db with test67 as test62 was working fine. [ The problem is the same as previously described in this list : - FreeBSD-5.3 - dovecot-1.0-test67 - openldap-2.1.27 --> "ldap(dovetest,127.0.0.1): No password in reply" --> "NO Temporary authentication failure." or --

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

Hello, I'm wondering if the following situation is valid (though I think it isn't since I still cannot authenticate with ldap pass/userdb on test67 running on FreeBSD-5.3). Is it normal that the passdb_ldap_conn->attr_names second element (for instance) "turns to" "homeDirectory" as the following step by step gdb run sample shows ? : -- Breakpoint 1,

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:

Hello Timo, I'm curious about 2 points (I'm using alpha2 but these are general questions) : Background : . I connect to dovecot-1.0.alpha2 through thunderbird . I use ldap pass/userdb and PLAIN mech . I've only got one auth block in dovecot.conf (all pass/userdb/mech except ldap/PLAIN are commented) 1) I notice that, for one thunderbird connection trial, imap-login

We've had another random imap process crash. This is with the original 1.2.5 imap (I haven't applied the patch for two processes creating an index simultaneously): > Oct 03 13:24:56 imap-login: Info: Login: user=<xxxxxxxx>, method=PLAIN, rip=134.225.1.46, lip=134.225.16.6 > Oct 03 13:25:59 IMAP 6067 xxxxxxxx 134.225.1.46 : Info: delete: uid=483, msgid=<xxxxxxxx> > Oct

Hello, The installation of 1.0-test66 (still on FreeBSD 5.3-RELEASE-p1 with openldap-2.1.27) solved the SIGSEV problem I posted here on March 30 but I still cannot authenticate correctly with ldap. logs report "ldap(dovetest,127.0.0.1): No password in reply" and my client gets a "NO Temporary authentication failure." Obviously the attr_names array of the

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)

Hi, I had successfully set up dovecot-1.0-test62 + ldap pass/user db, but now I'm encoutering a SIGSEV problem with a similar set up of a brand new dovecot-1.0-test65 installation. The auth process is killed by a SIGSEV as reported in the error log file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the

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:

Hello, What has changed from test77 to test78 in the way imap manages its descriptors? I upgraded to test78 this morning on a small site which I use as a testbed for testing various things. Running the same copy of my kqueue patch with test77 works quite well [*], with test78 imap has some problems. Here is some debugging output I recorded: Jul 14 12:55:27 egg dovecot: imap-login: Login:

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: