Connect to private/dovecot-auth failed - Revision history

Woozle: post-move tweaks, updates, SMW markup

2011-06-08T18:44:15Z

post-move tweaks, updates, SMW markup

← Older revision		Revision as of 18:44, 8 June 2011
Line 1:		Line 1:
			{{#set:page type=article}}
			{{#set:thing type=error message}}
			{{#set:generated by=Postfix}}
			[[category:error messages]]
	==About==		==About==
	~~[[category:error messages]]~~[[Connect to private/dovecot-auth failed~~: No such file or directory~~]] is an [[error message]] which appears in [[/var/log/mail.log]] ~~and~~ is ~~generated~~ by [[Postfix]].		[[Connect to private/dovecot-auth failed]] is an [[error message]] which appears in {{link/subpage\|pfx=Linux/files\|/var/log/mail.log}}. It is generated by [[Postfix]], but is actually caused by the failure of a [[Dovecot]] component which is supposed to provide a pipe for Postfix to talk to. The pipe is usually located at {{link/subpage\|pfx=Linux/files\|/var/spool}}/[[postfix]]{{link/subpage\|pfx=Postfix\|/private/dovecot-auth}}.

	A more complete and generalized version of this message is:		A more complete and generalized version of this message is:
	: <u>servername</u> nss-mysql[<u>number</u>]: warning: SASL: Connect to <u>pipe</u> failed: No such file or directory		: <u>servername</u> nss-mysql[<u>number</u>]: warning: [[SASL]]: Connect to <u>pipe</u> failed: No such file or directory
	Where:		Where:
	* '''servername''' is the network name of the machine generating the error		* '''servername''' is the network name of the machine generating the error
Line 10:		Line 14:
	** (is "pipe" correct, or do I mean "socket"? not sure.)		** (is "pipe" correct, or do I mean "socket"? not sure.)

	In one particular scenario, it is preceded by an [[SMTP]] connection attempt from a remote server, and followed by a [[~~fatal:~~ no SASL authentication mechanisms]] error message.		In one particular scenario, it is preceded by an [[SMTP]] connection attempt from a remote server, and followed by a fatal: [[no SASL authentication mechanisms]] error message.
	==Example==		==Example==
	: ~~Oct 3 07~~:~~42:32 rizzo nss-mysql[26619]: warning: SASL: Connect to private/dovecot-auth failed: No such file or directory~~		{{:User:Woozle/log dumps/2011/06/08/0743}}
	~~: Oct 3 07:42:32 rizzo nss-mysql[26619]: fatal: no SASL authentication mechanisms~~		===fixes===
	~~: Oct 3 07:42:33 rizzo postfix~~/~~master[4272]: warning: process~~ /~~usr~~/~~lib~~/~~postfix~~/~~smtp~~		One fix involved the following:

	~~In this particular case, a~~ fix involved the following:
	* ls /var/spool/postfix/private		* ls /var/spool/postfix/private
	* look for pipe with "auth" in the name		* look for pipe with "auth" in the name

Woozle: moved Connect to private/dovecot-auth failed: No such file or directory to Connect to private/dovecot-auth failed: title should be shortest descriptive part of message

2011-06-08T18:32:09Z

moved Connect to private/dovecot-auth failed: No such file or directory to Connect to private/dovecot-auth failed: title should be shortest descriptive part of message

← Older revision	Revision as of 18:32, 8 June 2011
(No difference)

Woozle: another note

2011-02-11T22:12:54Z

another note

← Older revision		Revision as of 22:12, 11 February 2011
Line 24:		Line 24:
	==Notes==		==Notes==
	* [http://www.group-office.com/wiki/Mailserver#Enabling_TLS_and_SMTP_authentication This] gives more information about configuring Postfix for secure SMTP authentication in [[Group-Office]]		* [http://www.group-office.com/wiki/Mailserver#Enabling_TLS_and_SMTP_authentication This] gives more information about configuring Postfix for secure SMTP authentication in [[Group-Office]]
			* Make sure the file referred to by postfix's main.cf is the same file referred to by dovecot's dovecot.conf. They had been the same, but when I checked them just now, one had apparently been updated from "auth-dovecot" to just "auth" and this was causing error messages in the log and some emails were being silently rejected. --[[User:Woozle\|Woozle]] 17:12, 11 February 2011 (EST)

Woozle: another link

2010-10-08T01:34:23Z

another link

← Older revision		Revision as of 01:34, 8 October 2010
Line 22:		Line 22:

	If that doesn't work, go to the [[Postfix]] and [[Dovecot]] web sites and read up on [[SASL]], especially [http://www.postfix.org/SASL_README.html#server_sasl_enable this section].		If that doesn't work, go to the [[Postfix]] and [[Dovecot]] web sites and read up on [[SASL]], especially [http://www.postfix.org/SASL_README.html#server_sasl_enable this section].
			==Notes==
			* [http://www.group-office.com/wiki/Mailserver#Enabling_TLS_and_SMTP_authentication This] gives more information about configuring Postfix for secure SMTP authentication in [[Group-Office]]

Woozle: another related link

2010-10-07T01:09:46Z

another related link

← Older revision		Revision as of 01:09, 7 October 2010
Line 21:		Line 21:
	* modify [[Dovecot]]'s {{link/subpage\|pfx=Dovecot/\|dovecot.conf}} file so that the '''auth default''' section includes at least the "client" section shown [http://www.linuxmail.info/postfix-smtp-auth-dovecot-sasl/ here], but with the "path" parameter pointing at your actual auth pipe.		* modify [[Dovecot]]'s {{link/subpage\|pfx=Dovecot/\|dovecot.conf}} file so that the '''auth default''' section includes at least the "client" section shown [http://www.linuxmail.info/postfix-smtp-auth-dovecot-sasl/ here], but with the "path" parameter pointing at your actual auth pipe.

	If that doesn't work, go to the [[Postfix]] and [[Dovecot]] web sites and read up on [[SASL]].		If that doesn't work, go to the [[Postfix]] and [[Dovecot]] web sites and read up on [[SASL]], especially [http://www.postfix.org/SASL_README.html#server_sasl_enable this section].

Woozle: Created page with '==About== category:error messagesConnect to private/dovecot-auth failed: No such file or directory is an error message which appears in /var/log/mail.log and is g…'

2010-10-07T01:04:26Z

Created page with '==About== category:error messages Connect to private/dovecot-auth failed: No such file or directory is an error message which appears in /var/log/mail.log and is g…'

New page

==About==
[[category:error messages]][[Connect to private/dovecot-auth failed: No such file or directory]] is an [[error message]] which appears in [[/var/log/mail.log]] and is generated by [[Postfix]].

A more complete and generalized version of this message is:
: servername nss-mysql[number]: warning: SASL: Connect to pipe failed: No such file or directory
Where:
* '''servername''' is the network name of the machine generating the error
* '''number''' is an integer, significance unknown (it seems to be a standard thing in mail.log files)
* '''pipe''' is the filespec of a pipe for communication between [[Postfix]] and [[Dovecot]], typically "private/dovecot-auth"
** (is "pipe" correct, or do I mean "socket"? not sure.)

In one particular scenario, it is preceded by an [[SMTP]] connection attempt from a remote server, and followed by a [[fatal: no SASL authentication mechanisms]] error message.
==Example==
: Oct 3 07:42:32 rizzo nss-mysql[26619]: warning: SASL: Connect to private/dovecot-auth failed: No such file or directory
: Oct 3 07:42:32 rizzo nss-mysql[26619]: fatal: no SASL authentication mechanisms
: Oct 3 07:42:33 rizzo postfix/master[4272]: warning: process /usr/lib/postfix/smtp

In this particular case, a fix involved the following:
* ls /var/spool/postfix/private
* look for pipe with "auth" in the name
* modify [[Dovecot]]'s {{link/subpage|pfx=Dovecot/|dovecot.conf}} file so that the '''auth default''' section includes at least the "client" section shown [http://www.linuxmail.info/postfix-smtp-auth-dovecot-sasl/ here], but with the "path" parameter pointing at your actual auth pipe.

If that doesn't work, go to the [[Postfix]] and [[Dovecot]] web sites and read up on [[SASL]].