Tickets :: [#1124] message templates

6.0.0-beta1

7/29/25

Summary	message templates
Queue	IMP
Queue Version	HEAD
Type	Enhancement
State	Resolved
Priority	1. Low
Owners
Requester	tmerritt (at) email (dot) arizona (dot) edu
Created	01/10/2005 (7505 days ago)
Due
Updated	10/22/2005 (7220 days ago)
Assigned	01/12/2005 (7503 days ago)
Resolved	10/22/2005 (7220 days ago)
Milestone
Patch	No

10/22/2005 11:02:41 AM	Jan Schneider	Comment #7 State ⇒ Resolved	Reply to this comment
This has been implemented through stationery support in IMP 4.1.

01/12/2005 07:57:49 PM	tmerritt (at) email (dot) arizona (dot) edu	Comment #6 New Attachment: imp.template[1].patch	Reply to this comment
The attached patch gets rid of the separate template template, as well as fixing the warnings when running with E_ALL. Thanks

01/12/2005 06:13:06 PM	Jan Schneider	Comment #5	Reply to this comment
This indeed makes sense, I didn't notice from your patch that this is possible.

01/12/2005 05:57:03 PM	tmerritt (at) email (dot) arizona (dot) edu	Comment #4	Reply to this comment
It is more flexible than using save as draft. Although I didn't implement it yet, my thinking was that this could be used to respond to email with various canned messages for use by support people. This would be able to be used in replies where resuming drafts cannot. If that makes sense for inclusion by somebody other than me I'll go ahead and make the changes that you suggested to the patch.

01/12/2005 05:22:56 PM	Jan Schneider	Comment #3 State ⇒ Assigned	Reply to this comment
How is this different from drafts? Beside that some comments on the patch: - make sure that the code is E_ALL safe - the template template :-) is more or less a copy of the compose template. that makes maintaining it a mess, the general compose template should be extended instead.

01/12/2005 05:01:59 PM	tmerritt (at) email (dot) arizona (dot) edu	Comment #2 New Attachment: imp.template.patch	Reply to this comment
Attached is a patch against HEAD that implements this.

01/10/2005 05:19:16 PM	tmerritt (at) email (dot) arizona (dot) edu	Comment #1 Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ message templates Queue ⇒ IMP State ⇒ New	Reply to this comment
A feature which I think would be useful would be to allow message templates to be stored per user that would either automatically populate some of the fields in a message composition page, at least the message text field. More elaborately, it could pop up a js dialog to fill in variables that are in the template, like a manual version of mail merge.