>> auth: in openpam_parse_chain(): /etc/pam.d/dovecot(1): missing or invalid facility > > I do not think that it has something to do with the dovecot settings > itself but perhaps with the pam facility settings instead?i can believe that. any clues to debug? randy
What is in the pam.d/dovecot file? (Remember to strip passwords if included) Cheers, Remko Lodder /* sent from my phone and thus brief and to the point *\ Op 3 aug. 2017 om 15:08 heeft Randy Bush <randy at psg.com> het volgende geschreven:>>> auth: in openpam_parse_chain(): /etc/pam.d/dovecot(1): missing or invalid facility >> >> I do not think that it has something to do with the dovecot settings >> itself but perhaps with the pam facility settings instead? > > i can believe that. any clues to debug? > > randy
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 3 Aug 2017, Randy Bush wrote:> Date: Thu, 03 Aug 2017 22:08:22 +0900 > From: Randy Bush <randy at psg.com> > To: Remko Lodder <remko at FreeBSD.org> > Cc: Christian Kivalo <ml+dovecot at valo.at>, dovecot at dovecot.org > Subject: Re: pam auth problem > >>> auth: in openpam_parse_chain(): /etc/pam.d/dovecot(1): missing or invalid facility >> >> I do not think that it has something to do with the dovecot settings >> itself but perhaps with the pam facility settings instead? > > i can believe that. any clues to debug?do you have a /etc/pam.d/dovecot file, does it define all necessary settings? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBWYMiAHz1H7kL/d9rAQLmcAgArM/RKrUk2g3MUWN7O51VZ4wIBXL0aIwh EqyG7Tj7CnWPWu+sZY64omu6beoD6WC3ThfRkY2uAWEP9MKGU6Nt9W6vZSsLdDeH cegMSHnfW19YZefiIhlYMZJHC7pyn2sEslS3iTkDNjja6FSoVbW/Qr+SUri9Gd5h rHF/DOUtLbLugrQymWe2KO2pJaL+WZvwhd4FP66pOlr+njEkxRfNjCQQx6L9kM7m Muq4beU9WvHFB6cXYxv1bGyxvLU1Y02YaAFVQAiKRVicNfBXo7RLXj1duQADtWqK 1tB60TVAFhREKR5Mu0tq3xRYuwYQc0tNVbuP1KrjfOTtJ9NLpeDE+g==9LWc -----END PGP SIGNATURE-----
> What is in the pam.d/dovecot file? (Remember to strip passwords if > included)# cat /etc/pam.d/dovecot passdb { driver = pam # args = failure_show_msg=yes # args = max_requests=12 args = %s } and /etc/pam.d/{imap,pop3} were untouched; both as follows # # $FreeBSD: releng/10.3/etc/pam.d/pop3 170771 2007-06-15 11:33:13Z yar $ # # PAM configuration for the "pop3" service # # auth #auth sufficient pam_krb5.so no_warn try_first_pass #auth sufficient pam_ssh.so no_warn try_first_pass auth required pam_unix.so no_warn try_first_pass # account #account required pam_nologin.so account required pam_unix.so