thunderbird / thunderbird/thunderbird-android
identities do not always adhear to signature setting in composition default
Open
Nobody has claimed this yet.
type: enhancement
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Expected behavior
- When changing the signature in composition default, all identities should update to this signature, or a prompt should come up asking if it should overwrite all identities.
- When adding a new identity, it should by default assume the signature as set in composition default
Actual behavior
- When changing the signature in composition default, identities retain their current signature.
- New identities have no signature, even though composition default it set.
Steps to reproduce
- create account
- create 1 or more new identities
- set a composition default signature
- create more identities
- realise it's weird and you are glad someone reported this (thank me later)
- thank me
Environment
K-9 Mail version:
5.400
Android version:
7.0
Account type (IMAP, POP3, WebDAV/Exchange):
IMAP
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in K-9 Mail 5.400 on Android 7.0 with an IMAP account, following the listed identity and composition-default steps. Trace where composition defaults and identity signatures are stored and applied. Done means existing identities update or prompt on signature changes, and new identities inherit the configured default signature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100