More details on courier/offlineimap problem

[Eric Jonas <jonas@xxxxxxx>]

At the moment, using courier 1.4.3-2.5 (via debian) and offlineimap
(either from debian or from the web site, versions 4.0.7 and 4.0.6
respectively) I get:

...
022,16295,16027,16296,16033,34029,16039,39213,16051,16063,16069,16081:16082,16101,16129,16141,16176,10727,16198,31678,31729,31800,6515:6516,6521,10799,6523,16266,16282,16285,1073,10859,32479,6541,16356,5442,32694,5499,32707,32709,16375,32740:32741,32743,32750,32752
+FLAGS (\Deleted)
imap:   30:20.68 < * BYE [ALERT] Fatal error: max atom size too small:
Invalid argument
imap:   30:20.68        matched r'\* (?P<type>[A-Z-]+)( (?P<data>.*))?' =>
('BYE', ' [ALERT] Fatal error: max atom size too small: Invalid argument',
'[ALERT] Fatal error: max atom size too small: Invalid argument')
imap:   30:20.68 untagged_responses[BYE] 0 += ["[ALERT] Fatal error: max
atom size too small: Invalid argument"]
imap:   30:20.68 BYE response: [ALERT] Fatal error: max atom size too
small: Invalid argument
imap:   30:20.68 last 0 IMAP4 interactions:
...

when running with -d imap . This comes shortly after a command to delete a
around 4000 messages; might this be courier not being able to handle
really large message commands? (I really don't know much about imap). Has
anyone else experienced this problem?

Thanks,
                ...Eric