OK, so I'm much more of a googler than a thinker, but hey, if them Internets did this to me, they must have done this to you, too, so I suppose someone might find this helpful.
It all started when my boss had the idea of switching from Windows to Linux. Ten minutes later I was installing Debian on a spare server while surfing the web for a decent alternative to MS Exchange with an acceptable client side, and found Kolab.
It is relatively easy to set up, comes integrated with webmail and plays along nicely with any IMAP-capable client. I've had it up in an hour and running in a day, that is, once I found which release to use, a process that took about 2 days. After that it worked with only minor glitches, most of which were resolved in a couple of minutes. I'm using an OpenPKG binary install of Kolab 2.2-beta2, which has Horde 3.2-alpha included
Anyway, if you see the error "Unable to create VFS directory" when trying to create an attachment for a message, your VFS temp directory setting is probably incorrect.
The file /kolab/var/kolab/www/horde/config/conf.php contains a line:
$conf['vfs']['params']['vfsroot'] = '/../tmp';
which, besides being totally wrong, is also very sneaky about it. The path, when in the context of the Horde's PHP files, expands to /kolab/lib/php/Horde/../tmp, which does not exist. Of course, you'd have seen this if you had been able to access the Horde's administration menus with 'manager', the default Kolab administrator, however, neither of my several installations made it possible for manager to log in to the Horde. So you should probably do as I did and find the line
$conf['auth']['admins'] = array('manager');
in the same file and expand or modify the array to contain the UID of the person to grant Horde administrator access to. As for the temporary directory, I simply deleted the '/..' to make attaching files work.
Hozzászólás