[pfx] Re: Intermittent fatal: no SASL authentication mechanisms

First, why use SASL auth? It needs a database. Have you considered more scalable alternatives such as TLS client certificates? Postfix can use certificate fingerprints instead of PKI. Second, if you must use SASL auth: What is the authentication backend database query latency? Have you looked

[pfx] Re: Intermittent fatal: no SASL authentication mechanisms

First, why use SASL auth? It needs a database. Have you considered more scalable alternatives such as TLS client certificates? Postfix can use certificate fingerprints instead of PKI. Second, if you must use SASL auth: What is the authentication backend database query latency? Have you looked at

[pfx] Re: Intermittent fatal: no SASL authentication mechanisms

Some feedback. It may be possible that you're running out of file handles, either the kernel limit, or the per-process limit. I did not have time to actively check this. postconf "max_use = 10" postfix reload Error fatal: no SASL authentication mechanisms and postf

[pfx] Re: Intermittent fatal: no SASL authentication mechanisms

Wietse Venema via Postfix-users: > Stuart Armstrong via Postfix-users: > > Thank you for your response. For clarity, this issue has been present > > for several weeks now. > > > > > warning: SASL: Connect to Dovecot auth socket 'private/auth' > > > failed: REASON FOR FAILURE HERE > > I do

[pfx] Re: Intermittent fatal: no SASL authentication mechanisms

Stuart Armstrong via Postfix-users: > Thank you for your response. For clarity, this issue has been present > for several weeks now. > > > warning: SASL: Connect to Dovecot auth socket 'private/auth' > > failed: REASON FOR FAILURE HERE > I do not have this warning in the logs. All the d

[pfx] Re: Intermittent fatal: no SASL authentication mechanisms

Thank you for your response. For clarity, this issue has been present for several weeks now. warning: SASL: Connect to Dovecot auth socket 'private/auth' failed: REASON FOR FAILURE HERE I do not have this warning in the logs. Can you try these commands: postconf "max_use =

[pfx] Re: Intermittent fatal: no SASL authentication mechanisms

Stuart Armstrong via Postfix-users: > Hello, > > Currently our Postfix server is experiencing a problem with intermittent > SASL auth problems. With all the useless debug logging you forgot to include this important log message: warning: SASL: Connect to Dovecot auth socket 'private/auth'

[pfx] Intermittent fatal: no SASL authentication mechanisms

Hello, Currently our Postfix server is experiencing a problem with intermittent SASL auth problems. This mail server worked well up to a point, when the "fatal: no SASL authentication mechanisms" errors started. From this point I started researching and changing the m

Re: Fatal: no SASL authentication mechanisms

Ken Wright: > > There are many other possibilities.? Perhaps, instead of doing all > > the integration work yourself, you may be better off with a "turnkey" > > email server such as ? > > If I don't do the work, how will I learn? You learn by starting with a WORKING syst

Re: Fatal: no SASL authentication mechanisms

On Tue, 2022-01-04 at 22:58 -0500, Jim Popovitch wrote: > Those lines above look debian'ish to me.  If you are running debian, > then make sure you have libsasl2-2, libsasl2-modules and libsasl2- > modules-db installed. Definitely debian-ish. Ubuntu. 20.04, to be specific. I checked, and those l

Re: Fatal: no SASL authentication mechanisms

On Tue, 2022-01-04 at 21:14 -0500, Ken Wright wrote: > flags=DRhu > user=vmail argv=/usr/bin/maildrop -d ${recipient} > uucp unix - n n - - pipe > flags=Fqhu > user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) > ifmail unix -

Re: Fatal: no SASL authentication mechanisms

On Tue, 2022-01-04 at 22:29 -0500, post...@ptld.com wrote: > > That's what I have, except my passdb driver is sql.  Could that be > > the problem? > > > Following the lines of what Viktor said about creating the auth socket. > You only confirmed you have the service auth{...} in dovecot config. >

Re: Fatal: no SASL authentication mechanisms

> That's what I have, except my passdb driver is sql. Could that be the > problem? Following the lines of what Viktor said about creating the auth socket. You only confirmed you have the service auth{...} in dovecot config. Did you confirm the socket is being physically created? If there are p

Re: Fatal: no SASL authentication mechanisms

> That's what I have, except my passdb driver is sql. Could that be the > problem? To test if you have dovecot configured correctly for auth you can use the doveadm tool. Examples: doveadm auth lookup doveadm auth test

Re: Fatal: no SASL authentication mechanisms

