Package: offlineimap Version: 4.0.9 Severity: normal *** Please type your report below this line ***
I can reproduce this, though not always at the same point in the transfer. My setup is as follows server: ms exchange 2000 version 6.0.6603.0 On the server I have two folders in the listed in the rc file, the first with about 27,000 messages the second with about 7,000. client: offlineimap-4.0.9, Maildir format I start in a clean slate, only .offlineimaprc and empty ~/Test maildir (just a directory at this point). With the Tk.Blinkenlights it fails out pretty early, after a few hundred messages. The virtual memory utilisation is about 230Mb when it dies, on a host with 1Gb and about 2Gb swap. With TTY.TTYUI I can get through both folders cleanly. Does this mean the segfault is really in Tk? One thing I'm puzzled about is that only the local Maildir tree is created on the first time through, not the LocalStatus dir. The latter does not get created until the next sync attempt. Perhaps this is the famed algorithm at work? I have a bunch of -d imap -l output to support this report but I'd prefer to send that privately for analysis. So let me know what you want. Cheers! -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-3-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages offlineimap depends on: ii python2.3 2.3.5-3sarge2 An interactive high-level object-o -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
