331391 - Filter with copy and move actions causes the copy to fail.

Status: RESOLVED DUPLICATE of bug 398498

(MailNews Core :: Filters, defect)

Description

[Leo A. Notenboom]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b2) Gecko/20050702

From http://forums.mozillazine.org/viewtopic.php?p=2158717
See repro steps as well.

Reproducible: Always

Steps to Reproduce:
Created new profile
Created (single) account
Created two folders - both at same level (peers) as Inbox.
Created the two Filters. Copy to Folder A, followed by Move to Folder B

Actual Results:  
1) Received a single peice of email.

The Copied-to folder shows a new blank entry with date 12/31/1969
The Moved-to folder shows the new email correctly.

Looking at the actual mbox files for the two folders, they are identical.

Compacting the Copied-To folder did nothing, even across a restart of Thunderbird.

Deleting the msf for the copied-to folder caused the mail to be displayed properly on restart.


2) Received TWO peices of email.

The Copied-to folder shows a single new blank entry with date 12/31/1969
The Moved-to folder shows the two new emails correctly.

Looking at the actual mbox files for the two folders, the copied-to folder is missing the second email of the pair.

Compacting the Copied-To folder did nothing, even across a restart of Thunderbird.

Deleting the msf for the copied-to folder caused the first message to be displayed properly on restart, but the second that was missing from the mbox file is not there.


Expected Results:  
With these rules, for each message recieved matching the filter criteria, it should be copied into one folder, and also moved into another - effectively duplicating the message.

Blocking a power-user migration from Outlook.

Comment 1

[Andrew Schultz]

I do see this with linux Mozilla 1.8b1, but it worksforme with linux seamonkey release 1.0 and linux seamonkey trunk 2006032212

The old Mozilla suite won't have a 1.8 release (although 1.7.x releases will continue).  SeaMonkey has continued on the same code base.  SeaMonkey 1.0 was released off the Mozilla 1.8 branch.
http://www.mozilla.org/projects/seamonkey/

resolving WFM

Comment 2

[Leo A. Notenboom]

Since this bug was originally discovered using Thunderbird, how will it be affected? Will this fix (or lack of bug) eventually make it to Thunderbird?

Comment 3

[Leo A. Notenboom]

Re-opening bug. Just downloaded SeaMonkey
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060130 SeaMonkey/1.0

And the bug still repros for me. Maybe Windows specific?

Comment 4

[Andrew Schultz]

There is a Thunderbird product for Thunderbird bugs (although this is Core).  :)  What version of Thunderbird did you see the bug in?

Comment 5

[Leo A. Notenboom]

Well, I'm just trying to play by the rules. The Thunderbird bug reporting instructions are exrememly adamant that if the bug repros in Mozilla, that it should be reported against Mozilla and NOT Thunderbird. So here I am.

Thunderbird version 1.5 (20051201)

Comment 6

[Andrew Schultz]

Hmm... which instructions?

If you can reproduce a bug in Thunderbird /and/ SeaMonkey, it often means that it's a Core issue, but you should never file bugs you see in Thunderbird in the Moz App Suite product.  Also, some bugs you see (even when they do also occur in Thunderbird) should have separate bug reports (one for SeaMonkey, one for Thunderbird).

Comment 7

[Leo A. Notenboom]

Well, the instructions were here:
http://www.mozilla.org/support/thunderbird/bugs
note that the details for point #3 in the list (check Mozilla) are now gone.

So ... what do I need to do, if anything, to ensure that this bug is in the right place, and getting some attention at some point? I'd hate to see this bug languish because it's sitting in the wrong bucket.

Comment 8

[Andrew Schultz]

Ah, indeed.  They got updated in February (they were ~1 year out of date even at that point): http://bonsai-www.mozilla.org/cvslog.cgi?file=mozilla-org/html/support/thunderbird/bugs.html&rev=&root=/cvsroot/

This is in the proper component.  One thing to try is to try a build from the 1.8 branch (which will eventually become TBird 2)
ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-mozilla1.8/
and see if the bug still exists there.

Comment 9

[Leo A. Notenboom]

Problem still repros in version 2 alpha 1 (20060411)

Comment 10

[Andrew Schultz]

Can you attach the msgFilterRules.dat file for the account the filters are in?

[profile folder]\Mail\[account]\msgFilterRules.dat
(The Mail folder might not exist.  It's there in SM but perhaps not Thunderbird)

Profile folder should be
Documents and Settings\<UserName>\Application Data\Thunderbird

Comment 11

[Leo A. Notenboom]

msgFilterRules.dat:
-----
version="8"
logging="no"
name="Untitled Filter"
enabled="yes"
type="1"
action="Copy to folder"
actionValue="mailbox://nobody@Local%20Folders/Folder%20A"
action="Move to folder"
actionValue="mailbox://nobody@Local%20Folders/Folder%20B"
condition="OR (subject,contains,test)"
-----
This is with the latest Thunderbird from 
ftp://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-mozilla1.8/
version 2 beta 1 (20061104)

And the bug continues to repro.

Thanks.

Comment 12

[Andrew Schultz]

Ah, that's one filter with two actions.

I am seeing that with SeaMonkey build 2006-11-04-08-trunk, but the opposite.  The copy operation succeeds and the move fails silently.  The filter log showed a successful copy and no mention of a move.  If I reverse the order, the move succeeds and the copy fails.  I'm using "Run Filters on Folder" rather than handling new mail.

I tried copy + flag actions and that worked fine.

Comment 14

[Mike Cowperthwaite]

xref bug 368383 -- something strange reported there that might be related to this.

Comment 15

[WADA:World Anti-bad-Duping Agency]

Root problem seems to be found in Bug 384735(problem while first copy by filter or just after first copy by filter). Putting Bug 384735 in "Depends on:".
Is there JS Error of Bug 384735 Comment #4 in Error Console?

Comment 16

[WADA:World Anti-bad-Duping Agency]

(In reply to comment #0)
> The Copied-to folder shows a new blank entry with date 12/31/1969

This phenomenon itself looks to be Bug 209501.
> Bug 209501 – Phantom mail from 1/01/1970 11:00 AM or 12/31/1969 keeps reappearing in my inbox
And your next comment indicates problem of Bug 209501. 
> Deleting the msf for the copied-to folder caused the first message to be
displayed properly on restart,

> first message to be displayed properly on restart,
> but the second that was missing from the mbox file is not there.
It sounds that this part is same symptom as Bug 384735, and "copy to fail" part in bug summary sounds phenomenon of Bug 384735.

To Leo A. Notenboom(bug opener):
(Q1) Is the phantom mail of Bug 209501 frequently created by message filter of "copy", even after "delete msf"? (or after "rebuild index" which is new feature of Tb 2.0)
(Q2) Bug 384735 has been fixed. Does problem("copy to fail" part in bug summary) occur even on latest trunk of Tb?
(Q3) Analysis of problem when "copy then move by filter" is in progress by Bug 376235. Is problem of Bug 376235 involved in your case? 

Comment 17

[Magnus Melin [:mkmelin]]

Sounds like bug 398498.