| Summary | Mark messages as draft when being copyied/moved into the drafts folder |
| Queue | IMP |
| Queue Version | 4.3.6 |
| Type | Enhancement |
| State | Rejected |
| Priority | 1. Low |
| Owners | |
| Requester | klaeser (at) univention (dot) de |
| Created | 06/09/2011 (5117 days ago) |
| Due | |
| Updated | 06/10/2011 (5116 days ago) |
| Assigned | |
| Resolved | 06/09/2011 (5117 days ago) |
| Milestone | |
| Patch | Yes |
instead meant to allow any message to act as a sort of "template"
for a future message. Setting as a draft is not proper for this
action.
specifications says the following about the \Drafts flag:
"Message has not completed composition (marked as a draft)."
So there is no other "very specific meaning" than "mark the message as
a draft". I understand, though, that a different approach where any
message in the drafts folder can be used as sort of template would be
a better one since it would preserve the original template (instead of
sending it away as this patch would do). However, seeing from a
pragmatic point of view and given that Horde interpretates this flag
correctly, I do not see any problem with this patch as a valid
workaround for a template-like functionality.
been fully implemented yet.
State ⇒ Rejected
instead meant to allow any message to act as a sort of "template" for
a future message. Setting as a draft is not proper for this action.
This kind of template support is planned for IMP 5.1, but has not been
fully implemented yet.
Priority ⇒ 1. Low
New Attachment: imp_mark_messages_as_drafts.patch
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ IMP
Summary ⇒ Mark messages as draft when being copyied/moved into the drafts folder
Type ⇒ Enhancement
State ⇒ New
draft flag ist only set when a new message is saved as draft. However,
in day-to-day business, it can be very useful to copy an existing
email and be able to modify it. The attached patch marks messages that
are copied/moved into the drafts folder as draft so that can be
resumed and modified.