similar to: 1.0-test11

http://dovecot.org/test/ - "Maildir sync: UID < next_uid (446 < 447, file = .." errors should be fixed - fixes for detecting changes in uidvalidity and external uidnext changes - several fixes and cleanups in index file handling. less code than before and now changes to index header also go through transaction log. that should mean that soon I can get mmap_disable = yes

http://dovecot.org/test/ Should work again with maildir. - Some bugfixes to indexes (possibly fixing the still persisting maildir sync errrors?) - Enabled cache file again. If client asks about something that can be cached for future, it's done. There's currently no smart logic about when not to do it or when to cache more than was asked for future use. Currently nothing is ever

http://dovecot.org/test/ Well, remember when I said: > Here you go, maildir syncing problems finally fixed (I hope). Well, > except there's this "new-dir-only syncing" optimization which I'm not > really sure if it works as it should. Just before I found the expunge bug in index, I was trying to fix the new-dir-only syncing because the code looked wrong. Then I

When attempting to save a message from the INBOX to a folder in a collection (like, .projects.dovecot), I get behavior like this (in GDB). Any clue what might be going wrong? Here's where a SIGABRT happens: 280 return array->buffer->used / array->element_size; This is the stack trace: (gdb) where #0 mail_index_map_get_ext_idx (map=0x1200c0db0, ext_id=0,

Timo + All, A few minutes after having some emails delivered into my mailbox I got the following messages in my maillog: May 24 03:05:27 myriad dovecot: imap(andrew): Maildir sync: UID inserted in the middle of mailbox (2 > 1, file = 1084812461.V27406I77e27.myriad.flat:2,S) May 24 03:05:27 myriad dovecot: child 81038 (imap) killed with signal 11 May 24 03:15:28 myriad dovecot: imap-login:

Hello, It seems dovecop pop3 server sometimes inserts a blank line at the top of the mbox. It only happens for certain users not all. I'm not sure why it's doing that. Looking back into the mailing list, I saw the same post in Oct 6, 2003 but there was no reply to it. Is there a patch or fix that i can use to get around the blank line? Thank you. Ken

Hi- I was able to get a coredump out of the new pop3 (from 0.99.9-test4) by attempting to simulate the execution environment and simply running the pop3 program. Running the older pop3 from 0.99.8.1 works fine, repeatedly: % /usr/local/libexec/dovecot/pop3 quit +OK Logging out. However running the new one: % /usr/local/libexec/dovecot/pop3.new pop3(user9): Error: Corrupted index file

http://dovecot.org/tmp/dovecot-1.0.2-rc.tar.gz Unless someone finds something broken, I'll release v1.0.2 in a few days. The most important changes since v1.0.1: * dbox isn't built anymore by default. It will be redesigned so it shouldn't be used. + Maildir: Support reading dovecot-uidlist (v3) files created by Dovecot v1.1. - Maildir: "UIDVALIDITY changed" errors

We upgraded from Dovecot 1.0.15 to 1.2.5 last night, on Solaris 10 using mboxes, mostly without issues. However I had to trash the index/cache files (too many folders were showing corruption issues which is especially bad for Prayer Webmail ".prayer" folders that store preferences; Prayer sees a disconnection as the folder being missing!). I've had one imap process panic in mailbox

Timo, I saw a couple of these cores over the weekend. The syslog says: May 21 19:04:48 emerald dovecot: [ID 107833 mail.error] IMAP(user): Corrupted index cache file /home/students/s/user/.imap/sent-mail-apr-2004/dovecot.index.cache: indexid changed With a resulting core file from imap at this time. I also discovered a remaining lock file on the person's imap file: -rw------- 1 user

hi, in the yesterday cvs, an internal error in the imap message appear in the client side and in the maillog: ------------------------- Apr 16 10:01:42 red imap(zgabor): Corrupted index file /home/zgabor/Maildir/.Lists.Bugtraq/.imap.index: Invalid seen messages count (284 < 285) Apr 16 10:01:43 red imap(zgabor): Corrupted index file /home/zgabor/Maildir/.Lists.Linux/.imap.index: Invalid

>From today's maillog: maillog:Dec 28 09:29:40 aurora dovecot: IMAP(doug): msync() failed with index file /home/doug/Maildir/.projects.job591/dovecot.index: Invalid argument maillog:Dec 28 09:30:21 aurora dovecot: IMAP(doug): msync() failed with index file /home/doug/Maildir/dovecot.index: Invalid argument maillog:Dec 28 09:30:22 aurora dovecot: IMAP(doug): msync() failed with index file

Hi,, In src/lib/mountpoint.c:53 the following had to be commented out: // point_r->type = p_strdup(pool, buf.f_fstypename); because f_fstypename is undeclared on this OS. Also the following errors occur with the DEC C compiler (which compiles the other files just fine): source='file-cache.c' object='file-cache.o' libtool=no DEPDIR=.deps depmode=none

http://dovecot.org/test/ I have very high hopes that mbox support is finally stable in this version. I've been running some stress tests for an hour now without it breaking (well, there are two potential problems but I think they were just fixing previous breakages). Before it took only a few minutes at most to break. - fixes several mbox syncing problems, especially expunges

just to let you know: the authentication doesn't work correctly under linux: Nov 29 22:35:06 zobi sshd[11661]: Server listening on 0.0.0.0 port 22. Nov 29 22:35:06 zobi sshd[11661]: Generating 768 bit RSA key. Nov 29 22:35:07 zobi sshd[11661]: RSA key generation complete. Nov 29 22:36:11 zobi sshd[11668]: Failed password for zvo from 127.0.0.1 port 738 Nov 29 22:36:18 zobi sshd[11668]: Failed

For example in src/lib/file-cache.c: if (cache->mmap_base == MAP_FAILED) { Should be fixed, probably like this: if ((int)cache->mmap_base == MAP_FAILED) { There are a lot of occurences for these in the source. GCC only warns because of this, but DEC C is known to consider this an error: Error: file-cache.c, line 79: In this statement, "new_base" and "(-1)" may

I performed a hg pull today for 1.0.1 and after recompilation my log was flooded with: Jul 12 10:29:21 postamt dovecot: IMAP(kxx4): UID larger than next_uid in file /home/k/j/kxx4/Maildir/dovecot-uidlist (6 >= 0) Jul 12 10:29:21 postamt dovecot: IMAP(rexxxes): UID larger than next_uid in file /home/r/e/rexxxes/Maildir/dovecot-uidlist (1 >= 0) Jul 12 10:29:21 postamt dovecot: IMAP(sxxkim):

Timo, Output of gdb session on the core file attached. This one only produced the following syslog: IMAP(user): UIDs broken with partial sync in mbox file /var/mail/r/user with no assert. Setup: Solaris 9, gcc 4.0.1 for dovecot build. Jeff Earickson Colby College -------------- next part -------------- Script started on Thu Sep 08 10:05:53 2005 %gdb imap core.rtohara GNU gdb 6.3 Copyright

Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit Intel. NFS may have been used. Panic: IMAP(user): file mail-index-sync-update.c: line 843 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index- >indexid || map->hdr.indexid == 0) Two different backtraces to this error are: 0 libSystem.B.dylib 0x00007fff87b775ea __kill + 10 1

Just out of curiosity: Is htree in 2.6.0-test11 ? -- Ralf Hildebrandt (Im Auftrag des Referat V a) Ralf.Hildebrandt@charite.de Charite - Universitätsmedizin Berlin Tel. +49 (0)30-450 570-155 Gemeinsame Einrichtung von FU- und HU-Berlin Fax. +49 (0)30-450 570-916 Referat V a - Kommunikationsnetze - AIM. ralfpostfix