From Kolab Wiki
Revision as of 04:13, 9 November 2015 by Donomar
- Is it possible to use newer OpenPKG packages to work with Kolab instead of using those provided by the Kolab project?
- You can use and update to the latest OpenPKG packages except those with "kolab" in the name as these have been patched especially to work within a Kolab Server. For upgrading instructions see Upgrading Clamav
- Do I have to use OpenPKG to run the Kolab2 Server?
- Kolab2 Server uses the OpenPKG environment to provide a constant base across multiple platforms and distributions. This allows to ensure that the server works under a variety of conditions. But you can look at Kolab2 linux distribution integration to find distributions that natively integrate Kolab without the use of OpenPKG. But please NOTE: this is for the experienced Kolab user and is not supported! You will be on your own when fixing problems with packages etc!
- How do I uninstall Kolab?
- See Uninstall Kolab.
Configuration - General
- I changed a configuration file xyz.conf to suit my own needs but now my changes have gone!
- The kolab server uses templates as a basis for all configuration files relevant to the server. These can be found in /kolab/etc/kolab/templates. Please edit only these files to make your changes permanent. Changes in the original configuration files will get overwritten! After editing a template, run /kolab/sbin/kolabconf to process your changes into the configuration files. There is a special page that describes the Kolab configuration concept.
- How can I make sure that I am using the openpkg environment when running a shell command, not my host's?
- Use Opa, it is a small script that sets the correct environment for you.
- How can I use multiple domains in my Kolab installation?
- Kolab Server 2.1 can handle multiple email domains.
- How can I use multiple domains in Kolab versions below 2.1?
- There is no "true" multidomain support, but you can add domains to /kolab/etc/kolab/templates/main.cf.template under the mydestination directive (mydestination = @@@postfix-mydestination|join @@@ extradomain.com). Run /kolab/sbin/kolabconf after that. Now you will need to add aliases to existing users (so that email@example.com has an alias for firstname.lastname@example.org). If you wish all users defined in mydomain.com also to recieve mail sent to the same user name under extradomain.com, then enter the folowing line in virtual.template:
- I want to allow local services (like Mysql, Cron or Backup) to send mails to local kolab-accounts.
- In this case the tiny application "nullmailer" can be helpful. It has very low dependencies and it´s easy to configure. You have to set localhost as smarthost in the configuration and optionally you can define an admin e-mail address which acts as local catchall. That's all. (debian: /etc/nullmailer/remotes, /etc/nullmailer/adminaddr).
- My ISP offers a POP mailbox for mail, how can I get kolab to fetch this mail and distribute it?
- See Fetchmail with Kolab2 for how to do this.
- How do I use shared folders?
- Please read the page Shared folders for detailed information.
- How do I handle SSL certificates on a Kolab server?
- Please read the SSL certificates section for detailed information.
Configuration - User management
- What are the "Kolab Account Types" that can be selected when creating a kolab user?
- The details are described in Kolab Account Types.
- I get an error when trying to create an account with the name "admin" (e.g. email@example.com). I am also unable to add it as alias to an existing account. How can I receive email for the "admin" address?
- The "admin" name is already being used for an internal distribution list, so it cannot be used again. If you really wish to create and use such an address you can read Allowing "admin" addresses.
Configuration - Errors
- Emails are not getting delivered and I find the error "failure to connect to port 10026" in the postfix log.
- Go and see if "localhost" points to 127.0.0.1 or to the real IP of the system. If not, correct it in /etc/hosts. The reason is that postfix listens on 127.0.0.1:10026, and if localhost does not point to this address, the system will not be able to forward emails.
- Sometimes the connection to Kolab-Server times out or it just takes long time even in a LAN.
- There is a detailed description of Timeout problems.
Configuration - Mail addresses
- I wish to be able to send mail to users like firstname.lastname@example.org by using the same username but with domain2.com (e.g. email@example.com).
- Sometimes you may have two or more domains matching a single company and you would like to map all the different domain endings to single addresses. In order to do that you can add this line in /kolab/etc/kolab/templates/virtual.template:
If you created a user with the mail address of firstname.lastname@example.org, you will now be able to also use email@example.com.
- How can I backup my kolab2 server, with emails and configuration etc
- Please look at Backups_for_kolab2 - If you have any other methods that work, please add them!
- How do I teach spamassassin what is spam and what is not?
- Spamassassin's Bayesian database can be updated to learn what is spam and what is not. This is done with `sa-learn` and switches. Learning from spam can make your spam filtering a lot more effective! To update the spam dbs, run `/kolab/bin/sa-learn --spam /kolab/var/spool/domain/path/to/spam/*`. Make sure to point it to a folder containing spam. This can be done by making a public folder and asking everyone to move their spam there. If you make a mistake, or if spamassassin is marking normal mail as spam, you can run sa-learn with the switch "--ham". This teaches it that these mails are not spam. Unfortunately, the openpkg used for the development kolab2 does not have cron, so you will need to use your host OS'es cron for scheduling spam learning. EDIT - kolab2-server-beta-2.0 has dcron installed, this may be used to schedule spam learning. See Fighting_spam for a complete working example.
Virus and content scanning
- I need to send/receive a file, but it just doesn't work - I get a mail about it being banned
- Amavisd has a list of banned file types. See Amavisd-new#Banned_file_types for details on how to change these.
- How do I release a mail from the amavisd quarantine?
- Use the amavisd-release tool for this. See Amavisd-new#Releasing_mails_from_quarantine for details.
- Can I use SASL with Kolabs LDAP?
- No. If you run ldapsearch -x -L -s "base" -b "" supportedSASLMechanisms you will see that kolab's LDAP server doesn't support any SASL mechanisms. Kolab's LDAP server doesn't use SASL because our SASL setup uses the LDAP server as a backend for authentication. If you're looking for a LDAP server, further refered to here as slapd, with SASL support, consider using the slapd package coming with your distribution in addition to kolab's slapd. Just run your distro's slapd on a non-default and not yet used port and you'll be fine.