Re: Cyrus IMAPd 2.3.8 Released

2007-02-09 Thread Simon Matter
 URLs for this release:
 ftp://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.8.tar.gz
 or
 http://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.8.tar.gz

 Questions and comments can be directed to
 info-cyrus@lists.andrew.cmu.edu (public list), or
 [EMAIL PROTECTED]

Attached patch adds the missing cyr_dbtool(8) manpage.

Simondiff -Naur cyrus-imapd-2.3.8.orig/man/cyr_dbtool.8 cyrus-imapd-2.3.8/man/cyr_dbtool.8
--- cyrus-imapd-2.3.8.orig/man/cyr_dbtool.8	1970-01-01 01:00:00.0 +0100
+++ cyrus-imapd-2.3.8/man/cyr_dbtool.8	2007-02-09 08:46:01.0 +0100
@@ -0,0 +1,91 @@
+.\ -*- nroff -*-
+.TH CYR_DBTOOL 8 Project Cyrus CMU
+.\ 
+.\ Copyright (c) 1998-2007 Carnegie Mellon University.  All rights reserved.
+.\
+.\ Redistribution and use in source and binary forms, with or without
+.\ modification, are permitted provided that the following conditions
+.\ are met:
+.\
+.\ 1. Redistributions of source code must retain the above copyright
+.\notice, this list of conditions and the following disclaimer. 
+.\
+.\ 2. Redistributions in binary form must reproduce the above copyright
+.\notice, this list of conditions and the following disclaimer in
+.\the documentation and/or other materials provided with the
+.\distribution.
+.\
+.\ 3. The name Carnegie Mellon University must not be used to
+.\endorse or promote products derived from this software without
+.\prior written permission. For permission or any other legal
+.\details, please contact  
+.\  Office of Technology Transfer
+.\  Carnegie Mellon University
+.\  5000 Forbes Avenue
+.\  Pittsburgh, PA  15213-3890
+.\  (412) 268-4387, fax: (412) 268-7395
+.\  [EMAIL PROTECTED]
+.\
+.\ 4. Redistributions of any form whatsoever must retain the following
+.\acknowledgment:
+.\This product includes software developed by Computing Services
+.\ at Carnegie Mellon University (http://www.cmu.edu/computing/).
+.\
+.\ CARNEGIE MELLON UNIVERSITY DISCLAIMS ALL WARRANTIES WITH REGARD TO
+.\ THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
+.\ AND FITNESS, IN NO EVENT SHALL CARNEGIE MELLON UNIVERSITY BE LIABLE
+.\ FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
+.\ WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN
+.\ AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING
+.\ OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
+.\ 
+.\ $Id: cyr_dbtool.8,v 1.1 2007/02/09 17:41:35 simix Exp $
+.SH NAME
+cyr_dbtool \- manage Cyrus databases
+.SH SYNOPSIS
+.B cyr_dbtool
+[
+.B \-C
+.I config-file
+]
+old db old db backend action
+[
+key
+]
+[
+value
+]
+.SH DESCRIPTION
+.I cyr_dbtool
+is used to manage a cyrusdb file. The usable actions are:
+.PP
+.BI show  [prefix]
+.PP
+.BI get  key
+.PP
+.BI set  key value
+.PP
+.BI delete  key
+.PP
+You may omit key or key/value and specify one per line on stdin. Keys are
+terminated by tab or newline, values are terminated by newline.
+.PP
+Running without any options will list the available database backends and
+usable actions.
+.PP
+.I cyr_dbtool
+reads any applicable configuration options out of the
+.IR imapd.conf (5)
+file unless specified otherwise by \fB-C\fR.
+note that the file locations are NOT read out of the configuration file,
+and must be supplied on the command line.
+.SH OPTIONS
+.TP
+.BI \-C  config-file
+Read configuration options from \fIconfig-file\fR.
+.SH FILES
+.TP
+.B /etc/imapd.conf
+.SH SEE ALSO
+.PP
+\fBimapd.conf(5)\fR
diff -Naur cyrus-imapd-2.3.8.orig/man/Makefile.in cyrus-imapd-2.3.8/man/Makefile.in
--- cyrus-imapd-2.3.8.orig/man/Makefile.in	2006-11-30 18:11:23.0 +0100
+++ cyrus-imapd-2.3.8/man/Makefile.in	2007-02-09 08:49:25.0 +0100
@@ -68,7 +68,7 @@
 	$(srcdir)/notifyd.8 $(srcdir)/chk_cyrus.8 $(srcdir)/mbexamine.8 \
 	$(srcdir)/nntpd.8 $(srcdir)/fetchnews.8 $(srcdir)/smmapd.8 \
 	$(srcdir)/sync_client.8 $(srcdir)/sync_server.8 $(srcdir)/sync_reset.8 \
-	$(srcdir)/unexpunge.8 $(srcdir)/make_md5.8
+	$(srcdir)/unexpunge.8 $(srcdir)/make_md5.8 $(srcdir)/cyr_dbtool.8
 
 all: $(MAN1) $(MAN3) $(MAN5) $(MAN8)
 
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus IMAPd 2.3.8 Released (UPDATED)

2007-02-09 Thread Simon Matter
 URLs for this release:
 ftp://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.8.tar.gz
 or
 http://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.8.tar.gz

 Questions and comments can be directed to
 info-cyrus@lists.andrew.cmu.edu (public list), or
 [EMAIL PROTECTED]

Sorry for posting again, this one should be complete.

Attached patch adds the missing cyr_dbtool(8) manpage.

Simon


cyrus-imapd-2.3.8-cyr_dbtool_8.patch.gz
Description: GNU Zip compressed data

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Cyrus IMAPd 2.3.8 Released

2007-02-09 Thread Muenz, Michael

Hi,

Ken Murchison schrieb:

URLs for this release:
ftp://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.8.tar.gz
or
http://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.8.tar.gz

Questions and comments can be directed to
info-cyrus@lists.andrew.cmu.edu (public list), or 
[EMAIL PROTECTED]


thanks for this release! Is there a need to update if 2.3.7
just works fine for me (security fixes)?

Thanks,
Michael


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Working unified murder configs?

2007-02-09 Thread Mirosław Jaworski
Anyone care to share working unified murder configs?

I am also sure that many would appreciate separate unified murder pages
in cyrus' wiki.

-- 
Mirosław Psyborg Jaworski
GCS/IT d- s+:+ a C++$ UBI$ P+++$ L- E--- W++(+++)$ N++ o+ K- w-- O-
M- V- PS+ PE++ Y+ PGP t 5? X+ R++ !tv b++(+++) DI++ D+ G e* h++ r+++ y?
Voltaire: It is dangerous to be right when the government is wrong.


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Re: Cyrus IMAPd 2.3.8 Released (UPDATED)

2007-02-09 Thread Ken Murchison

Simon Matter wrote:

URLs for this release:
ftp://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.8.tar.gz
or
http://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.8.tar.gz

Questions and comments can be directed to
info-cyrus@lists.andrew.cmu.edu (public list), or
[EMAIL PROTECTED]


Sorry for posting again, this one should be complete.

Attached patch adds the missing cyr_dbtool(8) manpage.


Applied to CVS.


--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


How to copy shared folders from one cyrus to another?

2007-02-09 Thread Tuomas Toropainen

Hello

I have succesfully copied users' mail folders with imapsync. But How can 
I copy shared folders? The problem seems to be that imapsync always adds 
INBOX. to the destination folder name, like this:


 From [shared.vitsit] Parse 1 
 To   [INBOX.shared.vitsit] Parse 1 
 Verifying [shared.vitsit] - [INBOX.shared.vitsit] 

I have tried lots of different options, like this:

imapsync --host1 source.imap.server --ssl1 --authuser1 cyrus --user1 
testi2 --authmech1 PLAIN --passfile1 cyrus-salasana.txt --host2 
localhost --ssl2 --authuser2 cyrus --user2 jorma --authmech2 PLAIN 
--passfile2 cyrus-salasana.txt --syncinternaldates --folder 
'shared.vitsit' --prefix1 'INBOX.'


Removing --prefix1 'INBOX.' makes no difference.

Or is there another tool which suits here better?

Thank you :)

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Re: Working unified murder configs?

