Re: kolab 2.3.4 installation problem on openSuSE 12.1 x64

Am 20:59, schrieb Christoph Wickert:
> On Thursday 22 December 2011 01:16:20 Christoph Wickert wrote:
>> OpenPKG itself is 32bit, so you need to at least be able to compile very
>> basic 32bit programs. In Fedora this can be achieved by installing the
>> glibc.i686 package and I assume it's similar for OpenSUSE.
> Of course this should be glibc-devel.i686.
>
> Regards,
> Christoph
>
I installed the package glibc-devel-32bit but the this did not solve the 
error.

Regards,
Manuel

Re: kolab 2.3.4 installation problem on openSuSE 12.1 x64

On Monday 02 January 2012 12:33:44 Manuel wrote:
> Am 20:59, schrieb Christoph Wickert:
> > Of course this should be glibc-devel.i686.
> 
> I installed the package glibc-devel-32bit but the this did not solve the
> error.

Did you verify the sha1sums of your downloads?

Regards,
Christoph
--

-- 
Christoph Wickert
Senior Engineer

Kolab Systems AG
Zürich, Switzerland

e: wickert <at> kolabsys.com
t: +49 251 871 369 77
w: http://kolabsys.com

pgp: 85DACC63 Christoph Wickert

_______________________________________________
Kolab-users mailing list
Kolab-users <at> kolab.org
https://kolab.org/mailman/listinfo/kolab-users

Re: Horde Identities - Kolab Server v2.3.2-v2.3.4 ??

_______________________________________________
Kolab-users mailing list
Kolab-users <at> kolab.org
https://kolab.org/mailman/listinfo/kolab-users

Re: Webmail login page problem

Quoting Gelpi Andrea <liste <at> gelpi.it>:

> Il 30/12/2011 15:19, Gelpi Andrea ha scritto:
>> On a Debian 6.03 Virtual machine I installed a fresh Kolab 2.3.4 system.
>>
>> I modified some preferences in client using /kolab/etc/kolab/tempaltes/
>>
>> I add my modifications to these files:
>>
>> webclient-config_registry.php.template
>
> I understand the error in this file.
>
> In the original file I copied some lines. There are two lines with:
>
> 'fileroot' => dirname(__FILE__) . '/..',
> 'templates' => dirname(__FILE__) . '/../templates',
>
> Now this file in a subdirectory, one level down, so I need to add /.. to
> have it working.
>
> 'fileroot' => dirname(__FILE__) . '/../..',
> 'templates' => dirname(__FILE__) . '/../../templates',
>
>> webclient-config_motd.php.template
>
> I can't understand why the motd logo doesn' t appear.
>
> I add this line:
>
> <table width="100%"><tr><td align="center"><img
> src="themes/graphics/Ggdef.jpg" alt="Powered by Gelpi.it"
> /></td></tr></table>
>
> If I comment it the original image doesn't appear.

So it sounds as if your edits do have an effect. Maybe it does not  
find the linked image? Did you try adding some non-sense text to see  
if it gets displayed on the login screen? If it does not work I can  
test on my side as well.

Cheers,

Gunnar

