Skip to content
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

Chatmail accounts should not use "move-to-deltachat" #5380

Closed
hpk42 opened this issue Mar 26, 2024 · 3 comments · Fixed by #5567
Closed

Chatmail accounts should not use "move-to-deltachat" #5380

hpk42 opened this issue Mar 26, 2024 · 3 comments · Fixed by #5567
Assignees

Comments

@hpk42
Copy link
Contributor

hpk42 commented Mar 26, 2024

Delta Chat should detect XCHATMAIL capability when connecting to IMAP and disable "move-to-deltachat" in this case.
Whether the server is a chatmail server should also be available to the UI via is_chatmail config value. The value of is_chatmail should be reset on reconfiguration and set when connecting to IMAP so it is set even for existing chatmail accounts.

Corresponding chatmail PR: deltachat/chatmail#278

@hpk42
Copy link
Contributor Author

hpk42 commented May 2, 2024

i think XCHATMAIL is better as a marker.

@adbenitez
Copy link
Member

I think all that is needed actually is just to disable the permissions to create folders, some servers already do this I think and Delta Chat tries to create the DeltaChat folder there, fails and then since there is no DeltaChat folder it only watch INBOX,

a XCHATMAIL flag might still be useful for other purposes but it doesn't avoid ex. old clients still creating folders

@hpk42
Copy link
Contributor Author

hpk42 commented May 2, 2024

looked a bit in dovecot docs but did not find a config to prevent folder creation. I guess one needs to play with unix-filesystem permissions to do so. An XCHATMAIL marker can also help to tweak other behaviours -- e.g. #5381

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

3 participants