We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Only the following options make sense for chatmail:
delete_server_after=0
delete_server_after=1
See deltachat/deltachat-android#3147 for the reference implementation. NB: Auto-adjusting of delete_server_after isn't needed, Core >= 1.143 will do that on its own (see deltachat/deltachat-core-rust#5840).
delete_server_after
Probably this may be done even after switching to new Core, but better before -- at least for consistency with DC Android.
The text was updated successfully, but these errors were encountered:
The same issue for iOS: deltachat/deltachat-ios#2296
Sorry, something went wrong.
Limit options for "Delete Messages from Server" for chatmail accounts
83d7168
closes #4113
37c349d
Limit options for "Delete Messages from Server" for chatmail accounts (…
d4e658e
…#4276) * Limit options for "Delete Messages from Server" for chatmail accounts closes #4113 * Apply suggestions from code review Co-authored-by: WofWca <[email protected]> * Update packages/frontend/src/components/Settings/Autodelete.tsx Co-authored-by: WofWca <[email protected]> * fix fmt --------- Co-authored-by: WofWca <[email protected]>
Simon-Laux
Successfully merging a pull request may close this issue.
Only the following options make sense for chatmail:
delete_server_after=0
i.e. the server decides when to delete messages).delete_server_after=1
).See deltachat/deltachat-android#3147 for the reference implementation. NB: Auto-adjusting of
delete_server_after
isn't needed, Core >= 1.143 will do that on its own (see deltachat/deltachat-core-rust#5840).Probably this may be done even after switching to new Core, but better before -- at least for consistency with DC Android.
The text was updated successfully, but these errors were encountered: