Rob Badub | 1 Sep 21:45 2014

Error connecting to database: SQLSTATE[28000] [1045] Access denied for user 'roundcube' <at> 'localhost'

Hi all,

My name is Rob Badub and I'm new to Kolab. My system is a Ubuntu server
14.04 and I'm following the instructions that I've found on

After executing the install script with 

Sudo aptitude install kolab

it fails at the install for roundcubemail

The error message says:

E: Sub-process /usr/bin/dpkg returned an error code (1)
A package failed to install.  Trying to recover:
Setting up roundcubemail (1:1.1~dev20140404-0~kolab3) ...
ERROR: Error connecting to database: SQLSTATE[28000] [1045] Access denied
for user 'roundcube' <at> 'localhost' (using password: YES)ERROR: Site
roundcubemail does not exist!

Subsequently the following packages with dependencies fail as well.

dpkg: error processing package roundcubemail (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of kolab-freebusy:
 kolab-freebusy depends on roundcubemail; however:
  Package roundcubemail is not configured yet.

And the same for 
(Continue reading)

Janszen, Josh | 1 Sep 18:44 2014

Kolab 3.3 https://

I changed mod_nss port from 8443 to 443. When accessing the page it 
looks that all images and css styles are not loaded. Is there an easy 
fix for this? This will also happen on a fresh install using port 8443. 
I have Kolab 3.3 installed on a CentOS 6.5 machine.

I also am having issues getting free-busy to work out the box are there 
any modifications I am missing.


Rick | 1 Sep 17:33 2014

Kolab version where it is not a must to be an email server developer?

I’ve been using Kolab for around one year for personal interests, after leaving it alone sometime in 2012
(which seems to be the last stable out of the box version) 
because it does seem to have huge potential. And I enjoy learning. 
When a new version comes out, I grab that and use it on another personal domain. (which was my demise after
more than a year or so)
I see new features, yet without a good bit of script editing they are for the most part un-usable. 

Such as chwala, I’ve not been able to get that running , inside or outside of roundcube. I’ve been
bounced back and forth between git pastes, 
email list threads and random personal sites that have solutions for one version of one or another script
within a certain version of Kolab. 

Take the initial Kolab-webadmin, one must place the API URI in the conf to even initially use the system, for
the last two versions. 
I should mention 3.3 one must now find the API URI to access chwala outside of roundcube. 

While ‘files’ within roundcube, the icons are greyed out, I’ve yet to find a solution for this. 
Although there are many requests for this issue one can spend countless hours searching through email
lists and still find no definitive solution. 

The administration guide for 3.3 is a work in progress I see, such as were the last two versions, which much
has yet to be completed. 

I understand this is a development version not a supported version, so I am not complaining, in any sense. 
It seems that after following this for the short time I have, much less focus on implementing fixes, than is
adding new features. 

Of course i do not understand why some of the basic initial patches are not implemented such as the API
HTTPS between chwala and Kolab conf files, that does not mean there is no good reason, I’m sure there are
(Continue reading)

Sebastian Walter | 1 Sep 16:25 2014

***UNCHECKED*** Kolab policy with alias domains

Dear list,

This is about a new installation of Kolab 3.3 on CentOS 7. I followd the
Multi-Domain Howto on and overall the system is working
fine. Amongst other small issues (to be posted later) I have a problem
of sending mails from other e-mail addresses than the parent domain.

I try to explain the issue with this virtual example: the parent domain
is and an alias domain is added via the Kolab
Web Admin. The user joe <at> has a lot of secondary email
addresses (catchall for other domains), as well as one specific address
mail <at> He wants to send emails from this address with his
user account. The mail server replies with:

An (SMTP) error occurred while sending mail. The server responded: 
5.7.1 <DATA>: Data command rejected: Could not find envelope sender user
mail <at>

The only working workaround is to empty the
"submission_data_restrictions" direction in /etc/postfix/ but I
would prefer to not disable Kolabs policies.

As a consequence, I got lots of errors from
/usr/libexec/postfix/kolab_smtp_access_policy (premature end-of-input)
which I got rid of by commenting out the "chache_uri" directive in

I guess my ldap system is somehow messed. Has anybody an idea?
Any help is greatly appreciated!

(Continue reading)

Nick Wiltshire | 31 Aug 20:28 2014

Kolab 3.1 -> 3.3 [centos 6.5]

After performing this upgrade, it appears I'm getting no new mail in my inbox.

Looking at maillog, it appears the messages are delivered, but I can't see 
them in Kmail or my Android.

The only clue I see is this:

SASL unable to open Berkeley db /etc/sasldb2: No such file or directory

Shouldn't SASL be authenticating via LDAP?
Pablo Casais Solano | 1 Sep 01:56 2014

Problems installing Kolab in Ubuntu

Hi all,

   My name is Pablo Casais and I'm new to Kolab. I'm trying to install Kolab on my own server and I'm facing some issues. My system is a Ubuntu server 14.04 and I'm following the instructions that I've found on

   However after completing the installation and running the setup-kolab command the web interface to administer kolab is not working. I can see that there's an Apache 2 service installed but the kolab-webadmin folder does not exist.

   Reviewing the installation I can see that there were the following messages:

Dependency problems prevent configuration of kolab-webclient:
 kolab-webclient depends on chwala; however:
  Package chwala is not configured yet.
 kolab-webclient depends on irony; however:
  Package irony is not configured yet.
 kolab-webclient depends on kolab-freebusy; however:
  Package kolab-freebusy is not configured yet.
 kolab-webclient depends on kolab-syncroton; however:
  Package kolab-syncroton is not configured yet.
 kolab-webclient depends on roundcubemail (>= 0.9); however:
  Package roundcubemail is not configured yet.
 kolab-webclient depends on roundcubemail-plugin-contextmenu; however:
  Package roundcubemail-plugin-contextmenu is not configured yet.
 kolab-webclient depends on roundcubemail-plugin-threadingasdefault; however:
  Package roundcubemail-plugin-threadingasdefault is not configured yet.
 kolab-webclient depends on roundcubemail-plugins-kolab (>= 3.0); however:
  Package roundcubemail-plugins-kolab is not configured yet.

   It seems that quite a few of the plugins and the webclient are not configured. I've tried everything I can but I have had no success so I thought that maybe you guys could point me on what I'm doing wrong and where I can find some help to get Kolab working.

   Thank you very much for your help!

Kind regards,

Pablo C.

There is no system but GNU and Linux is one of its kernels

Version: OpenPGP.js v.1.20130114


2014-09-01 0:49 GMT+01:00 <users-request <at>>:
Welcome to the users <at> mailing list!

To post to this list, send your message to:

  users <at>

General information about the mailing list is at:

If you ever want to unsubscribe or change your options (eg, switch to
or from digest mode, change your password, etc.), visit your
subscription page at:

You can also make such adjustments via email by sending a message to:

  users-request <at>

with the word `help' in the subject or body (don't include the
quotes), and you will get back a message with instructions.

You must know your password to change your options (including changing
the password, itself) or to unsubscribe without confirmation.  It is:


Normally, Mailman will remind you of your mailing list
passwords once every month, although you can disable this if you
prefer.  This reminder will also include instructions on how to
unsubscribe or change your account options.  There is also a button on
your options page that will email your current password to you.

users mailing list
users <at>
Nick Wiltshire | 1 Sep 01:30 2014

Dear Wallace: where's my mail?

I wrote to list earlier today regarding mail not showing up in my inbox. 
Ironically, I didn't see any replies because of the same issue.

I have since figured out that wallace was eating my mail. The new 3.3 Postfix 
config has mail delivered to wallaced on port 10026. This was happening.

Wallace is supposed to then re-inject mail back to  postfix on port 10027. It 
was not. Still isn't. So while I can now receive mail by bypassing wallace, I 
likely have mail stuck in a wallace queue somewhere (or perhaps it is gone?)

Since this daemon seems to be the worst documented piece of software in the 
history of man kind, can someone give me a hint of where to start looking? Or 
is all that mail just gone?

The sum of documentation for wallace on the entire internet seems to be this:

"Wallace is a modular daemon responsible for filtering the content passing 
through it as part of the mail flow between recipients and senders.

While it does not perform anti-spam and anti-virus content filtering, for which 
Kolab Groupware uses Amavisd, SpamAssassin and ClamAV, mail submitted through 
Wallace is handled with specific use-cases for particular mail flows in mind."

So I know what it doesn't do, and have a vague idea that it does something. 
I'm guessing it's not supposed to eat my mail.
Martin Teufel | 31 Aug 09:02 2014

kolab_smtp_access_policy; Kolab 3.3, CentOS 7

I’m running a fresh install of Kolab 3.3. under CentOS 7.

I cannot receive Mails from outside. Sending works.


/var/log/maillog reports the following:

Aug 31 08:50:12 email postfix/spawn[7725]: warning: command /usr/libexec/postfix/kolab_smtp_access_policy exit status 1

Aug 31 08:50:12 email postfix/smtpd[7712]: warning: premature end-of-input on private/recipient_policy_incoming while reading input attribute name


If I disable the “check_policy_service unix:private/…” in postfix (for submission_sender_restrictions, submission_recipient_restrictions, smtpd_recipient_restrictions, submission_data_restrictions) receiving of mail works.


But I don’t think that is workaround is ok for production?

Someone who can help me with this issue?




#submission_sender_restrictions = reject_non_fqdn_sender, check_policy_service unix:private/submission_policy, permit_sasl_authenticated, reject

submission_sender_restrictions = reject_non_fqdn_sender, permit_sasl_authenticated, reject


#submission_recipient_restrictions = check_policy_service unix:private/submission_policy, permit_sasl_authenticated, reject

submission_recipient_restrictions = permit_sasl_authenticated, reject


#smtpd_recipient_restrictions = permit_mynetworks, reject_unauth_pipelining, reject_rbl_client, reject_non_fqdn_recipient, reject_invalid_helo_hostname, reject_unknown_recipient_domain, reject_unauth_destination, check_policy_service unix:private/recipient_policy_incoming, permit

smtpd_recipient_restrictions = permit_mynetworks, reject_unauth_pipelining, reject_rbl_client, reject_non_fqdn_recipient, reject_invalid_helo_hostname, reject_unknown_recipient_domain, reject_unauth_destination, permit


#submission_data_restrictions = check_policy_service unix:private/submission_policy



users mailing list
users <at>
flesby . | 30 Aug 14:39 2014


users mailing list
users <at>
Pasi Kärkkäinen | 29 Aug 22:14 2014

Kolab 3.3 Calendar event invitations are not saved in Sent emails folder


While testing Kolab 3.3 I was playing with the Calendar in Roundcube and I noticed 
that I can't see sent calendar event invitations in Sent emails folder. 

Calendar event invitations *are* sent outside as emails (verified from smtp logs), 
but I just can't seem to be able to see them in Sent emails folder..

Is that like how it's designed to be? or am I hitting some bug..

With Outlook/Exchange you can see sent calendar invitations in Sent-items
(and also you can see accept/decline responses in Inbox aswell),
so many people expect them to behave like that..

I noticed there's this recent enhancement:

.. but that's not really the same thing..


-- Pasi
Christian Hügel | 29 Aug 19:02 2014

Support for Kolab 3.2

Just wanted to ask how long will kolab 3.2 be supported?