I have done something similar to this. I have configured saslauthd to use pam and pam uses pam_ldap to talk to the LDAP server on localhost. My LDAP server is the same host as the mail server. I'm pretty certain now that it is the TLS support in pam_ldap that is causing the seg faults. Why
check permissions on /var/imap/socket/lmtp
and are you sure you dont want no auth on the lmtp server ?
HTH
--
Simon Loader
Steve Clement wrote:
Hi,
first off all I want to say hello to the list as I am new on it. Small
and boring intro:
I am a Unix Sysadmin from Luxembourg and in constant
Another option is to run a LDAP replica on your email server. Configure
replication to use tls.
Configure saslauthd to connect to localhost ( 127.0.0.1 specifically ).
With this encryption is not necessary.
You get a substantial speed increase, as you save encryption plus ldap
lookups over t
Hi,
first off all I want to say hello to the list as I am new on it. Small
and boring intro:
I am a Unix Sysadmin from Luxembourg and in constant fight with lmtpd
when it comes to updates :(
following stuff has been updated:
cyrus-sasl/imapd-2.1.5 -> cyrus-imapd-2.1.11 sasl-2.1.10
I used the
--On Monday, December 30, 2002 12:52 AM -0200 Henrique de Moraes Holschuh
<[EMAIL PROTECTED]> wrote:
The codepaths in master are MUCH easier to audit, so I think it overall
enhances the security of Cyrus to run services inside chroot jails. IF it
is done right.
Any comments? Should I submit thi
Duh. Please apply the attached patch too. I really should regression-test
these things BEFORE I send out patches...
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon
The attached patch adds chroot() jailing support to Cyrus master.
Here's the catch:
1. If no jail= parameters are set, cyrus behaves exactly as it always did
2. If jail= parameters are set, we NEED to keep superuser privileges
so that we can chroot(). That means:
2a. If your system has set
