Feature Request: Allow Disabling the Default Signature for Individual Identities
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- backend
Research direction
Start by reading the identity and alias signature settings and the compose flow where the global default is applied. The issue does not name files or tests, so trace how blank custom signatures fall back to the global setting. Done means each identity can use the global signature, use a custom signature, or disable signatures regardless of the global default.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Currently, Mailflow has a global “Show signature by default” option that applies to all identities and aliases. While each identity can have its own custom signature, there is no way to explicitly disable the signature for a particular identity. Leaving the signature blank causes the global default signature to appear, even when I don't want one.
Describe the solution you'd like
Add an option to disable signatures for individual identities or aliases, regardless of the global default setting. Ideally, each identity should support three choices: use the global default signature, use a custom signature, or disable the signature entirely.
Describe alternatives you've considered
I considered leaving the signature field blank for the identity, but this doesn't work because Mailflow falls back to the global default signature. Disabling the global setting is also not ideal, as I still want signatures enabled for my other identities.
Additional context
This would be particularly useful for aliases used for different purposes, where a signature may not always be appropriate. I've attached a screenshot showing the current identity signature settings for reference.
- Dominant language
- JavaScript
- Stars
- 518
- Forks
- 50
- Avg merge
- 4d 45m
- Merged PRs (30d)
- 43
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from maathimself/mailflow
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
maathimself/mailflow#801 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
maathimself/mailflow#784 ·
Maintainers usually reply within 1 day
-
defaultShortcuts tests fail on macOSPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
maathimself/mailflow#783 ·
Maintainers usually reply within 1 day
-
Stored mail loses blockquote type=cite, so AI actions read Apple Mail and Thunderbird quoted historyOpen
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
maathimself/mailflow#782 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
maathimself/mailflow#799 ·
Maintainers usually reply within 1 day
All issues in maathimself/mailflow
Similar issues
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-token-meta#17 ·
-
enhancement good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
blixvip/solana-tx-parse#18 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
blixvip/solana-rpc-bench#18 ·
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100