On 25.8.2004, at 11:30, Pawel Salek wrote:
..I encountered a strange response to message part fetch command. It looks like a bug in the server to me but I would like to get a second opinion. Suggestions how to work around this problem are welcome too. The problem is the server promises to send 23824 octects long literal but sends 4040+ characters and happily announces the processing has finished (sanitized log below). Any clues?
IMAP S: * 68 FETCH (BODY[2] IMAP S: {23824}
[snip 4000 octects]
OABOAHUAbQAxAHoAMAAAAAgAT0oBAFFKAQAwAP4f)
9 OK FETCH completed.
Looks like some corruption in server's internal message store. I wouldn't suggest trying to add any workarounds for this in client side. The right fix would be to get that particular server's admins to fix it.
The server code of course should have made sure this never happens. Either it should have padded the missing data with spaces or something, or just disconnected the client. Mine does the latter.
PGP.sig
Description: This is a digitally signed message part
