258735 - new mail shown as read when not read if includes gif attachment

Status: RESOLVED DUPLICATE of bug 196749

(SeaMonkey :: MailNews: Message Display, defect)

Description

[John Edmondson]

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.2) Gecko/20040803
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.7.2) Gecko/20040803

Periodically, I receive spam email that includes a gif attachment.  This email
is marked as read even though it hasn't been read.  The text of the mail
includes html followed by a image/gif.

I tried replicating by sending myself an html message with a gif attachment and
it doesn't occur.

I looked at the source for the mail and the differences that I see are:

Spam contains:
  X-Identity-Key: id1
  X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; uuencode=0
  Content-Type: multipart/related;

Attempted replication
  X-Identity-Key:  <---- not present
  X-Mozilla-Draft-Info: <---- not present
  Content-Type: multipart/mixed;

By the way, I have no mail filters that would do this automatically.
I have the option to do not load remote images in mail and news turned on.

Reproducible: Always
Steps to Reproduce:
1.  Receive spam that includes a gif attachment
2 [review].  Marked as read in inbox even though not read
3.

Actual Results:  
Marked as read in inbox even though not read

Expected Results:  
Not marked the message as read

Comment 1

[Mike Cowperthwaite]

Interesting.
You don't also see extraneous (repeated) X-Mozilla-Status headers in the 
message?  See bug 196749 -- altho that fix is in 1.7.1.

Comment 2

[John Edmondson]

I relooked at the last email I received and you are right.  It does have two
sets of entries for X-Mozilla-Status:

At the top of the headers: 
X-Mozilla-Status: 0000
X-Mozilla-Status2: 00000000

Below Message-Id
X-Mozilla-Status: 0001
X-Mozilla-Status2: 10000000

By the way, this is happening on 1.7.2

Does this mean that it is a duplicate then?

Comment 3

[Mike Cowperthwaite]

(In reply to comment #2)
> By the way, this is happening on 1.7.2
> 
> Does this mean that it is a duplicate then?

Judging from the latest comment in that bug, yes -- altho the patch had approval 
for 1.7.x checkin, apparently it hasn't actually gotten that checkin yet.

*** This bug has been marked as a duplicate of 196749 ***