enhance k9 mail identity selection / catch-all support
Identity selection could enhanced to make life a lot easier. Today, it is really painful as it is in most client email readers. 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. Why? I use the catch-all of my domain to handle a lot of different addresses. Catch-all is really a great feature as it allows me to give anyone a unique email address in order to send me an email. Consequently, I can, if I receive spam on this address, deduce that this correspondant may have abused my personal information. I also use it to differentiate between groups of interest, without having to mess with a lot of mailboxes or aliases on the server side, as it is a painful task that can never be done correctly and is completely useless. The only problem I see is to correctly select the account to associate with the email to be sent. It could be deduced from the receiving account, when replying. Just use the same. When not replying, either you are in an account view, and it is this account, or you are in the unified view, and this where creativity lies. Simplest solution would be to use the default account, but in my case, it is not the catch-all, so it's not that simple. I would make it this way : if the identity is the one associated with an
Posted by SR-gh on Dec 6, 2015, 10:21 PM
Tags
Related issues
- The only thing keeping me on VSCode these days is the remote SSH development.
- Something similar was done in a sheep model: "A bioactive supramolecular and covalent polymer scaffold for cartilage repair in a sheep m...
- Proposal for OpenHarmony Adaptation of [ ThreadPool ]
- Proposal for a pipe-like operator to chain constructor/method invocations without nesting
- Implement support for Node Stashing
- RSC and CDN interaction makes next.js inefficient for highload projects
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
support (E-commerce)
The only thing keeping me on VSCode these days is the remote SSH development.
Something similar was done in a sheep model: "A bioactive supramolecular and covalent polymer scaffold for cartilage repair in a sheep m...
Proposal for OpenHarmony Adaptation of [ ThreadPool ]
Proposal for a pipe-like operator to chain constructor/method invocations without nesting
Implement support for Node Stashing
RSC and CDN interaction makes next.js inefficient for highload projects
Extract Action Notifier framework for push notifications
Improve support for monorepo by supporting git options such as depth, and sparse checkout
enhance k9 mail identity selection / catch-all support
Identity selection could enhanced to make life a lot easier. Today, it is really painful as it is in most client email readers. 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. Why? I use the catch-all of my domain to handle a lot of different addresses. Catch-all is really a great feature as it allows me to give anyone a unique email address in order to send me an email. Consequently, I can, if I receive spam on this address, deduce that this correspondant may have abused my personal information. I also use it to differentiate between groups of interest, without having to mess with a lot of mailboxes or aliases on the server side, as it is a painful task that can never be done correctly and is completely useless. The only problem I see is to correctly select the account to associate with the email to be sent. It could be deduced from the receiving account, when replying. Just use the same. When not replying, either you are in an account view, and it is this account, or you are in the unified view, and this where creativity lies. Simplest solution would be to use the default account, but in my case, it is not the catch-all, so it's not that simple. I would make it this way : if the identity is the one associated with an
Comments (0)
No comments yet. Start the discussion.