[ingo] more variables for maildrop backend vfs_path

[dev at stean.ch]

hello jan,

ticket has been made

regards, stephan


Quoting Jan Schneider <jan at horde.org>:

> Zitat von dev at stean.ch:
>
>> patch is attached. i am unsure about the Ingo.php:getDomain.
>> the Ingo.php:getUser checks whether shares are used or not.
>> i don't know if domains play a role with shares, i don't use
>> them at all.
>>
>> regards, stephan
>>
>>
>> Quoting Jan Schneider <jan at horde.org>:
>>
>>> Zitat von dev at stean.ch:
>>>
>>>> hello all,
>>>>
>>>> i am about to make tests with ingo using maildrop as backend.
>>>> using the latest stable release.
>>>>
>>>> i have running multiple virtual domains on the server and the
>>>> mail users do not have ftp nor ssh access to the server, so
>>>> i need to use one single system user that will be used by the
>>>> backend to transfer the scripts via ftp.
>>>>
>>>> so here some parts out of the backend.php:
>>>>
>>>> $backends['maildrop'] = array(
>>>>  'driver' => 'vfs',
>>>>  'hordeauth' => false,
>>>>  'params' => array(
>>>>      'filename' => '.mailfilter',
>>>>      'username' => 'MAILDROPUSER',
>>>>      'password' => 'MAILDROPPWD',
>>>>      'vfs_path' => '/SOMEWHERE/%u/',
>>>>      'vfstype' => 'ftp',
>>>> ...
>>>>
>>>> now having user sam at domain1 and sam at domain2 which are not the same
>>>> persons, i would get only one single /SOMEWHERE/sam/.mailfilter file.
>>>> setting hordeauth to false, needed to authenticate with a non horde
>>>> user, will cause ingo/lib/Driver/vfs.php to cut off the domain part
>>>> from the user.
>>>>
>>>> is there an existing way to get back the domain part without modifying
>>>> the ingo scripts?
>>>
>>> 'hordeauth' => 'full'
>>>
>>>> or what about extending ingo in a future release to be more flexible
>>>> to have more variables for the path? something like
>>>> /SOMEWHERE/domain1/sam and /SOMEWHERE/domain2/sam, by having new %d
>>>> variable for example. which i allready implemented for the time beeing
>>>> in Ingo.php and vfs.php to be able to go on with my tests.
>>>
>>> Sure. Patch?
>>>
>>> Jan.
>>>
>>> -- 
>>> Do you need professional PHP or Horde consulting?
>>> http://horde.org/consulting/
>>>
>>> --
>>> Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
>>> Frequently Asked Questions: http://horde.org/faq/
>>> To unsubscribe, mail: ingo-unsubscribe at lists.horde.org
>>
>>
>>
>
>
> Please create a ticket on http://bugs.horde.org/.
>
> Jan.
>
> -- 
> Do you need professional PHP or Horde consulting?
> http://horde.org/consulting/
>
> --
> Ingo mailing list - Join the hunt: http://horde.org/bounties/#ingo
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: ingo-unsubscribe at lists.horde.org