dovecot - Dec 2006 - assertion failed

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: line 423
(client_unref): assertion failed: (client->destroyed)

Dec 1 17:31:29 serv-01 dovecot: pop3-login: file client.c: line 423
(client_unref): assertion failed: (client->destroyed)

Dec 1 17:31:33 serv-01 dovecot: pop3-login: file client.c: line 423
(client_unref): assertion failed: (client->destroyed)

Dec 1 17:31:41 serv-01 dovecot: pop3-login: file client.c: line 423
(client_unref): assertion failed: (client->destroyed)

Dec 1 17:31:45 serv-01 dovecot: pop3-login: file client.c: line 423
(client_unref): assertion failed: (client->destroyed)

Dec 1 17:31:49 serv-01 dovecot: pop3-login: file client.c: line 423
(client_unref): assertion failed: (client->destroyed)

Dec 1 17:31:53 serv-01 dovecot: pop3-login: file client.c: line 423
(client_unref): assertion failed: (client->destroyed)

 
	
Regards
Richard
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20061204/e207e774/attachment-0001.html>

On Mon, 2006-12-04 at 14:36 +0200, Richard Mayhew - Nashua Mobile
Broadband Division wrote:
> 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)
Do you happen to be using proxying feature? I fixed this crash with it,
but I'm not really aware of other such problems..

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://dovecot.org/pipermail/dovecot/attachments/20061204/30dbf11f/attachment.bin>

We have been running 1.0-rc15 for some time on a very small set of users.
We recently have increased the user population and just ran into a problem
with one user.  That user is using a client we apparently had not tested
yet and is causing us to get these errors in the logs:

[Host name, IP address, and user name are not real]

Dec 21 15:23:00 [hostname] dovecot: imap-login: Login: user=<username>,
method=PLAIN, rip=10.10.10.10, lip=10.10.10.11, TLS
Dec 21 15:23:00 [hostname] dovecot: IMAP(username): file strfuncs.c: line 151
(p_strdup_until): assertion failed: ((const char *) start <= (const char *)
end)
Dec 21 15:23:00 [hostname] dovecot: child 7151 (imap) killed with signal 6

-- 

Steven F. Siirila			Office: Lind Hall, Room 130B
Internet Services			E-mail: sfs at umn.edu
Office of Information Technology	Voice: (612) 626-0244
University of Minnesota			Fax: (612) 626-7593

I installed dovecot on a RH9 server this evening, via an RPM from
atrpms.net (dovecot-1.0-0_34.rc15.RHL9.at.i386.rpm). The auth portion
is working perfectly, as I'm using it to do SMTP AUTH with my postfix
2.3.5 installation.

I have configured it to provide imaps. When I connect to it, it
rapidly connects, disconnects, connects ... ad infinitum, reporting
this, in the logs, each time:

Dec 30 16:03:33 max dovecot: imap-login: Login: user=<ste>,
method=plain, rip=192.168.32.168, lip=65.206.7.147, TLS
Dec 30 16:03:33 max dovecot: IMAP(ste): file istream-raw-mbox.c: line
499 (istream_raw_mbox_get_body_size): assertion failed:
(rstream->mail_size != (uoff_t)-1)
Dec 30 16:03:33 max dovecot:child 19228 (imap) killed with signal 6

Here is my dovecot.conf file:

listen = [*]
protocols = imaps
disable_plaintext_auth = yes
ssl_cert_file = /etc/postfix/max.blackdogsoft.net.crt
ssl_key_file = /etc/postfix/max.blackdogsoft.net.key
ssl_ca_file = /etc/postfix/cacert.pem
default_mail_env = mbox:%h:INBOX=/var/mail/%u
mail_read_mmaped = yes
verbose_proctitle = yes
protocol lda {
    postmaster_address = postmaster at blackdogsoft.net
}
auth default {
    mechanisms = plain login
    passdb pam {
    }
    userdb passwd {
    }
    socket listen {
        client {
            path = /var/spool/postfix/provate/auth
            mode = 0660
            user = postfix
            group = postfix
        }
    }
}

Suggestions?
-- 
        -ste