On Thu, 2011-05-19 at 12:25 +0200, Milan Crha wrote: > the bug is for IMAP, and technically makes sense only there, as it > doesn't make any sense on exchange servers, for example, because it's > user-configurable how the IMAP provider should behave, and that's the > main point. For what would it be with NNTP provider, for example?
The 'real trash folder' concept can apply to *any* mail store, not just IMAP. Even with a local Maildir or mbox store you can designate one "Deleted Items" folder, and then Evolution can move mail there instead of just setting the 'deleted' flag on it. It most certainly *does* apply to the Exchange server too, and is *exactly* what we want to do on Exchange to preserve the Outlook behaviour. NNTP is a special case because it's read-only. You don't actually write your 'deleted' state back to the server at all for NNTP. > Please do not call it "dirty hack", it is not any such thing. It's dirty > hack on IMAP protocol itself, but not for the code base. That's true. It's a dirty hack on the protocol. It's also a dirty hack in the back end, though. The back end *already* supported the "move messages" operation, and the UI could have just asked it to move the messages. Done in *Evolution*, or perhaps in higher levels of Camel and *not* in individual back ends, it wouldn't be a dirty hack. -- dwmw2 _______________________________________________ evolution-list mailing list evolution-list@gnome.org To change your list options or unsubscribe, visit ... http://mail.gnome.org/mailman/listinfo/evolution-list
