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