On Wed, 30 Jul 2008 08:34:36 +0200 and Thu, 31 Jul 2008 13:22:40 +0200
"Ricardo Mones" <[EMAIL PROTECTED]> wrote:
> I think this is probably and old bug now, but, can you still reproduce
> this with current sylpheed ? (2.5.0-1 is the version in sid)
> As far I can test current sylpheed (2.5.0) does not allow copying or
> moving queue mails outside like you're describing in the bugreport, so
> this can be considered fixed now.
Just retested with v2.5.0-1.
Still buggy on 'delete'. As mentioned on 1/24/07:
This bug also happens after deleting an item from the 'Queue' folder.
The deleted message goes to the 'Trash' folder, but the headers are
blank (moved to the message body) when the message changes folders.
Resulting difficulty: messages with blank headers can't be sorted by
date. So if the Trash has many messages, all sorted by date, a user
expecting to see the message just deleted at the bottom of the list
won't find it there. To find the lost message, sort by subject, and go
to the top of the list and look for messages with 'no subject'.
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343672#10
As you said, copy/move from 'queue' doesn't entirely work in
v2.5.0-1. Yet if the user right-clicks on a message in 'queue', the
'Move/Copy' options remain, (not grayed out), and the user can click
those, select a destination folder, etc. To the user it seems
'sylpheed' does allow copy/move, except that copy and move don't do
any actual copying or moving and the user is not warned of this.
While it's immediately obvious that 'move' doesn't completely work,
(because the source message isn't deleted), for 'copy' users may
not notice. (Whenever a generic function isn't allowed in some particular
case, its interface should be disabled.)
Wishlist: But I think it 'copy/move' should work; 'queue' is simply
another folder and users expect that function from any folder. (Why
must 'queue' be any different? I'd imagine the idea underlying
'sylpheed's method was that 'queue' and 'draft' messages were
considered as only potential messages, and thus less "real" than sent
or received messages, and should be strictly segregated.)
Maybe this should be split into 3 bugs:
1) Wishlist: add copy/move to 'queue'
2) copy/move interface in 'queue' wasn't disabled.
3) 'queue' delete function corrupts header of 'trash' copy.
HTH...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
