6975 - [PP] Move Messages won't copy header into destination folder

Status: VERIFIED FIXED

(MailNews Core :: Backend, defect, P3)

Description

[scottputterman]

When you do a move messages, the header won't be copied into the destination
folder.  The message gets copied, but you won't be able to see the results until
you start up the next time.

The reason for this is that I was always expecting an open database.  But when
waterson made his changes that sped us up by not causing us to open every folder
at startup, databases were no longer created unless you selected a folder.
Therefore, my assumption was no longer valid.  The fix is to make sure there's a
valid database prior to trying to copy over the header.

I have a fix for this in my tree.

Comment 1

[scottputterman]

I'm going to make this M7.  This feature hasn't worked in a while and it would
be good to play around with it rather than checking it in right away.

Comment 2

[scottputterman]

changing back to M6.

Comment 3

[lchiang]

Is this a PC only bug or cross platform?

Comment 4

[scottputterman]

Cross platform.  I checked in the fix for this.

Comment 5

[laurel]

This seems to be working on windows and linux using the may25 m6 builds, but I
can't see that it works using may25 m6 mac build on Mac OS 8.51.  Will keep
working with it before reopening.

Comment 6

[laurel]

Can't get it to work on the mac using may25m6 (1999052516)

Comment 7

[lchiang]

Since it's now only a problem on Mac, updating the summary.

Comment 8

[laurel]

For clarification,  the mac is showing symptoms as putterman described in this
bug description's first paragraph -- move results don't show until the next
session.  I wasn't clear and it appeared to some that Move message wasn't
working at all on Mac.  I believe Lisa is going to add this to m6 release notes.

Comment 9

[lchiang]

Yes, I wasn't reading very closely :-(
I'll add this to the release notes for the Mac.
Scott - if you'd like, change this to M7.

Comment 10

[lchiang]

Item added to release notes.  Pls move to M7.  Thanks.

Comment 11

[scottputterman]

Reassigning to M7

Comment 12

[scottputterman]

This fix just got checked in.

Comment 13

[fenella]

Win32 and Mac (1999-06-17-08 m7)
This problem has been fixed.