Closed
Bug 246638
Opened 22 years ago
Closed 22 years ago
Incoming junk mail is already read and not marked as junk
Categories
(MailNews Core :: Database, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 196749
People
(Reporter: peter, Assigned: Bienvenu)
Details
Attachments
(1 file)
|
9.43 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
I have received a couple of junk mails with subject line "! Citibank". These
appear in my inbox as already read. And they don't seem to be recognised as junk
mail although the seem to meet the criteria, which suggests that they are not
being tested to see if they are junk mail. This may be because these mails
already include X-Mozilla-Status lines when I receive them - which may be
because they are sent by Mozilla 1.4.
Reproducible: Always
Steps to Reproduce:
1. This type of mail arrives in my inbox
Actual Results:
It stays in my inbox, marked as read and as not junk
Expected Results:
The message should be marked as unread and as junk, and moved to my junk folder
Here is the header of the message, after I have read it and manually transferred
it to the junk folder:
From - Mon Jun 14 01:52:15 2004
X-UIDL: 541a55b22f08393d001551dbdd309bbd
X-Mozilla-Status: 0200
X-Mozilla-Status2: 00000000
Return-path: <user-billing6@citibank.com>
Envelope-to: fayitumowe@qaya.org
Delivery-date: Mon, 14 Jun 2004 09:50:16 +0100
Received: from [211.204.91.134] (helo=67.15.6.3)
by pan.hu-pan.com with smtp (Exim 4.34)
id 1BZnAT-0001iK-8U
for fayitumowe@qaya.org; Mon, 14 Jun 2004 09:50:13 +0100
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00000000
FCC: mailbox://user-billing6@citibank.com/Sent
X-Identity-Key: id1
Date: Mon, 14 Jun 2004 13:45:33 +0400
From: Citi <user-billing6@citibank.com>
X-Mozilla-Draft-Info: internal/draft; vcard=0; receipt=0; uuencode=0
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4)
Gecko/20030624 Netscape/7.1 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: fayitumowe@qaya.org
Subject: ! Citibank
Content-Type: multipart/related;
boundary="------------070309030906020500050004"
X-MailScanner-Information: Please contact the ISP for more information
X-MailScanner: Found to be clean
| Assignee | ||
Comment 1•22 years ago
|
||
we add the x-mozilla-status header when we download the message - and we don't
add the header when it's sent. So I suspect the sender added it manually, which
we shouldn't allow.
| Reporter | ||
Comment 2•22 years ago
|
||
It is of course possible that the sender, who is obviously malicious,
deliberately added it to confuse Mozilla. Mozilla should ignore or delete such
lines in incoming mail, for robustness against malicious behaviour like this.
| Assignee | ||
Comment 3•22 years ago
|
||
yes, we should strip out those headers if they're actually in the incoming mail.
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Reporter | ||
Comment 4•22 years ago
|
||
I received a few more of these Citibank spams. The attached is one of them
saved as .eml straight from my Inbox (the previous example had already been
marked as Junk). Note the double set of X-Mozilla-Status and X-Mozilla-Status2
lines. The second pair was presumably in the message as I received it. Note
that "jahiho@qaya.org" is an invalid address.
Comment 5•22 years ago
|
||
I've received a few emails like this in the last couple of days too. I think
this bug is a dup of Bug #196749.
| Reporter | ||
Comment 6•22 years ago
|
||
(In reply to comment #5)
> I've received a few emails like this in the last couple of days too. I think
> this bug is a dup of Bug #196749.
Yes, you're right. Glad to see plenty of activity on fixing it there. David B,
please mark this as a dup.
| Assignee | ||
Comment 7•22 years ago
|
||
dup
*** This bug has been marked as a duplicate of 196749 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: MailNews → Core
Updated•18 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•