Catch-all customizable sender for Thunderbird for Android

[kewisch]

As per https://github.com/thunderbird/thunderbird-android/issues/935

Identity selection could be enhanced to make life a lot easier for people who have a catch-all domain, similar to how Thunderbird allows customizing the sender.

Identity selection should be :
-free to edit and modify when writing a message (more or less as the recipient field currently is)
-automatically set with the best value guessed from the recipient values, when replying.
This would be a great feature to differentiate K9 mail from other rigid email clients.

[Jon]

Thanks for submitting an idea to the Mozilla Connect community! Your idea is now open to votes (aka kudos) and comments.

[SR__]

I like this idea 😉

[jpg]

Just want to indicate that there is 42 "+1" for this feature on https://github.com/thunderbird/thunderbird-android/issues/935 😉👍

[Jon]

@jpg thanks for sharing link! Always helps as we evaluate ideas. 

[bobemoe]

Definitely! I've been following the GitHub issue for many years now and even switched to FairEmail because of this. I do prefer Thunderbirds interface though so would love to switch back. Looking forward to the day I can!

Recent post on GitHub suggest:

Another way to contribute is to kick off a development discussion by providing some real feedback and insight on how the feature could look like and work. Especially, design mockups were requested by the team and could be a good first step to get some momentum going and possibly show, that the amount of effort is low enough for a quick implementation:

However I don’t think there is really any UX/Spec design to do, there is tones of feedback and use cases on that GH issue and its linked issues, and this is already implemented perfectly in Thunderbird Desktop: I enter "*@my.domain.tld" into the "Reply from this identity when delivery headers match:" field in the account settings for the specific account and then anything matching that wildcard is automatically selected as the "from" address on that account when replying.

I'd just love to see feature parity! Feels like a text field and a bit of logic needed probably portable from the desktop app!? I suspect there is a fundamental technical difference between the two preventing this happening? Any ideas what the road block is?

Thanks all 🙂