On Thu, Sep 18, 2003 at 07:14:19AM +0200, Andreas Aardal Hanssen wrote: > Yes, it does. :) I'd like you to try the following patch, and see if it > solves the problem: > > Andy
Sorry, but your patch doesn't apply to a vanilla bincimap-1.2.2 here on my box. |--- src/maildir.cc 2 Sep 2003 18:51:08 -0000 1.6 |+++ src/maildir.cc 18 Sep 2003 05:12:33 -0000 -------------------------- Patching file src/maildir.cc using Plan A... Hunk #1 succeeded at 336. Hunk #2 failed at 350. Hunk #3 succeeded at 381 with fuzz 1. Hunk #4 failed at 404. 2 out of 4 hunks failed--saving rejects to src/maildir.cc.rej Hmm... Ignoring the trailing garbage. done I'm just testing mutt_1.4.1i with bincimap-1.2.2 and have also seen a problem with new mails. I have different mailfolders configured to the mailboxes function in mutt. So when i type c (change-folder) mutt checks these folders for new mail. This works when the new mails are in the new/ directory. Opening the folder under bincimap moves all new mails to the cur/ directory (message_id:2,). Now closing mutt without reading the new mails and restarting it, mutt doesn't detect any new mails. It's only the check_for_new mails that does not work, if i change to the folder all new mails are there and marked as new mails. Mutt shows also following behaviour when it has direct access to a maildir: A mail which was seen (:2,S) can be toggled as new and mutt moves the mail from cur/ back to new/ directory. Maybe mutt is doing something wrong here. Helmut
