Skip to content

refactor: remove ConfiguredAddr - #8711

Draft
link2xt wants to merge 1 commit into
mainfrom
link2xt/remove-configured-addr
Draft

link2xt wants to merge 1 commit into
mainfrom
link2xt/remove-configured-addr

Conversation

@link2xt

@link2xt link2xt commented Sep 17, 2026 •

Copy link
Copy Markdown
Collaborator

Closes #8572

@link2xt
link2xt force-pushed the link2xt/smtp-failover branch from 2deae58 to 6ad0f04 Compare September 17, 2026 19:00
@link2xt
link2xt force-pushed the link2xt/remove-configured-addr branch from 46acbc7 to 494be7f Compare September 17, 2026 19:00
@link2xt
link2xt force-pushed the link2xt/smtp-failover branch from 6ad0f04 to afca961 Compare September 18, 2026 08:10
@link2xt
link2xt force-pushed the link2xt/remove-configured-addr branch from 494be7f to 9b3f6a6 Compare September 18, 2026 08:10
@link2xt
link2xt force-pushed the link2xt/smtp-failover branch 2 times, most recently from 4fc4ff3 to 4750068 Compare September 18, 2026 16:53
Base automatically changed from link2xt/smtp-failover to main September 18, 2026 17:10
@link2xt
link2xt force-pushed the link2xt/remove-configured-addr branch 2 times, most recently from 7c0aec6 to 233c2cb Compare September 19, 2026 20:19
@link2xt
link2xt force-pushed the link2xt/remove-configured-addr branch 8 times, most recently from ae10a5e to 240121c Compare October 9, 2026 20:28
@link2xt link2xt changed the title WIP: remove maybe_update_sending_transport (and remaining usage of ConfiguredAddr) WIP: refactor: remove ConfiguredAddr Oct 9, 2026
@link2xt link2xt changed the title WIP: refactor: remove ConfiguredAddr refactor: remove ConfiguredAddr Oct 9, 2026
@link2xt
link2xt force-pushed the link2xt/remove-configured-addr branch from 240121c to 4acf71d Compare October 9, 2026 20:34
@pbuzdin

This comment was marked as low quality.

@link2xt

link2xt commented Oct 9, 2026 •

Copy link
Copy Markdown
Collaborator Author

@pbuzdin please create a separate account for your bot and don't let it post any comments in any chatmail or deltachat organization repositories. There are some community standards at https://delta.chat/en/community-standards, but even if they were not written down, it should be obvious that it is not great to run a bot that posts comments here pretending to be a human and then note that "a first-class preferred-transport concept has been requested there (comment 6090501441)" in pbuzdin/velta#114 (comment)

@pbuzdin

pbuzdin commented Oct 10, 2026

Copy link
Copy Markdown

That wasnt a bot comment. I wrote it myself because I'm having trouble using Deltachat in my region without manually selecting a relay for sending.

@r10s

r10s commented Oct 10, 2026 •

Copy link
Copy Markdown
Contributor

our idea for situation "one relay cannot send" is to improve sending failover. or, in the future, replacing that relay automatically.

adding more options, that most ppl would not understand, is often not a solution from our view. a configured_addr or used_for_sending were always meant as temporary things since we introduced multi relay. not having tons of options is also easier for us to debug and to get the model.

nerds detecting smth is wrong with a relay, by some log or so, can remove it.

as a general rule of thumb, we avoid options and beforehand questions whereever we can.

btw: the screenshots of velta look great!

@link2xt
link2xt force-pushed the link2xt/remove-configured-addr branch from 4acf71d to e073767 Compare October 10, 2026 17:46
@link2xt
link2xt force-pushed the link2xt/remove-configured-addr branch from e073767 to f25c3ac Compare October 10, 2026 19:18

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

dissolve "primary" relay notion (configured_addr)

3 participants