search for: test62

Greetings: I've been using Dovecot 1.0-test62. It has been working well. I tried to upgrade to 1.0-test64 but users could not authenticate. Both versions I compiled with: ./configure --with-ssl=openssl; make; make install They compiled and installed fine. The /usr/local/etc/dovecot.conf needed to be modified due to the new syntax. 1.0-...

Hi, Got the following today with test62 and mbox: IMAP(juergen): Fixed index file /home/juergen/Mail/.imap/INBOX/dovecot.index: recent_messages_count 19 -> 0 imap-login: Login: juergen [192.168.0.1] file mail-index-sync-ext.c: line 118 (mail_index_sync_deinit_handlers): assertion failed: (size <= synch_size) child 31196 (ima...

...PS, I get "connection to server closed" and this appears in logs: dovecot: Feb 04 12:48:30 Error: IMAP(rathann): file mail-index-sync-ext.c: line 118: assertion failed: (size <= synch_size) The problem goes away after deleting the index from ~/Mail/.imap/INBOX. We're running 1.0-test62 on Solaris 9. -- Dominik 'Rathann' Mierzejewski <rathann*at*icm.edu.pl> Interdisciplinary Centre for Mathematical and Computational Modelling Warsaw University | http://www.icm.edu.pl | tel. +48 (22) 5540810

http://dovecot.org/test/ Nothing big, just random fixes. - Crashfixes in keyword code - -std=gnu99 wasn't working well in all systems, configure now checks for it - FreeBSD sendfile() calling was broken sometimes. No need to remove #define HAVE_FREEBSD_SENDFILE anymore. - FETCH BODY[] wasn't setting \Seen flag. - LDAP fixes (by Kazuo Moriwaka) - Don't crash if client

i noticed this while browsing through my maillog.. Feb 21 11:27:43 selenium dovecot: IMAP(ben): Corrupted index cache file /u/home/ben/Maildir/.INBOX.ML-SunHELP.rescue/dovecot.index.cache: field index too large (3337 >= 22) i have no problems reading that box after this, and see no other messages about corrupt index files from today, or the past 14 days. --ben

...y - shutting down dovecot: Feb 05 02:08:03 Error: child 8441 (login) killed with signal 6 dovecot: Feb 05 02:08:03 Error: child 8440 (auth) killed with signal 6 (sometimes the (login) line is not send, but always (auth)) Any thoughts on where to next start tracking this down? I tried to use test62, but get this (haven't dug much further into this one since I'd like a stable release for this application): main.c: In function `listen_protocols': main.c:284: error: structure has no member named `_listen' main.c: At top level:

Test version 61 ./configure is failing on my OpenBSD 3.6-stable system. The following corrects the problem. Would it be possible to test for gnu99 option before using it in subsequent tests? --- configure.in.orig Fri Jan 14 14:04:10 2005 +++ configure.in Fri Jan 14 16:44:22 2005 @@ -236,7 +236,7 @@ # say specifically that we want C99 features. # we can make use of

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 -- dovecot: Apr 12 18:22:41 Info...

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

...uncomment the dovecot section after I authenticate. The log is below: [root at cerebus:/opt/sbin] ./pop-before-smtp --version version: 1.36 Mar 4 05:14:09 cerebus last message repeated 5 times Mar 4 05:19:46 cerebus dovecot: Killed with signal 15 Mar 4 05:20:00 cerebus dovecot: Dovecot v1.0-test62 starting up Mar 4 05:20:34 cerebus dovecot: imap-login: Login: user [ip.ad.dr.ess] Mar 4 05:30:21 cerebus dovecot: imap-login: Login: user [ip.ad.dr.ess] I had uncommented the stock pattern in the latest version to no avail: # For Dovecot POP3/IMAP #$pat = '^(... .. ..:..:..) \S+ (?:doveco...

...ocess-id...) Something is very wrong with this PID. Maybe someone can explain the Master <--> Auth IPC to me so I can understand and fix it myself? Where does Master take this client number from? Hints are highly appreciated, Peter --- LOG --- Feb 21 21:04:36 office dovecot: Dovecot v1.0-test62 starting up Feb 21 21:04:48 office dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=192.168.23.1 rip=192.168.23.42 resp=AHZpYwBzeXNpbnQyMQ== Feb 21 21:04:48 office dovecot: auth(default): client out: OK 1 user=vic Feb 21 21:04:48 office dovecot: auth(default): master in: R...

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, I'm using (or trying to at least) a combination of PAM/passwd and MySQL authentication: auth vmail { mechanisms = plain userdb = sql /etc/dovecot/dovecot-sql.conf passdb = sql /etc/dovecot/dovecot-sql.conf user = root } auth system { mechanisms = plain userdb = passwd passdb = pam imap user = root } MySQL