Hi,
I used ptlaoder quite successfully up to version 2.4 of cyrus. Since the
upgrade to 2.5 I get SEGFAULTs.
After the upgrade to 3.2.2 I tested it again, but still:
process type:SERVICE name:ptloader path:/usr/lib/cyrus/bin/ptloader
age:0.665s pid:19082 signaled to death by signal 11
Hi Sven,
On Thu, Jun 13, 2019, at 12:27 AM, Sven Schwedas wrote:
> Is there another way to get ptloader to spit out debug information and
> pinpoint what's not set up correctly?
>
I remember this thing as being very noisy, let me see...
Okay, in your cyrus.conf SERVICES entry, if you
ck: /path/to/some/socket
> auth_mech: pts
> pts_module: ldap
> ...
>
> cyrus.conf:
> SERVICES {
> ...
> ptloader cmd="ptloader" listen="/path/to/some/socket"
> ...
> }
>
> Does this get you going?
It starts
Hi Sven,
I don't know much about running it in a production capacity, but our test suite
sets up the following for LDAP pts:
imapd.conf:
...
ptloader_sock: /path/to/some/socket
auth_mech: pts
pts_module: ldap
...
cyrus.conf:
SERVICES {
...
ptloader cmd="ptloader" listen=&quo
This has nothing to do with my problem. Please stop spamming.
On 23.04.19 13:56, Willem Offermans wrote:
> Dear Cyrus friends and Sven,
>
> A reason to look for authentication by radius.
> But maybe this should go to feature request.
>
>
> Wiel Offermans
> wil...@offermans.rompen.nl
Dear Cyrus friends and Sven,
A reason to look for authentication by radius.
But maybe this should go to feature request.
Wiel Offermans
wil...@offermans.rompen.nl
> On 23 Apr 2019, at 13:50, Sven Schwedas wrote:
>
> On 23.04.19 13:43, Willem Offermans wrote:
>> Dear Cyrus Friends and
On 23.04.19 13:43, Willem Offermans wrote:
> Dear Cyrus Friends and Sven,
>
> I don’t know if this is of any help.
>
> I have setup saslauthd to do LDAP authentication of Cyrus.
That's what I want to get away from, because saslauthd cannot handle
groups, and I need to maintain PAM LDAP auth in
to set up direct LDAP auth via auth_meth=pts, but on start I
> always get "ptload(): can't connect to ptloader server: No such file or
> directory" as error. The directory for ptloader_sock exists and is the
> same as for all other sockets, so there shouldn't be any permissio
I'm trying to set up direct LDAP auth via auth_meth=pts, but on start I
always get "ptload(): can't connect to ptloader server: No such file or
directory" as error. The directory for ptloader_sock exists and is the
same as for all other sockets, so there shouldn't be any permissio
Hi all,
suddenly, I got the following errors in my mail.log:
May 2 21:18:05 mail ptloader[3980]: IOERROR: mapping
/srv/imap/config/ptclient/ptscache.db file: Cannot allocate memory
May 2 21:18:05 mail ptloader[3980]: failed to mmap
/srv/imap/config/ptclient/ptscache.db file
May 2 21:18:06
ldap_bind_dn: uid=cyrus-admin,ou=services,dc=example,dc=org
Case 2
ldap_bind_s: uid=cyrus-admin,ou=special users,dc=example,dc=org
In case 1 both testsaslauthd and mupdatetest can authenticate just
fine, but in case 2 only testsaslauthd will.
2 In a murder deployment like this, should ptloader
ldap_bind_s: uid=cyrus-admin,ou=special users,dc=example,dc=org
In case 1 both testsaslauthd and mupdatetest can authenticate just fine,
but in case 2 only testsaslauthd will.
2 In a murder deployment like this, should ptloader be running on all
server or just a part of it, backend? frontend? (M
Hi,
I have cyrus-imapd-2.3.16 with virtualdomain and a total administrator
in default domain (username without '@%d').
I use saslauthd for authentication and ptloader for authorization, all
with LDAP.
My problem stays on ptloader conf.
To optimize query I would like to restrict searches using
On 10/20/2010 10:51 AM, Dave McMurtrie wrote:
Hi,
I'm curious to learn whether anyone is using ptloader with AFS.
We're using it here, but our build environment is somewhat...
interesting. I'd be mildly surprised if anyone is actually able to
compile and link ptclient/afskrb.c from
Hi,
I'm curious to learn whether anyone is using ptloader with AFS.
We're using it here, but our build environment is somewhat...
interesting. I'd be mildly surprised if anyone is actually able to
compile and link ptclient/afskrb.c from the provided Cyrus source tarballs.
In the not-so
Dear list,
I use saslauthd to auth against ldap (bind auth) and I am trying to use
ptloader to fetch group information from LDAP so that group based ACL's
can be used for shared folders.
The ldap auth works fine, but the group information gets screwed up
somewhere. With tcpdump I see my
Jos De Graeve wrote:
JDG I use saslauthd to auth against ldap (bind auth) and I am trying
JDG to use ptloader to fetch group information from LDAP so that group
JDG based ACL's can be used for shared folders.
We have several similar systems in production.
JDG If I look with ptdump each user
Hi Duncan,
JDG My groups are posixGroup with the uid's of the members listed
JDG in the memberUid attribute, the group name is listed in the cn
JDG attribute:
If you add
ldap_member_attribute: cn
to your config, it should work. Certainly something very similar works
on our
On 27 May 2010, at 06:38, Duncan Gibb wrote:
Yes. It would be nice when someone has time to make the configuration
of pts_ldap more similar to other things likely to be using the same
data (eg pam/nss/samba as well as saslauthd).
Comments on:
Hello,
I have got one more problem with Cyrus IMAP and SASL/ptloader, that
does not allow me to be entirely happy with my setup.
The issue is that I want to be able to store the Cyrus IMAP admin
credentials locally on the Linux server, while all other users are
using LDAP backend for login. I
On Wed, 2010-01-13 at 13:39 +0200, Evgeniy Arbatov wrote:
Hello,
I have got one more problem with Cyrus IMAP and SASL/ptloader, that
does not allow me to be entirely happy with my setup.
The issue is that I want to be able to store the Cyrus IMAP admin
credentials locally on the Linux server
ptloader on the Cyrus IMAP
server and hence all the authentication is working well, but the
authorization fails (because ptloader always tries to query LDAP).
Does this fail because ptloader finds no object in LDAP representing the
admin account?
Is there a way to specify two different auth
nodens2099 wrote:
EA I want to be able to store the Cyrus IMAP admin credentials
EA locally on the Linux server, while all other users are
EA using LDAP backend for login. [..]
EA this does not work, because I also use ptloader on the Cyrus IMAP
EA server and hence all the authentication
I have a similar patch which assumes proxy and admin lines are
authoritative, so if they are not found in whatever authorization
system (including LDAP) but they are found in imapd.conf, then they
are considered valid canonicalized.
I don't see this issue in BZ, but I suspect it's there...
Hello,
Finally I am able to get the ptloader working. In my case the major
issue was that I used Cyrus IMAP 2.3.7, that has a segmentation fault
when reading from LDAP. This issue was previously discussed in
http://www.irbs.net/internet/info-cyrus/0608/0129.html I solved the
problem by updating
On 8 20, 2009 8:10 PM, Wil Cooley wcoo...@nakedape.cc wrote:
WC Do I understand correctly [..] that the LDAP ptloader
WC module can be used to manage group ACLs with
WC auth_mech=pts/pts_module=ldap, instead of
WC auth_mech=unix/unix_group_enable=1?
Yes.
WC Does this solve the slowness caused
Thank you for your suggestions! They helped me a great deal.
The situation is better now, in a sense that ptloader connects to LDAP
and finds something.
After corrections my imapd.conf:
auth_mech: pts
pts_module: ldap
ptloader_sock: /var/lib/imap/socket/ptsock
ldap_uri: ldaps://ldap.example.com
Hi,
Evgeniy Arbatov schrieb:
Thank you for your suggestions! They helped me a great deal.
The situation is better now, in a sense that ptloader connects to LDAP
and finds something.
OK. :)
After corrections my imapd.conf:
This ist what I have.
auth_mech: pts
pts_module: ldap
ptloader_sock
On Wed, 2009-08-19 at 15:33 +0300, Evgeniy Arbatov wrote:
Dear list,
I want to ask your advice on the use of ptloader for LDAP-based
authorization in Cyrus IMAP.
Do I understand correctly from this discussion and the sparse mention of
this in the documentation that the LDAP ptloader module
understand correctly from this discussion and the sparse mention of
this in the documentation that the LDAP ptloader module can be used to
manage group ACLs with auth_mech=pts/pts_module=ldap, instead of
auth_mech=unix/unix_group_enable=1?
Does this solve the slowness caused by UNIX groups in LDAP
: Dear list, I
want to ask your advic...
Do I understand correctly from this discussion and the sparse mention of
this in the documentation that the LDAP ptloader module can be used to
manage group ACLs with auth_mech=pts/pts_module=ldap, instead of
auth_mech=unix/unix_group_enable=1?
Does
Dear list,
I want to ask your advice on the use of ptloader for LDAP-based
authorization in Cyrus IMAP.
I configured my Cyrus IMAP to use ptloader:
ldap_uri: ldaps://ldap.example.com:636
ldap_sasl: 0
pts_module: ldap
ldap_filter: (uid=%U)
ldap_base: dc=example,dc=com
ldap_group_filter: (cn
On Wed, Aug 19, 2009 at 9:33 AM, Evgeniy
Arbatovarbatovevge...@gmail.com wrote:
Via cyradm I add needed permissions for admins group:
sam user/postmaster admins lrswipkxte
Then I successfully authenticate using earbatov UID, but shared
folders are not visible in the Thunderbird.
Do you
note: if I configure shared
access locally via cyradm interface, without using the ptloader and
LDAP - everything works as expected.
Evgeniy
auth_mech: pts
--
Reinaldo de Carvalho
http://korreio.sf.net
http://python-cyrus.sf.net
Don't try to adapt the software to the way you work, but rather
Evgeniy Arbatov wrote:
EA pts_module: ldap
This module is currently very difficult to configure, IMHO. I've posted
previously that there's scope for a mini-project to make it behave more
similarly to other LDAP-group-orientated things such as nss_ldap or
saslauthd.
EA ldap_member_method:
Evgeniy,
Evgeniy Arbatov schrieb:
Dear list,
I want to ask your advice on the use of ptloader for LDAP-based
authorization in Cyrus IMAP.
I configured my Cyrus IMAP to use ptloader:
[...]
Can you tell where I am wrong?
auth_mech: pts was mentioned before.
Did you set ptloader_sock
Duncan,
Duncan Gibb schrieb:
EA pts_module: ldap
This module is currently very difficult to configure, IMHO.
That's true. :) But it's doable.
EA ldap_member_method: attribute
This method doesn't work they way you might expect. It finds the user
object and wants to see the names of the
Jul 2008, at 05:57, Dmitriy Kirhlarov wrote:
We find a problem -- when ptloader build with ldap support by gcc4 on
amd64 platform it's doesn't work.
After investigation ptloader core with gdb we find a problem. (I'm
sorry, for possible unpropper problem description)
1. ldap.h have hints
Hi, list
We find a problem -- when ptloader build with ldap support by gcc4 on
amd64 platform it's doesn't work.
After investigation ptloader core with gdb we find a problem. (I'm
sorry, for possible unpropper problem description)
1. ldap.h have hints:
#if LDAP_DEPRECATED
LDAP_F( char
Hi, list
We find a problem -- when ptloader build with ldap support by gcc4 on
amd64 platform it's doesn't work.
After investigation ptloader core with gdb we find a problem. (I'm
sorry, for possible unpropper problem description)
1. ldap.h have hints:
#if LDAP_DEPRECATED
LDAP_F( char
You can add it to the bugzilla here:
https://bugzilla.andrew.cmu.edu/
Thanks!
:wes
On 30 Jul 2008, at 05:57, Dmitriy Kirhlarov wrote:
We find a problem -- when ptloader build with ldap support by gcc4 on
amd64 platform it's doesn't work.
After investigation ptloader core with gdb
Hi Wes.
On 06 May 2008, at 15:51, Klaus Steinberger wrote:
I'm using cyrus-imapd-2.3.7-1.1.el5 (Scientific Linux).
That's pretty old, there have been a lot of fixes to the pt ldap
code in the intervening 5 or so releases.
Thanks! That solved my problem, i built the SRPM from Fedora 8 now
Hello,
I try to setup ptloader, but run into trouble with the way Novell handles
groups.
Novell edirectory does the following:
the groupMembership Attribute inside the person object is multivalued, and
contains the full DN's of the groups. Vice versa, the group Object contains a
multivalued
On 06 May 2008, at 08:35, Klaus Steinberger wrote:
ldap_group_base: ou=Gruppen,o=physik
ldap_group_filter: (member=%D)
The above is fine.
ldap_member_method: attribute
ldap_member_attribute: groupMemberShip
ldap_member_base: ou=Gruppen,o=physik
The above should be:
ldap_member_method:
, then
ptloader get's back the correct answer from the server (as i can see with
wireshark), but then ptloader seems to crash:
May 6 22:39:08 test-imap imap[9568]: starttls: TLSv1 with cipher AES256-SHA
(256/256 bits new) no authentication
May 6 22:39:18 test-imap imap[9568]: ptload(): pinging ptloader
Hi,
I'm setting up a cyrus mail server.
I would like connect Cyrus with my LDAP groups and members, in order
to provide group access rights to shared folders
After Internet surfing, I've read that I must start ptloader as Cyrus service
... but, in Debian etch distribution, there isn't
Hi,
Am Donnerstag, 3. Januar 2008 schrieb Lluis Faja:
Hi,
I'm setting up a cyrus mail server.
I would like connect Cyrus with my LDAP groups and members, in order
to provide group access rights to shared folders
After Internet surfing, I've read that I must start ptloader as Cyrus
service
There is a patch 140-kolab-ldap.dpatch mentioned in the annotations of the
debian-package.
I don't know if this ist somehow related with ptloader, I don't think so.
Cheers
Ingo
--
** Besuchen Sie uns auf der CeBIT vom 04.-09. März 2008 in Hannover **
** Halle 5 - Stand C45
Hi,
I get a connection refused when i try to enable sync_client with
ptloader. I use cyrus-imapd-2.3.9
sync_client[13982]: ptload(): pinging ptloader
sync_client[13982]: ptload(): can't connect to ptloader server:
Connection refused
kernel: Dec 13 17:32:11 sacco sync_client[13982]: ptload
Hi!
I'm trying to get LDAP groups to work with cyrus. I have ptloader
running, and have configured it to use LDAP (see below).
I can
* log in using users in LDAP
* set ACLs for groups in ldap: sam some/mailbox group:someGroup lrswp
I can not
* use the access rights from a group I am a member
--On Wednesday, August 15, 2007 12:34:39 PM +0200 Egil Möller
[EMAIL PROTECTED] wrote:
Why does ptloader show the sambaSid of two of the groups superadmin is a
member of, instead of the group name?
Disclaimer: I don't actually use the ldap code (nor am I a cyrus
developer).
From looking
Hello List,
I tryed to use ptloader with ldap - wich basically works fine but since
i use unixhirachysep: 1
my . get replaced by ^ sometimes in the ptloader chain?!?
So no problem with authentication because the server simply asks
salsauthd to authenticate m.karrer (uid=%u) via salsauthd
Hi, list.
1. I'm also using ldap-based groups ACL in cyrus. When I add any user to
more them 1 group, cyrus can't autorize them. I can't find any
documentation about this behavior. Is it normal?
2. How to configure default ldap_realm for connecting to saslauthd?
I have two domains --
Warren Turkal wrote:
On Wednesday 30 May 2007 14:30, Milen Dimov wrote:
We successfully run cyrus 2.2.12 and 2.3.8 both with LDAP users
authentication and authorization utilizing respectively saslauthd and
ptloader with LDAP support.
I was under the impression that you could avoid saslauthd
En/na Warren Turkal ha escrit:
On Wednesday 30 May 2007 14:30, Milen Dimov wrote:
We successfully run cyrus 2.2.12 and 2.3.8 both with LDAP users
authentication and authorization utilizing respectively saslauthd and
ptloader with LDAP support.
I was under the impression that you could avoid
Thanks Milen,
your answer is VERY useful to me and hopefully to many others!
I just added some comments to yours, describing my current vision on those
arguments.
I'm asking to check if it's correct or not.
Last question: what ptloader stands for? What is pts?
-Messaggio originale
Hi all
I find very difficult to understand relationships between groups, members, LDAP
and ptloader.
I have a cyrus 2.2.12 successfully authenticating users with saslauthd and my
user DB is openLDAP
I would like to upgrade to 2.3.8. It's now some days that I try to investigate
the differences
On Wednesday 30 May 2007 09:04, Toschi Pietro wrote:
Is there somebody on this list so kind and please try to explain me what
I'm missing?
You're not the only one lost with all of this. I hope someone can at least
post a working configuration that shows using LDAP without saslauthd so that
I
without saslauthd so that
I would at least know what a working config looks like.
Hi,
We successfully run cyrus 2.2.12 and 2.3.8 both with LDAP users
authentication and authorization utilizing respectively saslauthd and
ptloader with LDAP support.
The documentation that comes with Cyrus IMAP
On Wednesday 30 May 2007 14:30, Milen Dimov wrote:
We successfully run cyrus 2.2.12 and 2.3.8 both with LDAP users
authentication and authorization utilizing respectively saslauthd and
ptloader with LDAP support.
I was under the impression that you could avoid saslauthd for authentication
Some time ago I was report about problem with sync_client (sync_client
can't be run from cyrus.conf, when ptloader used)
For details:
http://lists.andrew.cmu.edu/pipermail/info-cyrus/2006-October/024121.html
2.3.8 have same issue.
How I can inform developers about it? Some other list? bug
On Wed, Apr 04, 2007 at 05:56:12PM +0100, Bernhard D Rohrer wrote:
Hi folks
I am trying to authorise ldap groups with cyrus for use in public
folders. now looking though the mailing list has led me to finding
that ptloader is responsible for this.
I have not been able to find any
is running 2.3.7. I'm happier storing cleartext
passwords to allow secure wire authentication protocols, so saslauthd is
not feasible (as I understand matters).
As near as I can figure, ptloader can handle the canonicalisation but
not the authentication, for which I can just use the built-in LDAP
support
On Wed, 9 Aug 2006, Ben Poliakoff wrote:
* Igor Brezac [EMAIL PROTECTED] [20060809 11:50]:
On Wed, 9 Aug 2006, Ben Poliakoff wrote:
* Igor Brezac [EMAIL PROTECTED] [20060809 07:39]:
On Tue, 8 Aug 2006, Ben Poliakoff wrote:
ptloader is segfaulting on multiple servers in my test
* Igor Brezac [EMAIL PROTECTED] [20060809 07:39]:
On Tue, 8 Aug 2006, Ben Poliakoff wrote:
ptloader is segfaulting on multiple servers in my test environment when
the user that is connecting for IMAP service is found in more than one
group.
I have a core file, but it doesn't seem
* Ben Poliakoff [EMAIL PROTECTED] [20060809 09:53]:
* Igor Brezac [EMAIL PROTECTED] [20060809 07:39]:
On Tue, 8 Aug 2006, Ben Poliakoff wrote:
ptloader is segfaulting on multiple servers in my test environment when
the user that is connecting for IMAP service is found in more than
On Wed, 9 Aug 2006, Ben Poliakoff wrote:
* Igor Brezac [EMAIL PROTECTED] [20060809 07:39]:
On Tue, 8 Aug 2006, Ben Poliakoff wrote:
ptloader is segfaulting on multiple servers in my test environment when
the user that is connecting for IMAP service is found in more than one
group.
I
Sorry, I must have butchered the original patch when I was pulling it
out of a larger patch (that does some Columbia specific stuff).
Igor's patch makes it look like the correct version.
-Patrick
The last commit has an issue.
Please try this patch and report back:
--- ldap.c.orig
* Igor Brezac [EMAIL PROTECTED] [20060809 11:50]:
On Wed, 9 Aug 2006, Ben Poliakoff wrote:
* Igor Brezac [EMAIL PROTECTED] [20060809 07:39]:
On Tue, 8 Aug 2006, Ben Poliakoff wrote:
ptloader is segfaulting on multiple servers in my test environment when
the user that is connecting
On Wed, 5 Jul 2006, Ben Poliakoff wrote:
Hi All,
I've been trying to use the LDAP pts module with Cyrus imapd 2.3.6.
I've had reasonably good success with ptloader configured to do
*anonymous* binds, but when I set 'ldap_sasl: 1' in imapd.conf ptloader
fails to bind to my LDAP server
Hi All,
I've been trying to use the LDAP pts module with Cyrus imapd 2.3.6.
I've had reasonably good success with ptloader configured to do
*anonymous* binds, but when I set 'ldap_sasl: 1' in imapd.conf ptloader
fails to bind to my LDAP server with the following error:
Unable to set
Am Thursday 15 June 2006 18:36 schrieb Sebas PRE:
Please do not Top-Post.
Yes, ptloader dies in both.
In 2.2.12 I run ptloader with this compile options:
--with-auth=pts --with-pts=ldap --with-ldap=/usr
But I obtain the same results with ptloader diyng and in cyrus.log appears
the same
Can the cyrus ldap ptloader tell cyrus which mailbox belongs to a
user(retrieving it from ldap)?
Or will cyrus simply get the mailbox name from the username used to login?
Thanks!
--
Pedro Algarvio
__ ___ ___ ______ __
| Y
Am Thursday 15 June 2006 18:36 schrieb Sebas PRE:
Please do not Top-Post.
Yes, ptloader dies in both.
In 2.2.12 I run ptloader with this compile options:
--with-auth=pts --with-pts=ldap --with-ldap=/usr
But I obtain the same results with ptloader diyng and in cyrus.log appears
This is my intallation:
- Red Hat Enterprise 3
- imapd-2.2.12 or imapd-2.3.3 (I tested both)
- cyrus-sasl-2.1.15
I have in 'cyrus.conf':
ptloader cmd=ptloader listen=/u01/config/ptclient/ptsock prefork=1
in the file 'imapd.conf':
# LDAP PTLOADER
auth_mech: pts
pts_module: ldap
Does ptloader die in both 2.2.12 and 2.3.3 or only 2.3.3?I've seen it die like that in 2.3 (don't recall the minor version), but never had a chance to investigate it.-PatrickOn Jun 15, 2006, at 5:30 AM, Sebas PRE wrote:This is my intallation:- Red Hat Enterprise 3- imapd-2.2.12 or imapd-2.3.3 (I
Yes, ptloader dies in both.
In 2.2.12 I run ptloader with this compile options:
--with-auth=pts --with-pts=ldap --with-ldap=/usr
But I obtain the same results with ptloader diyng and in cyrus.log appears the
same lines.
Thanks...
Sebastian Calero.
Citado por Patrick Radtke [EMAIL
Please keep the replies on the list.
On Fri, 14 Apr 2006, barsalou wrote:
Thanks for the reply.
So just to clarify my thinking
I would use the ptloader configuration to create a process for
authentication, then use sasl or whatever for authorization.
Other way around. ptloader
What is the role of the ptloader stuff? Would you use it in place of
sasl? I'm fairly new at this, so please be gentle. :)
I've gone over the overview doc a few times as well as the options and
through the mailing lists...
My goal is to use LDAP to provide the mailboxes_db, but from what I
On Tue, 3 Jan 2006, Simon Matter wrote:
On Mon, 26 Dec 2005, Milen Dimov wrote:
Hi,
Does Cyrus IMAPd 2.3.1 supports ldap authorization trought ptloader?
The
configuration parameters --with-auth=pts --with-pts=ldap used in the
2.2.x versions are not displayed in 2.3.1 with ./configure
On Tue, 03 Jan 2006, Simon Matter wrote:
could not build postfix with SASLv2 _and_ LDAP support if the installed
openldap has been built for SASLv1. This has just resulted in segfaults.
You are experienced what I call the missing versioned symbols hell. We
have that fixed in Debian by
-imapd with
such old version of openldap anyway.
It builds fine but then an ldd ptloader shows that it's linked against
both sasl1 and sasl2, which I'm sure won't work.
Simon
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http
On Wed, 4 Jan 2006, Simon Matter wrote:
BTW: I know that openldap built against SASLv1 is old, but I still want
the rpm to be suitable for older platforms. If it's a problem I simply
disable ldap pts support for those using openldap/SASLv1.
cyrus imapd configure checks for openldap version
should not be able to compile cyrus-imapd with
such old version of openldap anyway.
It builds fine but then an ldd ptloader shows that it's linked against
both sasl1 and sasl2, which I'm sure won't work.
Just curious, what version of openldap do you use?
--
Igor
Cyrus Home Page: http
not. You should not be able to compile cyrus-imapd
with
such old version of openldap anyway.
It builds fine but then an ldd ptloader shows that it's linked against
both sasl1 and sasl2, which I'm sure won't work.
Just curious, what version of openldap do you use?
It's openldap 2.0.27.
Simon
On Mon, 26 Dec 2005, Milen Dimov wrote:
Hi,
Does Cyrus IMAPd 2.3.1 supports ldap authorization trought ptloader? The
configuration parameters --with-auth=pts --with-pts=ldap used in the
2.2.x versions are not displayed in 2.3.1 with ./configure --help. We
use Cyrus IMAPd with ldap
On Tue, 3 Jan 2006, Simon Matter wrote:
On Mon, 26 Dec 2005, Milen Dimov wrote:
Hi,
Does Cyrus IMAPd 2.3.1 supports ldap authorization trought ptloader? The
configuration parameters --with-auth=pts --with-pts=ldap used in the
2.2.x versions are not displayed in 2.3.1 with ./configure
On Tue, 03 Jan 2006, Simon Matter wrote:
could not build postfix with SASLv2 _and_ LDAP support if the installed
openldap has been built for SASLv1. This has just resulted in segfaults.
You are experienced what I call the missing versioned symbols hell. We
have that fixed in Debian by force.
Hi,
Does Cyrus IMAPd 2.3.1 supports ldap authorization trought ptloader? The
configuration parameters --with-auth=pts --with-pts=ldap used in the
2.2.x versions are not displayed in 2.3.1 with ./configure --help. We
use Cyrus IMAPd with ldap authorization for about 2 years and it works
just great
On Mon, 26 Dec 2005, Milen Dimov wrote:
Hi,
Does Cyrus IMAPd 2.3.1 supports ldap authorization trought ptloader? The
configuration parameters --with-auth=pts --with-pts=ldap used in the
2.2.x versions are not displayed in 2.3.1 with ./configure --help. We
use Cyrus IMAPd with ldap
Igor Brezac wrote:
On Wed, 27 Jul 2005, Sava Chankov wrote:
Hi,
I'm using cyrus-imapd-2.2.12 with ptloader patch from Igor Brezac that
fixes the
SASL authz bug. Groups are read from LDAP by ptloader properly, but group
authorization doesn't work with this configuration:
virtdomains
Hi,
I'm using cyrus-imapd-2.2.12 with ptloader patch from Igor Brezac that fixes the
SASL authz bug. Groups are read from LDAP by ptloader properly, but group
authorization doesn't work with this configuration:
virtdomains: yes
ldap_version: 3
ldap_sasl: 0
ldap_size_limit: 500
ldap_bind_dn: uid
On Wed, 27 Jul 2005, Sava Chankov wrote:
Hi,
I'm using cyrus-imapd-2.2.12 with ptloader patch from Igor Brezac that fixes the
SASL authz bug. Groups are read from LDAP by ptloader properly, but group
authorization doesn't work with this configuration:
virtdomains: yes
ldap_version: 3
Hi, I'm trying to use the ldap ptloader with the following :
ldap_base: dc=naturvern,dc=no
ldap_member_base: dc=naturvern,dc=no
ldap_group_base: ou=groups,dc=naturvern,dc=no
#ldap_member_method: attribute
#ldap_member_filter: (memberUid: %u)
#ldap_member_scope: sub
#ldap_mech: plain login
# I've
On Sun, 10 Jul 2005, Tarjei Huse wrote:
Hi, I'm trying to use the ldap ptloader with the following :
ldap_base: dc=naturvern,dc=no
ldap_member_base: dc=naturvern,dc=no
ldap_group_base: ou=groups,dc=naturvern,dc=no
#ldap_member_method: attribute
#ldap_member_filter: (memberUid: %u
[127.0.0.1] smail04 plaintext User logged in
Jun 9 06:27:37 mail04 pop3[5180]: Unable to locate maildrop for
smail04: Mailbox does not exist
But as you can see in the ldap entry my maildrop exists.
If I understand it correctly, then ptloader checks if the mailbox is
available with an ldap search when
not exist which is
true. The server is looking for the 'smail04' mailbox.
If I understand it correctly, then ptloader checks if the mailbox is
available with an ldap search when I enter the login name. Thats why I get an
OK after that. Ptloader can find the alias value in the ldap database
Hi all
With ptload we've a nice tool to connect to an ldap backend. And with
ldap_filter in imapd.conf the user has the ability to do nice
things.This works very well. But as I understand this is only the
authorization mechanism. I always have problems with the
authentication (sasl).
/bin/imapd
Jan 5 14:48:46 server12 imap[21600]: executed
Jan 5 14:48:46 server12 imap[21600]: accepted connection
Jan 5 14:48:46 server12 imap[21600]: ptload(): pinging ptloader
Jan 5 14:48:46 server12 ptloader[6849]: accepted connection
Jan 5 14:48:46 server12 ptloader[6849]: mystore
]: about to exec /usr/cyrus/bin/imapd
Jan 5 14:48:46 server12 imap[21600]: executed
Jan 5 14:48:46 server12 imap[21600]: accepted connection
Jan 5 14:48:46 server12 imap[21600]: ptload(): pinging ptloader
Jan 5 14:48:46 server12 ptloader[6849]: accepted connection
Jan 5 14:48:46 server12
1 - 100 of 130 matches
Mail list logo
