| Summary | New ingo preference: max_forward_addresses |
| Queue | Ingo |
| Queue Version | Git master |
| Type | Enhancement |
| State | Feedback |
| Priority | 1. Low |
| Owners | |
| Requester | almarin (at) um (dot) es |
| Created | 07/12/2011 (676 days ago) |
| Due | |
| Updated | 01/30/2013 (108 days ago) |
| Assigned | |
| Resolved | |
| Attachments | ingo_max_forwards_perm_patch.tgz ![]() |
| Milestone | |
| Patch | Yes |
Version ⇒ Git master
New Attachment: ingo_max_forwards_perm_patch.tgz
a maximun number of forward recipients
too much the new permission system, but maybe the better way to
implement this functionality would be a script-specific param. As far
as i know, this limitation of number of forward recipients is a
"sieve" feature, so this should be checked and implemented inside the
sieve filter according to a parameter specified in key 'scriptparams'
of the backend.
From my point of view it could be a nice enhancement, but i can't
develop a patch so it's up to you to keep this ticket open.
Regards.
State ⇒ Feedback
that as a preference? If this is supposed to get into Ingo 2 (we won't
add any new features to Ingo 1), this should be implemented as a
permission instead.
State ⇒ New
New Attachment: ingo-forward-max-addresses-patch.tgz
Patch ⇒ Yes
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ New ingo preference: max_forward_addresses
Type ⇒ Enhancement
Priority ⇒ 1. Low
We are using Ingo to store forward filters with sieve driver. We have
limited in our mail servers the maximum number of addresses to
forward, but Ingo allows to indicate any number of addresses to forward.
We have developed a patch including a new preference called
max_forward_addresses in ingo prefs, to check it before store the
filters. I don't know if it could be a interesting functionality to
port to Horde 4.
Regards