[Dovecot] socket /var/spool/postfix/private/auth not created

lister171254

24 May 2014 24 May '14

12:56 p.m.

I'm on Ubuntu 13.10 and followed these instructions http://wiki2.dovecot.org/HowTo/PostfixAndDovecotSASL to configure Dovecot for Postfix.

No matter what I try, the listener is not created.

http://dovecot.2317879.n4.nabble.com/file/n48182/32.png

dovecot -n does not show the listener (I guess that's why its not created)

This is the extract from the /etc/dovecot/conf.d/10-master.conf

service auth { # auth_socket_path points to this userdb socket by default. It's typically # used by dovecot-lda, doveadm, possibly imap process, etc. Users that have # full permissions to this socket are able to get a list of all usernames and # get the results of everyone's userdb lookups. # # The default 0666 mode allows anyone to connect to the socket, but the # userdb lookups will succeed only if the userdb returns an "uid" field that # matches the caller process's UID. Also if caller's uid or gid matches the # socket's uid or gid the lookup succeeds. Anything else causes a failure. # # To give the caller full permissions to lookup all users, set the mode to # something else than 0666 and Dovecot lets the kernel enforce the # permissions (e.g. 0777 allows everyone full permissions). unix_listener auth-userdb { #mode = 0666 #user = #group = }

# Postfix smtp-auth unix_listener /var/spool/postfix/private/auth { mode = 0600 user = postfix group = postfix } # Auth process is run as this user. #user = $default_internal_user

}

Postfix is not involved in this right now as I expect the socket to be created when I restart dovecot. Can't find any meaningfull errors in the logs either. I hope I'm missing something obvious

Thanks,

Leo

-- View this message in context: http://dovecot.2317879.n4.nabble.com/socket-var-spool-postfix-private-auth-n... Sent from the Dovecot mailing list archive at Nabble.com.

Show replies by date

Thomas Leuxner

24 May 24 May

1:48 p.m.

lister171254 llsubscr@zudiewiener.com 2014.05.24 11:56:

...

No matter what I try, the listener is not created.

http://dovecot.2317879.n4.nabble.com/file/n48182/32.png

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.

Regards Thomas

Subscriptions

3 p.m.

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= 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.

http://dovecot.2317879.n4.nabble.com/file/n48182/32.png

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.

Regards Thomas

Subscriptions

25 May 25 May

1:21 a.m.

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.

Thanks

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= 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.

http://dovecot.2317879.n4.nabble.com/file/n48182/32.png

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.

Regards Thomas

Reindl Harald

1:28 a.m.

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= 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.

http://dovecot.2317879.n4.nabble.com/file/n48182/32.png

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.

Subscriptions

3:33 a.m.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

ok. Obviously I'm no guru here, I'm just trying to figure out why this socket is missing.

If I shut down postfix, the sockets in private are still there. They are also all owned by postfix. If postfix is only the consumer then I assume dovecot must have write access to private, which it doesn't

Thanks

On 25/05/14 08:28, Reindl Harald wrote:

...

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= 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.

http://dovecot.2317879.n4.nabble.com/file/n48182/32.png

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.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBAgAGBQJTgTo2AAoJEOXdNUiyB06kx/sP/27yQ1M0QpOkKomnibGh82H6 yLeGzJaofLVfIhClzXxUVRcyeWGvjKgVItKxrkuVTzz5ZPSku7Qs1h523BJzwvb0 FsZsqWDrvxQzZZW2HjTEdI6CfZeHiHBTyWdxORe0aadPz/BnuhbsQdH4Ob5d55XC ZMYhDev0R4idtuCDcsAbIlvcW9ZZO6Zi/+zxS9M1kr3E9I/I+Tzyu0BGyjtY+XQ7 rfAxjhM6BLgJlK9qohXXgyQEqSzkBA3sAzeF2HMaG5wWi0fGkLgfTW/hW1bzO9rk JIFa2+PB60Xy9nFM5zU4fTQMWsKlExEcV6HQLwr4mZE5lLRvpqyjrSA4Z1h9mN3x zUMpJy5/qq35gpu3bdpQ9Q8PB3hVKy4E+8s2hjXUohhEVsEuUkUoP00GER0Ibr3J feRPnDn8+Q3Y3ojHg8ExQp4Dk65+S5f5m31v48Qhaw0edErM+8WwIagP7ZSAgKpZ JXwVjGiRFJ/V1fswv+Rn0piavGFYVZM/ryvZpzpp2Ojo9xTeLfR0vzXeHOdnLo8F 5NOACiZs8YElx+e4SeyvPrC+KP5dHyQcVYtm150EeRpSPwPbJp+u8rQD/cL158KE ZuGXHCU6rgH+oQn2HQwOcXXam6fwdqM9Tzz1Mu8Wif7/2d0bbKfJfI0CiWM0Yz6R Jf3qrMwUcw2ksaYF9NkH =30bO -----END PGP SIGNATURE-----

Thomas Leuxner

11:18 a.m.

Subscriptions llsubscr@zudiewiener.com 2014.05.25 02:33:

Have you checked that no security extension comes in play preventing creation of sockets? https://wiki.ubuntu.com/Security/Features

Should manifest itself in syslog somewhere if you grep for the path in question...

Subscriptions

26 May 26 May

2:01 a.m.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Yes, have checked the logs, but cannot find any issues/errors in relation to dovecot anywhere

Just to clarify, when I restart dovecot, I expect the socket to be created. Is this correct?

Thanks,

Leo

On 25/05/14 18:18, Thomas Leuxner wrote:

...

Subscriptions llsubscr@zudiewiener.com 2014.05.25 02:33:

Have you checked that no security extension comes in play preventing creation of sockets? https://wiki.ubuntu.com/Security/Features

Should manifest itself in syslog somewhere if you grep for the path in question...

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBAgAGBQJTgnYrAAoJEOXdNUiyB06kSzUP/jR7iXkZ/iiQTBdoI9P5kAqZ +BD62baJ10Tk4isdz+tn0gosTvTqRCOd9hnxnUsi5hJ3Ayjpe1rU4AQ/4gPVWee1 Y2uZRW8bS1lYotrWDvuzf4ruy/ASkEVZ4iHVzsOoL0/KgjJ2fCg+O2GOYfSX7Uf2 2RZKtRukg9wvOQ+ARTfl6oEKzgJNOVuro+QW3QKVD70eZqEvjLBVz9uPw5h/eGo8 4O2LwnFGsnhwwk6phfbdv5B1EOZ3x36zfeD6i8vOgBWIao2ZAbP43P26qPP/s3kR mFflGzUxBblnwwZccXIEHuK8ZfPMpNjB+TQLgis1/THyrMnWITHA9JIVwoXwAnWz 11tmWVlii6uXDLUKdv2lIU4GaipWdOZb6d/k+tM5CCr09L0G3JJS0/HgefOUb+np 3OVKAfrJj8/TbHvdTYYM7nKAduEve4K1A7xGE7drWwS085rWEr4/qeSxM5oLR18G TeDTmGaOMEf/IecGLEprpBIr4iy2qEOJWE+1mQ9R8F0Z/2GptOSPtaRBh/R3xu9g 71oNiHQvtgGLeiiXiOgeQX6GKJh7+enzAVZ+pMnGeyVAt02pIqWUMGdlg9bQ3gUL F/Orz7+NqRqplhEBWMqP3hXNterBv4vMF/X5njOmvANZL+NmvbbJMiZpiuCeq01Q F/GiRchCMGDDZJ7hqKTr =YCkv -----END PGP SIGNATURE-----

Reindl Harald

2:09 a.m.

Am 26.05.2014 01:01, schrieb Subscriptions:

...

Yes, have checked the logs, but cannot find any issues/errors in relation to dovecot anywhere

Just to clarify, when I restart dovecot, I expect the socket to be created. Is this correct?

surely as you can see below and that works on 6 machines here for years

service auth { unix_listener /var/spool/postfix/private/auth { mode = 0660 user = postfix group = postfix } }

[root@testserver:~]$ stat /var/spool/postfix/private/auth stat: cannot stat '/var/spool/postfix/private/auth': No such file or directory

[root@testserver:~]$ systemctl status dovecot dovecot.service - Dovecot IMAP/POP3 Proxy Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled) Active: inactive (dead) since Mon 2014-05-26 01:05:21 CEST; 38s ago Process: 860 ExecStart=/usr/sbin/dovecot -F (code=exited, status=0/SUCCESS) Main PID: 860 (code=exited, status=0/SUCCESS)

