Date: Wed, 9 Sep 2020 07:43:18 -0400 From: Jerry <jerry@seibercom.net> To: "User Questions" <freebsd-questions@freebsd.org> Subject: Re: Postfix-sasl on FreeBSD will not authenticate Message-ID: <20200909074318.4cf75f6d@scorpio.seibercom.net> In-Reply-To: <alpine.BSF.2.21.9999.2009082208030.33406@fledge.watson.org> References: <523ffb82f14da9944a5368f28eddecac.squirrel@webmail.harte-lyne.ca> <0970ea44-1438-171a-4f44-221c4f9facd4@nethead.se> <c0b3c010829d6ce19e25cead6176d5de.squirrel@webmail.harte-lyne.ca> <alpine.BSF.2.21.9999.2009082208030.33406@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--Sig_/=1V9ilOS5OtX_Lcd6sFjnJ= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 8 Sep 2020 22:12:50 +0000 (UTC), doug@safeport.com stated: >On Tue, 3 Jul 2018, James B. Byrne via freebsd-questions wrote: > >> On Tue, July 3, 2018 18:12, Per olof Ljungmark wrote: =20 >>> >>> On 07/03/18 22:39, James B. Byrne via freebsd-questions wrote: =20 >>>> On server A we have cyrus-imapd running with spiped listening on >>>> TCP:143. On server B we have postfix-sasl-3.3.0 running with >>>> spiped listening on TCP:143 linked to server A. >>>> >>>> On server A saslauthd is configured in rc.conf to use rimap to the >>>> localhost: >>>> >>>> saslauthd_flags=3D"-a rimap \ >>>> -O localhost" # Use Remote IMAP to authenticat >>>> >>>> Postfix is configured to use saslauth to authenticate outgoing >>>> senders: >>>> >>>> smtpd_sasl_auth_enable =3D yes >>>> smtpd_sasl_authenticated_header =3D no >>>> smtpd_sasl_exceptions_networks =3D >>>> smtpd_sasl_local_domain =3D >>>> smtpd_sasl_path =3D smtpd >>>> smtpd_sasl_security_options =3D noanonymous >>>> smtpd_sasl_service =3D smtp >>>> smtpd_sasl_tls_security_options =3D $smtpd_sasl_security_options >>>> smtpd_sasl_type =3D cyrus >>>> >>>> But I cannot find any such file named smtpd.conf which, according >>>> to the Postfix documentation, should exist and should contain: >>>> >>>> pwcheck_method: saslauthd >>>> mech_list: PLAIN >>>> >>>> It appears to me that postfix is directly looking in >>>> /usr/local/etc/sasldb2.db itself and, finding no entries, failing >>>> to authenticate. How do I tell postfix to use the saslauthd daemon >>>> instead? >>>> =20 >>> >>> You must create the file yourself and adjust it to whatever mech you >>> use, in our case it is saslauthd: >>> >>> cat /usr/local/lib/sasl2/smtpd.conf >>> pwcheck_method: saslauthd >>> mech_list: plain login >> >> Thank you. Do you know where the path to the file location is >> specified in the FreeBSD documentation? =20 > >It is in the postfix docs. As I recall it says put it in ../sasls (or >some such). This question really belongs on the Postfix forum. In any case, have you investigated: http://www.postfix.org/DEBUG_README.html http://www.postfix.org/DEBUG_README.html#mail http://www.postfix.org/SASL_README.html I would highly recommend the following two suggestions: Better, provide output from the postfinger tool. This can be found at http://ftp.wl0.org/SOURCES/postfinger. If the problem is SASL related, consider including the output from the saslfinger tool. This can be found at http://postfix.state-of-mind.de/patrick.koetter/saslfinger/. --=20 Jerry --Sig_/=1V9ilOS5OtX_Lcd6sFjnJ= Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEIQb/tTwl6I1ueEVtOHMGOIfexWQFAl9Yv9YACgkQOHMGOIfe xWTUiAf9HF/71PhtCP7ZDTUiDk4VLIeCy4oGpqPgxwR4/khFfk9qYOUp6q7T8Auj yAvBKWcXPxL6YrE3BN3y8MRpKAL0w0kV0GTUw0/d0hChotz7s52sla6NG6/bkF1q cPK+U3JUXORCLUoD57JtS1kYqUiZamY9f6bndXEtBK1BCz4xD1F9Brsi+18owKUy FclLYbpULCobu41DS9r84xerAbKHqAjpH5t738m8j8o1W5uI+nYOeT4Q7n1/vMGR e/BhpFHNE3d59oIT6CddYOVlF8lDSei6pNZbMDjkel0EzOIXuFIhBh79FRfpq/7W LroTUJrW1t20aoI9fBUO3SdUniJ17Q== =YT75 -----END PGP SIGNATURE----- --Sig_/=1V9ilOS5OtX_Lcd6sFjnJ=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20200909074318.4cf75f6d>