| Summary | Allow empty subject for vacation |
| Queue | Ingo |
| Queue Version | Git master |
| Type | Enhancement |
| State | Feedback |
| Priority | 1. Low |
| Owners | |
| Requester | skhorde (at) smail (dot) inf (dot) fh-bonn-rhein-sieg (dot) de |
| Created | 05/15/2014 (4017 days ago) |
| Due | |
| Updated | 01/28/2016 (3394 days ago) |
| Assigned | |
| Resolved | |
| Milestone | |
| Patch | Yes |
subject form field has to be mandatory in Ingo_Form_Vacation. Then
make it optional in sieve's features.
bug #8376which made subject and reason mandatory.State ⇒ Feedback
Version ⇒ Git master
about the other script implementations that we support. Maybe we can
unconditionally make this a non-required field.
Priority ⇒ 1. Low
New Attachment: h5_ingo-vacation_empty-subject.diff.bz2
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ Allow empty subject for vacation
Type ⇒ Enhancement
State ⇒ New
and adds its own autogenerated one, which includes the subject line of
the incoming message.
Attached patch adds a backend option to allow this for Sieve.
I used a positive backend option name "subject_can_empty" and a
positive feature "subject_needed", in order to:
1) if the backend option is false or absent, the current behaviour is
the default,
2) if the feature is absent, the current behaviour is the default.
So, the config must set "subject_can_empty = true", in order to
change the current behaviour.
Can you easily remove one feature from a Horde_From_Vacation feature
list? I enumerated all features I found in the form.