[root@testserver:~]$ systemctl start dovecot.service

[root@testserver:~]$ stat /var/spool/postfix/private/auth File: '/var/spool/postfix/private/auth' Size: 0 Blocks: 0 IO Block: 4096 socket Device: 811h/2065d Inode: 253971 Links: 1 Access: (0660/srw-rw----) Uid: ( 89/ postfix) Gid: ( 89/ postfix) Access: 2014-05-26 01:06:13.288893380 +0200 Modify: 2014-05-26 01:06:13.288893380 +0200 Change: 2014-05-26 01:06:13.288893380 +0200 Birth: -

...

On 25/05/14 18:18, Thomas Leuxner wrote:

...

Subscriptions llsubscr@zudiewiener.com 2014.05.25 02:33:

...
Have you checked that no security extension comes in play preventing creation of sockets? https://wiki.ubuntu.com/Security/Features

...
Should manifest itself in syslog somewhere if you grep for the path in question...

Subscriptions

3:11 a.m.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

ok. I guess that narrows it down a bit.

I'm on Ubuntu 14.10 64 bit server.

my settings and ownership for /private are

drwx------ 2 postfix root 4096 May 26 09:04 private

There is nothing in the system (or devocot) logs that would indicate why the socket isn't created.

Finally, I would expect "dovecot -n" to show some indication of this listener, which for me it doesn't.

