It's during this operation that we see the introduction of a significant number of null characters into the message, sometimes over 5MB (yes megabytes). The nulls always occur right before the From line of a message though they aren't always introduced.
Hmm. I wonder if this is NFS inode vs. data cache skew; that is, the inode data returned by stat() (and in particular the file size) doesn't match the data on the NFS client.
I forgot to mention in my last mention that this is imap-2002d. Is this possibly fixed in 2004a?
Try it and see. Since this is probably not a c-client bug, and is instead something in your NFS infrastructure that c-client, it isn't clear that a version upgrade of c-client imapd will fix it. However, it could be that some subtle difference in how the new version does I/O may avoid tickling the NFS issue.
-- Mark --
http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