On Tue, Jan 04, 2022 at 09:57:55PM -0500, Ken Wright wrote: > > Is "Dovecot" configured to create the /var/spool/postfix/private/auth > > socket?  Did that happen?  Is "Dovecot" willing to support the > > expected SASL mechanisms (typically "PLAIN")? > > > > I have: > > > >     service auth { >

Re: Fatal: no SASL authentication mechanisms

On Tue, 2022-01-04 at 21:37 -0500, Viktor Dukhovni wrote: > > Is "Dovecot" configured to create the /var/spool/postfix/private/auth > socket?  Did that happen?  Is "Dovecot" willing to support the > expected SASL mechanisms (typically "PLAIN")? > > I have: > >     service auth { >   unix_lis

Re: Fatal: no SASL authentication mechanisms

On Tue, Jan 04, 2022 at 09:14:45PM -0500, Ken Wright wrote: > > > Jan  4 19:08:47 grace postfix/smtps/smtpd[17286]: fatal: no SASL > > > authentication mechanisms > > > > The selected SASL backend (Cyrus or Dovecot) is not configured to > > support any usabl

Re: Fatal: no SASL authentication mechanisms

On Tue, 2022-01-04 at 20:49 -0500, Viktor Dukhovni wrote: > On Tue, Jan 04, 2022 at 07:20:43PM -0500, Ken Wright wrote: > > > My Postfix woes continue.  Now I'm getting this error message: > > > > Jan  4 19:08:47 grace postfix/smtps/smtpd[17286]: fatal: no SASL

Re: Fatal: no SASL authentication mechanisms

On Tue, Jan 04, 2022 at 07:20:43PM -0500, Ken Wright wrote: > My Postfix woes continue. Now I'm getting this error message: > > Jan 4 19:08:47 grace postfix/smtps/smtpd[17286]: fatal: no SASL > authentication mechanisms The selected SASL backend (Cyrus or Dovecot) is not conf

Re: Fatal: no SASL authentication mechanisms

On 05/01/2022 10:50 am, Ken Wright wrote: > Jan 4 19:08:47 grace postfix/smtps/smtpd[17286]: fatal: no SASL > authentication mechanisms > > This is starting to get old. Posting your running config might get you some help Ken. Expecting good help otherwise may be a long shot. Mal

Fatal: no SASL authentication mechanisms

My Postfix woes continue. Now I'm getting this error message: Jan 4 19:08:47 grace postfix/smtps/smtpd[17286]: fatal: no SASL authentication mechanisms This is starting to get old. Ken

Re: fatal: no SASL authentication mechanisms

Thank you for the notification, Bernardo, but that mail server has been offline for some time now. It used to be a backup server which is no longer required. I left it live for the "benefit" of spammers. :) -- Dave Stiles

Re: fatal: no SASL authentication mechanisms

Hello, I'm not sure if you'll receive this message, so I send to the list as well. (and excuse me for top-posting, but this e-mail has no direct relevance to this thread..) Your server is refusing connections on port 25, so this, inter alia, prevents my server from sending you the DMARC repor

Re: fatal: no SASL authentication mechanisms

Wietse, thank you for your assistance. I tried removing (separately) unix_listener and unix_listener auth-userdb but neither cured the problem so they are now both reinstated. Apart from two connection messages in the log, the three lines I quoted are the only ones following a restart and are

Re: fatal: no SASL authentication mechanisms

Linkcheck: > Sorry Wietse, I thought it might be the other way around: postfix > wasn't picking up the dovecot reference. There is a real protocol between Postfix and Dovecot. Postfix will complain when it is unable to speak that protocol with Dovecot, or when it receives an unexpected response.

Re: fatal: no SASL authentication mechanisms

Maybe you can ask on the DOVECOT list why DOVECOT isn't providing Postfix with SASL mechanism names. Wietse

fatal: no SASL authentication mechanisms

which receives a lot of spam but that suddenly ceased. I actually get a triplet of error messages in the logs for every email: postfix/smtpd[54380]: fatal: no SASL authentication mechanisms postfix/master[54208]: warning: process /usr/lib/postfix/sbin/smtpd pid 54380 exit status 1 postfix/master[

Re: fatal: no SASL authentication mechanisms

Edgar Pettijohn skrev den 2015-01-18 15:07: I think its default in a lot of distros. I know it is in openbsd and I'm pretty sure freebsd also. its not so in gentoo, living on edge ? :=)

Re: fatal: no SASL authentication mechanisms

James Lockie skrev den 2015-01-18 05:40: On 01/17/15 22:55, Viktor Dukhovni wrote: On Sat, Jan 17, 2015 at 10:51:30PM -0500, James Lockie wrote: /var/log/mail.log postfix/smtpd[1519]: warning: SASL: Connect to /var/spool/postfix/private/auth failed: No such file or directory /etc/postfix/ma

Re: chroot defaults (was: fatal: no SASL authentication mechanisms)

On 01/18/15 10:57, Wietse Venema wrote: >> better make a bugreport at your distribution >> https://www.google.at/search?q=postfix+debian+chroot+problems > Scott K: >> Assuming this is Debian, there's no bug report needed. It's an >> intentional maintainer choice and not a bug. > Edgar Pettijohn: >

chroot defaults (was: fatal: no SASL authentication mechanisms)

> better make a bugreport at your distribution > https://www.google.at/search?q=postfix+debian+chroot+problems Scott K: > Assuming this is Debian, there's no bug report needed. It's an > intentional maintainer choice and not a bug. Edgar Pettijohn: > I think its default in a lot of distros. I kn

Re: fatal: no SASL authentication mechanisms

On 01/18/15 10:03, Edgar Pettijohn wrote: > > On 01/18/15 08:55, James Lockie wrote: >> On 01/18/15 09:07, Edgar Pettijohn wrote: > better make a bugreport at your distribution > https://www.google.at/search?q=postfix+debian+chroot+problems Assuming this is Debian, there's no bug repo

Re: fatal: no SASL authentication mechanisms

On 01/18/15 08:55, James Lockie wrote: On 01/18/15 09:07, Edgar Pettijohn wrote: better make a bugreport at your distribution https://www.google.at/search?q=postfix+debian+chroot+problems Assuming this is Debian, there's no bug report needed. It's an intentional maintainer choice and not a bu

Re: fatal: no SASL authentication mechanisms

* James Lockie : > > On 01/18/15 09:07, Edgar Pettijohn wrote: > > > >>> better make a bugreport at your distribution > >>> https://www.google.at/search?q=postfix+debian+chroot+problems > >> Assuming this is Debian, there's no bug report needed. It's an intentional > >> maintainer choice and not

Re: fatal: no SASL authentication mechanisms

On 01/18/15 09:07, Edgar Pettijohn wrote: > >>> better make a bugreport at your distribution >>> https://www.google.at/search?q=postfix+debian+chroot+problems >> Assuming this is Debian, there's no bug report needed. It's an intentional >> maintainer choice and not a bug. >> >> Scott K >> > I thi

Re: fatal: no SASL authentication mechanisms

better make a bugreport at your distribution https://www.google.at/search?q=postfix+debian+chroot+problems Assuming this is Debian, there's no bug report needed. It's an intentional maintainer choice and not a bug. Scott K I think its default in a lot of distros. I know it is in openbsd and

Re: fatal: no SASL authentication mechanisms

Am 18.01.2015 um 06:14 schrieb Viktor Dukhovni: On Sun, Jan 18, 2015 at 12:02:24AM -0500, Scott Kitterman wrote: better make a bugreport at your distribution https://www.google.at/search?q=postfix+debian+chroot+problems Assuming this is Debian, there's no bug report needed. It's an intentiona

Re: fatal: no SASL authentication mechanisms

On Sun, Jan 18, 2015 at 12:02:24AM -0500, Scott Kitterman wrote: > >better make a bugreport at your distribution > >https://www.google.at/search?q=postfix+debian+chroot+problems > > Assuming this is Debian, there's no bug report needed. It's an intentional > maintainer choice and not a bug. I t

Re: fatal: no SASL authentication mechanisms

On January 17, 2015 11:58:16 PM EST, "li...@rhsoft.net" wrote: > >Am 18.01.2015 um 05:40 schrieb James Lockie: >> On 01/17/15 22:55, Viktor Dukhovni wrote: >>> On Sat, Jan 17, 2015 at 10:51:30PM -0500, James Lockie wrote: >>> /var/log/mail.log postfix/smtpd[1519]: warning: SASL: Connect

Re: fatal: no SASL authentication mechanisms

Am 18.01.2015 um 05:40 schrieb James Lockie: On 01/17/15 22:55, Viktor Dukhovni wrote: On Sat, Jan 17, 2015 at 10:51:30PM -0500, James Lockie wrote: /var/log/mail.log postfix/smtpd[1519]: warning: SASL: Connect to /var/spool/postfix/private/auth failed: No such file or directory /etc/postfi

Re: fatal: no SASL authentication mechanisms

On 01/17/15 22:55, Viktor Dukhovni wrote: > On Sat, Jan 17, 2015 at 10:51:30PM -0500, James Lockie wrote: > >> /var/log/mail.log >> postfix/smtpd[1519]: warning: SASL: Connect to >> /var/spool/postfix/private/auth failed: No such file or directory >> >> /etc/postfix/master.cf >> submission inet n

Re: fatal: no SASL authentication mechanisms

On Sat, Jan 17, 2015 at 10:51:30PM -0500, James Lockie wrote: > /var/log/mail.log > postfix/smtpd[1519]: warning: SASL: Connect to > /var/spool/postfix/private/auth failed: No such file or directory > > /etc/postfix/master.cf > submission inet n - - - - smtpd -v >

fatal: no SASL authentication mechanisms

think): # doveadm auth -a /var/spool/postfix/private/auth test_user Password: passdb: test_user auth succeeded extra fields: user=test_user These are the relevant log entries: /var/log/mail.err postfix/smtpd[1704]: fatal: no SASL authentication mechanisms /var/log/mail.log postfix/smtpd[1519]: warning:

Re: fatal: no SASL authentication mechanisms

On 1/29/2013 12:13 PM, FigureoTV SFM wrote: > On Sun, Jan 27, 2013 at 12:05 PM, Erwan David wrote: >> Le 27/01/2013 16:14, FigureoTV SFM a écrit : >> >>> Hello. >>> >>> I'm a postfix newbie and experiencing a lot of problems trying to get >>> to run smoothly as it was on my previous server. >>> >>

Re: fatal: no SASL authentication mechanisms

On Sun, Jan 27, 2013 at 12:05 PM, Erwan David wrote: > Le 27/01/2013 16:14, FigureoTV SFM a écrit : > >> Hello. >> >> I'm a postfix newbie and experiencing a lot of problems trying to get >> to run smoothly as it was on my previous server. >> >> I don't know what's causing these errors: >> >> Jan

Re: fatal: no SASL authentication mechanisms

On Sun, 27 Jan 2013 11:58:45 -0400 FigureoTV SFM articulated: > Links broken. 1) Please don't "top post". 2) The links are working fine here. -- Jerry ✌ postfix-u...@seibercom.net _ TO REPORT A PROBLEM see http://www.postfix.o