>
> Is it disabled some where?
>
>
>> webclient-kronolith_prefs.php.template
>> webclient-turba_prefs.php.template
>> webclient-imp_prefs.php.template
>> webclient-config_mime_drivers.php.template
>> webclient-config_prefs.php.template
>> webclient-kolab-conf.template
>>
>> I change the image name in client login page, or the sentence Welcome to
>> Horde with Welcome to Webmail and some other preferences:
>>
>> Whe i load client login page, I can't see graphics and no image is
>> present after login form.
>>
>> In php.errors file I found:
>>
>> [30-Dec-2011 15:08:50] PHP Warning:
>> include_once(/kolab/var/kolab/www/client/config/registry.d/../lib/version.php)
>> [<a href='function.include-once'>function.include-once</a>]: failed to
>> open stream: No such file or directory in
>> /kolab/var/kolab/www/client/kronolith/lib/Kronolith.php on line 1341
>> [30-Dec-2011 15:08:50] PHP Warning:  include_once() [<a
>> href='function.include'>function.include</a>]: Failed opening
>> '/kolab/var/kolab/www/client/config/registry.d/../lib/version.php' for
>> inclusion
>> (include_path='/kolab/var/kolab/www/client/lib:.:/kolab/lib/php') in
>> /kolab/var/kolab/www/client/kronolith/lib/Kronolith.php on line 1341
>> [30-Dec-2011 15:08:50] PHP Notice:  Use of undefined constant
>> HORDE_VERSION - assumed 'HORDE_VERSION' in
>> /kolab/var/kolab/www/client/kronolith/lib/Kronolith.php on line 1342
>> [30-Dec-2011 15:08:50] PHP Notice:  Use of undefined constant
>> DATATREE_ROOT - assumed 'DATATREE_ROOT' in
>> /kolab/var/kolab/www/client/kronolith/lib/Kronolith.php on line 1343
>> [30-Dec-2011 15:08:50] PHP Warning:
>> include_once(/kolab/var/kolab/www/client/config/registry.d/../lib/version.php)
>> [<a href='function.include-once'>function.include-once</a>]: failed to
>> open stream: No such file or directory in
>> /kolab/var/kolab/www/client/nag/lib/Nag.php on line 288
>> [30-Dec-2011 15:08:50] PHP Warning:  include_once() [<a
>> href='function.include'>function.include</a>]: Failed opening
>> '/kolab/var/kolab/www/client/config/registry.d/../lib/version.php' for
>> inclusion
>> (include_path='/kolab/var/kolab/www/client/lib:.:/kolab/lib/php') in
>> /kolab/var/kolab/www/client/nag/lib/Nag.php on line 288
>> [30-Dec-2011 15:08:50] PHP Notice:  Use of undefined constant
>> HORDE_VERSION - assumed 'HORDE_VERSION' in
>> /kolab/var/kolab/www/client/nag/lib/Nag.php on line 289
>> [30-Dec-2011 15:08:50] PHP Warning:
>> include_once(/kolab/var/kolab/www/client/config/registry.d/../lib/version.php)
>> [<a href='function.include-once'>function.include-once</a>]: failed to
>> open stream: No such file or directory in
>> /kolab/var/kolab/www/client/nag/lib/Nag.php on line 288
>> [30-Dec-2011 15:08:50] PHP Warning:  include_once() [<a
>> href='function.include'>function.include</a>]: Failed opening
>> '/kolab/var/kolab/www/client/config/registry.d/../lib/version.php' for
>> inclusion
>> (include_path='/kolab/var/kolab/www/client/lib:.:/kolab/lib/php') in
>> /kolab/var/kolab/www/client/nag/lib/Nag.php on line 288
>> [30-Dec-2011 15:08:50] PHP Notice:  Use of undefined constant
>> HORDE_VERSION - assumed 'HORDE_VERSION' in
>> /kolab/var/kolab/www/client/nag/lib/Nag.php on line 289
>> [30-Dec-2011 15:08:50] PHP Warning:
>> require(/kolab/var/kolab/www/client/config/registry.d/../templates/common-footer.inc)
>> [<a href='function.require'>function.require</a>]: failed to open
>> stream: No such file or directory in
>> /kolab/var/kolab/www/client/imp/login.php on line 475
>> [30-Dec-2011 15:08:50] PHP Fatal error:  require() [<a
>> href='function.require'>function.require</a>]: Failed opening required
>> '/kolab/var/kolab/www/client/config/registry.d/../templates/common-footer.inc'
>> (include_path='/kolab/var/kolab/www/client/lib:.:/kolab/lib/php') in
>> /kolab/var/kolab/www/client/imp/login.php on line 475
>> [30-Dec-2011 15:08:50] PHP Notice:  Unknown: SECURITY PROBLEM: insecure
>> server advertised AUTH=PLAIN (errflg=1) in Unknown on line 0
>> [30-Dec-2011 15:08:50] PHP Notice:  Unknown: IMAP protocol error: Client
>> canceled authentication (errflg=2) in Unknown on line 0
>> [30-Dec-2011 15:08:50] PHP Notice:  Unknown: IMAP Authentication
>> cancelled (errflg=2) in Unknown on line 0
>> [30-Dec-2011 15:08:50] PHP Notice:  Unknown: SECURITY PROBLEM: insecure
>> server advertised AUTH=PLAIN (errflg=1) in Unknown on line 0
>> [30-Dec-2011 15:08:50] PHP Notice:  Unknown: IMAP protocol error: Client
>> canceled authentication (errflg=2) in Unknown on line 0
>> [30-Dec-2011 15:08:50] PHP Notice:  Unknown: IMAP Authentication
>> cancelled (errflg=2) in Unknown on line 0
>> [30-Dec-2011 15:08:50] PHP Notice:  Unknown: SECURITY PROBLEM: insecure
>> server advertised AUTH=PLAIN (errflg=1) in Unknown on line 0
>> [30-Dec-2011 15:08:50] PHP Notice:  Unknown: IMAP protocol error: Client
>> canceled authentication (errflg=2) in Unknown on line 0
>> [30-Dec-2011 15:08:50] PHP Notice:  Unknown: IMAP Authentication
>> cancelled (errflg=2) in Unknown on line 0
>>
>> I think is not clear to me how to modify a setting using templates files.
>>
>> Where can I found documentations?
>>
>> Thnaks
>>
>
>
> --
> ing. Andrea Gelpi
> ***************************************************
> La Terra non la abbiamo ereditata dai nostri avi,
> ma la abbiamo presa in prestito dai nostri bambini.
> ***************************************************
> We do not inherit the Earth from our parents,
> but borrow it from our children.
> ***************************************************
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users <at> kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

