Difference between revisions of "Connect to private/dovecot-auth failed"
Jump to navigation
Jump to search
(another related link) |
(post-move tweaks, updates, SMW markup) |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| + | {{#set:page type=article}} | ||
| + | {{#set:thing type=error message}} | ||
| + | {{#set:generated by=Postfix}} | ||
| + | [[category:error messages]] | ||
==About== | ==About== | ||
| − | + | [[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 [[ | + | 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== | ||
| − | : | + | {{:User:Woozle/log dumps/2011/06/08/0743}} |
| − | + | ===fixes=== | |
| − | + | One 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 | ||
| Line 22: | Line 24: | ||
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]] | ||
| + | * 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) | ||
Latest revision as of 18:44, 8 June 2011
About
Connect to private/dovecot-auth failed is an error message which appears in /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 /var/spool/postfix/private/dovecot-auth.
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
From /var/log/mail.info:
Jun 8 07:43:05 rizzo nss-mysql[14459]: connect from monitor.therealms.net[64.62.231.70] Jun 8 07:43:06 rizzo nss-mysql[14459]: warning: Connect to private/dovecot-auth failed: No such file or directory Jun 8 07:43:06 rizzo nss-mysql[14459]: fatal: no SASL authentication mechanisms Jun 8 07:43:07 rizzo postfix/master[1906]: warning: process /usr/lib/postfix/smtpd pid 14459 exit status 1 Jun 8 07:43:07 rizzo postfix/master[1906]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
fixes
One fix involved the following:
- ls /var/spool/postfix/private
- look for pipe with "auth" in the name
- modify Dovecot's dovecot.conf file so that the auth default section includes at least the "client" section shown 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, especially this section.
Notes
- 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. --Woozle 17:12, 11 February 2011 (EST)