ile.
And then see the documentation of saslauthd. Should ship with your
version locally. Anyhow
https://blog.sys4.de/cyrus-sasl-saslauthd-man-page-en.html
Little correction, it is the options.html file you should consult:
https://www.sendmail.org/~ca/email/cyrus2/options.html
Alexander
Am 02.07.2018 um 03:39 schrieb Andrew Bernard:
I am having trouble with getting imapd and saslauthd to work together on
Ubuntu 18.04, using the recent Cyrus imapd (3.0.7) and sasl (2.1.26)
releases. Using postfix (3.3.1), I have the saslauthd state directory in
/var/run/saslauthd (and also in
I am having trouble with getting imapd and saslauthd to work together on
Ubuntu 18.04, using the recent Cyrus imapd (3.0.7) and sasl (2.1.26)
releases. Using postfix (3.3.1), I have the saslauthd state directory in
/var/run/saslauthd (and also in the chroot'd postfix directory hierarchy).
For
Hi,
we have installed a cyrus-imapd server on a centos 6.6 architecture.
Unfortunatly our service has some bugs:
1. we stop the service, process cyrus files remain in /var/lib/imap/proc
2. we have many errors in /var/log/maillog
gt; You need access to plaintext passwords for CRAM/DIGEST-MD5.
>
> > >
>
> > > LDAP and saslauthd do not provide that.
>
> >
>
> > How can I use CRAM-MD5 with passwords stored in LDAP (in MD5 format )
>
> > then ?
>
&
On 12 March 2015 at 16:04, Vladislav Kurz
wrote:
> On Thursday 12 of March 2015 Ram wrote:
>
>
>
> > > You need access to plaintext passwords for CRAM/DIGEST-MD5.
>
> > >
>
> > > LDAP and saslauthd do not provide that.
>
> >
>
> &g
On Thursday 12 of March 2015 Ram wrote:
> > You need access to plaintext passwords for CRAM/DIGEST-MD5.
> >
> > LDAP and saslauthd do not provide that.
>
> How can I use CRAM-MD5 with passwords stored in LDAP (in MD5 format )
> then ?
>
> I need to disable
in.php says that I
> cannot use saslauthd with CRAM-MD5 or DIGEST-MD5
>
> Then how do I configure my imap server to use CRAM-MD5 ??
>
> Is there a simple howto ?
You need access to plaintext passwords for CRAM/DIGEST-MD5.
LDAP and saslauthd do not provide that.
How can I use CRAM-
On Thursday 12 of March 2015 Ram wrote:
> I am trying to use CRAM-MD5 for password authentication.
> The passwords are in ldap.
>
>
> But the cyrus document here
> https://cyrusimap.org/docs/cyrus-sasl/2.1.23/sysadmin.php says that I
> cannot use saslauthd with C
I am trying to use CRAM-MD5 for password authentication.
The passwords are in ldap.
But the cyrus document here
https://cyrusimap.org/docs/cyrus-sasl/2.1.23/sysadmin.php says that I
cannot use saslauthd with CRAM-MD5 or DIGEST-MD5
Then how do I configure my imap server to use CRAM-MD5
On 12/30/14 10:52 +0100, Gabriele Bulfon wrote:
>So, first I changed openldap configuration with "sasl-secprops none" to have
>also plain auth enabled.
>Running pluginviewer to see the plugins:
>sonicle@www:~$ pluginviewer -m PLAIN
>List of server plugins follows
>Plugin "plain" [loaded],
ibnsl.so.1 =/lib/libnsl.so.1
libsocket.so.1 =/lib/libsocket.so.1
libc.so.1 =/lib/libc.so.1
libgcc_s.so.1 =/usr/sfw/lib/libgcc_s.so.1
libmd.so.1 =/lib/libmd.so.1
libmp.so.2 =/lib/libmp.so.2
libm.so.2 =/lib/libm.so.2
Any clue? Or...any simpler way to let saslauthd do multiple search base
takes?...or may
On 12/23/14 16:07 +0100, Willy Offermans wrote:
>Hello Dan,
>
>On Tue, Dec 23, 2014 at 08:50:07AM -0600, Dan White wrote:
>> On 12/23/14 15:22 +0100, Gabriele Bulfon wrote:
>> >How can I let saslauthd support both configurations?
>>
>> Is the server OpenLDAP? If
base: ou=People,dc=%3,dc=%2,dc=%1
> >ldap_filter: uid=%u
> >How can I let saslauthd support both configurations?
>
> Is the server OpenLDAP? If so, using olcAuthzRegexp would be a far more
> flexible way to handle this scenario. Within saslauthd's ldap config, use
> 'lda
p_filter: uid=%u
>Enter a new domain, but this time it's a 3 level one (dc=dpt,dc=domain,dc=com).
>Sasl configuration should be like:
>ldap_search_base: ou=People,dc=%3,dc=%2,dc=%1
>ldap_filter: uid=%u
>How can I let saslauthd support both configurations?
Is the server OpenLDAP?
iguration is like:
> ldap_search_base: ou=People,dc=%2,dc=%1
> ldap_filter: uid=%u
> Enter a new domain, but this time it's a 3 level one
> (dc=dpt,dc=domain,dc=com).
> Sasl configuration should be like:
> ldap_search_base: ou=People,dc=%3,dc=%2,dc=%1
> ldap_filter: uid=%u
> How c
ne (dc=dpt,dc=domain,dc=com).
Sasl configuration should be like:
ldap_search_base: ou=People,dc=%3,dc=%2,dc=%1
ldap_filter: uid=%u
How can I let saslauthd support both configurations?
Google didn't find an answer to this, just a lot of confused discussions.
Any help? :)
Gabriele.
Cyrus
On Thu, 11 Dec 2014, Patrick Goetz wrote:
> On 12/11/2014 12:45 PM, Andrew Morgan wrote:
>> I only have PAM files for "imap", "lmtp", and "sieve"
>> although I have other service names for some of them.
>>
>
> I don't understand why you have PAM files for lmtp and sieve, but most
> particularly lm
> On 12/11/2014 12:45 PM, Andrew Morgan wrote:
>> I only have PAM files for "imap", "lmtp", and "sieve"
>> although I have other service names for some of them.
>>
>
> I don't understand why you have PAM files for lmtp and sieve, but most
> particularly lmtp. lmtpd is just a local daemon that tran
On 12/11/2014 12:45 PM, Andrew Morgan wrote:
> I only have PAM files for "imap", "lmtp", and "sieve"
> although I have other service names for some of them.
>
I don't understand why you have PAM files for lmtp and sieve, but most
particularly lmtp. lmtpd is just a local daemon that transfers stu
On 12/11/14 12:34 -0600, Patrick Goetz wrote:
>Surely someone on this list will know the answer to this question.
>
>Given sasl_pwcheck_method: saslauthd, with authentication mechanism=pam
>
>I'm trying to track down how saslauthd knows that the cyrus PAM service
>file is
On Thu, 11 Dec 2014, Patrick Boutilier wrote:
> On 12/11/2014 02:34 PM, Patrick Goetz wrote:
>> Surely someone on this list will know the answer to this question.
>>
>> Given sasl_pwcheck_method: saslauthd, with authentication mechanism=pam
>>
>> I'm tr
On 12/11/2014 02:34 PM, Patrick Goetz wrote:
Surely someone on this list will know the answer to this question.
Given sasl_pwcheck_method: saslauthd, with authentication mechanism=pam
I'm trying to track down how saslauthd knows that the cyrus PAM service
file is called imap; i.e. /etc/
Surely someone on this list will know the answer to this question.
Given sasl_pwcheck_method: saslauthd, with authentication mechanism=pam
I'm trying to track down how saslauthd knows that the cyrus PAM service
file is called imap; i.e. /etc/pam.d/imap.
Is this just built in? I can
On 19-04-13 14:06, Marc Patermann wrote:
> Paul,
>
> Paul van der Vlis schrieb (19.04.2013 11:58 Uhr):
>
>> I am trying to get saslauthd working
> While this is not IMAPd related, why don't your try a SASL list?
I am not a member of it. I have tried to post to it
Paul,
Paul van der Vlis schrieb (19.04.2013 11:58 Uhr):
> I am trying to get saslauthd working
While this is not IMAPd related, why don't your try a SASL list?
> to authenticate on openLDAP with
> passwords stored with a MD5 hash (base64 encoded) in the field
> UserPassword.
Hello,
I am trying to get saslauthd working to authenticate on openLDAP with
passwords stored with a MD5 hash (base64 encoded) in the field
UserPassword. The passwords are created with smb-ldap so I think it's
normal that they are base64 encoded.
"testsaslauthd -u mailtest -p sec
e got the following
issue
on authentication:
Users can login via a mailer (imap/pop) or use a webmail (horde). The
webmail uses a SSO-CAS and horde uses a CAS token to log in
cyrus-imap). As the CAS tokens are one-time tokens they must been
cached by saslauthd.
For this we use PAM with saslauthd
s can login via a mailer (imap/pop) or use a webmail (horde). The
webmail uses a SSO-CAS and horde uses a CAS token to log in
cyrus-imap). As the CAS tokens are one-time tokens they must been
cached by saslauthd.
For this we use PAM with saslauthd and 3 PAM modules. pam_cas checks if
the password
on authentication:
>>>
>>> Users can login via a mailer (imap/pop) or use a webmail (horde). The
>>> webmail uses a SSO-CAS and horde uses a CAS token to log in
>>> cyrus-imap). As the CAS tokens are one-time tokens they must been
>>> cached by saslaut
horde uses a CAS token to log in
cyrus-imap). As the CAS tokens are one-time tokens they must been
cached by saslauthd.
For this we use PAM with saslauthd and 3 PAM modules. pam_cas checks if
the password is a valid CAS token, then we try ldap and then a local
account.
cyrus-imap -> saslauth
AS token to log in
> cyrus-imap). As the CAS tokens are one-time tokens they must been
> cached by saslauthd.
>
> For this we use PAM with saslauthd and 3 PAM modules. pam_cas checks if
> the password is a valid CAS token, then we try ldap and then a local
> account.
>
> cyrus-i
been
cached by saslauthd.
For this we use PAM with saslauthd and 3 PAM modules. pam_cas checks if
the password is a valid CAS token, then we try ldap and then a local
account.
cyrus-imap -> saslauthd (cache) -> PAM (pam_cas, pam_ldap, pam_unix)
That works fine.
The problem is: when a us
Hello,
> i am assuming that you are running saslauthd with the -r argument --
> something like:
>
> saslauthd -a ldap -O/etc/saslauthd.conf -r
actually I did not, but thanks for pointing me on that!
I noticed before in /var/log/auth, that username and realm have been
splitted,
ng that you are running saslauthd with the -r argument --
something like:
saslauthd -a ldap -O/etc/saslauthd.conf -r
i usually saslauthd in the foreground so i can watch what is going
on ...
cheers
m
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu
of imapd.conf look
like this:
allowapop: no
sasl_mech_list: PLAIN
virtdomains: userid
sasl_pwcheck_method: saslauthd
How can I get more verbose output? Is there a separate saslauthd logfile
so I can see what cyrus is actually sending to it? I'm afraid cyrus
doesn't use the full email
On 06/08/11 11:44 +0100, John wrote:
>On 05/08/11 22:32, Dan White wrote:
>>Does your cyrus user have permissions to access the saslauthd mux?
>>
>>Try running your testsaslauthd command as your cyrus user... I'm assuming
>>that during testing you were using r
On 05/08/11 22:32, Dan White wrote:
> Does your cyrus user have permissions to access the saslauthd mux?
>
> Try running your testsaslauthd command as your cyrus user... I'm assuming
> that during testing you were using root, or another account.
>
Aha! Thank you so muc
tion-default: /srv/mail/cyrus/mail
>admins: cyrus
>sasl_pwcheck_method: saslauthd
>sasl_saslauthd_path: /var/run/saslauthd/mux
>allowplaintext: yes
>altnamespace: yes
>unixhierarchysep: yes
>virtdomains: userid
>defaultdomain: mydomain.com
>hashimapspool: true
>
>Firstly
with 2.4.10 but
I can't get anything to authenticate on it.
In both cases the host is Arch Linux and both have exactly the same
configuration files: Here is imapd.conf:
configdirectory: /srv/mail/cyrus
partition-default: /srv/mail/cyrus/mail
admins: cyrus
sasl_pwcheck_method:
On Sun, 2011-01-09 at 23:38 -0800, Andrew Morgan wrote:
> On Sun, 9 Jan 2011, j...@destar.net wrote:
> > I cannot wrap my mind around saslauthd and auxprop.
> > Does auxprop use the sasldb file to authenticate users that have been
> > added using the 'saslpasswd2'
On Sun, 9 Jan 2011, j...@destar.net wrote:
> I cannot wrap my mind around saslauthd and auxprop.
>
> Does auxprop use the sasldb file to authenticate users that have been
> added using the 'saslpasswd2' command?
>
> What is saslauthd trying to use for authentication, w
I cannot wrap my mind around saslauthd and auxprop.
Does auxprop use the sasldb file to authenticate users that have been
added using the 'saslpasswd2' command?
What is saslauthd trying to use for authentication, would it be the
mechs shown in a 'saslauthd -v' output?
Wh
rtain users. Any suggested methods?
> >
> > I have RHEL5 with
> > cyrus-imapd-2.3.7-7
> > cyrus-sasl-2.1.22-5
> > and use
> > sasl_pwcheck_method: saslauthd
> > sasl_mech_list: PLAIN LOGIN
> > and /etc/sysconfig/saslauthd
> > MECH=ldap
> Is ther
-2.3.7-7
> cyrus-sasl-2.1.22-5
> and use
> sasl_pwcheck_method: saslauthd
> sasl_mech_list: PLAIN LOGIN
> and /etc/sysconfig/saslauthd
> MECH=ldap
Is there something in LDAP that defines who may or may not have
access? If so, you can modify the LDAP search so only t
I wish a simple way to control who in the LDAP database may login
and autocreate a cyrus imap account. Not everyone in the LDAP database,
just certain users. Any suggested methods?
I have RHEL5 with
cyrus-imapd-2.3.7-7
cyrus-sasl-2.1.22-5
and use
sasl_pwcheck_method: saslauthd
sasl_mech_list
On 29/09/09 23:10 -0400, ravi raju wrote:
>Folks,
>I set up cyrus sasl2 to work with postfix smtp server. I am able to send
>e-mail by authenticating via sasl the first time after I start the saslauthd
>process. When I send another e-mail, it doesn't work. I looked through
>dif
Folks,
I set up cyrus sasl2 to work with postfix smtp server. I am able to send
e-mail by authenticating via sasl the first time after I start the saslauthd
process. When I send another e-mail, it doesn't work. I looked through
different logs, here is what I find:
1. Start saslauthd. I ch
Egoitz Aurrekoetxea wrote:
> Hi mates,
>
> I'm running Cyrus IMAP without saslauthd with cyrus-sasl library at
> this moment and integrated with Postfix. The OS I'm running is
> FreeBSD... it has taken me sometime to set up this testing server... I
> have tried sev
pd.log i get huge no
> of messages coming. donno how to trace the error. also i need to stop cyrus
> imap & saslauthd information coming to my /var/log/messages file as
> well. information is listed below. please help !
If restarting imapd solve your problem, this is probably related to
cyr
yrus imap & saslauthd
information coming to my /var/log/messages file as well. information is listed
below. please help !
[EMAIL PROTECTED] ~]# tail -f /var/log/messages
May 16 10:41:14 mxstore2a saslauthd[7860]: sqlLog called.
May 16 10:41:14 mxstore2a saslauthd[7860]: pam_mysq
>> This is the problem that is how my config file is set and it does not
>> work
>>
>> Even when it is set to pam it does not work. Which is werid as my
>> other setup works fine
>>
>> Theres nothing in the logs so I have no idea why Cyrus is not talki
ve no idea why Cyrus is not talking
> to saslauthd
Have you confirmed that saslauthd is working correctly by using testsaslauthd?
Cyrus Home Page: http://cyrusimap.web.cmu.edu/
Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
jpd wrote:
> This is the problem that is how my config file is set and it does not
> work
>
> Even when it is set to pam it does not work. Which is werid as my
> other setup works fine
>
> Theres nothing in the logs so I have no idea why Cyrus is not talking
> to saslau
This is the problem that is how my config file is set and it does not
work
Even when it is set to pam it does not work. Which is werid as my
other setup works fine
Theres nothing in the logs so I have no idea why Cyrus is not talking
to saslauthd
So any ideas? Could this be a fubar compile
> The problem seems to the that cyrus is not taking to saslauthd - as I
> have run saslauthd in a debug mode to see what happens.
>
> Any ideas why cyrus would not want the talk to saslauthd when it has
> been configured to.
>
> Binaries are of the blastwave repository
>
saslauthd - as I
have run saslauthd in a debug mode to see what happens.
Any ideas why cyrus would not want the talk to saslauthd when it has
been configured to.
Binaries are of the blastwave repository
Working version is on opensolaris b77 x86
Broke one is on Solaris 10 sparc
Any ideas on how you
Is there any reason why imapd would not send a realm to saslauthd
using plain authentication ?
Or could this be some type of error in the way I'm using imtest?
My command line is similar too...
imtest -u daniel -p password -r networks.com localhost
Cyrus Home Page:
Hi Holgar,
your problem is saslauthd related - I think so.
you have two way of auth cyrus imap against LDAP
either 'saslauthd -o ldap' -> /sasl_pwcheck_method: saslauthd
/or directly -> sasl_pwcheck_method: auxprop
sasl_auxprop_plugin: ldapdb
I
Hi Holger,
how does the output of
ps aux |grep saslauthd
look like?
It should look like:/usr/sbin/saslauthd -a ldap
and NOT:/usr/sbin/saslauthd -a pam
Best regards
Roland
FreiNet Technik wrote:
Roland Felnhofer schrieb:
Hi Holger,
Are you using Thunderbird
Roland Felnhofer schrieb:
> Hi Holger,
>
> Are you using Thunderbird ?
>
Hello Roland,
i use several clients, but with Thunderbird i do most of the tests. I
already tried all possible combinations of "secure authentication" and
TLS-Settings, but nothing works.
Regards,
Holger
Cyrus Home P
Hi Holger,
Are you using Thunderbird ?
Try these settings:
Port: 993
Use secure connection: SSL
Use secure authentication: NOT checked!
Best regards
Roland
FreiNet Technik wrote:
Hello all,
I set up a cyrus2.2 IMAP-Server with authentication to a
LDAP-userdirectory via "saslauthd&
Hello all,
I set up a cyrus2.2 IMAP-Server with authentication to a
LDAP-userdirectory via "saslauthd". All ist working well if i use IMAP.
When i try to use IMAPs "mail auth" ist still working (used in groupware
web-client), but IMAP connections from clients time out.
It is
Client: Thunderbird (V2 - beta 2) on Vista 32
I get a failure in my log when opening a (imap)mailbox with Tunderbird
but everything works!
#imap.conf
virtdomains: yes
defaultdomain: domain.xx
servername: domain.xx
loginrealms: domain.xx
saslauthd[55269] :cache_lookup: [login=] [service
re is logfile:
May 28 16:29:12 rambam2 imap[14066]: [ID 702911 auth.notice] cannot
connect to saslauthd server: Permission denied
May 28 16:29:12 rambam2 imap[14066]: [ID 914338 local6.notice] badlogin:
localhost [127.0.0.1] plaintext yk SASL(-1): generic failure: checkpass
failed
I checked tha
On Tue, 2007-04-17 at 12:50 +0530, ram wrote:
> I have a pam_mysql setup with a simple mysql table
> and saslauthd is running with the "-r" option on
> If I test with a user on the primary domain it works fine , but for a
> user on any other domain th
I have a pam_mysql setup with a simple mysql table
and saslauthd is running with the "-r" option on
If I test with a user on the primary domain it works fine , but for a
user on any other domain there is an auth failure
---
cat /etc/pam.d/imap
#%PAM-1.0
auth sufficient pa
entication.
Previously, I was using saslauthd against an sasldb2 database. This worked
well, but I would like to migrate from this to our Kerberos 5 infrastructure
(multiple domains with cross-domain authentication working). Unfortunately,
it appears there isn't any means to force an upper-case r
Am Tuesday 12 September 2006 15:16 schrieb AJ:
>I am using saslauthd 2.1.19 w/ RHEL4 and I am trying to
> authenticate to an ldap server via the user's mail attribute and
> userPassword. I am using the -r flag w/ saslauthd and here is my
> saslauthd.conf file:
>
Hi,
I am using saslauthd 2.1.19 w/ RHEL4 and I am trying to
authenticate to an ldap server via the user's mail attribute and
userPassword. I am using the -r flag w/ saslauthd and here is my
saslauthd.conf file:
ldap_servers: ldap://148.4.5.111
ldap_search_base: ou=Users,dc=doma
On Wed, 2006-08-30 at 20:13 +0200, Kjetil Torgrim Homme wrote:
> On Mon, 2006-08-28 at 13:39 -0700, Rob Tanner wrote:
> > I've setup an IMAP server using Cyrus IMAP4 v2.2.3 which I've setup
> > before without a problem. Authentication is handles through saslauthd.
&
On Mon, 2006-08-28 at 13:39 -0700, Rob Tanner wrote:
> I've setup an IMAP server using Cyrus IMAP4 v2.2.3 which I've setup
> before without a problem. Authentication is handles through saslauthd.
> When I use /etc/shadow as the authentication mechanism (-a shadow), my
>
Hi,
I've setup an IMAP server using Cyrus IMAP4 v2.2.3 which I've setup
before without a problem. Authentication is handles through saslauthd.
When I use /etc/shadow as the authentication mechanism (-a shadow), my
test accounts log in just fine. When, instead, I startup saslau
]
Sent: Wednesday, June 14, 2006 11:36 AM
To: Xue, Jack C
Cc: info-cyrus@lists.andrew.cmu.edu
Subject: Re: Cyrus saslauthd PAM authentication Issue
> I am experiencing a Cyrus-SASL and PAM authentication issue here:
>
> I have configured a Cyrus-IMAP Server to use saslauthd for
authenticati
> I am experiencing a Cyrus-SASL and PAM authentication issue here:
>
> I have configured a Cyrus-IMAP Server to use saslauthd for authentication.
> The system is a RHEL4 Update 3 64bit and runs the RPM package comes with
> Redhat. The Cyrus-SASL version is 2.1.19, Cyrus-IMAP vers
I am experiencing a Cyrus-SASL and PAM authentication issue here:
I have configured a Cyrus-IMAP Server to use saslauthd for authentication.
The system is a RHEL4 Update 3 64bit and runs the RPM package comes with
Redhat. The Cyrus-SASL version is 2.1.19, Cyrus-IMAP version is 2.2.12-3.
Here
ote:
>
> > hi all,
> >
> > no joy even after googling for hours and looking thru the archives ...
> >
> > i cannot get imap to pass the realm either in the userid or realm field
> > to saslauthd.
> >
> > i can successfully authenticate [EMAIL PROTECTED] u
On Fri, 7 Apr 2006, lartc wrote:
hi all,
no joy even after googling for hours and looking thru the archives ...
i cannot get imap to pass the realm either in the userid or realm field
to saslauthd.
i can successfully authenticate [EMAIL PROTECTED] using testsaslauthd,
however, imtest test
Am Fr, den 07.04.2006 schrieb lartc um 19:05:
> i cannot get imap to pass the realm either in the userid or realm field
> to saslauthd.
saslauthd runs with parameter "-r"?
Alexander
--
Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773
legal statement: http
hi all,
no joy even after googling for hours and looking thru the archives ...
i cannot get imap to pass the realm either in the userid or realm field
to saslauthd.
i can successfully authenticate [EMAIL PROTECTED] using testsaslauthd,
however, imtest test fails and debugging saslauthd does not
On Tuesday 21 February 2006 03:00, Sebastian Hagedorn wrote:
> --On 20. Februar 2006 22:08:04 -0600 Eric Renfro <[EMAIL PROTECTED]> wrote:
> > Hello. I'm having a problem with Cyrus-IMAPD 2.2.12 with Cyrus-SASL
> > 2.1.19's saslauthd.
> >
> > When I lo
--On 20. Februar 2006 22:08:04 -0600 Eric Renfro <[EMAIL PROTECTED]> wrote:
Hello. I'm having a problem with Cyrus-IMAPD 2.2.12 with Cyrus-SASL
2.1.19's saslauthd.
When I login using the LOGIN method, I see saslauthd doing it's lookup,
and OpenLDAP logs show it
Hello. I'm having a problem with Cyrus-IMAPD 2.2.12 with Cyrus-SASL 2.1.19's
saslauthd.
When I login using the LOGIN method, I see saslauthd doing it's lookup, and
OpenLDAP logs show it as well, and it's all successfull. However, when trying
to do a PLAIN, DIGEST-MD5, or
On Thu, 26 Jan 2006, Patrick T. Tsang wrote:
Hello,
I have seen there are some parameters in /etc/imapd.conf for LDAP connection.
However I cannot see any for user password login.
This is for ptloader (authorization module)
How can I connect to LDAP server without saslauthd?
ldapdb
> I have seen there are some parameters in /etc/imapd.conf for
> LDAP connection. How can I connect to LDAP server without
saslauthd?
And once you connected, what can you actually do with it? What
feature does the LDAP connection support?
Hello,
I have seen there are some parameters in
/etc/imapd.conf for LDAP connection.
However I cannot see any for user password
login.
How can I connect to LDAP server without
saslauthd?
Regards
Patrick
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http
> >> We have the following set in the imapd.conf for 2.3.1 install:
> >> virtdomains: on
> >> admins: globaladmin [EMAIL PROTECTED]
> >> defaultdomain: xyz.com
> >>
> >> and in saslauthd.conf:
> >> ldap_default_realm: xyz.com
> >>
> >> Following cyradm logins fail for the 'globaladmin', whether or
On Thu, 29 Dec 2005 [EMAIL PROTECTED] wrote:
We have the following set in the imapd.conf for 2.3.1 install:
virtdomains: on
admins: globaladmin [EMAIL PROTECTED]
defaultdomain: xyz.com
and in saslauthd.conf:
ldap_default_realm: xyz.com
Following cyradm logins fail for the 'globaladmin', whethe
> We have the following set in the imapd.conf for 2.3.1 install:
> virtdomains: on
> admins: globaladmin [EMAIL PROTECTED]
> defaultdomain: xyz.com
>
> and in saslauthd.conf:
> ldap_default_realm: xyz.com
>
> Following cyradm logins fail for the 'globaladmin', whether or not
> FQDN is passed as a
Hello,
We have the following set in the imapd.conf for 2.3.1 install:
virtdomains: on
admins: globaladmin [EMAIL PROTECTED]
defaultdomain: xyz.com
and in saslauthd.conf:
ldap_default_realm: xyz.com
Following cyradm logins fail for the 'globaladmin', whether or not
FQDN is passed as an option of
Am Mi, den 07.12.2005 schrieb Joseph Silverman um 1:03:
> Using cyrus-imapd on linux (fc3) - also using sendmail (not postfix):
>
> 1) /etc/sysconfig/saslauthd: MECH=pam
>
> 2) /etc/imapd.conf - no auxprocfunc or anything along those lines
>
> So, HOW COME I get tons
Using cyrus-imapd on linux (fc3) - also using sendmail (not postfix):
1) /etc/sysconfig/saslauthd: MECH=pam
2) /etc/imapd.conf - no auxprocfunc or anything along those lines
So, HOW COME I get tons of these in /var/log/messages? (also from
lmtpd, pop3, imaps)
Dec 6 15:58:49 hedwig pop3s
I've asked similar question over in cyrus-sasl but that's about postfix,
this is about cyrus itself.
What's the current state of how to tell cyrus to authenticate using mysql?
In the past it seems the combination was to have cyrus call saslauthd, which
is turn uses PAM via p
2005/8/8, Andrzej Kwiatkowski <[EMAIL PROTECTED]>:
> Hello.
>
> I've found that saslauthd is doing native authentication only in LDAP.
> Mysql i Pgsql authentication can't be done by saslauthd.
> Is one interested in using such configuration ?
>
> Now i'
thx in advance!
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
tware: http://oss.netfarm.it/
Index: saslauthd/auth_sasldb.c
===
RCS file: /cvs/src/sasl/saslauthd/auth_sasldb.c,v
retrieving revision 1.5
diff -u -r1.5 auth_sasldb.c
--- saslauthd/auth_sasldb.c 27 Jul 2002 18:44:46 - 1.5
++
lugin, that can be used to
authenticate against the passwords stored in /etc/sasldb2. Since
other mechanisms also use this database for passwords, using
this method will allow SASL to provide a uniform password
database to a large number of mechanisms.
saslauthd
con
]> wrote:
> > You are mixing auxprop and saslauthd methods. It looks like your
> > saslauthd is using pam database, which is really different
> > from /etc/sasldb2
> >
> > I recommend you to read carefully documentation to Cyrus IMAP and Cyrus
> > SASL (
Pardon - I mentioned the wrong file name. I meant /etc/sysconfig/saslauthd.
Rgrds
On 8/23/05, Gobbledegeek <[EMAIL PROTECTED]> wrote:
> > You are mixing auxprop and saslauthd methods. It looks like your
> > saslauthd is using pam database, which is really different
>
On Mon, 2005-08-22 at 16:57 +0530, Gobbledegeek wrote:
> Hello
>I reinstalled cyrus-imapd, after deleting spool/imap and
> lib/imap folders. Now again I'm struggling with getting saslauthd to
> work with cyrus. I managed to get root and cyrus user successfully
> logi
1 - 100 of 422 matches
Mail list logo
