Closed
Bug 59218
Opened 25 years ago
Closed 24 years ago
POP3 mail filtering on To: AND Subject: seems unreliable in 11/1 build
Categories
(MailNews Core :: Filters, defect, P2)
Tracking
(Not tracked)
VERIFIED
WORKSFORME
Future
People
(Reporter: ekrock, Assigned: Bienvenu)
Details
Using 11/1 N6 on WinNT 4.0 SP4:
Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m18) Gecko/20001101 Netscape6/6.0
I use POP3 and have numerous email filters of the form:
if (To or CC) contains _______ AND Subject contains ________ filter to ______.
I notice that in the 11/1 build, at least some messages that should be dropping
into folders because of such rules seem to be showing up in my Inbox instead.
Not sure if this is 100% broken or just occasionally failing because I have so
many filters of this kind active.
| Assignee | ||
Comment 2•25 years ago
|
||
nothing changed in the 11/1 build, so I don't know why this would have just
started happening. I'm surprised pop3 filters were working that well at all for
you given another bug I fixed a couple weeks ago where pop filters would fire
somewhat randomly.
Status: NEW → ASSIGNED
| Assignee | ||
Comment 6•25 years ago
|
||
Eric, are any of the filters in question disabled? You can tell this by bringing
up the filter editor.
I'm not seeing such a problem with jan10 commercial trunk build using win98 POP
filters.
During bug triage meeting yesterday it was brought up that Eric is on
sabbatical, so we won't get a response from him about his particular filter
situation for some time.
In the interest of getting this off the current radar, I'm going to mark this
worksforme and we can always reopen or log a new issue if necessary.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 9•25 years ago
|
||
Reopening. I saw this over sabbatical using N6 Messenger 11/8 RTM build, and I'm
still seeing this in N6 Messenger 20001020520 Commercial build today when
downloading new email. Both on WinNT 4.0 SP 5 or 6 (not sure).
The specific example I noticed today in the 2/5 build:
1) I have a filter (which is enabled) that says:
- match ALL
- To or CC contains stopbadtherapy.com
- Subject contains board
- Subject contains correction
- THEN move to folder correction on ekrock on nsmail-1
2) An email message came in with this header [identifying info for sender deleted]:
From - Wed Feb 07 22:29:45 2001
X-UIDL: 70962-913460658
X-Mozilla-Status: 0001
X-Mozilla-Status2: 00c00000
Return-Path: <>
Received: from netscape.com ([205.217.237.178]) by
judge.mcom.com (Netscape Messaging Server 4.15) with ESMTP id
G8E8MN00.Q3R for <ekrock@judge.mcom.com>; Wed, 7 Feb 2001 07:35:11 -0800
Received: from xwing.netscape.com (xwing.mcom.com [207.200.76.40])
by netscape.com (8.10.0/8.10.0) with ESMTP id f17FYp106939
for <ekrock@netscape.com>; Wed, 7 Feb 2001 07:34:51 -0800 (PST)
Received: from mail07a.vwh1.net (mail07a.vwh1.net [209.238.9.57])
by xwing.netscape.com (8.10.0/8.10.0) with SMTP id f17FYoZ02187
for <ekrock@netscape.com>; Wed, 7 Feb 2001 07:34:50 -0800 (PST)
Received: from 206.222.52.36 (206.222.52.36)
by mail07a.vwh1.net (RS ver 1.0.58s) with SMTP id 055723906
for <contact@stopbadtherapy.com>; Wed, 7 Feb 2001 10:34:43 -0500 (EST)
Received: by LINUS with Internet Mail Service (5.5.2650.21)
id <DRL5T0FC>; Wed, 7 Feb 2001 09:39:02 -0600
Message-ID: <405B05DE6FAFD311986B00A0C9822B970DF310@LINUS>
To: "'contact@stopbadtherapy.com'" <contact@stopbadtherapy.com>
Subject: board addition (don't change this subject!)
Date: Wed, 7 Feb 2001 09:39:00 -0600
Return-Receipt-To: [deleted]
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
X-Loop-Detect: 1
Expected: email should be dropped into corrections folder
Actual: was dropped into my inbox
These filters were working fine in Nav4.x before I upgraded to 6.x. In 6.x, POP3
filtering on message body seems unreliable (sometimes it works, sometimes it
doesn't) but not completely broken. Marking 4xp. Nominating nsbeta1--would like
fixed for nsbeta1 as this is really aggravating for folks like me who depend
heavily on message body filtering to manage the flow of email.
| Reporter | ||
Comment 10•25 years ago
|
||
Grr, sorry, I got confused between my "addition" filter and my "correction"
filter halfway through my explanation. I have both, and they're both enabled.
The above explanation should be corrected as follows:
...
1) I have a filter (which is enabled) that says:
- match ALL
- To or CC contains stopbadtherapy.com
- Subject contains board
- Subject contains addition
- THEN move to folder addition on ekrock on nsmail-1
...
Expected: email should be dropped into addition folder
Actual: was dropped into my inbox
Comment 11•25 years ago
|
||
marking nsbeta1-
Comment 12•24 years ago
|
||
I am seeing this, only worse. I have a very simple test account setup.
It has a filter on Subject = test It moves the messages to another folder. If I
send the account 1 message and then do get mail it works OK. If I send 2 then
both messages disappear. They do not end up in the destination folder and they
are lots from the inbox.
The number of messages causing the problem does seem to vary a bit so maybe this
is a timing issue.
I am now on the latest nightly build (21 March 2001), this problem was fixed
earlier but has come back in the last month or two.
I can run the same tests on the same account but setup to use IMAP and it works
fine.
| Assignee | ||
Comment 13•24 years ago
|
||
David Warnock, have you seen this recently with a build from the last two weeks
or so?
| Assignee | ||
Comment 14•24 years ago
|
||
marking worksforme due to lack of response. Please re-open if you stil see this.
I believe that some of Navin's fixes for getting new mail when the mail summary
files were out of date should have fixed this.
Status: REOPENED → RESOLVED
Closed: 25 years ago → 24 years ago
Resolution: --- → WORKSFORME
Comment 15•24 years ago
|
||
Marking verified worksforme. OK using aug27 commercial trunk build.
Status: RESOLVED → VERIFIED
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•