Reply/Forward Flags Lost When Message Moved, because IMAP server doesn't support flag for Replied state
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
People
(Reporter: eric, Unassigned)
References
Details
Comment 1•15 years ago
|
||
Comment 2•15 years ago
|
||
Comment 4•10 years ago
|
||
Comment 5•9 years ago
|
||
Updated•9 years ago
|
Updated•3 years ago
|
Updated•2 years ago
|
Comment 6•2 years ago
|
||
Fair to say this shouldn't be much of an issue in modern times?
Comment 7•2 years ago
|
||
(In reply to Wayne Mery (:wsmwk) from comment #6)
Fair to say this shouldn't be much of an issue in modern times?
For me the \answered flag is surviving a move to a gmail folder so it should work for any server since /answered flag (meaning message was replied to) is an imap standard flag/tag. The answered flag shows as a small maybe purple arrow pointing away from the message subject.
As for a "forwarded" flag/tag, there is no standard tag for forward. Looks like tb just sets an internal flag on the forwarded message and displays a green arrow pointing back toward the messages and sets a non-standard flag $Forwarded, if supported by server. But when I copy (actually, imap append) this to a gmail imap folder, I don't see the "forwarded" arrow in the message now in gmail folder. Gmail (and most others) supports a $Forwarded flag but TB doesn't try to set it when it does the append, but it does set the \answered flag with the append when it is on the copied message.
Not sure if this is a bug or maybe imap append only supports "standard" flags (which start with back-slash) and not server-specific flags like $Forwarded.
Description
•