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

link2xt · October 22, 2026, 7:56pm

You can open the database (e.g. with sqlitebrowser) 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:

github.com/chatmail/core

src/transport/transport_tests.rs

41eed949a


      
              }],
              smtp_user: "".to_string(),
              smtp_password: "bar".to_string(),
              certificate_checks: ConfiguredCertificateChecks::Strict,
          };
          
          param
              .clone()
              .save_to_transports_table(&t, &EnteredLoginParam::default(), time())
              .await?;
          let expected_param = r#"{"addr":"alice@example.org","imap":[{"connection":{"host":"imap.example.com","port":123,"security":"Starttls"},"user":"alice"}],"imap_folder":"Folder","imap_user":"","imap_password":"foo","smtp":[{"connection":{"host":"smtp.example.com","port":456,"security":"Tls"},"user":"alice@example.org"}],"smtp_user":"","smtp_password":"bar","certificate_checks":"Strict","oauth2":false}"#;
          assert_eq!(
              t.sql
                  .query_get_value::<String>("SELECT configured_param FROM transports", ())
                  .await?
                  .unwrap(),
              expected_param
          );
          assert_eq!(t.is_configured().await?, true);
          let (_transport_id, loaded) = ConfiguredLoginParam::load_all(&t).await?.remove(0);
          assert_eq!(param, loaded);

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.

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

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
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.