[Tickets #10214] Re: Mark messages as draft when being copyied/moved into the drafts folder

[bugs at horde.org]

BITTE NICHT AUF DIESE NACHRICHT ANTWORTEN. NACHRICHTEN AN DIESE  
E-MAIL-ADRESSE WERDEN NICHT GELESEN.

Ticket-URL: http://bugs.horde.org/ticket/10214
------------------------------------------------------------------------------
  Ticket           | 10214
  Aktualisiert Von | klaeser at univention.de
  Zusammenfassung  | Mark messages as draft when being copyied/moved into the
                   | drafts folder
  Warteschlange    | IMP
  Version          | 4.3.6
  Typ              | Enhancement
  Status           | Rejected
  Priorität        | 1. Low
  Milestone        |
  Patch            | 1
  Zuständige       |
------------------------------------------------------------------------------


klaeser at univention.de (2011-06-10 13:00) hat geschrieben:

Thanks a lot for your response.

> The \Drafts flag has a very specific meaning in IMAP.  This patch is  
> 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.

I'm not sure whether I exactly understand your argumentation. The IMAP  
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.

> This kind of template support is planned for IMP 5.1, but has not  
> been fully implemented yet.

Great, looking forward to it.