On Wed, Apr 03 2013, Alan Schmitt wrote:
> Hello,
>
> As I was trying to find out how to deal with the trashed flag on my imap
> server, I think I've discovered a bug with mu4e.
>
> I have many trashed messages in my mailbox:
>
> ~/.Maildir/INBOX ls new
> 1364933080_0.92474.top.local,U=657542,FMD5=7e33429f656f1e6e9d79b29c3f82c57e:2,T
> 1364933080_1.92474.top.local,U=657537,FMD5=7e33429f656f1e6e9d79b29c3f82c57e:2,T
> 1364933080_2.92474.top.local,U=657511,FMD5=7e33429f656f1e6e9d79b29c3f82c57e:2,T
> 1364933081_4.92474.top.local,U=657524,FMD5=7e33429f656f1e6e9d79b29c3f82c57e:2,T
> 1364933081_7.92474.top.local,U=657527,FMD5=7e33429f656f1e6e9d79b29c3f82c57e:2,T
> ...
Well, messages in new/ shouldn't have any flags (as per the maildir
spec), so mu explicitly ignores them.
> (Question: am I mistaken by interpreting the 'T' as meaning trashed?)
>
> Unfortunately, when I restrict my view to trashed messages ("/
> flag:trashed"), no message is displayed. Does this mean that mu4e does
> not correctly recognized trashed messages? (In the interface, these
> messages have the flag "Nu" and do not mention "T".)
At least for me, trashed messages are handled fine; maybe there's a bug
somewhere else that puts those messages in new/.
Best wishes,
Dirk.
--
Dirk-Jan C. Binnema Helsinki, Finland
e:dj...@djcbsoftware.nl w:
www.djcbsoftware.nl
pgp: D09C E664 897D 7D39 5047 A178 E96A C7A1 017D DA3C