nix-community / home-manager

Manage a user environment using Nix [maintainer=@rycee]
https://nix-community.github.io/home-manager/
MIT License
6.94k stars 1.8k forks source link

bug: aerc.smtpAuth setting is not set in thunderbird #4777

Open lcnbr opened 10 months ago

lcnbr commented 10 months ago

Are you following the right branch?

Is there an existing issue for this?

Issue description

I have the following settings for my university email: https://github.com/lcnbr/nixosConf/blob/5a4704d1c9f38ddae12acf2422bdc16480de70ea/home-manager/users/lcnbr.nix#L32 However thunderbird does not seem to respect the setting.

Maintainer CC

No response

System information

- system: `"x86_64-linux"`
 - host os: `Linux 6.1.63, NixOS, 24.05 (Uakari), 24.05.20231129.e92039b`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - channels(root): `"nixos, nixos-hardware"`
 - nixpkgs: `/nix/store/cjvwy2rr87ir1nb6wvs9n6lvbnzlqrdg-source`
stale[bot] commented 7 months ago

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.

DerRockWolf commented 4 months ago

This is expected because aerc.smtpAuth is an option specific to aerc and the aerc home-manager module. For thunderbird specific options see accounts.email.accounts.<name>.thunderbird.*.

lcnbr commented 4 months ago

Ahh, but then how do I set the autentication? I don't see many options..

DerRockWolf commented 4 months ago

You sadly can't do so declaratively, but Thunderbird prompts you for passwords if it needs one. They can then optionally be persisted in Thunderbirds internal password store.

If you find a preference that could be set to make this more declarative, let us know.

stale[bot] commented 1 month ago

Thank you for your contribution! I marked this issue as stale due to inactivity. Please be considerate of people watching this issue and receiving notifications before commenting 'I have this issue too'. We welcome additional information that will help resolve this issue. Please read the relevant sections below before commenting.

If you are the original author of the issue

* If this is resolved, please consider closing it so that the maintainers know not to focus on this. * If this might still be an issue, but you are not interested in promoting its resolution, please consider closing it while encouraging others to take over and reopen an issue if they care enough. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

If you are not the original author of the issue

* If you are also experiencing this issue, please add details of your situation to help with the debugging process. * If you know how to solve the issue, please consider submitting a Pull Request that addresses this issue.

Memorandum on closing issues

Don't be afraid to manually close an issue, even if it holds valuable information. Closed issues stay in the system for people to search, read, cross-reference, or even reopen – nothing is lost! Closing obsolete issues is an important way to help maintainers focus their time and effort.