Re: New to kolab

On Sunday 30 September 2007 19:42:56 kitts wrote:
> On Sunday 30 Sep 2007 7:38:48 pm Thomas Spuhler wrote:
> > kitts wrote:
> > > Hello friends,
> > >
> > > I am new to kolab and to this list. I am currently experimenting with
> > > kolab on a test server before using it on a production server. I am
> > > using it to serve about 20 users and it is hosted on a server that
> > > performs other functions such as internet sharing, proxy, intranet
> > > webserver, dhcp etc.
> > >
> > > I know the preferred install process is to use openPKG. The server i
> > > have run kubuntu server (without GUI) and i would much prefer to use
> > > the native binaries available from the repos.
> > >
> > > Now i have installed kolabd and kolab-webadmin. On restart, i can see
> > > that imap, pop etc ports are open on server. i checked this running
> > > nmap on a client and the ports showed up only after installing kolab.
> > >
> > > Now i am unable to configure kolab. I installed kolab-webadmin but
> > > still https://serverip/admin returns nothing file not found on the
> > > client's browser. Apache2 is working as removing /admin shows me the
> > > default pages of apache2.
> > >
> > > Any hints how to get started?
> >
> > I am using the native Mandriva installation. I have a few more packages,
> > but that may be the way the packaged it.
> > But you did not mention doing a kolab_bootstrap -b
> > You need to do this at least before you can use kolab. I should have

Horde 3.1.5

Hello,

I saw that Horde 3.1.5 was out last week, I wonder if that's production-ready 
as a Kolab client, or if I need some extra patches.

I am using a separate horde install sitting on a different server from our 
Kolab servers and I like to stick with the official version as much as 
possible.

Thanks for helping,
--

-- 
Stéphane Konstantaropoulos -- Web Developer

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

Re: Horde 3.1.5

Stéphane Konstantaropoulos <skonstant <at> sgul.ac.uk> writes:

> Hello,
>
> I saw that Horde 3.1.5 was out last week, I wonder if that's production-ready 
> as a Kolab client, or if I need some extra patches.

No way :) The 3.1.x line is a bug fix line. You'll need 3.2.x. The
only thing available there is the newer alpha release. This will also
be used for the next Kolab-2.2-beta2 release. I hope to be able to
upload most required patches in
http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/patches/ today.

Cheers,

Gunnar
>
> I am using a separate horde install sitting on a different server from our 
> Kolab servers and I like to stick with the official version as much as 
> possible.
>
> Thanks for helping,
> -- 
> Stéphane Konstantaropoulos -- Web Developer
> _______________________________________________
> Kolab-users mailing list
> Kolab-users <at> kolab.org
> https://kolab.org/mailman/listinfo/kolab-users

--

-- 

****PossibleSPAM**** Re: Horde 3.1.5

Le lundi 1 octobre 2007, Gunnar Wrobel a écrit :
> Stéphane Konstantaropoulos <skonstant <at> sgul.ac.uk> writes:
> > Hello,
> >
> > I saw that Horde 3.1.5 was out last week, I wonder if that's
> > production-ready as a Kolab client, or if I need some extra patches.
>

Oops, I realised too late...

Are they aiming for a release of 3.2 some time soon?

> No way :) The 3.1.x line is a bug fix line. You'll need 3.2.x. The
> only thing available there is the newer alpha release. This will also
> be used for the next Kolab-2.2-beta2 release. I hope to be able to
> upload most required patches in
> http://kolab.org/cgi-bin/viewcvs-kolab.cgi/server/patches/ today.
>
> Cheers,
>
> Gunnar
>
> > I am using a separate horde install sitting on a different server from
> > our Kolab servers and I like to stick with the official version as much
> > as possible.
> >
> > Thanks for helping,
> > --
> > Stéphane Konstantaropoulos -- Web Developer
> > _______________________________________________

Re: Horde 3.1.5

Stéphane Konstantaropoulos <skonstant <at> sgul.ac.uk> writes:

> Le lundi 1 octobre 2007, Gunnar Wrobel a écrit :
>> Stéphane Konstantaropoulos <skonstant <at> sgul.ac.uk> writes:
>> > Hello,
>> >
>> > I saw that Horde 3.1.5 was out last week, I wonder if that's
>> > production-ready as a Kolab client, or if I need some extra patches.
>>
>
> Oops, I realised too late...
>
> Are they aiming for a release of 3.2 some time soon?

Otherwise they would not have released 3.2-ALPHA. It is planned but I
currently cannot give you any details. I think the current policy is
"It's done when it's done."

In any case in terms of the Kolab support I consider the ALPHA release
already rather mature. There are of couse still some minor problems
but there are sites running it successful in production.

Cheers,

Gunnar

>
>> No way :) The 3.1.x line is a bug fix line. You'll need 3.2.x. The
>> only thing available there is the newer alpha release. This will also
>> be used for the next Kolab-2.2-beta2 release. I hope to be able to

Re: Wiki not responding.

Wiki is back BUT NOT ITS CONTENT 

Here is the ERROR I get accessing the home page:

A database query syntax error has occurred. This may indicate a bug in
the software. The last attempted database query was:

    (SQL query hidden)

from within function "MediaWikiBagOStuff::_doquery". MySQL returned
error "1016: Can't open file: 'objectcache.MYI' (errno: 145)
(localhost)".