--

-- 
Core Developer
The Horde Project

e: wrobel <at> horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de

Re: kolab 2.3.4 installation problem on openSuSE 12.1 x64

Am 20:59, schrieb Christoph Wickert:
> On Monday 02 January 2012 12:33:44 Manuel wrote:
>> Am 20:59, schrieb Christoph Wickert:
>>> Of course this should be glibc-devel.i686.
>> I installed the package glibc-devel-32bit but the this did not solve the
>> error.
> Did you verify the sha1sums of your downloads?
>
> Regards,
> Christoph
I've verified the sha1sums as described in the readme. The files are all ok.

Regards,
Manuel

Sieve migration

Hi all,
	I just migrated a kolab server from V 2.2.0 to V 2.3.4.

I'm looking information on howto migrate sieve script from old users to 
new one.

Copying the script in /kolab/var/imapd/sieve/domain/x/x/x/user/x
is not enough.
If I login via webmail I can't see the rules corresponding.

Where can I find documentation?
Thanks

--

-- 
ing. Andrea Gelpi
***************************************************
La Terra non la abbiamo ereditata dai nostri avi,
ma la abbiamo presa in prestito dai nostri bambini.
***************************************************
We do not inherit the Earth from our parents,
but borrow it from our children.
***************************************************

Re: Webmail login page problem

Il 30/12/2011 15:46, Gelpi Andrea ha scritto:
> Il 30/12/2011 15:19, Gelpi Andrea ha scritto:
>> On a Debian 6.03 Virtual machine I installed a fresh Kolab 2.3.4 system.
>>
>> I modified some preferences in client using /kolab/etc/kolab/tempaltes/
>>
>> I add my modifications to these files:
>>
>> webclient-config_registry.php.template
>> webclient-config_motd.php.template
>> webclient-kronolith_prefs.php.template
>> webclient-turba_prefs.php.template
>> webclient-imp_prefs.php.template
>> webclient-config_mime_drivers.php.template
>> webclient-config_prefs.php.template
>> webclient-kolab-conf.template

I can't see a logo under webmail login morm page.

Looking around I found in:
/kolab/var/kolab/www/client/imp/login.php this code:

if (is_callable(array('Horde', 'loadConfiguration'))) {
     Horde::loadConfiguration('motd.php', null, null, true);
} else {
     if (is_readable(IMP_BASE . '/config/motd.php')) {
         require IMP_BASE . '/config/motd.php';
     }
}

I suppose none of the two "if" are never true.
Where have I to look  to diagnose my problems?

--

