Global setting to disable HTML
Open, Needs TriagePublic

Description

Since Kube is dealing with PGP-encrypted e-mails, it would be good to have a global setting to disable HTML in e-mails entirely.

Lack of this option makes it impossible to deploy Kube in organizations where HTML rendering is supposed to be disabled as organization-wide policy.

wozniak created this task.Apr 18 2019, 9:48 PM

This would be relatively simple to add, but I wouldn't want to have that as an option in the UI. Would a configuration-file option work and is there a concrete deployment planned that actually requires such an option?

This would be relatively simple to add, but I wouldn't want to have that as an option in the UI

I think it would be *nice* to have it in the UI, but I understand the reasons you might not want it. The reason it would be nice is that on support calls it's easier to tell the user to toggle an UI option, than to mess with a config file.

On the other hand, config-file-only option means users would be less likely to disable it themselves. So I can live with that!

Would a configuration-file option work

Yes.

is there a concrete deployment planned that actually requires such an option?

I work with (and am responsible for information security of) a few hundred journalists at OCCRP who are pretty tired of Thunderbird. We are constantly looking for a decent e-mail client, and Kube looks very promising.

By the way, I had some (not a lot) experience with QML so if I were to be pointed in the right direction, I *might* be able to submit a patch for this.

This would be relatively simple to add, but I wouldn't want to have that as an option in the UI

I think it would be *nice* to have it in the UI, but I understand the reasons you might not want it. The reason it would be nice is that on support calls it's easier to tell the user to toggle an UI option, than to mess with a config file.

On the other hand, config-file-only option means users would be less likely to disable it themselves. So I can live with that!

Cool =) If it's a organization-wide policy the point would exactly be to not have to deal with such support calls, because you'd just always configure it that way for the deployment.

Would a configuration-file option work

Yes.

is there a concrete deployment planned that actually requires such an option?

I work with (and am responsible for information security of) a few hundred journalists at OCCRP who are pretty tired of Thunderbird. We are constantly looking for a decent e-mail client, and Kube looks very promising.

Great =) If it is promising enough we should probably have a look at what features are currently missing to make this viable for your usecase.

By the way, I had some (not a lot) experience with QML so if I were to be pointed in the right direction, I *might* be able to submit a patch for this.

It should be possible to implement the necessary logic in framework/src/domain/partmodel.cpp (see TypeRole and ContentRole).
For the setting I'd just use QSettings