On 9/30/07, Alain Spineux <aspineux <at> gmail.com> wrote:
> Hi
>
> The kolab's wiki is not responding today.
> I tried using Firefox 2 and IE7 without success.
>
> Here is wget log :
>
> [root <at> max tmp]# wget http://wiki.kolab.org/
> --13:36:23--  http://wiki.kolab.org/
>            => `index.html'
> Resolving wiki.kolab.org... 80.68.94.186
> Connecting to wiki.kolab.org|80.68.94.186|:80... connected.
> HTTP request sent, awaiting response... Read error (Connection reset
> by peer) in headers.
> Retrying.
>

Re: New to kolab

On Monday 01 Oct 2007 1:42:29 pm Liutauras Adomaitis wrote:
> On Sunday 30 September 2007 19:42:56 kitts wrote:
> > On Sunday 30 Sep 2007 7:38:48 pm Thomas Spuhler wrote:
> > > kitts wrote:
> > > > Hello friends,
> > > >
> > > > I am new to kolab and to this list. I am currently experimenting with
> > > > kolab on a test server before using it on a production server. I am
> > > > using it to serve about 20 users and it is hosted on a server that
> > > > performs other functions such as internet sharing, proxy, intranet
> > > > webserver, dhcp etc.
> > > >
> > > > I know the preferred install process is to use openPKG. The server i
> > > > have run kubuntu server (without GUI) and i would much prefer to use
> > > > the native binaries available from the repos.
> > > >
> > > > Now i have installed kolabd and kolab-webadmin. On restart, i can see
> > > > that imap, pop etc ports are open on server. i checked this running
> > > > nmap on a client and the ports showed up only after installing kolab.
> > > >
> > > > Now i am unable to configure kolab. I installed kolab-webadmin but
> > > > still https://serverip/admin returns nothing file not found on the
> > > > client's browser. Apache2 is working as removing /admin shows me the
> > > > default pages of apache2.
> > > >
> > > > Any hints how to get started?
> > >
> > > I am using the native Mandriva installation. I have a few more
> > > packages, but that may be the way the packaged it.
> > > But you did not mention doing a kolab_bootstrap -b

Re: Horde 3.1.5

Op Monday 01 October 2007 13:16:38 schreef Gunnar Wrobel:
> > Are they aiming for a release of 3.2 some time soon?
>
> Otherwise they would not have released 3.2-ALPHA. It is planned but I
> currently cannot give you any details. I think the current policy is
> "It's done when it's done."

Right, there are 3 showstoppers left according this page:
http://wiki.horde.org/ShowStoppersThreeTwo

But how much time will those 3 take to get done?  E.g. this one 
http://bugs.horde.org/ticket/?id=5030 has not been updated since 7 July of 
this year.  Oh and this one http://bugs.horde.org/ticket/?id=4581 is almost a 
year unchanged....  This makes it very hard to judge when 3.2 will have no 
showstoppers anymore.

Hmmm, found this http://wiki.horde.org/ReleaseManagement on the horde wiki.  
When following the links, the only applications that are not "done" are: 
http://www.horde.org/kronolith/roadmap/ and http://www.horde.org/nag/roadmap/ 
With both the same functionality missing:
WebDAV/CalDAV/GroupDAV capabilities.  

It would be nice if e.g. Jan (Schneider) could shine a light on a possible 3.2 
release (beta) date.

--

-- 
Richard Bos
Without a home the journey is endless

Re: postfix: mail forwarding for domain if user unknown: solved

Am Mittwoch, 26. September 2007 20:35:59 schrieb Thomas Nintemann:
> OK, thanks very much for you advertence to my problem with the "one domain
> on two kolab-systems without direcly connection".
>
> On Friday i get a chance to test the scenario and i will post the outcomes
> here to the list.
>

Hello,
the problem was:

Two kolab-systems on different places, with no directly connection over the 
internet (no open port's), but proper for the same domain (example.com), must 
two-way mail exchange.
Because both kolab-systems have several mailboxes that must be able to 
communicate together over an ISP relay server.
Example: kolab-system1 has user1 <at> example.com and user2 <at> example.com.
Kolab-system2 has user3 <at> example.com and user4 <at> example.com.

here is my field report about the problem:

What you need to get it work:
A ISP with the whole mailboxaccounts for a domain.
The ISP mailserver must be able to let you relay mail's to the ISP via smtp 
and fetch mail's via pop3. 

The both kolab-servers simply needs a installed fetchmail, that is running in 
non multidrop mode and fetch the e-mail's from the ISP for his kolab-server 
mailboxes.
Example: On kolab-system1 fetch  user1 <at> example.com and user2 <at> example.com.

Re: Problem after upgrade to 2.1.0

* Alessio Cecchi <alessio <at> skye.it> [20071002 09:27]:
> Another problem is in the web interface, whe i click on "Services" and i try 
> to update "Enable or Disable individual Services" i have this error:
> 
> Errors:
> LDAP Error: failed to modify kolab configuration object: Invalid syntax

I'm not sure, but maybe the following from the upgrading docs helps:

Final Steps
-----------

1. The internal format of the ldap records for the list of privileged
   networks has changed, to updated these recods go to the kolab web
   interface an log in as administrative user.  Open the "Services"
   page and search for the "Privileged Networks" section.  Click the
   update button for the networks list.

If not, what is the value you have there?

Regards,
Thomas

--

-- 
thomas <at> intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Osnabrueck - Register: Amtsgericht Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner