Open Bug 667950 Opened 15 years ago Updated 3 months ago

Reply/Forward Flags Lost When Message Moved, because IMAP server doesn't support flag for Replied state

Categories

(MailNews Core :: Networking: IMAP, defect)

All
Other
defect

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: eric, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:5.0) Gecko/20100101 Firefox/5.0 Build ID: 20110615151330 Steps to reproduce: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Lightning/1.0b2 Thunderbird/3.1.11 I reply or forward a message (from my inbox, for example), and it gets flagged appropriately. Then I move it to another folder. Actual results: The reply/forward flags/status are lost. This happens ever since I started using IMAP one year ago. Expected results: The reply/forward flags/status should remain a property of the message even when moved to another folder.
Sounds like your server doesn't store the flags, can you capture an imap log where you just reproduce the issue so we can try to see what the server is doing (see https://wiki.mozilla.org/MailNews:Logging ) ?
Component: Folder and Message Lists → Networking: IMAP
Product: Thunderbird → MailNews Core
QA Contact: folders-message-lists → networking.imap
Version: 3.1 → Trunk
yeah, we require that the server support the built-in flags that the IMAP RFC mandates (which includes \answered, but not forwarded, I don't think)
See also: bug 543963
Removing myslef on all the bugs I'm cced on. Please NI me if you need something on MailNews Core bugs from me.
Some bugs look report for same phenomenon. It seems dup reports, but setting dependency for ease of problem analysys, search, tracking.
Blocks: 690194, 729732, 744562
No longer blocks: 690194
Summary: Reply/Forward Flags Lost When Message Moved → Reply/Forward Flags Lost When Message Moved, because IMAP server doesn't support flag for Replied state
No longer blocks: 744562
No longer blocks: 729732
See Also: → 268589
Severity: normal → S3
Severity: S3 → S4

Fair to say this shouldn't be much of an issue in modern times?

Flags: needinfo?(gds)
See Also: → 1088516, 744562
See Also: → 800828

(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.

Flags: needinfo?(gds)
See Also: → 1910984
You need to log in before you can comment on or make changes to this bug.