Summary | Make getUser configurable for vfs |
Queue | Ingo |
Queue Version | Git master |
Type | Enhancement |
State | Rejected |
Priority | 2. Medium |
Owners | |
Requester | rob (at) lensen (dot) nu |
Created | 01/15/2013 (4554 days ago) |
Due | |
Updated | 04/19/2013 (4460 days ago) |
Assigned | |
Resolved | 01/15/2013 (4554 days ago) |
Milestone | |
Patch | No |
Ingo::getUser() is used instead of Ingo::getUser(false)
Horde Groupware Webmail Edition 5.0.4
Horde (horde) 5.0.4
Filters (ingo) 3.0.3
Mail (imp) 6.0.4
FreeBSD port system.
Version displayed is:
E-mail (imp) 6.0.3
Filters (ingo) 3.0.2
Horde (horde) 5.0.3
But still the whole folder is made
horde installation with <username>@<domain>
State ⇒ Rejected
Priority ⇒ 2. Medium
Type ⇒ Enhancement
Summary ⇒ Make getUser configurable for vfs
Queue ⇒ Ingo
Milestone ⇒
Patch ⇒ No
State ⇒ New
change in the Ingo::getUser function.
I use a vpopmail setup with maildrop as filter and my users are stored as
/<domain>/<username>/Maildir
where <username> is without domain name. So I have :
'vfs_path' => '%d/%u/'
However the %u is now replaced with <username>@<domain> probably since
this is the way I log in to the server
So the result is that the maildrop script was stored in
<domain>/<username>@<domain>/.mailfilter and not as used to be:
<domain>/<username>/.mailfilter
I fixed this by a small change in lib/Transport/Vfs.php
Line 115 changed Ingo::getUser() to read Ingo::getUser(false)
It would be nice that this can configured, so I don't have to updates
vfs.php after every upgrade.