Re: fatal: no SASL authentication mechanisms

Le 27/01/2013 16:14, FigureoTV SFM a écrit : Hello. I'm a postfix newbie and experiencing a lot of problems trying to get to run smoothly as it was on my previous server. I don't know what's causing these errors: Jan 27 15:07:40 hawk084 postfix/smtpd[13897]: connect from unknown[190.80.213.58]

Re: fatal: no SASL authentication mechanisms

Links broken. hawk084:~# postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no config_directory = /etc/postfix content_filter = smtp-amavis:[127.0.0.1]:10024 inet_interfaces = all mail_owner = postfix mailbox_command = procmail -a "$EXTEN

Re: fatal: no SASL authentication mechanisms

On Sun, 27 Jan 2013 11:14:48 -0400 FigureoTV SFM articulated: > Hello. > > I'm a postfix newbie and experiencing a lot of problems trying to get > to run smoothly as it was on my previous server. http://www.postfix.com/DEBUG_README.html#mail Specifically: Output from "postconf -n". Please do n

fatal: no SASL authentication mechanisms

fix/smtpd[13897]: warning: SASL: Connect to private/auth failed: Connection refused Jan 27 15:07:40 hawk084 postfix/smtpd[13897]: fatal: no SASL authentication mechanisms Jan 27 15:07:41 hawk084 postfix/master[17615]: warning: process /usr/lib/postfix/smtpd pid 13896 exit status 1 Jan 27 15:07:41

