Re: trouble with auths on cyrus imap
I tried your suggestion. I added to pam.conf imapauthrequiredpam_unix.so try_first_pass imapaccount requiredpam_unix.so imappassword required pam_permit.so imapsession requiredpam_permit.so still can't authenticate. jg On Wed, 2003-01-08 at 11:35, Erik Enge wrote: jonathan giles [EMAIL PROTECTED] writes: Jan 7 14:20:10 popper2 saslauthd[113]: AUTHFAIL: user=user service=imap realm= [PAM auth error] I believe I had the same problem until I added /etc/pam.d/imap with the contents just like my /etc/pam.d/sshd (IIRC). Erik. -- Jonathan Giles Senior Unix Administrator Cline Davis Mann, Inc. -- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail of this kind. Opinions, conclusions, and other information in this message that do not relate to the official business of CDM shall be understood as neither given nor endorsed by it.
Re: trouble with auths on cyrus imap
Just tried that and it didn't help. Thanks for the help, tho. jg On Wed, 2003-01-08 at 12:39, Ken Murchison wrote: jonathan giles wrote: Hi: I have been looking around for the answer to this, and have not found it. I am running... 4.7-RELEASE FreeBSD with... cyrus-imapd-2.1.10 cyrus-sasl-2.1.9_1 installed as ports. Compilation and installation seems fine but... I trying to authenticate with the standard shadow password, but keep getting this in the log... Jan 7 14:20:10 popper2 saslauthd[113]: AUTHFAIL: user=user service=imap realm= [PAM auth error] Jan 7 14:20:10 popper2 imapd[158]: badlogin: localhost.clinedavis.com[127.0.0.1] plaintext user SASL(-13): authentication failure: checkpass failed imapd.conf includes the following... sasl_pwcheck_method: saslauthd saslauthd is started using -a pam in /usr/local/etc/rc.d/saslauthd.sh I checked the processes, and it shows up. /etc/pam.conf is standard conf for FreeBSD with only one line for imap... imapauthrequiredpam_unix.so try_first_pass try adding: imap account sufficient pam_permit.so -- Kenneth Murchison Oceana Matrix Ltd. Software Engineer 21 Princeton Place 716-662-8973 x26 Orchard Park, NY 14127 --PGP Public Key--http://www.oceana.com/~ken/ksm.pgp -- Jonathan Giles Senior Unix Administrator Cline Davis Mann, Inc. -- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail of this kind. Opinions, conclusions, and other information in this message that do not relate to the official business of CDM shall be understood as neither given nor endorsed by it.
trouble with auths on cyrus imap
Hi: I have been looking around for the answer to this, and have not found it. I am running... 4.7-RELEASE FreeBSD with... cyrus-imapd-2.1.10 cyrus-sasl-2.1.9_1 installed as ports. Compilation and installation seems fine but... I trying to authenticate with the standard shadow password, but keep getting this in the log... Jan 7 14:20:10 popper2 saslauthd[113]: AUTHFAIL: user=user service=imap realm= [PAM auth error] Jan 7 14:20:10 popper2 imapd[158]: badlogin: localhost.clinedavis.com[127.0.0.1] plaintext user SASL(-13): authentication failure: checkpass failed imapd.conf includes the following... sasl_pwcheck_method: saslauthd saslauthd is started using -a pam in /usr/local/etc/rc.d/saslauthd.sh I checked the processes, and it shows up. /etc/pam.conf is standard conf for FreeBSD with only one line for imap... imapauthrequiredpam_unix.so try_first_pass /usr/local/lib/sasl2/Cyrus.conf has... pwcheck_method: saslauthd it did have pwcheck_method: pwcheck but I changed it based on the notes that came off standard output during compilation. I have tried changing saslauthd to start with -a shadow, but it does not recognize the service. My understanding of this is that imap uses saslauthd for auth, saslauthd is looking, or should be looking at pam, and pam has a service (imap) configured for auths. However, it doesn't work. I am very new to pam, but would like to get it to work so I can do ldap auths instead of shadow auths. Any help, pointers to howtos, suggestions would be greatly appreciated. Thanks! jg -- Jonathan Giles Senior Unix Administrator Cline Davis Mann, Inc. -- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail of this kind. Opinions, conclusions, and other information in this message that do not relate to the official business of CDM shall be understood as neither given nor endorsed by it.
Procmail - deliver problems
Hello: Currently trying to get cyrus-imapd-2.0.16_1 cyrus-sasl-1.5.24_7 procmail-3.21 sendmail-8.11.6 to work nicely with on another, and having big problems with procmail - deliver. I can't seem to solve this data format error, even though I have tried a number of things listed here on the mailing list. Could someone here please tell me how they are working it out, some sample configs, etc. I would really like to get this to work, as I am enjoy working with cyrus. BTW cyrus imap without procmail does work when making the recommended changes to the sendmail.mc file. Please help. Thanks, jg -- Jonathan Giles Senior Unix Administrator Cline Davis Mann, Inc. -- Privileged/Confidential Information may be contained in this message. If you are not the addressee indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply e-mail. Please advise immediately if you or your employer do not consent to Internet e-mail of this kind. Opinions, conclusions, and other information in this message that do not relate to the official business of CDM shall be understood as neither given nor endorsed by it.
