Closed
Bug 33614
Opened 26 years ago
Closed 26 years ago
Filters firing only a couple times then don't work...
Categories
(MailNews Core :: Backend, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M17
People
(Reporter: laurel, Assigned: Bienvenu)
Details
(Whiteboard: [nsbeta2+][6/15])
Using 2000-03-27-09m15 commercial build NT 4.0
Haven't yet tried with other platforms, will assume All Platforms
Filters are firing only once or twice within a session then they stop working.
I've tried filters with delete and move to folder actions based on sender
contains <emailname>. I've seen them filter when it's a single message that's
incoming or multiple, whether they all match criteria or not. Not sure what's
causing it to stop...
Using IMAP filtering to IMAP folder on same server... haven't tried POP account
yet.
1. In 4.x open IMAP account and set up a single filter to delete message based
on sender contains.
For example, rules.dat would show:
version="6"
loggin="no"
name="foo"
enabled="yes"
description=""
type="1"
action="delete"
condition=" OR (from,contains,laurel)"
2. Exit 4.x after saving the filter. Migrate the profile to seamonkey.
3. Go to seamonkey mail window, open account and provide proper login password.
Messages are retrieved.
4. Send messages to this account which will match the filter criteria. Get
them. They appear in the trash folder, they're deleted.
5. Repeat sending messages at various intervals which match the criteria. Get
the messages. Filtering will happen properly only some times.
To reiterate:
-- Have seen failure using delete and move to folder actions based on sender
content.
-- Have seen failure when single or multiple messages incoming match
criteria.
-- Have seen when multiple incoming messages and some match criteria while
some don't.
--
Added note: Filters always seem to work at least once per session.
QA Contact: lchiang → laurel
| Assignee | ||
Comment 2•26 years ago
|
||
cc'ing alec in case he accidentally changed something. I haven't changed filters
in a very long time.
Status: NEW → ASSIGNED
I also noticed this yesterday on the trunk build. It was the first time I had
used a trunk build since the beta1 build. My filter action is to delete a
message based on sender.
| Assignee | ||
Comment 4•26 years ago
|
||
I have not seen this yet. All my filters are firing, about 10 times so far in
the same session.
| Assignee | ||
Comment 5•26 years ago
|
||
still have not seen this, with either a debug build, or a release build from
yesterday.
Aren't you special?! You're looking through those rose-colored glasses again.
(just kidding).
I'll look at again.
| Assignee | ||
Comment 7•26 years ago
|
||
I don't have any delete filters (except for you, Lisa!) so maybe that has
something to do with it.
If you were really smart, you'd have a delete filter for me.
Set up a delete filter and try it for a day, David, just to see if you get this
problem.
I can't believe you have a delete filter for me! No wonder you never answer any
of my email :-)
| Reporter | ||
Comment 10•26 years ago
|
||
Nope, still not working using mar30 m15 commercial builds.
My delete filter failed miserably on linux.
It failed after a couple time using NT.
I'm seeing even weirder behavior with both delete and move-to-folder filters
today. If I get messages then switch between INBOX and the destination folder
and back again, I keep seeing new copies of the filtered message in either place
which may be removed the next time I switch back.
So it's two things I see:
1. The filters stop working after awhile (particularly delete)
2. I'm seeing copies of the filtered message disappearing/reappearing in the
INBOX and destination folders when switching back and forth among the two
folders.
Not taking any drugs, but maybe that would help.
| Assignee | ||
Comment 11•26 years ago
|
||
that's a completely new bug that was introduced last night. I have a fix for it.
| Reporter | ||
Comment 12•26 years ago
|
||
separated the new bug out as bug #33963.
| Assignee | ||
Comment 13•26 years ago
|
||
let me know if you keep seeing this after today - I wonder if this was related
to 32742
| Reporter | ||
Comment 14•26 years ago
|
||
Using 2000-04-19-09m16 commercial build on linux: my delete filters still not
working.
Comment 15•26 years ago
|
||
Laurel, this just occurred to me - are you using custom headers by any chance?
Filtering on custom headers does not work with seamonkey yet.
(I know because I have like 20 filters based on Resent-From that don't work)
| Reporter | ||
Comment 16•26 years ago
|
||
No, nothing fancy like custom headers. Just filtering on subject contains and
sender contains. MoveToFolder actions seem to be working fairly consistently,
but action Delete doesn't.
| Assignee | ||
Comment 17•26 years ago
|
||
perhaps your trash folder has lost its trash flag. all delete is is a move to
the folder with the trash flag set.
| Reporter | ||
Comment 18•26 years ago
|
||
OK, same thing's happening over mac and linux (haven't gotten to NT yet): If
IMAP is set for mark as deleted, the delete filters fire. If delete is set for
Move to Trash, they don't.
Comment 19•26 years ago
|
||
Yes, I still have this problem and it's more consistent now. My set up is like
Laurel's: move to trash, no custom headers.
Comment 21•26 years ago
|
||
Putting on [nsbeta2+][6/01] radar. This work must be done by 06/01 or we may
pull this for PR2.
Whiteboard: [nsbeta2+][6/01]
Comment 23•26 years ago
|
||
Changing from [6/01] to [6/15]
Whiteboard: [nsbeta2+][6/01] → [nsbeta2+][6/15]
| Assignee | ||
Comment 24•26 years ago
|
||
fix checked in.
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
Comment 25•26 years ago
|
||
I have not seen in this a long time. Laurel?
| Reporter | ||
Comment 26•26 years ago
|
||
Lisa, I'm in the process of verifying all my resolved bugs. I will probably get
to it on Monday.
| Reporter | ||
Comment 27•26 years ago
|
||
This looks OK using july 18 commercial builds, linux rh6.0, NT 4.0, mac OS 9.0
Status: RESOLVED → VERIFIED
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
•