Thanks for your feedback. I did not remove the doFcc check, I just moved it below the initial check if an fcc value has been set. I still return "" if doFcc is false and no fcc override has been set. But if you think it is better to have just a partial override, I can restore the old behaviour (the folder set in defaultFcc will be ignored, if the used identity has fcc disabled). But it will break my overall concept (see below). For your second remark: The "disabled" value does not reflect the state of the identity, but the state of the override. This is what I want to achieve: "default" : do not change the default behaviour "disabled": force the fcc to be disabled (regardless what the default identity setting is) Mailfolder: force the fcc to store a copy in that folder (regardless what the default identity setting is) That is the most straightforward interface, I think. Do you agree, or am I missing something?
Bug 1746348 Comment 28 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Thanks for your feedback. I did not remove the doFcc check, I just moved it below the initial check if an fcc value has been set. I still return "" if doFcc is false and no fcc override has been set. But if you think it is better to have just a partial override, I can restore the old behaviour (the folder set in defaultFcc will be ignored, if the used identity has fcc disabled). But it will break my overall concept (see below). For your second remark: The "disabled" value does not reflect the state of the identity, but the state of the override. This is what I want to achieve: "default" : follow the default behaviour "disabled": force the fcc to be disabled (regardless what the default identity setting is) Mailfolder: force the fcc to store a copy in that folder (regardless what the default identity setting is) That is the most straightforward interface, I think. Do you agree, or am I missing something?
Thanks for your feedback. I did not remove the doFcc check, I just moved it below the initial check if an fcc value has been set. I still return "" if doFcc is false and no fcc override has been set. But if you think it is better to have just a partial override, I can restore the old behaviour (the folder set in defaultFcc will be ignored, if the used identity has fcc disabled). But it will break my overall concept (see below). For your second remark: The "disabled" value does not reflect the state of the identity, but the state of the override. This is what I want to achieve: "default" : follow the default behaviour "disabled": force the fcc to be disabled (regardless what the default identity setting is) MailFolder: force the fcc to store a copy in that folder (regardless what the default identity setting is) That is the most straightforward interface, I think. Do you agree, or am I missing something?