11697 - [FEATURE] need backend support for additional FCC

Status: VERIFIED FIXED

(MailNews Core :: Backend, defect, P3)

Description

[esther]

Using builds 19990811 on Win, mac and linux  FCC is not working as it should be.
Talking to rhp, he said currently if the FCC front end is hooked up it would be
changing the Sent Folder assignment.  FCC in 5.0 is suppose to let the user
select a Folder to send a FCC copy to in addition to a copy going to the Sent
folder.  This is done via a menu item while composing a message. This should not
replace the copy that goes to the Sent Folder.

Comment 1

[rhp (gone)]

will try to get to this before sabbatical :-)

Comment 2

[rhp (gone)]

I talked to some people, and now I'm not sure that changing the FCC for a
particular message should copy the message in ADDITION to the "Sent" folder
copy. The specs don't seem to really specify what should be happening. I would
like to get someone to clarify before I would change any code. Changing the UI
menu wouldn't change the pref, just override it for that particular message,
and this may be the way we want this to work.

Sol, can you clarify for us?

- rhp

Comment 3

[sol]

Rich: I've always thought of fcc as being *in addition to* the copy that is
saved in the Sent folder. If implemented this way, fcc allows end users to have
a chronological record of their sent mail, as well as placing an additional copy
in a project folder.

Comment 4

[Phil Peterson]

I don't think I agree with Sol. In particular, this suggestion doesn't allow
turning off FCC from the menu, right? I think there's one default FCC folder,
called "Sent", and if you want, on a per-message basis, you can change the FCC
folder from the default to something else.

Comment 5

[rhp (gone)]

Another data point is that I am afraid that having yet another copy operation
after a send operation is just asking for more problems. Think of the case
where someone is on IMAP and posts a news message and changes the FCC via the
UI. First, you have an NNTP posting operation...then you have an IMAP copy
operation for default Sent, then you have ANOTHER copy operation for the UI
changed Sent. Seems like a lot of places to have failures.

Also, I would personally only like 1 copy...so if I use the UI selector, I can
keep my sent folder from turning into the monster that it is today.

- rhp

Comment 6

[sol]

Not sure what to do here, since I just have a different opinion on the most
useful implementation of fcc.

As an end user, sometimes I want to drop a copy of a message in a project
folder, but I still want my Sent folder to contain a copy of all messages I have
sent. That way, if I look in a project folder where I think I filed a message
and don't find it, I know that Sent will contain the message. If we don't file
an fcc copy in addition to Sent, then I would need to search other project
folders and search Sent if that failed.

If Rich's performance considerations listed in the last comment are really
worrisome, I'm OK if we go with redirecting the sent message to an alternate
folder and not making another copy. If not, then I prefer the *additional copy*
approach. In any event, I will heavily use this feature, since I often bcc
myself on messages as a workaround for the lack of fcc. (Note that with my bcc
workaround, I still get a copy in my Sent folder.)

Comment 7

[Phil Peterson]

Bulk move rhp bugs to M11 for now

Comment 8

[lchiang]

target milestone is not m11 or m12 so removing this from the mail beta tracking
bug.  Add to feature tracking bug.

Comment 9

[Phil Peterson]

*** Bug 15874 has been marked as a duplicate of this bug. ***

Comment 10

[Phil Peterson]

Can't remember why I marked this bug M15. Maybe I was on drugs. I think we need
FCC for B1. What do you think, Rich.

Comment 11

[rhp (gone)]

We do have FCC....it works the way it worked in 4.5...that is, FCC is actually
the default setting where messages are stored after they are sent successfully.
This bug is the debate if FCC for 5.0 should mean that we have an ADDITIONAL
copy operation in addition to the default FCC operation.

- rhp

Comment 12

[esther]

FYI...This can probably stay at M15 since it is not directly the cause of Copy
to Sent folder not working (15874) in 1999100812M11 builds.  (15685) is the
reason Copy to Sent folder isn't working at this time and that bug has a M11
Target Milestone.

Comment 13

[rhp (gone)]

In a meeting this week, we decided that there will be on additional copy
operation available to the user. This will allow for on extra copy in addition
to the sent folder operation.

I'll need to add this support to the back end, then I would like to pass the FE
over to someone digging around in that part of the code if possible.

- rhp

Comment 14

[rhp (gone)]

This is M12 work.

- rhp

Comment 15

[Jon Granrose]

I'm glad to see we're doing the fcc: in addition to the Sent folder option.  I 
cannot count the number of times I've had users complain about Fcc: going away 
when I was in tech support.  And every single one of them wants to have a Sent 
folder where all their sent mail is saved, and then be able to use Fcc: on a per 
message basis to file a copy of a particular message to a particular 
person/project/etc folder.

Personally, I always Bcc: myself on important messages so that I have a copy, 
and then once it shows up in my inbox, file it in whatever folder is applicable.  
Rooting through the Sent folder, even though I clean it out every month, is not 
pretty.  Having the ability to send a copy of a specific message to a specific 
folder without any additional work is extremely useful.  Useful enough that I'm 
using one of my 5 votes on this bug.

Comment 16

[sol]

If we're not going to do this for beta 1, we need to remove/grey out the menu 
item.

Comment 17

[rhp (gone)]

Checked in this feature on Sunday.

- rhp

Comment 18

[esther]

Using build 2000020709m14 on win98 and 2000020708 on mac and linux this is 
fixed. Verfied