postfix can hardly create the socket because it is the *consumer* of it - so dovecot is responsible
as well as other sockets are *not* created at install but at start time - a socket is not a regular file and you can compare it to a listening TCP port
Am 25.05.2014 00:21, schrieb Subscriptions:
This may be a stupid question, but which process is supposed to create the socket. All other (existing) sockets in /var/spool/postfix/private are owned by Postfix, so am assuming they were created when Postfix was installed.
On 24/05/14 22:00, Subscriptions wrote:
Made the changes, so entries in 10-master.conf are now:
service auth { unix_listener auth-userdb { #mode = 0666 #user = #group = }
# Postfix smtp-auth unix_listener /var/spool/postfix/private/auth { mode = 0660 user = postfix group = postfix } # Auth process is run as this user. #user = $default_internal_user
}
Entries in 10-auth.conf are as follows (ass suggested by another post I found.
... auth_mechanisms = plain login ...
Output from dovecot -n
# 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-24-generic x86_64 Ubuntu 14.04 LTS ext4 auth_mechanisms = plain cram-md5 auth_verbose = yes base_dir = /var/run/dovecot/ info_log_path = /var/log/dovecot.info log_path = /var/log/dovecot log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n namespace { inbox = yes location = prefix = INBOX. separator = . } passdb { args = /etc/dovecot/passwd driver = passwd-file } protocols = imap pop3 service auth { executable = /usr/lib/dovecot/auth user = root } service imap-login { chroot = login executable = /usr/lib/dovecot/imap-login user = dovecot } service imap { executable = /usr/lib/dovecot/imap } service pop3-login { chroot = login executable = /usr/lib/dovecot/pop3-login user = dovecot }
Did a reload.
Tail of Logs files is as follows ------------dovecot.info ----- 2014-05-24 21:53:49 imap-login: Info: Login: user=<leo@zudiewiener.com>, method=CRAM-MD5, rip=110.20.34.128, lip=103.4.235.252, mpid=3469, TLS, session=<9m7L/yP6xgBuFCKA> 2014-05-24 21:53:55 imap-login: Info: Login: user=<inge@zudiewiener.com>, method=CRAM-MD5, rip=110.20.34.128, lip=103.4.235.252, mpid=3471, TLS, session=<c+ktACT6yABuFCKA> 2014-05-24 21:54:00 imap-login: Info: Login: user=<ilsubscr@zudiewiener.com>, method=CRAM-MD5, rip=110.20.34.128, lip=103.4.235.252, mpid=3473, TLS, session=<emh3ACT6zgBuFCKA>
-------- dovecot ------------- 2014-05-24 21:29:49 config: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) 2014-05-24 21:29:49 log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) 2014-05-24 21:29:49 master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) 2014-05-24 21:30:13 master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) 2014-05-24 21:30:13 log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill) 2014-05-24 21:41:41 master: Warning: SIGHUP received - reloading configuration
Thanks,
Leo
On 24/05/14 20:48, Thomas Leuxner wrote:
- lister171254 <llsubscr@zudiewiener.com> 2014.05.24 11:56:
No matter what I try, the listener is not created.
Text does the trick as well and survives pictures in the archives ;)
# Postfix smtp-auth unix_listener /var/spool/postfix/private/auth { mode = 0600 user = postfix group = postfix
The wiki quoted and my running config both use 'mode = 0660'. Give that a try:
service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = doveauth }
You may leave out the extra doveauth user which is a specific flavor of my configuration. If that still fails, you should post some log excerpts from dovecot after a reload which probably show the problem.