# Don't remove the option “Move automatically to DeltaChat Folder"!

**URL:** <https://forum.delta.chat/t/dont-remove-the-option-move-automatically-to-deltachat-folder/4818>\
**Category:** Uncategorized\
**Tags:** open-standards, classic-mailbox\
**Created:** [February 27, 2026, 8:02pm UTC](https://forum.delta.chat/t/dont-remove-the-option-move-automatically-to-deltachat-folder/4818 "2026-02-27T20:02:05Z")\
**Posts on this page:** 1\
**Showing post:** 44

<div class="post-metadata">

**Author:** ![link2xt](https://forum.delta.chat/user_avatar/forum.delta.chat/link2xt/32/1971_2.png) [@link2xt](https://forum.delta.chat/u/link2xt)\
**Post date:** [October 22, 2026, 7:56pm UTC](https://forum.delta.chat/t/dont-remove-the-option-move-automatically-to-deltachat-folder/4818/44 "2026-10-22T19:56:25Z")

</div>

> [@bleb](#):
>
> How would I enforce this setting on Linux in lieu of a UI option?

You can open the database (e.g. with [sqlitebrowser](https://sqlitebrowser.org)) located somewhere in `~/.config/DeltaChat/accounts`. If you have multiple profiles, refer to `~/.config/DeltaChat/accounts.toml` for the order or just try all databases if you have multiple profiles and check the display name in the `config` table. Then find the `transports` table and modify the transport to add `imap_folder: "DeltaChat"` next to `imap_user` into `configured_param`. Here is an example of how it may look like:

> <https://github.com/chatmail/core/blob/41eed949ac83089283ff8baa6a41b1f1be9de8bc/src/transport/transport_tests.rs#L56>

If you have multiple devices, also increase `add_timestamp` and add and remove another transport in the UI to trigger synchronization of all transports to your other devices.  
This should work with 2.64.0, noting it here because this may get outdated.

> [@bleb](#):
>
> You pay your small monthly fee to an email provider you like and you set up a filter to direct an alias to the DeltaChat folder. This is often easier and more affordable than setting up a separate mailbox dedicated to Delta Chat

I would not call it easier, not all providers even allow aliases and filters. When I tried to configure this sort of filtering with Mailcow I had to use X-Original-To header because there is no way to access original envelope address, it is already rewritten to non-alias address by the time the filter is reached: [It may be unobvious that the "Deltachat" folder use case is going away (update: is apparently still being looked into) - #37 by link2xt](https://forum.delta.chat/t/it-may-be-unobvious-that-the-deltachat-folder-use-case-is-going-away-update-is-apparently-still-being-looked-into/4495/37)

> [@bleb](#):
>
> Is there a technical reason why this usage should be considered “weird” and therefore discouraged?

This problem with writing a proper filter have in the past resulted in users relying on filtering based on `Chat-Version` header. E.g. here is a bad advice that is not going to work anymore: [Sieve rule to move DeltaChat mails to DeltaChat folder - #10 by cracker0dks](https://forum.delta.chat/t/sieve-rule-to-move-deltachat-mails-to-deltachat-folder/288/10)  
But then when the user realizes that the filter does not work and they cannot write a working filter, they are already receiving a lot of chat messages in their inbox and cannot get rid of them.

If you have your own server or server operated by someone for you, setup a separate mailbox with a separate login instead of an alias and a folder. There is no technical reason for why aliases are cheaper than proper mailboxes.

---

_[View the full topic](https://forum.delta.chat/t/dont-remove-the-option-move-automatically-to-deltachat-folder/4818)._