O Plameras wrote:
OK, let me just confirm a number of items to ensure we talking on the same 'frequency':
1. when you access HORDE, the web address is:
http://your.domain.au/horde
2. if your docroot is /usr/html, then your installation has the ff structure:
/usr/html/horde -------------where you untarred horde-2.2.5
-------------as horde (renaming 'horde-2.2.5' as 'horde')
-------------important because all libs refs 'horde'.
/usr/html/horde/imp -------------where you untarred imp-3.2.5
-------------as imp (renaming 'imp-3.2.5' as 'imp')
3. then in 'cd /usr/html/horde/config' you did,
#for i in `ls *.dist`; do cp $i `basename $i .dist`; done
4. then in 'cd /usr/html/horde/imp/config' you did,
#for i in `ls *.dist`; do cp $i `basename $i .dist`; done
5. in 'vi /usr/html/horde/config/registry.php', uncommented:
$this->registry['auth']['login'] = 'imp'; $this->registry['auth']['logout'] = 'imp';
changed:
'status' => 'inactive' to 'status'=>'active'
6. in 'vi /usr/html/horde/imp/config/servers.php', modify to your correct mail server, domain name. I use standard UW-IMAP not Cyrus-IMAP. So, change
'server' => 'mail.acay.com.au' instead of 'server' => 'imap.example.com'
'maildomain' => 'acay.com.au' 'smtphost' => 'mail.acay.com.au' 'realm' => 'acay.com.au'
instead of default example.com.
So, once *.dist files have been copied to their operational config names, there are only two files to change to be able to login and use EMAIL functionalities. These two files are:
/usr/html/horde/config/registry.php and /usr/html/horde/imp/config/servers.php.
At this point there is no need to specify backend as IMP does not use it.
Backend like MySQL is good for Turba, Kronolith, etc that use lots of data to store.
Have fun.
O Plameras
Correct. Did all that, re-did and then did it again just to be sure. All to no avail. However, just to add something else into the mix, what I have just tried is downloading the rpm's from the horde ftp site (rh9 I think - I am using a derivative of RHEL3 - Centos) to see if they worked.....which they did. The only difference in the procedure is the untarring as opposed to rpm'ing and the different versions (rpm's are horde-2.2.3, imp-3.2.1). I haven't tried turba yet (there is no rpm for turba so have to tarball it). I suspect the major difference is the version as opposed to rpm or tar. Maybe I should try the same version from tar instead of rpm? I hate relying on rpm for something like this.....
Think I'll look through change-logs to see if anything relevant has changed. Maybe it's an incompatability between horde 2.2.5 and PHP 4.3.2?
Any ideas? Your help so far has been much appreciated... :)
Fil -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
