On Sun, 5 Oct 2014 21:05:26 +0200, Patrick Ben Koetter <p...@sys4.de> wrote:
> * Mail List <maill...@nerdworld.org>:
>> I am in the process of setting up postfix 2.9.6, postgrey, and dovecot
>> 2.1.7 on a clean install of Debian wheezy 7.6 AMD. I'm doing this very
>> systematically in a VirtualBox virtual machine, which lets me
experiment
>> and screw up the settings, since I just recreate the VM if I makes
things
>> unusable.
>>
>> I've gotten to the point that postfix, postgrey, and dovecot all work
>> just
>> fine. I can send & receive eMails (relaying outgoing mail through my
>> comcast account). However, I'm stuck on setting up SASL authorization
>> for
>> incoming SMTP connections. Up until the time I try to implement SASL
>> authorization, I can successfully telnet into the system for SMTP and
>> IMAP
>> connections. Once I try to start SASL authorization it all goes
>> horribly
>> wrong.
>>
>> I can't even get SMTP to work.
>>
>> #telnet localhost 25
>> Trying ::1...
>> Trying 127.0.0.1...
>> Connected to localhost.
>> Escape character is '^]'.
>> Connection closed by foreign host.
>>
>> /var/log/mail.info shows:
>> Oct 5 14:29:31 VMailServerTest postfix/smtpd[16181]: connect from
>> localhost[127.0.0.1]
>> Oct 5 14:29:31 VMailServerTest postfix/smtpd[16181]: warning: SASL:
>> Connect to private/auth failed: Permission denied
>
> Postfix smtpd daemon cannot write to dovecot's socket. Either because
the
> perms are wrong or because the socket belongs to the wrong user.
>
> Try this in dovecot's 10-master.conf:
>
> unix_listener /var/spool/postfix/private/auth {
> mode = 0600
> user = postfix
> group = postfix
> }
>
>
Thanks for your suggestion Patrick! Changing the mode didn't work, but I
think you are on the right track. I played around with permissions on the
socket. Here is the directory entry for the socket file:
srw------- 1 root root 0 Oct 5 15:13 /var/spool/postfix/private/auth
Interestingly, I tried changing the perms to 777 (wide open!) it worked!.
Also, if I left the file permissions to 600 and set the owner and group to
postfix, it also worked.
Unfortunately, restarting postfix wiped out any changes and reset the file
to the root owner and default permissions, so there must be some setting
somewhere that I'm missing.
Any ideas?
TIA!
--
Casey Bralla