Thanks,

Leo

On 26/05/14 09:09, Reindl Harald wrote:

...

Am 26.05.2014 01:01, schrieb Subscriptions:

...
Yes, have checked the logs, but cannot find any issues/errors in relation to dovecot anywhere

Just to clarify, when I restart dovecot, I expect the socket to be created. Is this correct?

surely as you can see below and that works on 6 machines here for years

service auth { unix_listener /var/spool/postfix/private/auth { mode = 0660 user = postfix group = postfix } }

[root@testserver:~]$ stat /var/spool/postfix/private/auth stat: cannot stat '/var/spool/postfix/private/auth': No such file or directory

[root@testserver:~]$ systemctl status dovecot dovecot.service - Dovecot IMAP/POP3 Proxy Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled) Active: inactive (dead) since Mon 2014-05-26 01:05:21 CEST; 38s ago Process: 860 ExecStart=/usr/sbin/dovecot -F (code=exited, status=0/SUCCESS) Main PID: 860 (code=exited, status=0/SUCCESS)

[root@testserver:~]$ systemctl start dovecot.service

[root@testserver:~]$ stat /var/spool/postfix/private/auth File: '/var/spool/postfix/private/auth' Size: 0 Blocks: 0 IO Block: 4096 socket Device: 811h/2065d Inode: 253971 Links: 1 Access: (0660/srw-rw----) Uid: ( 89/ postfix) Gid: ( 89/ postfix) Access: 2014-05-26 01:06:13.288893380 +0200 Modify: 2014-05-26 01:06:13.288893380 +0200 Change: 2014-05-26 01:06:13.288893380 +0200 Birth: -

...
On 25/05/14 18:18, Thomas Leuxner wrote:

...

Subscriptions llsubscr@zudiewiener.com 2014.05.25 02:33:

