[kmail2] [Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2013-03-22 Thread Andy Goss
https://bugs.kde.org/show_bug.cgi?id=117717 Andy Goss aeg...@internode.on.net changed: What|Removed |Added CC||aeg...@internode.on.net ---

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2012-08-19 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=117717 Luigi Toscano luigi.tosc...@tiscali.it changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2012-08-19 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=117717 Luigi Toscano luigi.tosc...@tiscali.it changed: What|Removed |Added Status|UNCONFIRMED |NEW Ever

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2012-08-19 Thread Holger
https://bugs.kde.org/show_bug.cgi?id=117717 --- Comment #12 from Holger private_l...@yahoo.com --- My kmail claims to be version 4.7.3 in KDE 4.7.4 ... so is this now kmail 1 or kmail 2 ??? How to tell the difference, if the program doesn't know for itself? Back to topic: Yes, this is still an

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2012-08-18 Thread Luigi Toscano
https://bugs.kde.org/show_bug.cgi?id=117717 Luigi Toscano luigi.tosc...@tiscali.it changed: What|Removed |Added CC|

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2012-08-18 Thread Murz
https://bugs.kde.org/show_bug.cgi?id=117717 --- Comment #10 from Murz mur...@gmail.com --- This feature is missed in kmail2, but will be very useful, because after deleting unread message we see uread messages in Trash folder, this is not good. -- You are receiving this mail because: You are

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2012-08-18 Thread Murz
https://bugs.kde.org/show_bug.cgi?id=117717 --- Comment #11 from Murz mur...@gmail.com --- But I can't reopen the bug. Another way for fixing this bug is marking message as read when moving to trash. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2009-12-30 Thread Björn Ruberg
https://bugs.kde.org/show_bug.cgi?id=117717 Björn Ruberg bjo...@ruberg-wegener.de changed: What|Removed |Added CC|

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2009-12-24 Thread Björn Ruberg
https://bugs.kde.org/show_bug.cgi?id=117717 Björn Ruberg bjo...@ruberg-wegener.de changed: What|Removed |Added Keywords||junior-jobs

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2009-02-06 Thread Pablo Montepagano
http://bugs.kde.org/show_bug.cgi?id=117717 Pablo Montepagano pmontepagano gmail com changed: What|Removed |Added CC|

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2009-02-06 Thread Holger
http://bugs.kde.org/show_bug.cgi?id=117717 --- Comment #6 from Holger private_lock yahoo com 2009-02-06 22:42:20 --- Maybe I was not clear enough on my problem. The trash is *not* counted against the tray-icon ... Instead I see it as bold to the left in the folder overview. Whenever I'm done

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2008-12-22 Thread Murz
http://bugs.kde.org/show_bug.cgi?id=117717 Murz MurzNN gmail com changed: What|Removed |Added CC||mur...@gmail.com -- Configure

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2008-11-30 Thread Holger
http://bugs.kde.org/show_bug.cgi?id=117717 Holger private_lock yahoo com changed: What|Removed |Added CC||[EMAIL PROTECTED] ---

[Bug 117717] Feature: allow a folder to automatically mark everything in it as Read

2008-11-30 Thread Oded Arbel
http://bugs.kde.org/show_bug.cgi?id=117717 --- Comment #4 from Oded Arbel oded geek co il 2008-11-30 14:54:28 --- Having an ignore new mail in this folder checkbox, AND having that configuration apply the behavior specified in this bug's description (*) will indeed close this ticket and most