On Thu, 16 Dec 2004, Jorge Almeida wrote: >No, just one client! >This is a low-level session example: > $ mconnect 127.0.0.1 14333 > * OK Welcome to Binc IMAP v1.2.10final Copyright (C) 2002-2004 Andreas >* Aardal Hanssen at 2004-12-16 22:19:08 WET > A001 login jorge <****> > A001 OK LOGIN completed > A002 select INBOX > * 706 EXISTS > * 0 RECENT > * OK [UNSEEN 2] Message 2 is first unseen > * OK [UIDVALIDITY 1099133605] > * OK [UIDNEXT 897] 897 is the next UID > * FLAGS (\Answered \Flagged \Deleted \Recent \Seen \Draft) > * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft)] >Limited > A002 OK [READ-WRITE] SELECT completed > A003 select LISTAS/gentoo > * BYE The server died unexpectedly. Please contact your system > * administrator for more information.
Oh my - this should never happen. >Is it possible that some of the bincimap-* files in the maildir is >corrupted? If so, is there something I can do about it? It shouldn't matter; Binc should handle corrupt files. But hmm.. just to make sure, you should try attaching to bincimapd after logging in using gdb (gdb <pid>), then reproduce the error so that gdb catches the crash. Then do a backtrace in gdb with "bt" to see where Binc crashes. Andy :-) -- Andreas Aardal Hanssen | http://www.andreas.hanssen.name/gpg Author of Binc IMAP | "It is better not to do something http://www.bincimap.org/ | than to do it poorly."
