443906 - switch to disable email forwarding in filters

Status: RESOLVED WONTFIX

(Thunderbird :: General, enhancement)

Description

[Noèl Köthe]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9) Gecko/2008062908 Iceweasel/3.0 (Debian-3.0~rc2-2)
Build Identifier: 

In an enterprise enviroment it is sometimes not allowed to forward emails to your private/other account.
In Thunderbird 1.5, 2.0 it is possible to create a filter which forwards emails to another email address.
The request is have an (compile) option, configuration switch which disables "forward to:" in actions.

Reproducible: Always

Steps to Reproduce:
1.email filters
2.actions
3.forward to:
Actual Results:  
to action "forward to:" is available

Expected Results:  
the "option "forward to:" is not available

Comment 1

[Mark Banner (:standard8)]

I very much doubt we would do this on a compile-time option. You could probably write an extension to override that menu, another option could be that we provide a pref to disable various options based on the setting of that pref, you would then be able to lock that preference via our current methods for pref locking.

Comment 2

[Noèl Köthe]

Yes, this is correct. A preference option would be the best.

Comment 3

[Tobias Koenig]

Attachment: Adds preference to disable 'Forward Message to' entry

This patch adds a new preference 'mail.forward_restricted' of type boolean, which disables the 'Forward Message to' action in the filters edit dialog
if the preference is set to true.

Question to reviewer: Should a better naming be used? If yes, what name is preferred?

Comment 4

[Magnus Melin [:mkmelin]]

I have a hard time imagining there is any real demand for this functionality, and suggest to keep (make) it an extension. 

Comment 5

[jra]

Y'know, that's not the first time I've seen "I have a hard time imagining anyone needs this" in a bug comment that was started with an explanation of who needs it, and it's getting pretty tiresome.

I'm not sure we *care* if you can imagine it.

Comment 6

[Magnus Melin [:mkmelin]]

Well, IMO the use case is invalid. It's just (possibly) satisfying some corporation use case where that corp refuse to trust their employees. Or rather making it appear that way, taking away functionality without a sane reason. We can add corporate features, but we shouldn't when it's pretty clear they could/should handle it by other means by a) informing employees, b) filter outgoing mail on the server side c) make it an extension

Also , the patch doesn't really disable the forwarding functionality, so anyone could still make a filter at home, drop in the filter file in their profile and have it work. 

Comment 7

[Tobias Koenig]

Ok, after some discussion with the bug reporter we came to the same conclusion.
Can someone with enough rights close the bug report, please?