neil@parkwaycc.co.uk Reporter
	Description • 17 years ago

We only set nocopy:// in one place (per app): for clearing the second file copy option. We check for nocopy:// in four places:
* in nsMsgCompose.cpp we check the fcc, which can never be nocopy://
* in nsMsgSend.cpp we check the fcc, which can never be nocopy://
* in nsMsgSend.cpp we check the prefs, which can probably never be nocopy://
* in nsMSgSend.cpp we check the fcc2, and set it to null if it's nocopy://
As far as I can tell, the idea is that you could set the fcc to nocopy:// to inhibit the default copy, but I don't remember seeing any UI for that.

Unless anyone objects I think we should just remove nocopy://

	Phil Ringnalda (:philor)
	Comment 1 • 17 years ago

The only use for it I've seen was to take ten minutes off my life trying to figure out what the point was, while looking at bug 412319.

	Serge Gautherie (:sgautherie)
	Comment 2 • 17 years ago

(In reply to comment #0)
> As far as I can tell, the idea is that you could set the fcc to nocopy:// to
> inhibit the default copy, but I don't remember seeing any UI for that.

See bug 74134: that UI/feature is missing/wanted;
but I don't know if it would need to use nocopy:// or not.

	Günter Gersdorf
	Comment 3 • 15 years ago

I'm the developer of the 'CopySent2Current' add-on and i'm using this feature.

	Michael Harris
	Comment 4 • 15 years ago

As Günther mentions, the "no copy" command of the CopySent2Current add-on uses this feature. This command allows the user to send an email without a copy being saved. This feature is very useful, especially to IMAP users who send "large" attachments and do not want/need these to be copied into any IMAP folder.

By removing nocopy://, the add-on's "no copy" command makes a copy to the trash folder - for IMAP users a real nuisance. An email with a sizeable attachment will be sent twice to the mail server before the sent process terminates. As a workaround the user can interrupt this process by clicking three separate warning dialogs.

See also 503798