Re: Sourceforge (was Re: Cyrus documentation)

2001-08-09 Thread Amos Gouaux
> On Fri, 10 Aug 2001 12:49:11 +1000, > Jeremy Howard <[EMAIL PROTECTED]> (jh) writes: jh> I think it would add lots. Not just for a documentation project, but for the jh> whole Cyrus project. It would make it more of a community project rather jh> than a CMU project, which means more peo

Re: Sourceforge (was Re: Cyrus documentation)

2001-08-09 Thread Rob Siemborski
On Fri, 10 Aug 2001, Jeremy Howard wrote: > If you moved across to SourceForge you get web-based CVS browsing (really > handy for developers getting involved the first time) and web-based list > archives that work (the current horde-based archive is slow as molasses, and > the IMAP-based archive

Sourceforge (was Re: Cyrus documentation)

2001-08-09 Thread Jeremy Howard
Walter Wong wrote: > Part of the problem is that people are distributing binaries without > the source code and all the docs are in the doc/ subdir of the source > distribution. > Partly. And partly the docs don't provide a great beginners overview of everything you need to know, but are more usef

sendmail configuration for Cyrus LMTP delivery

2001-08-09 Thread mills
Since this information hasn't shown up yet in recent Cyrus or sendmail distributions, I decided to make it available on a web site. feature/local_cyrus.m4 This is a sendmail feature file for a site that uses the Cyrus LMTP server exclusively for local mail delivery. It re

Re: Cyrus documentation

2001-08-09 Thread Ken Murchison
Jeremy Howard wrote: > > Tarjei Huse wrote: > > Would it be possible to host a cyrus-(IMAP/SASL) documetnation page? I > feel > > a great need for a Cyrus faq/howto page. The current doc's are not exactly > > in a perfect state. > > > > Also, they could bennefit a lot from dynamic updates. > >

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap + cyrus-imapd-2.0.x)

2001-08-09 Thread Walter Wong
Devdas Bhagat <[EMAIL PROTECTED]> writes: > > The current implementation of SASL does not support remote > connectivity. I believe the basic problem is that you don't see where SASL fits in. Your comment is much like saying that you can't use an orange to chew gum. > What most people are looki

Re: Cyrus documentation

2001-08-09 Thread Walter Wong
re: doc updates. Part of the problem is that people are distributing binaries without the source code and all the docs are in the doc/ subdir of the source distribution. I'm not sure what Sourceforge would add for us. I believe we've applied most of the documentation changes sent our way. We jus

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap +cyrus-imapd-2.0.x)

2001-08-09 Thread David Lang
note there are (or were) limits on the size of usernames and passwords that pwcheck can deal with. David Lang On Fri, 10 Aug 2001, Jeremy Howard wrote: > Date: Fri, 10 Aug 2001 05:59:54 +1000 > From: Jeremy Howard <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], Marco Colombo <[EMAIL PROTECTED]> >

Re: cyradm and perl problem

2001-08-09 Thread Toni Andjelkovic
chirs charter wrote on Thu, Aug 09 2001 (11:46:49 -0700): > Can't load > '/usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris/auto/Cyrus/IMAP/IMAP > .so' for module Cyrus::IMAP: ld.so.1: perl: fatal: > libdb-3.2.so: open failed: No s > uch file or directory at > /usr/local/lib/perl5/5.6.0/sun4-solar

Re: Script admin problems

2001-08-09 Thread Jeremy Howard
Jules Agee wrote: > How strange. if I remember correctly, the IMAP::Admin module does > everything through an IMAP connection using standard RFC IMAP > commands, just like cyradm does. So if you're using the same login and > password with cyradm as you're using with your perl script, and cyradm

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap + cyrus-imapd-2.0.x)

2001-08-09 Thread Jeremy Howard
Devdas Bhagat wrote: > The problem with the current design of imapd is that it assumes that > SASL will be available locally in some form, ignoring that it may not > be available there. > Do the pwcheck daemons provide support for this? Yes. The pwcheck 'API' is this simple: - SASL sends usernam

Re: cyradm and perl problem