...
Have you checked that no security extension comes in play preventing creation of sockets? https://wiki.ubuntu.com/Security/Features

...
Should manifest itself in syslog somewhere if you grep for the path in question...

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBAgAGBQJTgoalAAoJEOXdNUiyB06ksKwP/1/QoDuoY7VEPKbFSfUVYLxp LuR3ZmI4GqaOTDe+P3d/g7wkMbpQ3k7hQFNh60NyN2G0WgEApjzZmNq3TYsW38sJ f+j873k7XDdekqjQy7G9Cx60/mMXCmLHOelpn0W+jtQ0xypYVSW8o8DgtiuY4f6Y 7KHq0VaFj5fzZoo3y8eS39At9H4huwypKPZGpR30gfT5n/V2LoE8EoBDtUHf3LXl YFouPpG/63SEC1279YIY5T7zumUcxhzx4P6wdIqmf5+EkDF3XrxLgtwqGjzC3NvF nnCssm3pt8srVva1gUyapDdkB46owfq8cK/tOHqmNlyCJCqfbkYcAvLQh5A+YOet 7Ky9EpTt4e3C/ZgH83ffoxNLeKkNxbFMCbpiCLD0SFSy0rSKMYgk/1qhCmEmMXH3 Qv3Pz2FPuWebByP+RFUPEMzuK4aw+ykDAACAgKlmCFpbVNknOxMShRWyzhstKMF5 c4CCyF0YYDQIqYi0KVDKbF3qag7qEIvlpPybX2u13NlVXAAbjcc0s4DmB3Xqo42/ P5FaZf9RZ6s6kUOdyNKWa4qnKiYrTIY0UUF4hPHuQLonC0Qr1krlHJKH3gSLOKH6 b2P2gI1ONmRbZBM06jMJAZM6l/kKbg7S44xhy9L+wyrYAZNrfzaNWEcmGvi4Ufjl PKYYATbXfHDDlfInzcGA =c8YW -----END PGP SIGNATURE-----

Subscriptions

7:08 a.m.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

ok. Problem found and resolved.

