-
-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check_encrypted too strict, doesn't work with K-9, for example #209
Comments
Unencrypted mail is prohibited because we want to avoid spam, more specifically sending unwanted content to people whose public key you don't know. The subject is a message part which is typically shown in the recipient's UI, and therefore interesting for spammers, that's why we want to avoid showing it. I suggest to also allow |
It occurred to us that chatmail could simply normalize the subject to |
On Mon, Feb 05, 2024 at 07:36 -0800, Justus Winter wrote:
chatmail was pitched to me as allowing encrypted outbound mail, and working with clients other than delta.chat.
We don't guarantee other clients work. If there are small things
to make it work for other clients, that's fair game, however.
There is upcoming work to provide Delta Chat Core<->Chatmail integration
so that settings such as automatic message-removal and e-mail routing policies
can be set from within the app. See #185
There is, for now, no plan to add a web-interface like typical e-mail providers offer.
I believe the reason for that is that the function `check_encrypted` is too strict and checks that the subject is `...`. K-9 on the other hand, if subject encryption is enabled, sets the unencrypted subject to `Encrypted Message`.
Is this `Encrypted Message` subject localized?
If not, wouldn't it rather make sense if K-9 also used "..."?
The "..." subject was at some point discussed by Autocrypt folks,
including Patrick and Vincent IIRC, and was commonly agreed to be the best choice
as it does not need any localization (which is tricky, because sender-localization
might be different from receiver-localization).
|
On Mon, Feb 05, 2024 at 15:10 -0800, Justus Winter wrote:
It occurred to us that chatmail could simply normalize the subject to `[...]` instead.
do you mean we could overwrite the clear-text subject to "..." when we find a
valid PGP-mime structure? I am not currently using K-9 -- could you try to provide
a more precise algorithm or a PR for making K-9 work, or, failing that,
provide example full-source K-9 generated messages that are rejected by chatmail?
|
I don't think I have asked for a web interface.
I don't know, I am not a K-9 developer.
I'm the wrong person to suggest this to, I am not a K-9 developer.
Yes.
Sure:
|
i started a PR at https://github.com/deltachat/chatmail/compare/allow_k9_encrypted_subject?expand=1 but then went to look in k-9 source and it localizes "Encrypted Subject" ( https://github.com/thunderbird/thunderbird-android/blob/main/app/ui/legacy/src/main/res/values/strings.xml#L1064 ) so we can not reasonably detect it, especially since we want our focus on chatmail/deltachat usage for the time being. Overwriting the subject because it contains a valid pgp-encryption body mime structure i consider too surprising to users. thereby closing this issue. Thanks for reporting anyway, and if needed we can revive the branch, and/or talk to cketti some time (as far as i see they are pretty focused on doing a first thunderbird/android release with unclear ETA) |
Seems like this concern should at least be reported to k-9/thunderbird-android, so i've done that. |
See also #370 |
chatmail was pitched to me as allowing encrypted outbound mail, and working with clients other than delta.chat. However, when I tried to send an encrypted outbound mail using K-9, it was rejected, saying that the message is not encrypted when in fact it was.
I believe the reason for that is that the function
check_encrypted
is too strict and checks that the subject is...
. K-9 on the other hand, if subject encryption is enabled, sets the unencrypted subject toEncrypted Message
. If I disable subject encryption, and manually use...
as subject, my mail is relayed.I don't think
check_encrypted
should consider the subject at all. Looking at draft-ietf-lamps-header-protection-18 it seems to me that there is no fixed replacement string to obscure the subject with, with the recommended default being[...]
.The text was updated successfully, but these errors were encountered: