[pkg-kolab] r184 - trunk/kolab-cyrus-imapd/debian
Steffen Joeris
white-guest at costa.debian.org
Mon Jan 23 13:41:01 UTC 2006
Author: white-guest
Date: 2006-01-23 13:41:00 +0000 (Mon, 23 Jan 2006)
New Revision: 184
Removed:
trunk/kolab-cyrus-imapd/debian/README.Debian.database
trunk/kolab-cyrus-imapd/debian/README.Debian.debug
trunk/kolab-cyrus-imapd/debian/README.Debian.simpleinstall
trunk/kolab-cyrus-imapd/debian/README.exim
trunk/kolab-cyrus-imapd/debian/README.postfix
trunk/kolab-cyrus-imapd/debian/README.sendmail
trunk/kolab-cyrus-imapd/debian/UPGRADE.Debian
trunk/kolab-cyrus-imapd/debian/watch
Log:
* we don't need these READMEs
Deleted: trunk/kolab-cyrus-imapd/debian/README.Debian.database
===================================================================
--- trunk/kolab-cyrus-imapd/debian/README.Debian.database 2006-01-23 13:34:49 UTC (rev 183)
+++ trunk/kolab-cyrus-imapd/debian/README.Debian.database 2006-01-23 13:41:00 UTC (rev 184)
@@ -1,122 +0,0 @@
-Cyrus IMAP for Debian: Database backend conversion
-$Id: README.Debian.database 5 2005-03-12 23:19:45Z sven $
---------------------------------------------------
-
- "All systems administrators have their horror stories. For me, it was
- setting up a HP Color Bubblejet under Linux using ghostscript before
- linuxprinting.org was alive. Well that was a piece of cake compared
- to what I am about to describe in this document."
- -- "Hosting email for virtual domains using Postfix and Cyrus"
- Haim Dimermanas, 2001-08-01
-
- "I warned you to read all the documentation first, didn't I?"
- -- Henrique M. Holschuh, 2002-10-01
-
-For more information, please consult http://asg.web.cmu.edu/cyrus/imapd/.
-There is also Cyrus-HOWTO (Cyrus-IMAP.txt) available as part of the LDP HOWTO
-collection. Upgrade hints are in UPGRADE.Debian. Outdated documentation will
-cause you much grief, so beware of that when hunting anywhere else than the
-Cyrus mailinglist for information.
-
-
-Database backends
------------------
-
-Cyrus can be compiled to use different types of database backends for each of
-its databases. The package will warn you if you try to start Cyrus and the
-database backends seem to have changed since the last active version.
-
-After converting all the mail stores and /var/lib/cyrus to use the proper
-database backends using cvt_cyrusdb(8), remove
-/usr/lib/cyrus/cyrus-db-types.active and run "dpkg-reconfigure cyrus22-common"
-once to reset the error trigger, and start cyrmaster.
-
-If cvt-cyrusdb locks up just at the beginning of the conversion, your databases
-might be locked. Unlock them (i.e. REALLY stop Cyrus if it is still running,
-use the db3* utilities to clean any stray locks, or try a reboot).
-
-Step-by-step conversion guide:
-
-1. Stop the Cyrus system
- /etc/init.d/cyrus22 stop
-
-2. Find out which databases to convert:
- diff -u /usr/lib/cyrus/cyrus-db-types.active \
- /usr/lib/cyrus/cyrus-db-types.txt
-
- The databases are these in the default install:
- DUPLICATE /var/lib/cyrus/deliver.db
- MBOX /var/lib/cyrus/mailboxes.db
- TLS /var/lib/cyrus/tls_sessions.db
-
- Don't bother upgrading the TLS database, just delete it: the information
- there is not reused when you stop Cyrus.
-
- If the BerkeleyDB version is what was changed, you need to use the
- Berkeley DB upgrade utility in all db* databases. See the manpages for
- db*_upgrade.
-
- The SUBS and SEEN databases are different: there are many of them (one
- for every mail folder of every user for SEEN; one for every user for
- SUBS) and you need to convert every single one of them.
-
- SUBS /var/lib/cyrus/...../*.subs
- SEEN /var/lib/cyrus/...../*.seen
-
- SUBS contains the subscribed folders, and SEEN contains the seen state
- of every mail in a folder.
-
- Types db3_nosync and db3 are the same for database conversion matters.
-
-2.1 Converting from DB* to SKIPLIST
-
- As user cyrus, do the following:
-
- cd /
- /usr/sbin/cvt_cyrusdb <fullpath to database> db3 \
- /var/lib/cyrus/temp.db flat
- rm -f <fullpath to database>
- /usr/sbin/cvt_cyrusdb /var/lib/cyrus/temp.db flat \
- <fullpath to database> skiplist
- chown cyrus:mail <fullpath to database>
- rm -f /var/lib/cyrus/temp.db
-
-2.2 Converting from FLAT to SKIPLIST
-
- As user cyrus, do the following:
-
- cd /
- mv <fullpath to database> <fullpath to database>.old
- /usr/sbin/cvt_cyrusdb <fullpath to database>.old flat \
- <fullpath to database> skiplist
- chown cyrus:mail <fullpath to database>
- rm -f <fullpath to database>.old
-
-2.3 SUBS and SEEN databases
-
- I suggest using a small shell script and using "find" to mass-convert
- the SEEN databases:
- find /var/lib/cyrus -type f -name '*.seen' -exec myshellscript {} \;
-
- The "find" command above you give you the name of the database as "$1"
- inside your shell script.
-
-3. Reset the database backend change system
- rm /usr/lib/cyrus/cyrus-db-types.active
- dpkg-reconfigure cyrus22-common
-
-4. Start Cyrus, if not started by step 3
- /etc/init.d/cyrus22 start
-
-WHY THERE IS NO AUTOMATED UPGRADE SCRIPT: Because I dislike people who do not
-read docs, and one Debian user asked me exactly the wrong thing (about
-cyrus21-imapd) while I was in the middle of writing said script AND I am quite
-short on time lately: it is much faster to write a doc than to write and test
-the script. So, now everyone will need to read the docs to get Cyrus working
-again. I am not holding back the skiplist change for that script anymore.
-
-Maybe someday I will finish the upgrade script. Maybe someone else will write
-one (I will certainly include it in the package, if it is good enough). Don't
-hold your breath, though.
-
- -- Henrique de Moraes Holschuh <hmh at debian.org>
Deleted: trunk/kolab-cyrus-imapd/debian/README.Debian.debug
===================================================================
--- trunk/kolab-cyrus-imapd/debian/README.Debian.debug 2006-01-23 13:34:49 UTC (rev 183)
+++ trunk/kolab-cyrus-imapd/debian/README.Debian.debug 2006-01-23 13:41:00 UTC (rev 184)
@@ -1,121 +0,0 @@
-Cyrus IMAP for Debian, debugging procedures
-$Id: README.Debian.debug 5 2005-03-12 23:19:45Z sven $
--------------------------------------------
-
-For more information, please consult http://asg.web.cmu.edu/cyrus/imapd/.
-
-Cyrus has various levels of debugging aid, which can and should be used to
-offer more information about any problems you are facing with Cyrus.
-
-First, edit /etc/default/cyrus22, and set CYRUS_VERBOSE to a number higher
-than zero. The higher the number, more debug information is provided. Numbers
-above 30 will cause Cyrus services to pause for 15s before executing (so that
-you can do something to it, such as attach strace or a debugger to the
-process).
-
-You can, and should use strace and ltrace to gather more information about what
-was happening to Cyrus when it malfunctioned. straces are useful when
-networking or signal problems appear to be the issue, and ltraces can give
-hints on what the problem might be.
-
-If a Cyrus service is crashing and cyrmaster logs that the service is being
-killed by a signal, please use the debugging hooks to provide a back-trace
-using gdb (see below). Back-traces are extremely useful when locating where
-Cyrus is dying, and why.
-
-Debugging information is sent to syslogd, using the DEBUG priority, facilities
-MAIL and DAEMON.
-
-You can also try to set MALLOC_CHECK_=2 in the environment, so that malloc()
-will cause Cyrus to dump core if it detects any sort of corruption.
-
-
-Telemetry logs
---------------
-
-Cyrus will happily log all communications between the Cyrus store closed-box and
-the outside world. These logs are sometimes vital to understand exactly what
-is happening and to reproduce bugs.
-
-To enable telemetry logging, create a directory under /var/lib/cyrus/log with
-the same name as the username for which you want the communication sessions to
-be logged. Cyrus will log all imap, pop3, sieve and lmtp talks authenticated
-as that user (including proxied connections). Make sure the directory is owned
-by user cyrus.
-
-Watch out for sensitive information such as passwords when you submit the
-telemetry logs to a public bug-tracking system or mailinglist.
-
-
-Recompiling Cyrus with debugging information
---------------------------------------------
-
-In order to produce useful back-traces, or to interactively debug Cyrus,
-you must rebuild the package with debugging information. It is quite
-easy to do so:
-
-1. Install all source dependencies to build the package (needs root):
- apt-get install build-essential fakeroot
- apt-get build-dep cyrus22-imapd
-
-2. Download and rebuild Cyrus with debug information:
- apt-get source cyrus22-imapd
- cd cyrus22-imapd-*
- DEB_BUILD_OPTIONS=debug,noopt,nostrip dpkg-buildpackage -uc -us -rfakeroot
-
-3. Install the Cyrus packages with debug information (needs root):
- cd ..
- dpkg -i *deb (or something like that)
-
-Now Cyrus should be working fine, using binaries with full debug information
-for gdb. For interactive debugging, you may want to make sure there are no
-optimizations, in which case you should use "DEB_BUILD_OPTIONS=noopt,nostrip
-dpkg-buildpackage -uc -us -rfakeroot".
-
-Warning: the next time you run apt-get update, apt will probably download the
-non-debugging version of the Cyrus debs, and install them over the debugging
-packages.
-
-To install the non-debugging, optimized version of Cyrus over the debugging
-one, issue "apt-get --reinstall install (package)" commands for all the Cyrus
-packages you want replaced.
-
-
-Attaching debuggers to Cyrus, and getting traces
-------------------------------------------------
-
-You can tell Cyrus services to run a debugging command just before they
-start doing real work. This can be used to run strace, ltrace and gdb
-or ddd (for interactive debugging and back-tracing) quite easily.
-
-Set the shell command to be run in /etc/imapd.conf, option debug_command.
-Then, add the command line switch "-D" to the Cyrus services you want to
-run the debug_command in /etc/cyrus.conf, and restart cyrmaster using
-/etc/init.d/cyrus22 restart.
-
-The debugging command must be given as a single line in the configuration file.
-
-To get a back-trace using gdb:
-debug_command: /usr/bin/gdb -batch -cd=/tmp -x /usr/lib/cyrus/getbacktrace.gdb /usr/lib/cyrus/bin/%s %d >/tmp/gdb-backtrace.cyrus.%1$s.%2$d <&- 2>&1 &
-
-The above will produce a back-trace of every service run with -D that segfaults
-in the files /tmp/gdb-backtrace.cyrus.*; /usr/lib/cyrus/getbacktrace.gdb
-simply has the sequence of commands for gdb: c (to continue running the
-service), bt (to get the back-trace if the program didn't exit normally), quit
-(to quit gdb).
-
-For strace, you can use:
-debug_command: /usr/bin/strace -tt -o /tmp/strace.cyrus.%s.%d -p %2$d <&- 2>&1 &
-
-Which will produce straces in /tmp/strace.cyrus.*
-
-For ltrace, you can use:
-debug_command: /usr/bin/ltrace -tt -n 2 -o /tmp/ltrace.cyrus.%s.%d -p %2$d <&- 2>&1 &
-
-Which will produce ltraces in /tmp/ltrace.cyrus.*
-
-Be warned that sensitive information such as passwords may be disclosed in the
-strace and ltrace output, so mangle them before sending such traces to public
-bug-tracking systems or mailing lists.
-
- -- Henrique de Moraes Holschuh <hmh at debian.org>
Deleted: trunk/kolab-cyrus-imapd/debian/README.Debian.simpleinstall
===================================================================
--- trunk/kolab-cyrus-imapd/debian/README.Debian.simpleinstall 2006-01-23 13:34:49 UTC (rev 183)
+++ trunk/kolab-cyrus-imapd/debian/README.Debian.simpleinstall 2006-01-23 13:41:00 UTC (rev 184)
@@ -1,173 +0,0 @@
-Cyrus IMAP for Debian, Simple Install Guide
-$Id: README.Debian.simpleinstall 5 2005-03-12 23:19:45Z sven $
--------------------------------------------
-
- "All systems administrators have their horror stories. For me, it was
- setting up a HP Color Bubblejet under Linux using ghostscript before
- linuxprinting.org was alive. Well that was a piece of cake compared
- to what I am about to describe in this document."
- -- "Hosting email for virtual domains using Postfix and Cyrus"
- Haim Dimermanas, 2001-08-01
-
- "I warned you to read all the documentation first, didn't I?"
- -- Henrique M. Holschuh, 2002-10-01
-
-
-This document describes how to get Cyrus running with a simple configuration
-that you can then tweak to your real needs.
-
-READ README.Debian AS WELL. I MEAN IT! Cyrus is easy, all the trouble is
-in SASL, and even that becomes easy after you understand how SASL works.
-
-IMPORTANT: Cyrus is a closed-box email system. Your system will access your
-email through LMTP, IMAP and POP3 *only*. No direct file access to the email
-store is supposed to take place.
-
-
-To setup Cyrus so that you can administer it (i.e. create users),
-and get email inside it for those users:
-
- 1. Make sure libsasl2-modules, libsasl2 and sasl2-bin are installed
-
- 2. Make sure /etc/sasldb2 is readable by group sasl. Pay attention
- to overrides (dpkg-statoverride)!
-
- 3. Make sure user cyrus belongs to group sasl (cyrus22-common's install
- tries to do this automatically for you).
-
- 4. Edit /etc/cyrus.conf, and make sure the services you need are
- enabled. These are most probably "imap", "pop3", "lmtpunix".
-
- 5. Edit /etc/imapd.conf, and make sure you have some admin users
- listed in the entry "admins:". I suggest using "cyrus" as your
- admin.
-
- I also suggest enabling plain text logins, and setting
- sasl_minimum_layer: 0
-
- If you have unixhierarchysep enabled in imapd.conf, change all
- "." in mailbox names mentioned on this document to "/", since Cyrus
- will use "/" as the hierarchy separator instead of the default ".".
- I suggest you just leave unixhierarchysep set to false for now.
-
- 6. Restart Cyrus (/etc/init.d/cyrus22 restart)
-
- 7. Use saslpasswd2 -c to create an account for your admin:
- saslpasswd2 -c cyrus
-
- 8. Use sasldblistusers2 to make sure step 7 worked fine.
-
- 9. Add other users to SASL likewise (saslpasswd2 -c).
-
-10. Log in cyrus as the administrator, and create the mailboxes:
- cyradm --user cyrus localhost
- cm user.bob
- cm user.anna
- cm user.clark...
- ^D
-
- (notice that there is an "user." in front of the mailbox name!)
- You must use "user/bob", "user/anna" instead if you have the
- unixhierarchysep option enabled in imapd.conf.
-
- For this to work, you obviously need the cyrus22-admin package
- installed.
-
-11. Try to login as a normal user, using imtest or a IMAP/POP3 client.
- If you have trouble with mutt and CRAM-MD5 or DIGEST-MD5, edit
- /etc/imapd.conf, and look for sasl_mech_list. Set it to:
- sasl_mech_list: plain cram-md5
- (this will disable digest-md5, which causes trouble with mutt).
-
-12. Setup your MTA to deliver email inside Cyrus. Basically that can
- be done (easily) by:
-
- a) running /usr/sbin/cyrdeliver (SLOW)
- You need the lmtpunix service enabled in /etc/cyrus.conf for this
- to work.
- b) delivering using LMTP to /var/run/cyrus/socket/lmtp
- You need the lmtpunix service enabled in /etc/cyrus.conf for this
- to work.
-
- Just make sure (and use dpkg-statoverride to do that) that your
- MTA can get to /var/run/cyrus/socket/lmtp. It works just like any
- file in a Unix system.
-
- Cyrus REQUIRES a valid RFC2822 message, and will refuse messages with
- bad headers (such as that From foobar header, notice the missing ':'),
- embedded NULLs or any other crap.
-
-
-That's it. See /usr/share/doc/cyrus22-common/README.{postfix,exim,sendmail}
-for help on how to setup your MTA to correctly deliver to Cyrus.
-
-
-LDAP SETUP
-----------
-
-First, do the steps above and verify that your system is working fine.
-
-SASL is perfectly capable of trying various authentication methods one after
-another. We will change our Cyrus setup for SASL to use a LDAP server lookup
-through saslauthd.
-
-1. Create the configuration for saslauthd to know what it must do:
-
- Write the following file to /etc/saslauthd.conf:
-----CUTHERE----
-ldap_servers: ldap://127.0.0.1/
-ldap_version: 3
-ldap_timeout: 10
-ldap_time_limit: 10
-ldap_cache_ttl: 30
-ldap_cache_mem: 32768
-ldap_scope: sub
-ldap_search_base: ou=mail,o=mydomain
-ldap_auth_method: bind
-ldap_filter: maildrop=%u
-----CUTHERE----
- And of course, edit it to fit your LDAP setup.
-
-2. Now, configure saslauthd to use LDAP mode and our config file:
-
- Modify /etc/default/saslauthd so that it reads:
- MECHANISMS="ldap"
- PARAMS="-O /etc/saslauthd.conf"
-
- (MECHANISMS can be a space-separated list of authentication
- mechanisms. If you wanted saslauthd to try LDAP, then PAM, you
- could use MECHANISMS="ldap pam")
-
-3. Start saslauthd
-
- /etc/init.d/saslauthd restart
-
-4. Make sure Cyrus will be able to talk to saslauthd
-
- Set the following options in /etc/imapd.conf:
- sasl_mech_list: PLAIN
- allowapop: no
- allowplaintext: yes
- sasl_minimum_layer: 0
- sasl_pwcheck_method: saslauthd
-
- And restart Cyrus. You'd better understand that the above allows
- plaintext logins over the network. There is a LDAP SASL auxprop
- plugin being worked on that might fix this issue. As it stands
- right now, you're better off by only accepting IMAPS (secure IMAP)
- connections.
-
- (sasl_pwcheck_method is a space separated list of SASL methods to
- try. If you want to have some local users in /etc/sasldb2, for
- example, you could have "sasl_pwcheck_method: auxprop saslauthd"
- and also "sasl_auxprop_plugin: sasldb")
-
- One *extremely* important point to notice is that saslauthd works
- ONLY with plaintext. APOP, CRAM-MD5, OTP, DIGEST-MD5 and any other
- "auxprop" SASL mech will *not* work through saslauthd.
-
-5. That's it. There is a LDAP auxprop module in the works which can deal
- with APOP, CRAM-MD5, OTP, DIGEST-MD5 and so on, look for it in the SASL
- docs and openldap's contrib stuff.
-
- -- Henrique de Moraes Holschuh <hmh at debian.org>
Deleted: trunk/kolab-cyrus-imapd/debian/README.exim
===================================================================
--- trunk/kolab-cyrus-imapd/debian/README.exim 2006-01-23 13:34:49 UTC (rev 183)
+++ trunk/kolab-cyrus-imapd/debian/README.exim 2006-01-23 13:41:00 UTC (rev 184)
@@ -1,66 +0,0 @@
-Setting up Cyrus IMAPd for Exim
-$Id: README.exim 5 2005-03-12 23:19:45Z sven $
-===========================================================
-
-This is very incomplete information, if you are an exim user, please send
-in a more complete document.
-
-
-General configuration hints (configuration examples assume you are using
-the Debian Exim4 configuration scheme and paths are relative to
-/etc/exim4):
-
-1. Use Exim version 4. Exim version 3 just doesn't cut it in the lmtp
- area, which is very important for performance when dealing with Cyrus
- IMAPd.
-
-2. Use the LMTP transport to deliver using a unix socket (fastest), or
- the SMTP transport in LMTP mode to deliver over a TCP/IP socket.
-
- For local delivery over a unix socket, add a file into conf.d/transports
- with the following:
-
- cyrus_delivery:
- driver = lmtp
- socket = /var/run/cyrus/socket/lmtp
- batch_max = 20
- user = mail
-
- (set batch_max to whatever is best for your setup, and make sure you
- allow enough Cyrus lmtp processes to serve that many lmtp connections)
-
- If that doesn't work, I suggest you create a group for lmtp delivery,
- add whichever user exim is running as to it, and use dpkg-statoverride
- to make /var/run/cyrus/socket/lmtp writeable by that group.
-
- To then deliver to Cyrus, you will need to comment check_local_user in
- conf.d/router/900_exim4-config_local_user, and change the LOCAL_DELIVERY
- macro in conf.d/main/01_exim4-config_listmacrosdefs to
- LOCAL_DELIVERY=cyrus_delivery.
-
- If you still want to deliver some messages to a mail spool then create
- conf.d/router/899_exim4-config_copy_to_mbox and put this in it, changing
- the local_parts as necessary:
-
- copy_to_mbox:
- debug_print = "R: copy_to_mbox for $local_part@$domain"
- driver = accept
- unseen
- local_parts = postmaster
- transport = mail_spool
-
- This will deliver postmaster mail to both cyrus and
- /var/mail/postmaster. You can comment the unseen option to have it only
- deliver once to the mail_spool. If you don't set check_local_user or
- the user option the spool files will be owned by mail.
-
-3. Kill any NULs (ASCII 0x00) inside the message, if you don't want Cyrus
- to bounce such malformed crap. Calling "tr -d '\000'" as a filter might
- do the trick.
-
-4. Sieve often needs to set -f option on /usr/sbin/sendmail when doing
- redirects. Exim allows only trusted_users to do this. It is recommended
- that you make sure "cyrus" is in the list of trusted_users in
- conf.d/main/02_exim4-config_options:
- trusted_users = uucp:cyrus
-
Deleted: trunk/kolab-cyrus-imapd/debian/README.postfix
===================================================================
--- trunk/kolab-cyrus-imapd/debian/README.postfix 2006-01-23 13:34:49 UTC (rev 183)
+++ trunk/kolab-cyrus-imapd/debian/README.postfix 2006-01-23 13:41:00 UTC (rev 184)
@@ -1,143 +0,0 @@
-Setting up Cyrus IMAPd for Postfix (Debian)
-$Id: README.postfix 5 2005-03-12 23:19:45Z sven $
-===========================================================
-
-Cyrus works wonderfully well with Postfix, both in single-system stores (where
-Postfix runs in the same host as Cyrus IMAPd), and remote mail stores (where
-Cyrus IMAPd is in a different host than Postfix).
-
-Delivery to Cyrus should _always_ be done through direct LMTP from Postfix. It
-is far simpler and faster to do such delivery using Unix sockets, but Unix
-sockets are only an option for single-system stores. Cyrdeliver is just a
-stdio-to-LMTP proxy, and it slows down mail delivery greatly.
-
-Cyrus requires LMTP deliveries to be authenticated. It assumes that any
-deliveries done through an Unix socket are trustable, and pre-authenticates
-them as if coming from the "postman" (fictitious) user (but you _can_
-re-authenticate them as another lmtp admin user, if you wish).
-
-Deliveries done through TCP sockets are not limited to the same host, unlike
-the Unix socket ones, and can therefore be used in remote mail stores.
-However, Cyrus requires that the LMTP session be authenticated using one of the
-SASL mechs available to Cyrus (you can switch this off by giving a "-a"
-parameter to lmtpd in cyrus.conf, but that is unsafe since anyone can bypass
-any user authentication controls you might have on mail delivery, that way).
-
-TCP-socket LMTP sessions should be authenticated as one of the Cyrus LMTP
-admins, normal Cyrus users are not enough. This requires Postfix with SASL
-support.
-
-
-Setting up Postfix for LMTP delivery to Cyrus
-=============================================
-
-Just set up a transport (either using a transport map, or the default_transport
-configuration directive of Postfix). Do not use cyrdeliver.
-
-I suggest that the lmtp transport be duplicated and renamed to cyrus if you
-use it to talk to anything else (such as amavisd-new, or amavis-ng). That
-way, LMTP connection caching to the Cyrus store gets optimized, and you can
-use the lmtp-named LMTP transport for something else.
-
-WARNING: Postfix 2.0 does not downcase the recipient in LMTP deliveries, so if
-your users require it, you will have to set lmtp_downcase_rcpt: yes in
-imapd.conf.
-
-
-Unix sockets:
--------------
-
-For Unix sockets, the Postfix transport is specified as
-"lmtp:unix:/var/run/cyrus/socket/lmtp", (we are using the default Cyrus unix
-socket location as an example, you can change it in /etc/cyrus.conf and
-/etc/imapd.conf).
-
-You need a Cyrus lmtpd service listening on that socket, of course, so make
-sure something like:
-
-lmtpunix cmd="lmtpd" listen="/var/run/cyrus/socket/lmtp"
-
-is in the SERVICES section of the /etc/cyrus.conf file. You also need to make
-sure both Cyrus and Postfix can talk through that socket. Unix sockets work
-just like files, so that translates to making sure both the user "cyrus" and
-the user Postfix is using for LMTP delivery can both read and write to that
-file.
-
-WARNING: Since Cyrus pre-auths anything coming through the Unix socket, anyone
-who can write to it will be able to inject email into Cyrus directly.
-
-Use dpkg-statoverride to make sure your configuration for the socket
-permissions will not be overwritten by the Cyrus packages. Do remember that
-Postfix usually runs the LMTP transport as user "postfix" (configurable in
-/etc/postfix/master.cf). Also, do not run the postfix lmtp transport chrooted
-if the socket is not inside the chroot.
-
-1. Create a lmtp group:
- # addgroup lmtp
-
-2. Put user postfix in that group:
- # adduser postfix lmtp
-
-3. Fix the socket directory permissions:
- # dpkg-statoverride --force --update --add \
- cyrus lmtp 750 /var/run/cyrus/socket
-
-4. Restart Postfix and Cyrus IMAPd
- # /etc/init.d/postfix restart
- # /etc/init.d/cyrus22 restart
-
-
-TCP sockets:
-------------
-
-TCP sockets are easier on the Cyrus side, and more complicated on the Postfix
-side. For Cyrus, it is enough to have an "lmtpd" service listening on the
-desired IP interface (or in all of them, if you leave the interface unspecified
-as in the example below), that means something like this in /etc/cyrus.conf
-SERVICES area:
-
-lmtp cmd="lmtpd" listen="lmtp"
-
-(do note that you MUST have an lmtp entry in /etc/services for this to work).
-
-Also, remember to set the tcpwrapper permissions up (/etc/hosts.allow and
-/etc/hosts.deny), or Cyrus might refuse the connections.
-
-To configure Postfix' lmtp transport to authenticate using SASL, do the
-following:
-
-1. Configure the lmtp transport SASL layer:
- (add to /etc/postfix/main.cf):
- lmtp_sasl_auth_enable = yes
- lmtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
- lmtp_sasl_security_options =
- lmtp_destination_concurrency_limit = 100
- lmtp_destination_recipient_limit = 0
-
- The *_limit values should match whatever you configured as limits in
- Cyrus. The above configuration will allow plain text logins.
-
- Create the password map /etc/postfix/sasl_passwd to tell postfix
- of a Cyrus LMTP administrator user and password to use.
-
- e.g.:
- echo "mycyrusspool.my.domain.org postman:foobar" >sasl_passwd
- postmap sasl_passwd
-
-2. Configure Cyrus to accept that user as a lmtp administrator
- (add to /etc/imapd.conf)
- lmtp_admins: postman
-
-3. Tell postfix to use the lmtp transport to deliver email using
- transport maps or something else. I suggest making a copy of the
- postfix lmtp transport in master.cf, renaming it to "cyrus", and
- using that.
-
-4. Note that to use the new feature of virtual domains in Cyrus v2.2,
- you need to tell postfix to use the lmtp transport as the
- virtual_transport. If you also want "local" mail recipients, i.e.
- those that are addressed to hosts listed in mydestination, to
- be delivered to Cyrus v2.2, you also need to use lmtp as the
- mailbox_transport.
-
- That's it!
Deleted: trunk/kolab-cyrus-imapd/debian/README.sendmail
===================================================================
--- trunk/kolab-cyrus-imapd/debian/README.sendmail 2006-01-23 13:34:49 UTC (rev 183)
+++ trunk/kolab-cyrus-imapd/debian/README.sendmail 2006-01-23 13:41:00 UTC (rev 184)
@@ -1,69 +0,0 @@
-Setting up Cyrus IMAPd for Sendmail (Debian)
-$Id: README.sendmail 5 2005-03-12 23:19:45Z sven $
-===========================================================
-
-[This is user-contributed, unverified information]
-
-First, do *not* use the old cyrus*.m4 macros, they won't work well. The one
-you can use is cyrusv2.m4. There are many methods of connecting Cyrus to
-sendmail, and replacing the local mailer with Cyrus lmtpd is just one of
-them.
-
-Andrzej Filip <anfi at priv.onet.pl> says:
-http://www.polbox.com/a/anfi/sendmail/localNalias.html
- Cyrus Aliases
- It allows to use user at CYRUS redirections in virtusertable,
- aliases and .forward file e.g. I use the following ~anfi/.forward:
- anfi at CYRUS
-
-http://www.polbox.com/a/anfi/sendmail/localtab.html
- Local Table
-
-http://www.polbox.com/a/anfi/sendmail/rtcyrus.html
- Real Time Cyrus Integration [requires sendmail patch]
- It allows sendmail to check presence of cyrus mailbox in real time,
- sendmail rejects message to non existing cyrus mailboxes in reply to
- "RCPT TO:"
-
-
-I am not sure how well these will work with sieve. The one report I have
-for Cyrus + sendmail with working sieve is:
-
-"cyrus/sieve vacation seems to work only if you integrate cyrus via
-cyrusv2.m4 into sendmail (8.12.3-4)."
-
-Sample sendmail.mc that seems to work:
---------
-[...]
-dnl define BIND_OPTS',`-DNSRCH -DEFNAMES')dnl
-define(`confLOCAL_MAILER', `cyrusv2')dnl
-MAILER(`local')dnl
-MAILER(`smtp')dnl
-MAILER(`cyrusv2')dnl
-dnl MODIFY_MAILER_FLAGS(`cyrus',`+w')dnl
-
-LOCAL_RULE_0
-Rbb + $+ < @ $=w . > $#cyrusbb $: $1
-[...]
---------
-
-Here's a sieve test script you can try. Change it as needed for your
-site:
-
-require "fileinto";
-require "vacation";
-require "envelope";
-
-if header :contains "subject" "vactest" {
- vacation :days 7 :addresses ["me at home.de"] "vactest!";
-}
-
-
-Pierre Gambarotto <pierre.gambarotto at enseeiht.fr> says:
-The minimum in order to make it work with sendmail is:
-
-define(`confLOCAL_MAILER', `cyrusv2')
-define(`CYRUSV2_MAILER_ARGS',`FILE /var/run/cyrus/socket/lmtp')
-MAILER(`cyrusv2')
-
-The CYRUSV2_MAILER_ARGS is the key.
Deleted: trunk/kolab-cyrus-imapd/debian/UPGRADE.Debian
===================================================================
--- trunk/kolab-cyrus-imapd/debian/UPGRADE.Debian 2006-01-23 13:34:49 UTC (rev 183)
+++ trunk/kolab-cyrus-imapd/debian/UPGRADE.Debian 2006-01-23 13:41:00 UTC (rev 184)
@@ -1,155 +0,0 @@
-Upgrading cyrus-imapd to cyrus2-imapd on Debian
-(thanks to David D. Kilzer <ddkilzer at theracingworld.com> for this document)
------------------------------------------------
-
-For more information, see README.Debian[.gz] in /usr/share/doc/cyrus22-common/
-and the web page below, part of the cyrus-utils project at SourceForge:
-
- http://cyrus-utils.sourceforge.net/faq
-
-Upgrading form cyrus 2.1
-========================
-
-If you upgrade from cyrus 2.1, all you need to do is to upgrade the
-database files from the old database backend to the new one. If you use
-sieve-scripts, you will also need to use sievec on them. The information
-how to do upgrade your database files is contained in the upgrade
-information from cyrus v1.6 below. In a later version of this package,
-we will give more detailed information on upgrades.
-
-NOTE: The default value of the dracinterval imapd.conf option changed from
-the old default value of 5 to 0 as it had been documented to be for ages.
-
-Upgrading sieve scripts
------------------------
-
-Cyrus IMAPD 2.2 uses bytecode for sieve scripts. This means that you need to
-compile all existing sieve scripts so that they will work with cyrus22. There
-is a small tool in /usr/lib/cyrus/upgrade, called masssievec which will
-automatically compile all installed scripts when called correctly. Please
-refer to the scripts usage information for details.
-The command line you will probably want to use is (as user cyrus):
-/usr/lib/cyrus/upgrade/masssievec /usr/lib/cyrus/bin/sievec /etc/imapd.conf
-
-Upgrading from cyrus 1.5.x
-==========================
-
-This document describes the procedure for upgrading from the old cyrus-imapd
-(v1.5.x) package to the new cyrus22-imapd (v2.2) package. While this is a
-manual process, it is very straightforward.
-
-The procedure for converting a v1.6 cyrus store to v2.2 is not explained here,
-but the tools to convert the sieve scripts are in /usr/lib/cyrus/upgrade.
-
-Your SASL installation may require further conversion steps, as Cyrus v2.2 uses
-SASL v2, while Cyrus v1.5 used SASL v1.5. /usr/share/doc/libsasl2 has more
-information on SASL v2. Do pay attention to your SASL v2 installation, such
-as permissions and such. When in doubt, read the README.simpleinstall
-document, as it describes an initial SASLv2 setup.
-
-NOTE: If you've already installed the cyrus22 packages, skip to step 5.
-
- 1. Become the "root" user on your local system.
-
- $ /bin/su -
- #
-
- 2. Look for any running cyrus daemons using the ps(1) command. Use
- kill(1) to stop any processes that are found.
-
- # /etc/init.d/pwcheck stop
- # ps auwwx | grep cyr
- # ps auwwx | grep pop3d
- # ps auwwx | grep imapd
- # ps auwwx | grep nntpd
-
- 3. Remove the old cyrus packages.
-
- # apt-get --purge remove cyrus-common cyrus-admin cyrus-imapd cyrus-pop3d \
- cyrus-nntpd
-
- or use dselect/aptitude/synaptic/your favorite deb management tool.
-
- IMPORTANT: You must answer "n" to this question: "Do you want me to
- remove the Cyrus mail and news spool (y/n) [n] ?"
-
- NOTE: You could also copy -a the /var/spool/cyrus and /var/lib/cyrus
- folders somewhere else, just in case.
-
- 4. Install the new cyrus22-imapd packages. Make sure no user will try
- to connect to imapd/pop3d and that no MTA will try to deliver to lmtpd
- until you do step 5.
-
- cyrus22-common [required]
- cyrus22-admin [required]
- cyrus22-imapd [optional; must have one of imapd or pop3d]
- cyrus22-pop3d [optional; must have one of imapd or pop3d]
- libcyrus-imap-perl22 [required]
-
- # apt-get install PACKAGE-NAME [PACKAGE_NAME ...]
-
- or use dselect.
-
- 5. Stop the cyrmaster process.
-
- # /etc/init.d/cyrus22 stop
-
- 5a. Make sure Cyrus won't start until the upgrade process is over.
-
- # cp -f /usr/lib/cyrus/upgrade/cyrus-db-types.upgrading_from_1.5.txt \
- /usr/lib/cyrus/cyrus-db-types.active
-
- 6. Change to the "cyrus" user.
-
- # /bin/su - cyrus
- $
-
- 7. Run the rehash program.
-
- $ /usr/lib/cyrus/upgrade/rehash basic
-
- 8. Run ctl_mboxlist to update the "mailboxes" file.
-
- $ cd /var/lib/cyrus
- $ /usr/sbin/ctl_mboxlist -u < mailboxes
-
- 9. Run the cyrreconstruct program from the /var/spool/cyrus directory
- to reconstruct the mailboxes.
-
- $ cd /var/spool/cyrus
- $ /usr/sbin/cyrreconstruct -r user.*
-
- (you may need to cyrreconstruct other mailboxes, if you have any
- system mailboxes or shared mailboxes not in the user hierarchy)
-
-10. Exit the "cyrus" user, back to "root".
-
- $ exit
- #
-
-11. Upgrade all of the db2 files used by Cyrus from to db4.2.
-
- # find /var/lib/cyrus -name \*.db -print -exec /usr/bin/db4.2_upgrade {} \;
-
-12. Convert the state databases to those used by new Cyrus 2.2
-
- Read /usr/share/doc/cyrus22-common/README.Debian.database, and follow
- whatever steps you need to change the backends from db3 to skiplist.
-
- This step needs some work, if you can send your experiences with it
- to hmh at debian.org, I will update this document accordingly.
-
-**** The upgrade of Cyrus' stores are now complete ****
-
-You may want to remove any left-over empty directories from the old version,
-and re-run /usr/sbin/cyrus-makedirs just in case you got one of them wrong.
-
-Now, you need to reconfigure the new Cyrus imapd to adequate it to your system
-and SASL requirements. The Cyrus config files are /etc/imapd.conf,
-/etc/cyrus.conf and /etc/default/cyrus22.
-
-Depending on your SASL configuration, you may also need to modify
-/etc/pam.d/{imap,pop,sieve,lmtp} and other SASL configuration files.
-
-Do not forget to edit /etc/imapd.conf to e.g. set the "admins: cyrus" line (if
-you use "cyrus" as the name for the administrator).
Deleted: trunk/kolab-cyrus-imapd/debian/watch
===================================================================
--- trunk/kolab-cyrus-imapd/debian/watch 2006-01-23 13:34:49 UTC (rev 183)
+++ trunk/kolab-cyrus-imapd/debian/watch 2006-01-23 13:41:00 UTC (rev 184)
@@ -1,2 +0,0 @@
-version=2
-ftp://ftp.andrew.cmu.edu/pub/cyrus-mail/cyrus-imapd-(2\.2\..*).tar.(?:gz|bz2)
More information about the pkg-kolab-devel
mailing list