Re: upgrade from Cyrus 2.1.15 to cyrus 2.2.3 breaks LDAP auxprop authentication.

On Wed, 11 Feb 2004, Edward Rudd wrote: > OpenLDAP 2.1.22, LDAP AuxProp CVS release 1.1.2.3, I had tried updating > to a newer release but it broke things due to the handling of the LDAP > v4 PROXY_AUTHZ control in openldap (you directed me to the bug report > about it), Cyrus SASL 2.1.15 (2.1.1

[Fwd: Re: serious over quota problem]

The cc: didn't seem to work so here it goes. Original Message Subject: Re: serious over quota problem Date: Wed, 11 Feb 2004 11:19:57 -0800 From: Joao Pedras <[EMAIL PROTECTED]> To: David R Bosso <[EMAIL PROTECTED]> CC: [EMAIL PROTECTED] References: <[EMAIL PROTECTED]> <[E

Re: SIEVE weirdness

> A friend of mine has tried to get Cyrus 2.1.5 running on RHEL 3 and all > works except sieve. > > Doing something like 'sieveshell -u cyrus -a cyrus' prompts for the > password over and over. > > The error message I get is > Feb 5 17:09:48 agentsmith timsieved[4172]: unable to open Berkeley db >

cyrus-imapd-2.2.x and web-cyradm+pam_mysql+saslauthd?

Does web-cyradm + mysql + pam_mysql + cyrus-imapd-2.2.3-4 combination work anymore, or should I change the authentication mechanism? Any help would be greatly appreciated. Thanks Khan __ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http:

RE: upgrade from Cyrus 2.1.15 to cyrus 2.2.3 breaks LDAPauxpropauthentication.

It looks like the ldapdb plugin sent an Unbind immediately after sending the first SASL Bind request. It seems that the SASL client library didn't like the challenge it got from the slapd server. At this point it would have been helpful to enable LDAP debugging in the ldapdb plugin, but I never cod

RE: upgrade from Cyrus 2.1.15 to cyrus 2.2.3 breaks LDAP auxpropauthentication.

Here is the "nohup slapd -d 255" file. and the entries from auth.log when running "imtest -a cyrus -u cyrus -m login devel" Feb 11 20:48:13 devel slapd[2927]: auxpropfunc error -7 Feb 11 20:48:13 devel slapd[2927]: _sasl_plugin_load failed on sasl_auxprop_plug_init for plugin: ldapdb Feb 11 20:4

Re: upgrade from Cyrus 2.1.15 to cyrus 2.2.3 breaks LDAP auxprop authentication.

OpenLDAP 2.1.22, LDAP AuxProp CVS release 1.1.2.3, I had tried updating to a newer release but it broke things due to the handling of the LDAP v4 PROXY_AUTHZ control in openldap (you directed me to the bug report about it), Cyrus SASL 2.1.15 (2.1.17 causes SLAPD to crash completely). sample client

RE: upgrade from Cyrus 2.1.15 to cyrus 2.2.3 breaks LDAP auxpropauthentication.

Step one is there just before the imtest: DIGEST-MD5 client step 2.. forgot to copy it in there.. On Wed, 2004-02-11 at 19:58, Howard Chu wrote: > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Edward Rudd > > > OK I patched my OpenLDAP and recom

Re: upgrade from Cyrus 2.1.15 to cyrus 2.2.3 breaks LDAP auxprop authentication.

Hmm... Can you email me your libraries/libldap/cyrus.c? What version of openldap do you use? I use the latest ldapdb auxprop and OPENLDAP_REL_ENG_2_1 (which is 2.1.26 + some patches) Does ldapdb auxprop work with sample(client|server)? -Igor On Wed, 11 Feb 2004, Edward Rudd wrote: > OK I pat

RE: upgrade from Cyrus 2.1.15 to cyrus 2.2.3 breaks LDAP auxpropauthentication.

> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Edward Rudd > OK I patched my OpenLDAP and recompiled, installed restarted postfix, > cyrus imapd, and started up ldap. And it still retuns "user not found" > when I try to login to cyrus imap. But the aut

Re: upgrade from Cyrus 2.1.15 to cyrus 2.2.3 breaks LDAP auxprop authentication.

OK I patched my OpenLDAP and recompiled, installed restarted postfix, cyrus imapd, and started up ldap. And it still retuns "user not found" when I try to login to cyrus imap. But the auth.log now shows something different.. --- auth.log --- Feb 11 19:19:46 devel imtest: DIGEST-MD5 client step 2 Fe

rename problems with murder

I've pretty much got most of processes working, the problem that I am having is that when I try to move a mail box from one backend to another using rename. In cyradm the command that I used is rename user.dragon user.dragon 2 or rename user.dragon user.dragon mailbackend2.{mydomain}.com I

Re: login problem

> Hi, > > When try connect me from MUA in messages log through this error: > > Feb 11 17:11:40 mymachine imap(pam_unix)[3395]: could not identify user (from > getpwnam(user.domain.cl)) > > Exist any way that cyrus take users created in mysql and not mapped over linux > users?? yes, there is a wa

Re: SIEVE weirdness

dear listeners, Am Mittwoch, 11. Februar 2004 15:34 schrieb Brian: > Doing something like 'sieveshell -u cyrus -a cyrus' prompts for the > password over and over. Is there a file /etc/sasldb2 ? If not create it with saslpasswd2 ... (see help) peace & luck Stefan --- Home Page: http://asg.web.cmu

login problem

Hi, When try connect me from MUA in messages log through this error: Feb 11 17:11:40 mymachine imap(pam_unix)[3395]: could not identify user (from getpwnam(user.domain.cl)) Exist any way that cyrus take users created in mysql and not mapped over linux users?? Thanks in advance. Arturo --- Hom

autentication problemq

Hi!... I cant autenticate to my imap... and found this mail... > Meantime I found the source of the problem. > Before I had started with src.rpm version I tried to install from sources. > A residue of this attempt was lmtpd deamon still running. > To make long story short; postfix used one socket,

Re: saslauthd and ldap and ??? pam

On Wed, 11 Feb 2004, Igor Brezac wrote: > > On Wed, 11 Feb 2004, Shelley Waltz wrote: > > > I am interested in knowing the difference and/or advantages > > of the ways one can use ldap authentication with sasl. > > > > One way is to use saslauthd -a ldap, which uses the auth_ldap > > module for sas

Re: serious over quota problem

See: Cyrus IMAP uses a 32bit int to store quota in bytes internally, this causes problems with large quotas. While the bug says 2GB, from what I saw in the code a while back it's an unsigned long which should max out at 4GB. Can one of the

Re: wiki suggestion: integrated products bundling Cyrus IMAPd

Craig Ringer wrote: Hi folks I thought it might be an idea to start a wiki page tracking products that ship an integrated Cyrus IMAPd. This would be useful in (a) saving people who don't want to roll their own a lot of frustration and (b) potentially saving the mailing list participants a lot of r

Re: saslauthd and ldap and ??? pam

On Wed, 11 Feb 2004, Shelley Waltz wrote: > I am interested in knowing the difference and/or advantages > of the ways one can use ldap authentication with sasl. > > One way is to use saslauthd -a ldap, which uses the auth_ldap > module for saslauthd. > > Another way is to use saslauthd -a pam and

SIEVE weirdness

A friend of mine has tried to get Cyrus 2.1.5 running on RHEL 3 and all works except sieve. Doing something like 'sieveshell -u cyrus -a cyrus' prompts for the password over and over. The error message I get is Feb 5 17:09:48 agentsmith timsieved[4172]: unable to open Berkeley db /etc/sasldb2: I

Re: upgrade from Cyrus 2.1.15 to cyrus 2.2.3 breaks LDAP auxprop authentication.

On Wed, 11 Feb 2004, Edward Rudd wrote: > I'm using the ldapdb auxprop plugin that comes with OpenLDAP 2.1.22 with > cyrus sasl 2.1.15, which works perfectly with the sasl2 sample server > and client programs, postfix 1.1.12, postfix 2.0.16, and cyrus imapd > 2.1.13 to cyrus imapd 2.1.15.. Howev

Need help with cyrus.logwatch.tgz

Hi! networkers,   I'm using imapd-cyrus 2.1.15-2 on RedHat 9   I did the following commands:   # cd  /tmp # wget http://acs-wiki.andrew.cmu.edu/twiki/pub/Cyrus/Logwatch/cyrus.logwatch.tgz # gunzip  cyrus.logwatch.tgz # cd  / # tar  -xvf  /tmp/cyrus.logwatch.tar # logwatch --service  cyrus  --

Re: upgrade from Cyrus 2.1.15 to cyrus 2.2.3 breaks LDAP auxprop authentication.

Check http://www.openldap.org/its/index.cgi/Software%20Bugs?id=2926;selectid=2926 Cyrus-imap needs to be fixed, but it was easier to change openldap api. -Igor On Wed, 11 Feb 2004, Edward Rudd wrote: > I'm using the ldapdb auxprop plugin that comes with OpenLDAP 2.1.22 with > cyrus sasl 2.1.15

Sieve not working (Fedora / Cyrus (RPMS)

Hello, Been tinkering around with Cyrus now for 4 days, all the mail side of things seem to be ok, the major fly in the ointment (and in fact the reason I moved to cyrus) is that sieve doesn't want to seem to work at all... I've done a fair bit of googling and hunting around to try and work out t

saslauthd and ldap and ??? pam

I am interested in knowing the difference and/or advantages of the ways one can use ldap authentication with sasl. One way is to use saslauthd -a ldap, which uses the auth_ldap module for saslauthd. Another way is to use saslauthd -a pam and then specify ldap as the auth mechanism in the various

wiki suggestion: integrated products bundling Cyrus IMAPd

Hi folks I thought it might be an idea to start a wiki page tracking products that ship an integrated Cyrus IMAPd. This would be useful in (a) saving people who don't want to roll their own a lot of frustration and (b) potentially saving the mailing list participants a lot of repeat questions and

Re: lmtp permision denied

Rafel Amer wrote: Hi, I have installed debian gnu/linux sarge and postfix/cyrus mail server. When I trie to send an e-mail, I get the following error in the mail.log Feb 10 17:46:47 claimcenter postfix/lmtp[19109]: B6D0EDB: to=<[EMAIL PROTECTED]>, relay=none, delay=0, status=deferred (connect t

Re: ldap/cyrus server

On Tue, 10 Feb 2004 10:06:38 +0100, Lindner wrote: > I recommend the kolab-server which was designed to replace Exchange. The > project is still relatively young but it is free and I am satisfied with > it. It's VERY easy to install /maintain and the KDE 3.2 comes with a > prerelease of "Kontact"

lmtp permision denied

Hi, I have installed debian gnu/linux sarge and postfix/cyrus mail server. When I trie to send an e-mail, I get the following error in the mail.log Feb 10 17:46:47 claimcenter postfix/lmtp[19109]: B6D0EDB: to=<[EMAIL PROTECTED]>, relay=none, delay=0, status=deferred (connect to /var/lib/cyrus/so