Summary | Support customizable folder and filename in maildrop-backend for all ingo-generated maildrop files |
Queue | Ingo |
Queue Version | Git master |
Type | Enhancement |
State | Accepted |
Priority | 2. Medium |
Owners | |
Requester | stephan (at) admin (dot) nabira (dot) de |
Created | 09/12/2011 (4993 days ago) |
Due | |
Updated | 02/01/2013 (4485 days ago) |
Assigned | |
Resolved | |
Milestone | |
Patch | No |
Version ⇒ Git master
New Attachment: Recipe.php.diff
ingo/lib/Transport/Vfs.php
The file belonging to the diff posted with this comment is located in
ingo/lib/Script/Maildrop/Recipe.php
New Attachment: Vfs.php.diff
New Attachment: horde4-ingo-mailfilterfolders.zip
the ticketing system. I try it again with a zip-archive.
Priority ⇒ 2. Medium
State ⇒ New
New Attachment: horde4-ingo-mailfilterfolders.rar
Patch ⇒ No
Milestone ⇒
Queue ⇒ Ingo
Summary ⇒ Support customizable folder and filename in maildrop-backend for all ingo-generated maildrop files
Type ⇒ Enhancement
example: /home/%u/mailfilter
%u is substituted to "username" just for the path part, not the filename part.
I need the following substitution working when creating maildrop scripts:
/var/kunden/mailfilter/%u
The same is true for vacation helper files that need to be in a
admin-configurable path and filenames like:
For the vacation message: /var/kunden/mailfilter/%u_vacation.msg
For the mailbot database: /var/kunden/mailfilter/%u_vacation
I have patched my installation in a way that works for me (with
hardcoded paths and just for the maildrop-backend and vfs-transport),
but I suppose this could be of interest to others. In this case there
is some work necessary to generalise my customizations. I am not deep
enough into the horde-code to do this myself, so I report this as
enhancement request with my customizations attached in the hope they
are useful.