Re: Fatal: No SASL Authentication Mechanisms Error

nied > Aug 21 19:08:46 localhost postfix/smtpd[26252]: fatal: no SASL > authentication mechanisms > Aug 21 19:08:47 localhost postfix/master[26226]: warning: process > /usr/libexec/postfix/smtpd pid 26252 exit status 1 > Aug 21 19:08:47 localhost postfix/master[26226]: warning: &g

Fatal: No SASL Authentication Mechanisms Error

l s_client -starttls smtp -connect localhost:25 Aug 21 19:08:46 localhost postfix/smtpd[26252]: connect from localhost[::1] Aug 21 19:08:46 localhost postfix/smtpd[26252]: warning: SASL: Connect to private/auth failed: Permission denied Aug 21 19:08:46 localhost postfix/smtpd[26252]: fatal: no SASL auth

Re: fatal: no SASL authentication mechanisms

* Jeff Lacki : > >> Are these yum packages (which I tried under the names above > >> with no luck)? Where do I acquire them? > > > For which SASL provider? > > Im assuming digest-md5 is good enough, unless > you think another mechanism is better? plain and login are plaintext mechanisms. You ca

Re: fatal: no SASL authentication mechanisms

>> Are these yum packages (which I tried under the names above >> with no luck)? Where do I acquire them? > For which SASL provider? Im assuming digest-md5 is good enough, unless you think another mechanism is better? Jeff

