[ingo] Configuring VFS 'file' driver for maildrop

[Jan Schneider]

Zitat von Murdo Morrison <murdo at isle-of-harris.com>:

> Hi I've been configuring backend.php in Ingo to create local courier  
> maildrop files.  The configuration below works ok but I had issue  
> creating correct file_perms.  The example has 0640 which I assumed  
> to be rw-r----- but it turns out that what is actually required is  
> the decimal of this octal number, so 644 for rw-r--r-- needs file  
> perms for '420' and rw-r----- isn't 640 but 416.
>
> Is this a bug or is it expected behaviour, if its expected then  
> perhaps there should be a comment in backends.php.dist to explain  
> this... it would have saved me some time while trying to figure this  
> out :-)

http://www.php.net/integer

> As it turns out all this was somewhat irrelevant as courier maildrop  
> wants owner read write permissions and doesn't care it group/all  
> have read only access.  What I have is a standard courier virtual  
> domains install where /var/vmail is containing folder and  
> vmail:vmail is user/group for all read/write access to this folder.   
> As indo will run in horde via http user I was trying to give group  
> write access to the folder so Ingo could create the maildrop file  
> without the need for ftp as courier and horde run on same server.   
> With the backends.php below this works but maildrop doesn't like the  
> group writable folder.
>
> What are my options, I'm thinking I could hook ftp server into  
> virtual users db and all files will be written as vmail user but I  
> was trying to avoid this, the only other option I can think of is  
> ditch vmail user and configure courier to use apache as the account  
> for writing mail

Using FTP is the much safer solution.

Jan.

-- 
Do you need professional PHP or Horde consulting?
http://horde.org/consulting/