I upgraded at last to bincimap 1.1.8 (using IMAPdir) 3 days ago, and today I had some strange behaviour at home (that's where my server is connected with 100MBit to the client).
I received an email with 2 large attachments (2 PDFs, 1 MB each).Now when I clicked on the 1st one (using Mozilla 1.4), the acrobat reader opened it instantly (wow, what a speed).
After that I clicked on the 2nd one, but now the retrieval is very slow! Mozilla showed me a download rate of only 30 kBytes/sec! So I should have waited over half a minute to open it. Ofcourse I did not :)
Now I made some changes in bincimap.conf and I found out some really strange behaviour: Originally I had a transfer buffer size of 8096 (hmmm shouldn't this be 8192?). When I changed this to a lower (!!) number, that was 4096, the download rate of the 2nd attachment doubled to over 70kB/sec! Now I set it to 1024 and 512, and with both settings I got way over 100kB/sec (this is still slow on a 100MBit net, but it's acceptable for me right now).
Could anyone investigate in this? What is the optimal "transfer buffer size"? Why this slowness? Shouldn't the default transfer buffer size be changed?
And one little thing: in the default standard bincimap.conf the line "depot = ....." is missing (when upgradeing, I always changed "type = Maildir" into "type = IMAPdir" and that was ofcourse wrong.
BTW: I'm using the debian-package of bincimap.
Thanks in advance, I still think bincimap rocks, it seems stable to me (=most important to me, I use it for my personal mail archive since V.1.1.1, loosing mails is not an option).
Greetings, Tibor
