-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
Add Python tests for message forwarding from encrypted to unencrypted chat #5123
Comments
So it seems we managed to pin down the issue... do you have an idea which is the latest core version which doesn't force encryption like this? Then I could pin the deltachat version in teams-bot as a quickfix. |
It was always working like this I think. |
no, if the message is forwarded like this, and was encrypted, but not in a protected group, it works - see the test in the first commit of the attached PR, before I made it run in a protected group in the second commit. |
ah wait, it was with an unencrypted message, my bad. You are correct, it was always working like this I guess. |
Related teams-bot issue: https://git.0x90.space/missytake/teams-bot/issues/16 |
Taking a Message object (dc_msg_t) of incoming message and sending it to another chat should work:
https://git.0x90.space/missytake/teams-bot/src/commit/b899b6c3eb8514d39470c2f7a3eed2acb86ffe81/src/teams_bot/bot.py#L198
Currently it seems not to clear Param::GuaranteeE2ee so if the message has a padlock this param is set but for outgoing message it means that encryption should actually be guaranteed and fails sending if there is no key for some recipient.
The text was updated successfully, but these errors were encountered: