Mathias Koerber schrieb am Tue, Apr 09, 2002 at 02:20:18PM +0800:
Hi all,
I am trying to install cyrus-imapd on my RH7.2 system. As there don't seem
to
be any RPMs for this, I downloaded
db-4.0.14
cyrus-sasl-2.1.2
cyrus-imapd-2.1.3
[...]
OCNS Consulting schrieb am Tue, Apr 02, 2002 at 09:39:28AM -0500:
I have Cyrus IMAP 2.1.3 + SASLV2 2.1.2 deployed and clients
authenticate via saslauthd with auth mechanism PAM which in
turn looks into /etc/pam.d/imap utilizing module pam_ldap-140
to check an LDAP repository (OpenLDAP
Where would you find this patch?
Tony
At 11:00 PM 04/09/2002 -0700, you wrote:
Russell schrieb am Mon, Apr 08, 2002 at 05:29:56PM +0100:
Ok, after much hunting finally discovered its not implemented in
2.0.16. Ooops.
There exists a patch to have it in 2.0.16.
Birger
Whenever I leave cyradm with the quit command it segfaults. From the
stacktrace alone, I suspect a double free in IMAP.so from the perl
module. Stacktrace below.
PS. someone really should update the INSTALL doc to mention changing the
permissions on the /etc/sasldb2 file to 660 and 'mail'
At 10:17 PM -0700 4/9/02, Anthony Brock wrote:
How are you dealing with groups? I am interested in having Cyrus get
it's passwords from sasl, but am not certain how to implement
groups. Specifically, I am using sasl against MIT Kerberos, which
does not appears to have group support. So how do
At 11:43 PM 04/09/2002 -0700, you wrote:
I haven't needed to. I maintain listserves for group delivery,
generally. If I'm hearing you correctly, though, it sounds like
something the MTA would do, rather than Cyrus.
I wasn't speaking of group delivery. More specifically, I am looking for
ACL
Anthony Brock schrieb am Tue, Apr 09, 2002 at 11:19:28PM -0700:
Where would you find this patch?
Mmmh, maybe my post was a littly fast - I was sure I saw it flying around
somewhere. However, you may begin with
http://www.surf.org.uk/downloads/HIERSEP-r2.patch
but that seems to apply to
At 7:52 AM +0200 4/10/02, Birger Toedtmann wrote:
But why not storing *authentication* information (i.e. passwords) in
LDAP as well so you don't have to maintain two userbases (one authE
in SASLs sasldb and one authO in LDAP)?
Because in theory, Directories are better suited for authorization,
Michael Bartosh schrieb am Wed, Apr 10, 2002 at 12:56:31AM -0600:
At 7:52 AM +0200 4/10/02, Birger Toedtmann wrote:
But why not storing *authentication* information (i.e. passwords) in
LDAP as well so you don't have to maintain two userbases (one authE
in SASLs sasldb and one authO in LDAP)?
I haven't seen a definitive howto here or elsewhere for building
2.0.16 on Mac OS X, so I thought I'd post this for the archives.
I'm using 2.0.16 since the project I'm working on needs OpenLDAP,
which doesn't yet support sasl 2.x.
I used fink (a package manager, for those of you not familiar
At 9:25 AM +0200 4/10/02, Birger Toedtmann wrote:
SASL is a lib for
faciliating authentication mechanisms,
not directly for
storing authentication credentials.
True, although it can store secrets in sasldb, which is what I tend
to use for a lot of projects (most organizations don't
On Wed, 2002-04-10 at 07:59, [EMAIL PROTECTED] wrote:
Anthony Brock schrieb am Tue, Apr 09, 2002 at 11:19:28PM -0700:
Where would you find this patch?
Mmmh, maybe my post was a littly fast - I was sure I saw it flying around
somewhere. However, you may begin with
On 10/04/02 13:48 +0800, Mathias Koerber wrote:
I'm trying to build Cyrus-IMAP on RedHat 7.2.
It seems that Cyrus by default installs its perl libs under
/usr/local/lib/...
Pass the -I flag to the perl script.
perl -I /usr/local/lib/ -MCyrus::IMAP -e shell
Devdas Bhagat
I just installed SASL-2.1.2 and IMAPD-2.1.3 from the source RPMS which
were mentioned here yesterday on my RH-7.2 system..
(I had to modify the IMAPD SPEC file somewhat to avoid configure
complaining about missing des libraries (where can I get those??)
# cd /usr/src/redhat/SRPMS
David Wright schrieb am Wed, Apr 10, 2002 at 01:13:37AM -0700:
Since there is such as SASL love-fest going on here, allow me to chime
in with my dissenting viewpoint. SASL adds nothing but an annoying
dependency to LDAP. No, I take that back, it also adds a security hole.
Michael Bartosh wrote:
At 7:52 AM +0200 4/10/02, Birger Toedtmann wrote:
In practice, most LDAP implementations don't have great authentication
mechanisms without sasl. You can always use TLS, and probably should,
anyway, but that's not the point. Keeping hashed password in the
This means the exaxt line in /etc/postfix/master.cf looks like this?
cyrus unix - n n - - pipe
flags=R -r ${sender} user=cyrus argv=/usr/cyrus/bin/deliver -e -m
${extension} ${user}
cyrus unix - n n - - pipe
I read this as:
cyrus unix - n n - - pipe
flags= user=cyrus argv=/usr/cyrus/bin/deliver -e -m -r ${sender}
${extension} ${user}
but I haven't actually tried it...
Luc de Louw wrote:
On 10 Apr 2002, Hein Roehrig wrote:
The following message is a
On 10 Apr 2002, Hein Roehrig wrote:
This means the exaxt line in /etc/postfix/master.cf looks like this?
cyrus unix - n n - - pipe
flags=R -r ${sender} user=cyrus argv=/usr/cyrus/bin/deliver -e -m
${extension} ${user}
cyrus unix - n
Luc de Louw schrieb am Wed, Apr 10, 2002 at 02:41:39PM +0200:
On 10 Apr 2002, Hein Roehrig wrote:
The following message is a courtesy copy of an article
that has been posted to comp.mail.imap as well.
Hein Roehrig [EMAIL PROTECTED] writes in comp.mail.imap:
I also get bitten by
On Wed, 10 Apr 2002, Birger Toedtmann wrote:
snip
This means the exaxt line in /etc/postfix/master.cf looks like this?
cyrus unix - n n - - pipe
flags=R -r ${sender} user=cyrus argv=/usr/cyrus/bin/deliver -e -m
${extension} ${user}
No, read the
oops...I should pay more attention to where I paste stuff...see Birger's
response.
Galen Johnson wrote:
I read this as:
cyrus unix - n n - - pipe
flags= user=cyrus argv=/usr/cyrus/bin/deliver -e -m -r ${sender}
${extension} ${user}
but I haven't
Hello all,
It seems as though INBOX just drops my connection to it without warning.
Background:
I upgraded from 1.6x IMAP to 2.1.2 and now INBOX is not happy with me.
It just drops my connection to it without warning... no autologout or anything
just drops it.
Any insight? Where there
This message took so long to appear, I was hoping it would not :)
On Mon, 08 Apr 2002, Henrique de Moraes Holschuh wrote:
Right now, in master/README (CVS head), the notifyd entry reads:
# notify cmd=notifyd listen=/notify proto=udp prefork=1
Is that correct? proto=udp with a UNIX
On Wed, 10 Apr 2002, David Wright wrote:
Since there is such as SASL love-fest going on here, allow me to chime
in with my dissenting viewpoint. SASL adds nothing but an annoying
dependency to LDAP. No, I take that back, it also adds a security hole.
SASL does not in any way force the
form). That means if anyone ever gets access to your sasldb, you are
hosed. Not true for an LDAP database, stores passwords in hashed form.
There is no requirement in SASL that says that passwords must be stored in
cleartext. Yes, it is true that libsasl's sasldb does so, however this
On 10 Apr 2002, simon wrote:
I dont see how this would work ? An auxprop plugin gets a username/
realm and a list of properties to return ? Are you saying it should
return the password encrypted and then use a patch like someone did
a couple of weeks ago. Or is there some other way for an
On 10 Apr 2002, simon wrote:
I dont see how this would work ? An auxprop plugin gets a username/
realm and a list of properties to return ? Are you saying it should
return the password encrypted and then use a patch like someone did
a couple of weeks ago. Or is there some other way for an
O
Most of the mechanisms that can take plaintext passwords can also take the
hashes, the problem is that the type of hash they need varies based on
mechanism.
This is, by the way, how the database conversion works.
So, any auxprop plugin that can return either a hash of the correct
While we're on the subject of SASL and authorization/authentication, if
Cyrus IMAP has abstracted authentication through SASL, why is the group ACL
still handled locally (in Cyrus) via UNIX groups or Kerberos?
I would really like to base group ACL's on the same scheme that
authentication is
On 10 Apr 2002, simon wrote:
userPassword and cmusaslsecret(what ever) .
So for all those people who might want to use this they just need
to set a property in ldap or mysql of cmusaslsecret(MECHNAME) (in case
of mysql you %p the select statement to make sure it gets the correct
thing).
On Wed, 10 Apr 2002, Igor Brezac wrote:
Auxprop has to return a clear text password unless you make neccessary
changes to lib/checkpw.c.
I don't agree, auxprop_verify_password() will take either a userPassword
(plaintext) or a cmusaslsecretPLAIN.
It would be nicer if auxprop would simply
Hi folks.
I am currently testing a postfix/cyrus-2.1.3 combination to find the
best installation option for a 50 mailbox system.
I am experiencing heavy i/o from the seen-db files.
Although I can split the i/o from mailboxes using paritions to
different disks, all the seen-db's go to one
On Wed, 10 Apr 2002, Rob Siemborski wrote:
On Wed, 10 Apr 2002, Igor Brezac wrote:
Auxprop has to return a clear text password unless you make neccessary
changes to lib/checkpw.c.
I don't agree, auxprop_verify_password() will take either a userPassword
(plaintext) or a
From: Tim Pushor [EMAIL PROTECTED]
Date: Wed, 10 Apr 2002 10:35:39 -0600
While we're on the subject of SASL and authorization/authentication, if
Cyrus IMAP has abstracted authentication through SASL, why is the group ACL
still handled locally (in Cyrus) via UNIX groups or
On Wed, 2002-04-10 at 21:59, Dustin Puryear wrote:
Any help on this one? We are quite stumped. At this point our only other
option is to drop Cyrus, which we'd rather not do.
What is the quota of the users ???
--
Simon
Hi,
What is the correct way to shutdown cyrus imap service? I'm starting
with '/usr/cyrus/bin/master ' and shutdown using 'pkill master'. Is
this correct.
Is there a more graceful way to start/stop cyrus?
--Kervin
--
http://linuxquestions.org/ - Ask linux questions, give linux help.
I just installed SASL-2.1.2 and IMAPD-2.1.3 from the source RPMS which
were mentioned here yesterday on my RH-7.2 system..
(I had to modify the IMAPD SPEC file somewhat to avoid configure
complaining about missing des libraries (where can I get those??)
# cd /usr/src/redhat/SRPMS
I have only problems getting IMAPD-2.1.3 to work on my RH7.2 system.
I removed all prior instances I had compiled and totally re-made
both SASLv2 (2.1.2) and IMAPD 2.1.3 (from the source RPMS announced
here a few days ago, with the single modification that I configure
cyrus-imapd with
Mathias Koerber schrieb am Thu, Apr 11, 2002 at 12:35:46PM +0800:
I have only problems getting IMAPD-2.1.3 to work on my RH7.2 system.
I removed all prior instances I had compiled and totally re-made
both SASLv2 (2.1.2) and IMAPD 2.1.3 (from the source RPMS announced
[...]
Hi,
I suggest you take my RPMs at http://home.teleport.ch/simix/ as a
starting point. They should build and run out of the box, using PAM for
auth. It is easier to upgrade/modify a running system than to get it
work for the first time.
-Simon
Mathias Koerber schrieb:
I just installed
42 matches
Mail list logo
