Opened 3 years ago
Closed 11 months ago
#1486892 closed Feature Requests (duplicate)
Automatic, context-sensitive choice of Sent folder.
| Reported by: | kaz | Owned by: | |
|---|---|---|---|
| Priority: | 5 | Milestone: | later |
| Component: | Addressbook | Version: | 0.4-beta |
| Severity: | normal | Keywords: | |
| Cc: | m.duelli@… |
Description (last modified by alec)
Currently, when you are composing a new message, you can manually select an alternative Sent folder where it will be filed.
It would be nice if this was context-sensitive. For instance, when sending a message to a particular user in the Address book, it might go to a particular folder associated with that user.
Or perhaps (as an alternative to, or inaddition to the above behavior), roundcube could be aware of the folder context in which a new message is created, and choose a folder according to that.
For instance, suppose I have a folder called Friends where I keep conversations with friends. Suppose I am reading this folder and invoke the command to compose a new message. The program could be aware that I composed a new message in the context of the Friends folder; consequently it could choose that folder for filing the message (or some other configured folder associated with Friends, like a FriendsSent?).
This latter feature should be easy to implement by itself (without the per-user association). You just need a piece of information associated each folder with a Sent folder. This value is used as the default value of the "Save sent message in:" combo box.
This would give us a simple workflow. You see a message in the Inbox, and recognize it needs to be filed into some folder, so you move it there. Next, you switch to that folder and reply. Automatically, the "Save sent message in:" is filled in with the appropriate container for that folder (often, that same folder itself).
Change History (2)
comment:1 Changed 3 years ago by duelli
- Cc m.duelli@… added
comment:2 Changed 11 months ago by alec
- Description modified (diff)
- Resolution set to duplicate
- Status changed from new to closed

Guess, I described the same feature request in #1485945. Please close either of both.