Summary | Ingo Sieve driver: Allow including original $subject into vacation response |
Queue | Ingo |
Queue Version | Git master |
Type | Enhancement |
State | Rejected |
Priority | 1. Low |
Owners | |
Requester | ralf.lang (at) ralf-lang (dot) de |
Created | 03/03/2013 (4504 days ago) |
Due | |
Updated | 03/04/2013 (4503 days ago) |
Assigned | |
Resolved | 03/04/2013 (4503 days ago) |
Milestone | |
Patch | No |
State ⇒ Rejected
You can only leave out the subject completely which would
auto-generate a subject line constructed from the original message.
It is possible to store the old Subject with the "variables"
extension and add it later to the auto-reply subject line.
not supported by any other of Ingo's filter backends, and requiring
knowledge of internal Sieve (variables) syntax, though. This is more a
hack than a general approach to this problem.
You can only leave out the subject completely which would
auto-generate a subject line constructed from the original message.
It is possible to store the old Subject with the "variables" extension
and add it later to the auto-reply subject line.
-----snip-----
require ["variables", "vacation"] ;
# store old subject to variable "old_subject"
if header :matches "Subject" "*" {
set "old_subject" ": ${1}";
}
vacation
:days 7
:subject "Out of office - ${old_subject}"
"I am out of office until .........";
-----snip-----
This will create a subject for the auto-reply: "Out of office - I am
the old subject"
see RFC5229 - http://tools.ietf.org/html/rfc5229
greets
Milestone ⇒
State ⇒ Rejected
You can only leave out the subject completely which would
auto-generate a subject line constructed from the original message.
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ Ingo Sieve driver: Allow including original $subject into vacation response
Queue ⇒ Ingo
Milestone ⇒ Ingo H5.1
Patch ⇒ No
State ⇒ New
Re: Invitation for meeting ... (Out of office) which allows the
receiver to recognize the original mail which triggered the vacation
response.