Closed
Bug 388051
Opened 18 years ago
Closed 17 years ago
IMAP filters not logging in filter log
Categories
(MailNews Core :: Filters, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: nelson, Assigned: Bienvenu)
Details
(Keywords: regression)
SM trunk, beginning with the 2007-07-07 build.
I receive several hundred emails each day. I have many IMAP filters
in place to sort out the incoming email into various folders. Those
filters seem to mostly work (with some exceptions, which will be the
subject of my next bug), but they don't seem to create log entries
any more.
In the last 48 horus, I have received MANY message, but less than 25
of them created log entries. The ones that created log entries are
ones that I changed last week, adding an action of "stop filter execution"
to them, and my catch-all filter at the end (which catches all email not
addressed specifically to me). Those filters create log entries, the
rest do not.
Reporter | ||
Updated•18 years ago
|
Assignee: nobody → bienvenu
Assignee | ||
Updated•18 years ago
|
Status: NEW → ASSIGNED
Reporter | ||
Updated•18 years ago
|
Flags: blocking1.9?
Assignee | ||
Comment 1•18 years ago
|
||
filter logging is working for me - what are the filter actions in the case where the filter logging isn't working? Do they just move new incoming messages into folders on the same imap server? I tried filters that do that, and filters that move messages to local folders, and both those seemed to log fine.
Reporter | ||
Comment 2•18 years ago
|
||
Yes, all the filters move new incoming messages into folders on the same
IMAP server.
Some filter actions get logged. Others do not.
Hmmm. Dave, I'm going to ask/suggest that you do no further work on this
bug while I do some more investigation at my end. I now suspect that there
is some other actor (e.g. another email client) that is filtering my arriving
emails at the same time as my email client is doing so. Until I get to the
bottom of that, I suggest you put this on hold. You could even mark it
WORKSFORME, and if I later decide that it's still valid, I can reopen it.
Assignee | ||
Comment 3•18 years ago
|
||
would it be doing the same moves for you? In any case, I'm looking at the Received header filter bug now - I think that one I was able to reproduce that one.
Reporter | ||
Comment 4•17 years ago
|
||
I'm marking this, my bug report, invalid. In this particular case, the problem was indeed that another client was filtering the messages at the same time,
The log message for the filter action was appearing in the other client,
not in the one I was checking.
Note that this does NOT invalidate bug 388055 (which, *I think*, David has
now fixed).
Status: ASSIGNED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
Updated•16 years ago
|
Product: Core → MailNews Core
Updated•4 years ago
|
Flags: blocking1.9?
You need to log in
before you can comment on or make changes to this bug.
Description
•