-- 
ing. Andrea Gelpi
***************************************************
La Terra non la abbiamo ereditata dai nostri avi,
ma la abbiamo presa in prestito dai nostri bambini.
***************************************************
We do not inherit the Earth from our parents,
but borrow it from our children.
***************************************************

Re: Sieve migration

Hi Andrea,
copying sievescripts should work and your mails should be filtered by sieve.

If you want to see the old filtersettings in webclient (Horde-Ingo) you have 
to change something in kolab template folder, because webclient filter (ingo) 
shows you only what is stored in the prefs and not what is in sieve folders.

This is because webclient in 2.3.4 read and write prefs by default to file.
Older installations of webclient has done this by default to ldap.

First be sure that ldap has loaded the horde.schema.
Take a look in slapd.conf.template.
# The schema remains available at
# /kolab/var/kolab/www/client/scripts/ldap/horde.schema
# include  <at>  <at>  <at> ldapserver_schemadir <at>  <at>  <at> /horde.schema

Uncomment the include line and after a kolabconf you schould have a running 
ldap with horde.schema. If ldap would not start, make sure that you have a 
copy from /kolab/var/kolab/www/client/scripts/ldap/horde.schema to your ldap 
schemadir.

After that edit the webclient-kolab-conf.template. If you uncomment the 
$conf['prefs']['driver'] = 'kolab';. Don't forget a kolabconf for write the 
template to webclient systemfolder.
After that you should able to login in webclient and the filter should show 
you the old settings.

A the moment it seems that there is no migrationtool for webclient prefs from 
ldap to file.

Regards
Thomas

Am Mittwoch, 4. Januar 2012, 14:31:42 schrieb Gelpi Andrea:
> Hi all,
> 	I just migrated a kolab server from V 2.2.0 to V 2.3.4.
> 
> I'm looking information on howto migrate sieve script from old users to
> new one.
> 
> Copying the script in /kolab/var/imapd/sieve/domain/x/x/x/user/x
> is not enough.
> If I login via webmail I can't see the rules corresponding.
> 
> Where can I find documentation?
> Thanks

Re: Sieve migration

Il 04/01/2012 18:27, Thomas Nintemann ha scritto:
> Hi Andrea,
> copying sievescripts should work and your mails should be filtered by sieve.

Yes, it works.

>
> If you want to see the old filtersettings in webclient (Horde-Ingo) you have
> to change something in kolab template folder, because webclient filter (ingo)
> shows you only what is stored in the prefs and not what is in sieve folders.

OK, that's my problem.

>
> This is because webclient in 2.3.4 read and write prefs by default to file.
> Older installations of webclient has done this by default to ldap.
>
> First be sure that ldap has loaded the horde.schema.
> Take a look in slapd.conf.template.
> # The schema remains available at
> # /kolab/var/kolab/www/client/scripts/ldap/horde.schema
> # include  <at>  <at>  <at> ldapserver_schemadir <at>  <at>  <at> /horde.schema
>
> Uncomment the include line and after a kolabconf you schould have a running
> ldap with horde.schema. If ldap would not start, make sure that you have a
> copy from /kolab/var/kolab/www/client/scripts/ldap/horde.schema to your ldap
> schemadir.

I copied horde.schema in openldap/schema dir. I change ownership and 
permissions so that they are equal to all other schema files, but ...
openldap start and fails immediately without any messages.
I had to comment horde schema to have openldap start again.

>
> After that edit the webclient-kolab-conf.template. If you uncomment the
> $conf['prefs']['driver'] = 'kolab';. Don't forget a kolabconf for write the
> template to webclient systemfolder.
> After that you should able to login in webclient and the filter should show
> you the old settings.
>
> A the moment it seems that there is no migrationtool for webclient prefs from
> ldap to file.
>

By the way the user recreate rules with a printout of old sieve script.

--

-- 
ing. Andrea Gelpi
***************************************************
La Terra non la abbiamo ereditata dai nostri avi,
ma la abbiamo presa in prestito dai nostri bambini.
***************************************************
We do not inherit the Earth from our parents,
but borrow it from our children.
***************************************************

Location of Files

_______________________________________________
Kolab-users mailing list
Kolab-users <at> kolab.org
https://kolab.org/mailman/listinfo/kolab-users