2001-08-09 Thread Jeremy Howard
chirs charter wrote: > I just installed Cyrus 2.0.16 on Solaris 8. When I go > to run run: > > /usr/local/bin/cyradm -user cyrus localhost > > I get the following errors: > > Ccatfish# /usr/local/bin/cyradm -user cyrus localhost > Can't load > '/usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris/aut

Re: saslauthd (was Re: SASL re-entrancy crisis)

2001-08-09 Thread Ken Murchison
Jeremy Howard wrote: > > Ken Murchison wrote: > > "Kevin J. Menard, Jr." wrote: > > > > Hmm . . . I honestly haven't checked this out yet. I'll have to take > > > a look at it. > > > > If you're serious about this, you should really check out cmu-sasl > > v1.5.27 or the latest CVS and use sas

Re: Cyrus documentation

2001-08-09 Thread Jeremy Howard
Tarjei Huse wrote: > Would it be possible to host a cyrus-(IMAP/SASL) documetnation page? I feel > a great need for a Cyrus faq/howto page. The current doc's are not exactly > in a perfect state. > > Also, they could bennefit a lot from dynamic updates. > Agreed! > Does anyone have a suggestion o

saslauthd (was Re: SASL re-entrancy crisis)

2001-08-09 Thread Jeremy Howard
Ken Murchison wrote: > "Kevin J. Menard, Jr." wrote: > > Hmm . . . I honestly haven't checked this out yet. I'll have to take > > a look at it. > > If you're serious about this, you should really check out cmu-sasl > v1.5.27 or the latest CVS and use saslauthd. This is the replacement > for pwc

Re: Script admin problems

2001-08-09 Thread Jules Agee
How strange. if I remember correctly, the IMAP::Admin module does everything through an IMAP connection using standard RFC IMAP commands, just like cyradm does. So if you're using the same login and password with cyradm as you're using with your perl script, and cyradm works, the problem would

Re: Script admin problems

2001-08-09 Thread Alain Turbide
Since IMAP::Admin requires the LOGIN auth method to be compiled into SASL, that might be the problem. You need LOGIN auth for that. The best check would be to telnet to the imap port as suggested by Jules. Alain - Original Message - From: "Jules Agee" <[EMAIL PROTECTED]> To: "Warren Flem

cyradm and perl problem

2001-08-09 Thread chirs charter
Hello, I just installed Cyrus 2.0.16 on Solaris 8. When I go to run run: /usr/local/bin/cyradm -user cyrus localhost I get the following errors: Ccatfish# /usr/local/bin/cyradm -user cyrus localhost Can't load '/usr/local/lib/perl5/site_perl/5.6.0/sun4-solaris/auto/Cyrus/IMAP/IMAP .so' for modu

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap + cyrus-imapd-2.0.x)

2001-08-09 Thread Jules Agee
Have you considered using stunnel? It's very easy to set up. I'm using it with pam_ldap and cyrus. [EMAIL PROTECTED] wrote: >>BTW, I noticed an LDAP pwcheck daemon here: >> http://www.linc-dev.com/auth.html >> > > I looked at this daemon (pwcheck_ldap). It does not do secure (ssl) > ldap. Th

Re: SASL and SHADOW

2001-08-09 Thread Marco Colombo
On Thu, 9 Aug 2001, Tyrone Vaughn wrote: > I did search the archives and the closest solution I can find is to > abandon checking the shadow file via PAM and run the program "pwcheck" > as the root user -- something I don't want to do. > > If you know the answer, would you please forward it on to

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap +cyrus-imapd-2.0.x)

2001-08-09 Thread Julio Sánchez Fernández
Marco Colombo wrote: > The fact I can write a little client/server application that supports > many different mechs, from weaker ones to stronger ones, *without* > almost any knowledge of them is great. Sorry, I think my point was lost in the rest of the drivel. The point is that the protocol

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap +cyrus-imapd-2.0.x)

2001-08-09 Thread Marco Colombo
On 9 Aug 2001, Julio Sanchez Fernandez wrote: > Marco Colombo <[EMAIL PROTECTED]> writes: > > > because that's the right place to use SASL. Despite of PAM not being > > a replacement for SASL, of course. I think that OpenLDAP requirement > > for a modular, configurable network security layer (SAS

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap +cyrus-imapd-2.0.x)

2001-08-09 Thread Marco Colombo
On Thu, 9 Aug 2001, Devdas Bhagat wrote: > On Thu, 09 Aug 2001, Marco Colombo spewed into the ether: > > > BTW, if really OpenLDAP 2 is build on SASL, you can't really get rid > > of it. You'll have an IMAPD -> LDAP -> SASL (for authentication of > > the LDAP client to the LDAP server) solution.

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap + cyrus-imapd-2.0.x)

2001-08-09 Thread Devdas Bhagat
On Thu, 09 Aug 2001, Marco Colombo spewed into the ether: > BTW, if really OpenLDAP 2 is build on SASL, you can't really get rid > of it. You'll have an IMAPD -> LDAP -> SASL (for authentication of > the LDAP client to the LDAP server) solution. This is what I'm asking for. Quite a few people are

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap +cyrus-imapd-2.0.x)

2001-08-09 Thread Marco Colombo
On Thu, 9 Aug 2001, Devdas Bhagat wrote: > On Thu, 09 Aug 2001, Marco Colombo spewed into the ether: > > > This is a completely different issue. David Wright is proposing to > > *remove* SASL from Cyrus IMAPd in favor of a PAM-only solution, and > > I was answering to him. I don't want SASL to b

Re: SASL and SHADOW

2001-08-09 Thread Rob Tanner
PAM has no special privleges. PAM library call run with the same privilege level as the calling program. Therefore, not even the user 'cyrus' can authenticate without permissions set to 444. With that said and your obvious experience to the contrary, are you talking about cyrus authenticati

Re: SASL and SHADOW

2001-08-09 Thread Tyrone Vaughn
I did search the archives and the closest solution I can find is to abandon checking the shadow file via PAM and run the program "pwcheck" as the root user -- something I don't want to do. If you know the answer, would you please forward it on to me? Thanks. Tyrone Amos Gouaux wrote: > >

Re: Script admin problems

2001-08-09 Thread Darron Froese
On 8/9/01 2:34 AM, "Warren Flemmer" <[EMAIL PROTECTED]> wrote: > Cyrus is working well with postfix using pam (mysql) > for authentication. I now need to setup automated > scripts to create mailboxes, set quotas etc. I have tried > three different approaches each of which ending without > success

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap + cyrus-imapd-2.0.x)

2001-08-09 Thread Devdas Bhagat
On Thu, 09 Aug 2001, Marco Colombo spewed into the ether: > This is a completely different issue. David Wright is proposing to > *remove* SASL from Cyrus IMAPd in favor of a PAM-only solution, and > I was answering to him. I don't want SASL to be removed from IMAPd, Nor do I. SASL does fine for w

Re: SASL and SHADOW

2001-08-09 Thread Amos Gouaux
> On Thu, 09 Aug 2001 08:40:58 -0500, > Tyrone Vaughn <[EMAIL PROTECTED]> (tv) writes: tv> I have done six implementations of Cyrus (2.0.11 - 2.0.16) and in each tv> one I have the same problem. No user, other than cyrus, can tv> authenticate unless I make the shadow file 444 verses it o

SASL and SHADOW

2001-08-09 Thread Tyrone Vaughn
I have done six implementations of Cyrus (2.0.11 - 2.0.16) and in each one I have the same problem. No user, other than cyrus, can authenticate unless I make the shadow file 444 verses it original 400. Pertinent information: OS's -- RH 6.2, 7.0 & Mandrake 7.2, 8.0 Cyrus -- 2.0.11 - 2.0.16 Sasl -

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap + cyrus-imapd-2.0.x)

2001-08-09 Thread Julio Sanchez Fernandez
Marco Colombo <[EMAIL PROTECTED]> writes: > because that's the right place to use SASL. Despite of PAM not being > a replacement for SASL, of course. I think that OpenLDAP requirement > for a modular, configurable network security layer (SASL itself) is > weaker than the IMAPd one. So IFF you nee

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap +cyrus-imapd-2.0.x)

2001-08-09 Thread Marco Colombo
On Wed, 8 Aug 2001, Devdas Bhagat wrote: > On Wed, 08 Aug 2001, Marco Colombo spewed into the ether: > > > And BTW, why don't you remove SASL from OpenLDAP, instead? You're just > > asking CMU people to remove SASL from their Cyrus IMAPD so that > > OpenLDAP 2 can use it to implement the encrypt

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap + cyrus-imapd-2.0.x)

2001-08-09 Thread Ken Murchison
"Kevin J. Menard, Jr." wrote: > > Hey Jeremy, > > Thursday, August 09, 2001, 1:14:51 AM, you wrote: > > JH> Kevin J. Menard, Jr. wrote: > >> I still say add all this to SASL. That's what it's there for anyway, so > JH> you > >> don't need to hack imapd.c or pop3d.c everytime you want to add

Cyrus documentation

2001-08-09 Thread Tarjei Huse
Hi All. Would it be possible to host a cyrus-(IMAP/SASL) documetnation page? I feel a great need for a Cyrus faq/howto page. The current doc's are not exactly in a perfect state. Also, they could bennefit a lot from dynamic updates. Does anyone have a suggestion on where and how this could

Re: Re[2]: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap + cyrus-imapd-2.0.x)

2001-08-09 Thread GOMBAS Gabor
On Thu, Aug 09, 2001 at 03:14:51PM +1000, Jeremy Howard wrote: > You mean like pwcheck, which lets you dynamically add auth methods to SASL? ? You can dynamically add auth methods to SASL without using pwcheck. Gabor -- Gabor Gombas Eotvos Lorand Universi

Re: SASL re-entrancy crisis (was: OpenLDAP 2.0.x + pam_ldap + cyrus-imapd-2.0.x)

2001-08-09 Thread GOMBAS Gabor
On Wed, Aug 08, 2001 at 04:12:43PM -0700, [EMAIL PROTECTED] wrote: > Aehm! Please persuse, at your leasure, the man page > http://sunsite.queensu.ca/cgi-bin/man-cgi?pam_krb5+5 > or the rpm summary > http://www.redhat.com/swr/i386/pam_krb5-1-7.i386.html > for pam_krb5, and feel free to downloa

Re: Linux Redhat 7.1 blues

2001-08-09 Thread Devdas Bhagat
On Thu, 09 Aug 2001, Tarjei Huse spewed into the ether: > > Can't locate Cyrus/IMAP/Shell.pm in @INC and it goes on to list what > > @INC includes. I think it all about this crap with redhat where it > > doesn't put things in /usr/local/whatever and all these proggys expect > > stuff there.. *si

Re: Script admin problems

2001-08-09 Thread Warren Flemmer
With the package IMAP-Admin-1.4.3 running test.pl as follows: [root@mail121 IMAP-Admin-1.4.3]# perl test.pl 1..14 ok 1 Remaining tests require a connection an imap server Please enter the server and the admin user and password at the prompts Enter server: localhost Enter login: adm Enter password

Re: Script admin problems

2001-08-09 Thread Matt Prigge
> Attempt two: Using module IMAP::Admin from > IMAP-Admin-1.4.3 The test gives me the following > error: > IMAP::Admin [ initialize ]: try NO Login failed: authentication failure > Again getting me past this error should allow me > to complete the task. IMAP::Admin has worked very well for me. Ca

Re: Linux Redhat 7.1 blues

2001-08-09 Thread Tarjei Huse
Hia, > The next problem I got to is it (sieve I think) wanted to find > bison.simple in /usr/local/share but it was in /usr/lib. So I make a > symbolink /usr/local/share to /usr/lib - is this a bad idea? Wouldn't think so, but me no expert. > Anyway, it got further and now I get the following

Script admin problems

2001-08-09 Thread Warren Flemmer
Greetings Cyrus is working well with postfix using pam (mysql) for authentication. I now need to setup automated scripts to create mailboxes, set quotas etc. I have tried three different approaches each of which ending without successes so I now pass it to the group. I should point out that cyra

Too much is logged! (or, how do I quell logging?)

2001-08-09 Thread Björn Törnqvist
Hi! I've finally been able to make postfix -> cyrus work (it was an error in the configuration of postfix, thanks) and I now have this question: I have coded a pwcheck program that authenticates with some servers here at work - as far as cyrus is concerned this is a plaintext login, and hence, e