gmane.comp.kde.devel.kroupware

Re: Kolab-users Digest, Vol 111, Issue 35

John Borhek — 2013-05-25T15:02:03

 

I think you may have the same wallace issue I did. look back in the
archives a few weeks and see if the issue fits the bill. 

-John 

On 2013-05-25 03:00 AM, kolab-users-request< at >kolab.org wrote:

Stops sending and receiving mail

Whitnall, Dale (North — 2013-05-24T23:39:33

Hi all,
I have a Kolba3 install working on a centos 6.4 virtual machine,
For whatever reason after 4 days of up time it stops sending and receiving mail, I have tried looking in the logs but nothing stands out.
A reset gets it all going again.
I have noticed the following in the logs and thought it would be a good start to solve these first though.

2013-05-25 09:14:01,933 pykolab.conf WARNING Option does not exist in defaults.
2013-05-25 09:14:01,954 pykolab.plugins.dynamicquota ERROR Quota 'default_quota' not an integer!
2013-05-25 09:14:01,954 pykolab.plugins.dynamicquota ERROR Quota 'default_quota' not an integer!
2013-05-25 09:15:02,532 pykolab.conf WARNING Option imap/virtual_domains does not exist in config file /etc/kolab/kolab.conf, pulling from defaults
2013-05-25 09:18:21,302 pykolab.conf WARNING Option ldap/modifytimestamp_format does not exist in config file /etc/kolab/kolab.
May 25 09:27:15 talax imaps[3551]: unable to open Berkeley db /etc/sasldb2: No such file or directory
May 25 09:24:53 tal

Working with multiple domains...

Christian Tardif — 2013-05-24T04:16:13

Hi,

Going forward. My Kolab 3 installation is now complete.

First, I created a user in the primary domain. So far so good, the user 
gets created with first.last< at >domain.com  Going on the roundcubemail 
interface, I can login.

Now, I created a second domain, and cloned the section of the primary 
domain to the new domain in kolab.conf file, then restarted kolabd.

Now back on Kolab Admin Panel. I can see the newly created group on the 
top-right, which I can select. I can create a user in the primary domain 
but, when I go back to its config, he get the email address of the 
second domain, and I just can't login to roundcubemail. I can also 
create a user on the second domain, but he can't login to roundcubemail 
either.  What do I do wrong?

Another thing I've noted. When I create a user in the primary domain, 
his emails look like this:



As you can see, the secondary email got scrambled. What causes that?

Regards,

Fighting SPAM

John Borhek — 2013-05-23T14:41:18

I read an article in: 
http://www.kolab.org/blog/tobru/2013/03/19/kolab-3-anti-spam which 
indicated something I find contradictory.

The article said I should uncomment the line that reads:

# < at >bypass_spam_checks_maps  = (1);  # controls running of anti-spam 
code

to enable spam filtering. I read that line as "bypass spam checks = 1" 
in other words, bypass spam checks

What is the correct setting -  I pre-seeded my Bayes Database?

Thx.

Also I had to disable Wallace to keep my server running longer than 24 
hours - does this affect my ability to tag spam?

Coexistence of freeipa and kolab

Wilfred de Bondt — 2013-05-23T09:25:09

Dear all,

Currently I'm investigating kolab and I like what I see.
But now my question is, can kolab and freeipa coexist?
That is, there are no clashes in LDAP or something like that?

Regards,

Wilfred de Bondt
_______________________________________________
Kolab-users mailing list
Kolab-users< at >kolab.org
https://www.intevation.de/mailman/listinfo/kolab-users

Re: Backup Software or Solution for Kolab 3 [Scanned]

Chloé Desoutter — 2013-05-22T18:26:44

Le 22/05/2013 19:59, William Reynolds a écrit :
Dear,

We use daily btrfs snapshots and send them incrementally to our FreeBSD 
backup server using rsync. This way we get backups with little to no 
performance overhead, no need for locks and such things.

On the FreeBSD side, we use a ZFS raidz that is backuped daily.

Since this solution has virtually no impact on performance and disk 
space, you could even consider backing up messages every 30 mn w/o very 
much performance problems.

One advantage with Kolab (compared to, say, Bluemind) is that almost 
everything lies on the filesystem, so there is no need for database backups.

Yours sincerely,

Backup Software or Solution for Kolab 3 [Scanned]

William Reynolds — 2013-05-22T17:59:24

Hey Guys,



I was wanting to see what you all were using as a backup solution for kolab 3. I need to get something setup in case something happens to the system. Its installed on a Raid 1 with dual 500 gb Seagate HDDs but I still need to get a backup solution in place.


Wm. Reynolds
President | Co-Founder
RRWDS Co.
Toll Free +1 855 GO RRWDS (855.467.7937)
Office +1 979.383.2953 x2501 | Cell +1 979.204.4658
www.rrwds.com<http://www.rrwds.com/>

A Dell Registered Partner
Small & Medium Business Partner
State & Local Government Partner

P Please consider the environment before printing this email.


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

RE: Upgrade Procedure from 2.4 to 3.0 on the Same Server

Isaac Aaron — 2013-05-22T13:10:59

If roundcube, syncroton and the Outlook plugin all read both formats - it isn't really an issue.
Calender items for non-reoccuring items are considered ancienct history about 2 hours after being overdue. The only real thing to worry about are contacts and as far as I seen, at least on Roundcube they are displayed correctly.

________________________________

From: kolab-users-bounces< at >kolab.org [mailto:kolab-users-bounces< at >kolab.org] On Behalf Of Mihai Badici
Sent: Wednesday, May 22, 2013 1:57 PM
To: kolab-users< at >kolab.org
Subject: Re: Upgrade Procedure from 2.4 to 3.0 on the Same Server

The big issue is to export personal data from kolab v2 to kolab v3.

There are calendar and contacts info in imap folders wich will stay in kolab v2 format after upgrade.

--

Mihai Badici

http://mihai.badici.ro

Quality Bytes MailXpress Message: Spam? Click this link <http://10.0.0.3:16000/spam.php?spam=1&qid=000000000026f23a>

Re: SyncKolab 3

Niko Berger — 2013-05-22T12:24:23

It should work with the current nightly. I fixed everything I could find 
but I didnt have time to test it completely yet.

Chec kout the new nightly and maybe write a bug report if it still does 
not work.



Niko

On 05/22/2013 10:10 AM, Mihai Badici wrote:

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

Re: Upgrade Procedure from 2.4 to 3.0 on the Same Server

Mihai Badici — 2013-05-22T10:56:47



The big issue is to export personal data from kolab v2 to kolab v3.
There are calendar and contacts info in imap folders wich will stay in kolab 
v2 format after upgrade.

Re: Upgrade Procedure from 2.4 to 3.0 on the Same Server

Chloé Desoutter — 2013-05-22T10:56:01

Le 22/05/2013 12:48, Isaac Aaron a écrit :

Hello Isaac,

We've been doing it like this. No warranty whatsoever but it worked for 
us several times. It's not optimal or optimized, but it's pretty much OK :

* save your LDAP tree *
* save your mailboxen *
Run

cd
mkdir -p kolab3
cd kolab3
rpm -Uvh 
http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
yum -y install vim wget screen
wget 
http://mirror.kolabsys.com/pub/redhat/kolab-3.0/el6/development/i386/kolab-3.0-community-release-6-2.el6.kolab_3.0.noarch.rpm
yum localinstall --nogpgcheck 
http://mirror.kolabsys.com/pub/redhat/kolab-3.0/el6/development/i386/kolab-3.0-community-release-6-2.el6.kolab_3.0.noarch.rpm
yum install kolab
yum remove $(yum list installed | grep kolab-2.4 | grep php | awk 
'{print $1}')
yum install kolab-webclient kolab-webadmin kolab-cli kolab-imap 
kolab-mta kolab-server

Apply our Wallace patches (they're available on the list) to avoid nasty 
bugs that occur randomly with the Resources plug-in. This way Resou

Upgrade Procedure from 2.4 to 3.0 on the Same Server

Isaac Aaron — 2013-05-22T10:48:40

Hello

Googling for an upgrade procedure from 2.4 to 3.0 on the same server only lead my to the two-machine migration howto. That didn't feel right to me. Apart from z-push, the daemons from 2.4 all exist on 3.0 and I felt it should be worth a try to upgrade a live system from 2.4 to 3.0. I have put together a recipe for upgrading Kolab 2.4 to 3.0:

1. Remove kolab-2.4-community package
rpm -e kolab-2.4-community-release-6-1.el6.kolab_2.4.noarch kolab-2.4-community-release-development-6-1.el6.kolab_2.4.noarch

2. Install kolab-3.0 community package
rpm -Uvh http://mirror.kolabsys.com/pub/redhat/kolab-3.0/el6/release/x86_64/kolab-3.0-community-release-6-2.el6.kolab_3.0.noarch.rpm

3. Remove packages causing dependency issues (causing trouble with yum upgrade)
rpm -e mysql-server-5.5.24-1.el6.kolab_2.4.x86_64 mysql-libs-5.5.24-1.el6.kolab_2.4.x86_64 php-pear-MDB2-Driver-mysql-1.5.0-0.1.b3.el6.noarch php-mysql-5.3.10-2.el6.kolab_2.4.x86_64 mysql-5.5.24-1.el6.kolab_2.4.x86_64 postfix MySQL-python-1.2.3-4.el6.kol

Upgrade Procedure from 2.4 to 3.0 on the Same Server

Isaac Aaron — 2013-05-22T10:46:15

Hello

Googling for an upgrade procedure from 2.4 to 3.0 on the same server only lead my to the two-machine migration howto. That didn't feel right to me. Apart from z-push, the daemons from 2.4 all exist on 3.0 and I felt it should be worth a try to upgrade a live system from 2.4 to 3.0. I have put together a recipe for upgrading Kolab 2.4 to 3.0:

1. Remove kolab-2.4-community package
rpm -e kolab-2.4-community-release-6-1.el6.kolab_2.4.noarch kolab-2.4-community-release-development-6-1.el6.kolab_2.4.noarch

2. Install kolab-3.0 community package
rpm -Uvh http://mirror.kolabsys.com/pub/redhat/kolab-3.0/el6/release/x86_64/kolab-3.0-community-release-6-2.el6.kolab_3.0.noarch.rpm

3. Remove packages causing dependency issues (causing trouble with yum upgrade)
rpm -e mysql-server-5.5.24-1.el6.kolab_2.4.x86_64 mysql-libs-5.5.24-1.el6.kolab_2.4.x86_64 php-pear-MDB2-Driver-mysql-1.5.0-0.1.b3.el6.noarch php-mysql-5.3.10-2.el6.kolab_2.4.x86_64 mysql-5.5.24-1.el6.kolab_2.4.x86_64 postfix MySQL-python-1.2.3-4.el6.kol

Re: SyncKolab 3

Henning H — 2013-05-22T09:29:29

I filed a bug report #25417 noticing now that #25328 seems to be the 
same and it is not fixed yet.

Am 22.05.2013 10:10, schrieb Mihai Badici:

Re: SyncKolab 3

Mihai Badici — 2013-05-22T08:10:45


There are some bugs in kolab format which Niko Berger solved in Contacts but 
not in Calendar.
See bugs 25328 and 25231
I put a comment on 25231 but I think Niko had no time to solve, probably if 
you fill a bugreport will be better.

SyncKolab 3

Henning Holly — 2013-05-22T08:04:22

Hi,

I wonder if anyone has got synckolab into action with kolab3. The most
recent nightlies (17-05-2013) claim that they support kolab3 formats for
calendars and contacts, however my roundcube cannot read the calendar items.

Contacts seem to work. Could it be an error not of synckolab but of my
roundcube? Do I have to configure something there?

kind regards,
Henning

Re: Integration of Kolab 3 with Samba4 LDAP

Christian Tardif — 2013-05-22T04:07:32

Hi,

I have an environment where I run two LDAP servers (samba4+ 389) in the 
same machine. To achieve this, I just added a second interface on my 
server, and made sure to attach every ldap server to only one interface. 
Easy to do on the samba side (in smb.conf, use "interfaces" and "bind 
interfaces only" to attach samba to a particular interface). On the 389, 
you need to modify /etc/dirsrv/<directory instance>/dse.ldif (while the 
directory server is down). Just add
     nssldap-listenhost: <desired ip>
just below nssldap-port and restart the 389 directory server to have it 
hooked to the other network interface. You now have two ldap servers 
running on the same machine.

But that does help much into integrating Samba4 to Kolab.

I did that in the past (when things were much simpler) to integrate 
samba 3 to kolab 2. That was working, but samba 3 was not so hungry 
about ldap requirements. Now, if you want to seemlessly intergrate 
Samba4 into a windows environment (and be able to use Windows tools to

Re: Integration of Kolab 3 with Samba4 LDAP

Mat Cantin — 2013-05-21T21:37:52

The implementation I was developing was with Active Directory and 
actually quite simple. It was a one way sync from Kolab to users in a 
specific OU in AD and it didn't touch any of Kolab's configurations. I 
was only syncing usernames and passwords and forced users to use Kolab 
to change their passwords. Never did get to finish this up though and I 
had to move on to different projects.

When I get some time I want to look into integrating Samba into Kolab's 
LDAP, but in my case that's for file sharing where there's no other 
central authentication server.

--
Mat

Re: Ubuntu 12.04 LTS - How to install kolab-webadmin ?

2013-05-21T19:17:19

Thanks, I'll check.

Bests,

EM

Le 21/05/2013 14:08, Henning H a écrit :

Re: Ubuntu 12.04 LTS - How to install kolab-webadmin ?

2013-05-21T19:16:47

OK thanks. Let's find some time to try now.

Bests,

EM


Le 21/05/2013 13:51, Torsten Grote a écrit :

RE: continuously getting undeliverable mail notices from eroski.es

Troy Carpenter — 2013-05-21T17:45:55

My guess is everyone on the list is getting them.  I was planning to mention
it as well.

-----Original Message-----
From: kolab-users-bounces< at >kolab.org [mailto:kolab-users-bounces< at >kolab.org]
On Behalf Of Thomas Spuhler
Sent: Tuesday, May 21, 2013 11:49 AM
To: kolab-users< at >kolab.org
Subject: continuously getting undeliverable mail notices from eroski.es

I have been getting this e-mail notice for about two weeks.
I cannot quite figure out what's going on.

From: 
Mailer-Daemon< at >slx00018102
  To: 
thomas< at >btspuhler.com
  Date: 
Today 08:37:45 AM
   
The attached file had the following undeliverable recipient(s):
        v087a< at >vmail.eroski.es



Information about your message: 
        GroupWise Message Id: 51964911.946:184:39238
        Message log tag: 75308061
        Number of send attempts: 96
        Time of initial send attempt: 05-17-13 17:13:22
        Time of last send attempt: 05-21-13 17:35:39

Transcript of session follows: 
          Command:  [192.168.175.12]
          Response: 450 Host down ([192