Arnie Goetchius wrote:
Daniel Barclay wrote:
Rick Merrill wrote:
Ray_Net wrote:
Most of people doesn't understand this simple problem.
When a mail is moved from one folder to another one (even while with
the
delete action) this is not normal that the characteristics of the mail
are changed. Someone told us that resetting the "unread" status is done
by design; therefore this is a *BAD* design. But the developpers lives
in their gold-tower.
On the other hand this only happens if you do it manually. When a filter
moves something to the trash the 'unread' status sticks.
Since filters can move messages to the Trash folder, but don't have any
other explicit "Delete" operation, and in SeaMonkey 1.1 deleting a
message (from anything folder other than the Trash folder) just moves
it to the Trash folder, "deleting" is the same as "moving to the Trash
folder" (in SeaMonkey 1.1).
Why break that correspondence? SeaMonkey 2 filters don't differentiate
between between deleting and moving to Trash, do they?
Daniel
You are correct SM 2 filters do not differentiate between deleting and
moving to Trash. However, that is not the subject of this discussion.
So? It's closely related--to whether deleting a message is the same
as just moving it to the Trash folder or is something more.
If filtering something to the Trash folder leaves the read/unread
status alone, why should moving something to the Trash folder via the
delete-message command work differently?
The discussion is centered on what happens when you manually delete a
message.
Yes, I know.
In SM2, "deleting" an "unread" message moves it to trash and
classifies it as "unread". However, in SM2, "moving" an "unread" message
to Trash changes the status to "read". It should leave the status as
"unread" just as "moving" (or using a filter) does.
Exactly my point.
Daniel
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
