Hi,

I really don't get this guys, why mutt whouldn't modify a timestamp after 
modifying a mbox! And the worst is that it rely on the timestamps to know 
when there are new msgs.

So tell me, is it "normal" to always get a N flag on all the mboxes until 
the timestamps are externally modified?

If this is called a "feature" then anyway that's not the way to implement 
it, why not --diable-stupid-timestamps-unmodify or something in the 
configure script.

PS. I don't remember to have seen this behavior before.

Reply via email to