Skip to content

Conversation

@Simon-Laux
Copy link
Contributor

@Simon-Laux Simon-Laux commented Dec 9, 2025

follow up to #7583

@Simon-Laux
Copy link
Contributor Author

I'm not sure if we can also remove entered_account_settings. the old configure method still seems to exist (set_config then call configure) and atleast bots are not migrated to the new add transport API yet: deltachat-bot/echo#85

@r10s
Copy link
Contributor

r10s commented Dec 9, 2025

i think, already now entered_account_settings can be removed from the info.

even if bots are using setConfig/configure, this will end up in a used_transport_settings, and that is what counts

@Simon-Laux Simon-Laux changed the title fix: remove now redundant "used_account_settings" from Context.get_info() fix: remove now redundant "used_account_settings" and "entered_account_settings" from Context.get_info() Dec 9, 2025
@Simon-Laux Simon-Laux requested a review from r10s December 9, 2025 14:12
@Simon-Laux
Copy link
Contributor Author

python tests still use some of those properties, so this needs another iteration, converting to draft until it is mergable

@Simon-Laux Simon-Laux marked this pull request as draft December 9, 2025 17:44
@Simon-Laux Simon-Laux requested a review from link2xt December 12, 2025 21:16
@Simon-Laux Simon-Laux marked this pull request as ready for review December 12, 2025 21:16
@link2xt
Copy link
Collaborator

link2xt commented Dec 13, 2025

entered_account_settings is sometimes useful, to detect if user has entered the port manually and this results in not using autoconfig.

Copy link
Collaborator

@link2xt link2xt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's merge as is, but entered_transport_settings are useful IMO, we had recently some user who configured port 443 manually and this results in resolving mail.*, imap.* etc. domains that do not exist.

@Simon-Laux
Copy link
Contributor Author

Simon-Laux commented Dec 13, 2025

you can not add relays/transports with invalid configuration. So I think it would be sufficient if the entered & used login params would be just logged to the log on configuration failure.

@Simon-Laux
Copy link
Contributor Author

but entered_transport_settings are useful IMO

So I think it would be sufficient if the entered & used login params would be just logged to the log on configuration failure.

@Simon-Laux Simon-Laux merged commit 5925f72 into main Dec 13, 2025
30 checks passed
@Simon-Laux Simon-Laux deleted the simon/remove-redundant-used_account_settings branch December 13, 2025 21:21
Simon-Laux added a commit that referenced this pull request Dec 15, 2025
…n failure (#7610)

#7587 removed "used_account_settings" and "entered_account_settings"
from Context.get_info(). link2xt pointed out that
entered_account_settings can still be useful to debug login issues, so
tis pr adds logs both on failed configuration attempts.

example warning event:
```
Warning src/configure.rs:292: configure failed: entered params [email protected] imap:unset:***:unset:0:Automatic:AUTH_NORMAL smtp:unset:0:unset:0:Automatic:AUTH_NORMAL cert_automatic, used params [email protected] imap:[mailcow.testrun.org:993:tls:[email protected], mailcow.testrun.org:143:starttls:[email protected]] smtp:[mailcow.testrun.org:465:tls:[email protected], mailcow.testrun.org:587:starttls:[email protected]] provider:none cert_automatic
```

---------

Co-authored-by: iequidoo <[email protected]>
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.

5 participants