Re: fatal: no SASL authentication mechanisms

* Jeff Lacki : > >> smtpd_sasl_security_options = noanonymous, noplaintext > >> smtpd_tls_sasl_security_options = noanonymous > >> SMTPD crashed. I really can't understand where is a problem. > > > Blind guess: There are no other mechanisms installed. > > > If that doesn't fix it, send debug outp

Re: fatal: no SASL authentication mechanisms

>> smtpd_sasl_security_options = noanonymous, noplaintext >> smtpd_tls_sasl_security_options = noanonymous >> SMTPD crashed. I really can't understand where is a problem. > Blind guess: There are no other mechanisms installed. > If that doesn't fix it, send debug output. Dumb question Im sure, b

Re: fatal: no SASL authentication mechanisms

* Неворотин Вадим : > I have same problem. When I try to add smtpd_sasl_security_options = > noanonymous, noplaintext to my config smptd start to say FATAL ERROR))) Auth > throw dovecot, works perfectly with > > smtpd_tls_auth_only = yes > > but then I only replace it with > > smtpd_sasl_securit

Re: fatal: no SASL authentication mechanisms

* Jeff Lacki : > > Im trying to setup SASL+TLS+dovecot. Overall Ive > gotten things somewhat working, but have a couple questions > since Im new to this aspect of postfix. > > I get 'fatal: no SASL authentication mechanisms' in maillog > I ran saslfinger and i

Re: fatal: no SASL authentication mechanisms

On Thu, Feb 11, 2010 at 06:22:55PM -0800, Jeff Lacki wrote: > > >> smtpd_tls_auth_only = yes > > > > > Do you know what this parameter setting does? > > After hours of digging into this, that particular message > seems to have come up because I didnt want plaintext > coming across in the smtp con

Re: fatal: no SASL authentication mechanisms

> >> smtpd_tls_auth_only = yes > > > Do you know what this parameter setting does? > After hours of digging into this, that particular message seems to have come up because I didnt want plaintext coming across in the smtp connection so I set: smtpd_sasl_security_options = noanonymous, n

Re: fatal: no SASL authentication mechanisms

On Thu, Feb 11, 2010 at 03:55:52PM -0800, Jeff Lacki wrote: > >> smtpd_tls_auth_only = yes > > > Do you know what this parameter setting does? > > Not exactly, Ive been reading all kinds of docs and since > Im new to some of it, Im a little confused between > SASL and TLS. I've used postfix for

Re: fatal: no SASL authentication mechanisms

Jeff Lacki: > >> I get 'fatal: no SASL authentication mechanisms' in maillog > > >> smtpd_tls_auth_only = yes > > > Do you know what this parameter setting does? > > Not exactly, Ive been reading all kinds of docs and since > Im new to some o

Re: fatal: no SASL authentication mechanisms

>> I get 'fatal: no SASL authentication mechanisms' in maillog >> smtpd_tls_auth_only = yes > Do you know what this parameter setting does? Not exactly, Ive been reading all kinds of docs and since Im new to some of it, Im a little confused between SASL and TLS. I&#x

Re: fatal: no SASL authentication mechanisms

On Thu, Feb 11, 2010 at 03:13:52PM -0800, Jeff Lacki wrote: > I get 'fatal: no SASL authentication mechanisms' in maillog > smtpd_tls_auth_only = yes Do you know what this parameter setting does? -- Viktor. P.S. Morgan Stanley is looking for a New York City based, Se

fatal: no SASL authentication mechanisms

Im trying to setup SASL+TLS+dovecot. Overall Ive gotten things somewhat working, but have a couple questions since Im new to this aspect of postfix. I get 'fatal: no SASL authentication mechanisms' in maillog I ran saslfinger and it showed no mechanisms, my /usr/lib/sasl2/smtpd.con