!include conf.d/*.conf

was missing from my dovecot.conf.

Don't know how or why, but putting the line in fixed the problem.

Thanks,

Leo

On 25/05/14 10:33, Subscriptions wrote:

...

ok. Obviously I'm no guru here, I'm just trying to figure out why this socket is missing.

If I shut down postfix, the sockets in private are still there. They are also all owned by postfix. If postfix is only the consumer then I assume dovecot must have write access to private, which it doesn't

Thanks

On 25/05/14 08:28, Reindl Harald wrote:

...
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= 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.

http://dovecot.2317879.n4.nabble.com/file/n48182/32.png

...
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.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux)

iQIcBAEBAgAGBQJTgr5WAAoJEOXdNUiyB06kdSQP/R/kd+CXyuBbTtGhh5YnRES4 bmSM3rOJmGWrr9iB4Z7T6VMOeunvLvXSNfcGA6Vx2U49PkyGhk1+15QNiJN5zrk7 cCU0P7xKpSiqvCCLARbu+vtLu3vY8DWLqIMK61NC5b178dpN3Zw26F05Koc33+zE OPE1sHF5cMzl4uueU3+yKPWURPDd/cop2SkugEKHlZbTV8RowKGRbVuDyhNfsqRz vNxhg7u63/89BPH5T4N8iegEw4bunqVo823kGAzIwyYTBW0f+U9IVtOTkVfY5eDl xDQxHMVBNF6f+iqwN6wRENFFW6k3OYTmgGWjB4qrJP/n+zNkcQPfZTUTWKxmKZnU OAT2EQbkAFVo9mtM+yNmjkaVAlrTX4gGf84lJJfJzPbPrI1SEmsbZ8RRqiw5dCdw 1+yX36hK2n5Mg3HYAk/fmcQPKNNq7CJ51wUVdKoXD9Dz8+5uEqFtWb/U9eSp1Jvf mHyMjmqbTLRnom//yrY62C//M3Cs12DAbs4BzfDEs7JFgEYrpCmA5o77+HVXvOQI RL0oTpojIyRPG/4CU/xwG//hz0v4ptHH9kOHU7NdEpUcUoXXat3OJ5qgRchF2LYP 8dQRrxlFmzAqxKcZnT/xqMHRe/r/PhaB9CkVSYyvT0PWF0yBaDpXiZFZpXxi6JTh DDs8LHG+xvuCtNS7Qqed =PX9h -----END PGP SIGNATURE-----

Nick Edwards

25 May 25 May

10:58 a.m.

On 5/24/14, Subscriptions llsubscr@zudiewiener.com wrote:

...

Made the changes, so entries in 10-master.conf are now:

service auth { unix_listener auth-userdb { #mode = 0666 #user = #group = }

this should have user/group that should match how postfix master.cf see's it

eg:

master.cf: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/dovecot-lda -f ${sender} -e -d ${user}@${nexthop}

dovecot:

service auth { client_limit = 2248 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail group = vmail } }

...

# 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= 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.

http://dovecot.2317879.n4.nabble.com/file/n48182/32.png

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.

Regards Thomas

Subscriptions

26 May 26 May

2:19 a.m.

ok. My 10-master.conf now looks like this:

service auth { client_limit = 2248 unix_listener auth-userdb { mode = 0600 user = virtual group = virtual }

# 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 }

Have added the following to master.cf

dovecot unix - n n - - pipe flags=DRhu user=virtual:virtual argv=/usr/libexec/dovecot/dovecot-lda -f ${sender} -e -d ${user}@${nexthop}

Restarted both dovecot and postfix; still no socket.

BTW,

When would yo expect the socket to be created; after restarting dovecot or postfix?

Thanks,

Leo

On 25/05/14 17:58, Nick Edwards wrote:

...

On 5/24/14, Subscriptions llsubscr@zudiewiener.com wrote:

...
Made the changes, so entries in 10-master.conf are now:

service auth { unix_listener auth-userdb { #mode = 0666 #user = #group = }

this should have user/group that should match how postfix master.cf see's it

eg:

master.cf: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/dovecot-lda -f ${sender} -e -d ${user}@${nexthop}

dovecot:

service auth { client_limit = 2248 unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0600 user = vmail group = vmail } }

...
# 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= 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.

http://dovecot.2317879.n4.nabble.com/file/n48182/32.png

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.

Regards Thomas

Reindl Harald

2:25 a.m.

Am 26.05.2014 01:19, schrieb Subscriptions:

...

ok. My 10-master.conf now looks like this:

service auth { client_limit = 2248 unix_listener auth-userdb { mode = 0600 user = virtual group = virtual }

# 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 }

Have added the following to master.cf

dovecot unix - n n - - pipe flags=DRhu user=virtual:virtual argv=/usr/libexec/dovecot/dovecot-lda -f ${sender} -e -d ${user}@${nexthop}

Restarted both dovecot and postfix; still no socket.

BTW,

When would yo expect the socket to be created; after restarting dovecot or postfix?

DOVECOT as explained multiple times postfix is just the customer

what about looking at your systemlogs as already asked? what operating system? are you running SELinux or another MAC system?

Charles Marcus

5:21 p.m.

On 5/24/2014 8:00 AM, Subscriptions llsubscr@zudiewiener.com 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 <snip> 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 } <snip>

Sorry, but if you make changes to a dovecot config file, and those changes are not reflected in the doveconf -n output, then you are quite simply editing the wrong file.

I don't see any evidence of the service auth change you made in that output, so you are editing the wrong config file(s).

Best regards,

Charles

3795

Age (days ago)

3797

Last active (days ago)

List overview

14 comments

6 participants

participants (6)

Charles Marcus
lister171254
Nick Edwards
Reindl Harald
Subscriptions
Thomas Leuxner