2007-02-09 Thread Shawn Nock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Mirosław Jaworski wrote:
 Anyone care to share working unified murder configs?
 
 I am also sure that many would appreciate separate unified murder pages
 in cyrus' wiki.
 

That'd be great for us as well (both working configs and wiki pages).
We're trying to migrate our testing setup from 2.3.3 - 2.3.7 and
unified murder documentation seems non-existent.

Thanks,
Shawn

- --
Shawn Nock (OpenPGP: 0xB64200E1)
Unix Systems Group; CCIT
University of Arizona
nock at email.arizona.edu
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.3 (GNU/Linux)

iD8DBQFFzIvfbbRzLz6id34RAgQhAJ4hDOLjw1oYD4NthlIe37Vi0hpfsQCeJQ/L
/zNzadfY4dwCpCUsrJ1HEUE=
=SQYQ
-END PGP SIGNATURE-

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Re: Thunderbird + Kerberos 5 + Cyrus SASL-and-IMAP?

2007-02-09 Thread Jeff Blaine

A little more info, in case anyone finds the time to help
me out:

I've tried everything I can imagine.

saslauthd:

saslauthd -a kerberos5 -d (with additional debug code by me!)

Feb  9 13:22:20 noodle.foo.com saslauthd[27437]:
auth_krb5: krb5_kt_read_service_key returned -1765328203
- going to fini: in k5support_verify_tgt()

I can find no information on that Kerberos error, but I
most certainly have imap/noodle.foo.com in a readable
/etc/krb5.keytab (and truss shows it being read fine).

imapd.conf:

sasl_pwcheck_method: saslauthd

Jeff Blaine wrote:

I have a healthy MIT Kerberos 1.5.2 realm and Cyrus IMAP 2.2.12
server configured (SASL 2.1.22).

I can't get Thunderbird (latest 1.5 official release) to perform
GSSAPI authentication against the Cyrus IMAP server.

I have valid Kerberos 5 credentials (for user jblaine) via Kerberos
for Windows 3.1.  I have restarted Thunderbird.

Anyone know how to do this?  This is supposed to work if I am
not mistaken.

Thunderbird states the server does not support secure authentication
(which is BS).



imtest authenticates (as jblaine) via GSSAPI fine!

C: A01 AUTHENTICATE GSSAPI YIICBblahblahblah
S: + YIGWBgkqhkblahblah
...
S: A01 OK Success (privacy protection)
Authenticated.
Security strength factor: 56

...

Feb  8 16:36:44 noodle.foo.com imap[26514]: [ID 529592 local6.notice] 
login: noodle.foo.com [192.168.168.100] jblaine GSSAPI User logged in




/etc/imapd.conf reads as follows:

configdirectory:/var/imap
defaultpartition:   default
partition-default:  /var/spool/imap
imap_admins:root cyrus
sieveusehomedir:false
autocreatequota:20
duplicate_db:   skiplist
allowplaintext: false
force_sasl_mech:GSSAPI
sasl_log_level: 4




Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Re: Thunderbird + Kerberos 5 + Cyrus SASL-and-IMAP?

2007-02-09 Thread Ben Poliakoff
* Jeff Blaine [EMAIL PROTECTED] [20070209 10:42]:
 A little more info, in case anyone finds the time to help
 me out:
 
 I've tried everything I can imagine.
 
 saslauthd:
 
 saslauthd -a kerberos5 -d (with additional debug code by me!)
 
 Feb  9 13:22:20 noodle.foo.com saslauthd[27437]:
 auth_krb5: krb5_kt_read_service_key returned -1765328203
 - going to fini: in k5support_verify_tgt()
 
 I can find no information on that Kerberos error, but I
 most certainly have imap/noodle.foo.com in a readable
 /etc/krb5.keytab (and truss shows it being read fine).
 
 imapd.conf:
 
 sasl_pwcheck_method: saslauthd
 

I'm fairly certain that saslauthd is going to be looking for a *host*
principle in the keytab (i.e. host/noodle.foo.com).  Do you have a host
principle in the same keytab file?

Of course saslauthd won't be involved at all if you're doing GSSAPI auth
with Thunderbird, saslauthd is only used for plaintext authentication.

Ben


signature.asc
Description: Digital signature

Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html

Re: Working unified murder configs?

2007-02-09 Thread Farzad FARID
Hi,

on 09.02.2007 10:40 Mirosław Jaworski said the following:
 Anyone care to share working unified murder configs?

 I am also sure that many would appreciate separate unified murder pages
 in cyrus' wiki.

   
Sure, here's a working config, deployed in a production system. Since I
haven't written a final administration manual, these informations  may
be incomplete. If they aren't sufficient, send me a mail and I'll
complete what's missing.


  Environment:

There are 3 servers (not couting the smtp relays or the LDAP servers):

* 2 imap servers: imap1  imap2
* 1 murder server: murder1

All 3 servers run *Cyrus Imapd 2.3.7*, home made, yet to become
official, Debian packages, with some patches. You can check the source
code here if you want to see what patches have been applied :
http://www.pragmatic-source.com/Cyrus-Imapd-2-3-7-for-the-Linux

*Note:* All cyrus commands must be run under the cyrus user, not root!


  SASL settings

All 3 server have SASL libraries  tools installed, and an /etc/sasldb2
authentification file.

*Note:* Take care of using *matching passwords* where necessary. For
example: the /etc/sasldb2 file on murder1 has got an
[EMAIL PROTECTED] account. The same imap1 user is defined in the
/etc/cyrus.conf file on server imap1, with the same password.


  Configuration on murder1

*Note*: I stripped some unnecessary lines, comments and white lines from
the sample config files. Don't use these configuration files as is!


SASL file /etc/sasldb2

The auth file contains these users (with a password of course):

murder1# sasldblistusers2
[EMAIL PROTECTED]: userPassword
[EMAIL PROTECTED]: userPassword
[EMAIL PROTECTED]: userPassword


File /etc/cyrus.conf:

START {
recover cmd=/usr/sbin/ctl_cyrusdb -r
}
SERVICES {
# (mupdate master, only one in the entire cluster)
mupdate   cmd=mupdate -m listen=3905 prefork=1
proto=tcp4
}
EVENTS {
checkpoint  cmd=/usr/sbin/ctl_cyrusdb -c period=30
}


File /etc/imapd.conf:

configdirectory: /var/lib/cyrus
defaultpartition: default
partition-default: /var/spool/cyrus/mail
servername: mydomain.com
admins: cyrus
mupdate_admins: imap1 imap2
allowplaintext: yes
sasl_pwcheck_method: auxprop
sasl_auxprop_plugin: sasldb
sasl_auto_transition: no

Nothing else is configured on murder1.


  Configuration on imap1 and imap2

Configuration is identical on these 2 servers, except from their names
(substitute imap1 with imap2 and you'll get the 2nd server's
configuration).

The IMAP servers run the saslauthd daemon, connected to an LDAP
server, but I don't document this here as it has no influence on the
murder configuration.


File /etc/services:

Add the following line to the /etc/service file.

mupdate 3905/tcp# Cyrus Mupdate


SASL file /etc/sasldb2:

# sasldblistusers2
[EMAIL PROTECTED]: userPassword
[EMAIL PROTECTED]: userPassword

postman is used along with postfix + lmtp for mail delivery. But I won't
talk about this here.


File /etc/cyrus.conf:

START {
recover cmd=/usr/sbin/ctl_cyrusdb -r
idled   cmd=idled

# this is useful on backend nodes of a Murder cluster
# it causes the backend to syncronize its mailbox list with
# the mupdate master upon startup
mupdatepush   cmd=/usr/sbin/ctl_mboxlist -m

# this is recommended if using duplicate delivery suppression
# but the expiration takes more than 5 minutes on startup!
# So I disabled this line
##delprune  cmd=/usr/sbin/cyr_expire -E 3 -X 3
# this is recommended if caching TLS sessions
tlsprunecmd=/usr/sbin/tls_prune
}
SERVICES {
# --- Normal cyrus spool, or Murder backends ---
# add or remove based on preferences
imapcmd=imapd -U 30 listen=imap prefork=10
maxchild=250 babysit=1 maxforkrate=10 proto=tcp4
imaps   cmd=imapd -s -U 30 listen=imaps
prefork=5 maxchild=250 babysit=1 maxforkrate=10 proto=tcp4

lmtpcmd=lmtpd listen=lmtp prefork=10
maxchild=60 babysit=1 maxforkrate=10 proto=tcp4
sieve   cmd=timsieved listen=sieve prefork=2
maxchild=30 proto=tcp4
notify  cmd=notifyd
listen=/var/run/cyrus/socket/notify proto=udp prefork=1

# --- Murder frontends -
# mupdate database service - must prefork at least 1
# (mupdate slaves)
mupdate   cmd=mupdate listen=3905 prefork=1 proto=tcp4
}
EVENTS {
checkpoint  cmd=/usr/sbin/ctl_cyrusdb -c period=30
delprunecmd=/usr/sbin/cyr_expire -E 3 -X 3 at=0201

Re: How to copy shared folders from one cyrus to another?

2007-02-09 Thread Farzad FARID
Hi,

on 09.02.2007 15:21 Tuomas Toropainen said the following:
 Hello

 I have succesfully copied users' mail folders with imapsync. But How
 can I copy shared folders? The problem seems to be that imapsync
 always adds INBOX. to the destination folder name, like this:

  From [shared.vitsit] Parse 1 
  To   [INBOX.shared.vitsit] Parse 1 
  Verifying [shared.vitsit] - [INBOX.shared.vitsit] 

 I have tried lots of different options, like this:

 imapsync --host1 source.imap.server --ssl1 --authuser1 cyrus --user1
 testi2 --authmech1 PLAIN --passfile1 cyrus-salasana.txt --host2
 localhost --ssl2 --authuser2 cyrus --user2 jorma --authmech2 PLAIN
 --passfile2 cyrus-salasana.txt --syncinternaldates --folder
 'shared.vitsit' --prefix1 'INBOX.'

 Removing --prefix1 'INBOX.' makes no difference.

The following sample works perfectly for me. I even used a more
complicated configuration:

* Shared prefix on server 1 is commun. (means common in french)
* Shared prefix on server 2 is shared.

I copied commun.test to shared.test. shared.test did not exist on
the destination and was created automatically.

imapsync --host1 SERVER1 --ssl1 --authmech1 LOGIN --user1 USER1 --host2
SERVER2 --ssl2 --authmech2 LOGIN --user2 USER2 --prefix1 commun.
--prefix2 shared. --folder commun.test

So the trick is to provide both source and destination shared prefixes,
and give the complete source folder path.
My imapsync version is *1.182*.

 Regards

-- 
Farzad FARID [EMAIL PROTECTED]
Architecte Open Source / Associé
Pragmatic Source - http://www.pragmatic-source.com/
Tel : +33 9 53 19 21 90 / Mob : +33 6 03 70 65 46


Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html