This should work with any carddav server, but if you use Kolab’s
carddav server here’s some extra tip!
The problem you want to fix is: it’s impossible to remember
everyone’s email address. This problem is solved by most email
programs because they are linked to a contact list already.
However, for those of us using mutt, there’s no full contact
integration so you need to rely on something else.
Recently I set up a spam-filter for my Kolab 3.0 server system. There are plenty of how-tos out there, so I only highlight some bits of my setup. Since I’m running Kolab on Ubuntu Server 12.04 (always use LTS for servers!), I started off installing the package for the clamav and spamassassin wrapper amavis and configured it according Combating Spam with a preseeded a (non-sql) bayes databayes and did some testing.
I had another chance to look at Kolab and the dependency graph recently. Having been inspired by the prospect of chat integration within Roundcube, I set out to install a suitable XMPP server, and it seemed that ejabberd was the most likely choice on Debian systems such as my own.
I picked up my cup of coffee from the dinner table this morning, and then it came to me. Why could we not encrypt an incoming message before it is delivered to IMAP?
After all, with Wallace, we do have the component in place to interrupt the mail flow like that -- we're using it for Resource Management already, and we have a module that can append a footer as well.
So I build a proof-of-concept. This is what I do:
# date | mail -s "test" firstname.lastname@example.org
I watch this being picked up by Postfix, go through Amavis, and be delivered to Wallace.
Normally, today's just that one day you are a little bit more attentive to those you admire.
In secret, or outspoken, it doesn't really matter. Anonymous, or with an email address -- whatever floats your boat goes, really.
Today however also marks the day that Kolab is being that little bit more attentive to you, whom we secretly admire.
We are proud to announce the immediate availability of Kolab 3.2! This is for you, yours and everyone else, for this release marks another milestone in the Kolab story, as previously seen on the Internet.
Having a chat right from your Kolab webclient will be possible soon. The email addresses of your Kolab users will automatically work as Jabber (XMPP) addresses. This feature is still in development, but Thomas already proposed a possible path of how to integrate XMPP into the Kolab web client for those who already have a Jabber server running along with their Kolab installation.
By default, Kolab does not allow you do send mails from external email addresses that are not hosted by Kolab itself. However, it is quite easy to change this.
In /etc/kolab/kolab.conf find the section [kolab_smtp_access_policy] and add mailalternateaddress to the address_search_attrs. Now you just have to enter all external addresses a user should be able to use to the External Addresses field in the Kolab Web Admin.