10295 - Filter IMAP action mark as read not working...

Status: VERIFIED WORKSFORME

(MailNews Core :: Backend, defect, P3)

Description

[laurel]

Using m9 build of jul21

I'm logging this bug as a placeholder/reminder for me to re-test the mark as
read filter action against IMAP once bug #7513 is fixed.

POP filter action of mark as read is currently working.

Comment 1

[laurel]

I can't get this to work, even after 7513 has been fixed and verified.  When
filtering IMAP messages for action "Mark read" the messages matching filter
criteria stay unread -- bold, green dot, and nothing in the status column.  All
platforms, doesn't correct after second get message, change folders, exit and
restart.

Changing assignee to bienvenu and clearing TFV.

Comment 2

[David :Bienvenu]

I added a comment to 7513 to the effect that I didn't think this bug had
anything to do with that bug.

Comment 3

[David :Bienvenu]

I suspect storing imap flags must not be working, which I'm looking at next
(mark read wasn't hooked up to imap at all, though the internal imap code is all
written)

Comment 4

[David :Bienvenu]

Should be fixed when necko branch lands- that's where I made my fix. ETA is
currently Wednesay, I believe. Mark Read/Unread should work from the UI as well,
though only the status column is updated, due to an existing tree control or rdf
bug...don't know the number of that one, but it's assigned to Waterson, as I
understand.

Comment 5

[laurel]

Using jul30 necko builds (tried linux and NT, didn't get to mac) mark read
filter action is still not working on IMAP. It does indeed work for POP
accounts.

Comment 6

[David :Bienvenu]

Did you notice if the message got marked read on the server? That's all I
changed (i.e., sending protocol to mark it read on the server). You can tell
this by shutting down and restarting, and seeing if the message is now displayed
as read.

Comment 7

[leger]

Clearing FIXED resolution due to Re-open.  But if it is fixed, please set to
Resolved/Fixed :-)

Comment 8

[laurel]

Exit doesn't help. It doesn't work.

Comment 9

[lchiang]

(target milestone is M11 or M12 - add to mail beta tracking bug)

Comment 10

[David :Bienvenu]

I tried this - it worked fine.

Comment 11

[laurel]

Using NT 4.0 with 1999-10-19-08m11 commercial build:

OK, it's marking it read on the server because after I use seamonkey with a Mark
Read filter action (IMAP account), I can open Communicator 4.7 to the same
account and see the message is marked read, so the server has it marked as read.

HOWEVER, seamonkey never does display it with a read status (in status column or
un-green the diamond).

So, something is wrong in seamonkey in getting that read status to display. Exit
and relaunch doesn't clear the status, but I bet re-migrating would.

Reading a message displays read status, and when using Message|Mark Read (after
first marking unread) seems to work.

Now what?  This isn't working visibly to the seamonkey user!

Comment 12

[David :Bienvenu]

If that's the case, that's a separate problem, which is that synchronizing of
flag states isn't being commited to the database, or reflected in the UI. A
simple case is to mark an existing message unread with 4.5, shutdown 4.5, and
start up 5.0. If the message is still shown as read in 5.0, then we're not
synchronizing correctly.

Comment 13

[laurel]

That's the case...I guess I'll log a separate bug about synchronizing.

Marking this bug verified.