LMTP with unix socket (core 8.7.8, Debian 9.6)

fbartels

Did you follow the instructions from https://documentation.kopano.io/kopanocore_administrator_manual/configure_kc_components.html?highlight=lmtp#postfix-integration ?

mapo

Yes. Every step.

I created dir:
mkdir -p /var/spool/kopano

then fixed acls:
chown kopano:kopano /var/spool/kopano
chmod go= /var/spool/kopano
setfacl -m u:postfix:rwx /var/spool/kopano

Edited config files for dagent and postfix:

My dagent.cfg:
#lmtp_listen = *:2003
lmtp_listen = unix:/var/spool/kopano/dagent.sock

My postfix main.cf:
#virtual_transport = lmtp:127.0.0.1:2003
virtual_transport = lmtp:unix:/var/spool/kopano/dagent.sock

Then restarted dagent & postfix:
service kopano-dagent restart
service postfix restart

Dagent.sock is created, but somehow Postfix can’t access it:
postfix/lmtp[2345]: […] status=deferred (connect to srv3.test.loc[/var/spool/kopano/dagent.sock]: No such file or directory)

Well… I’ll just stay with TCP sockets for now. But if anyone has a working unix socket implementation, i could use some help. Like the manual says:
“Starting with the 8.7 release of Kopano Groupware Core it is possible to deliver messages not only via a tcp LMTP connection, but also through a linux socket. While for backwards compatibility the default value will continue to use the tcp socket, we recommend to use the unix socket for new installations.”

jengelh

The directory appears to be still unreadable by postfix: there is no “+” shown for the ACL that was supposedly set.

root@srv3:/var/log/kopano# ls -al /var/spool/kopano/
total 8
drwx------ 2 kopano kopano 4096 Nov 29 19:44 .
drwxr-xr-x 6 root   root   4096 Nov 29 19:09 ..
srw-rw-rw- 1 root   root      0 Nov 29 19:44 dagent.sock

The other idea is that, because postfix reports “No such file or directory”, that it might be running in some kind of mount namespace. You can use nsenter -r -m -w -t P with the postfix pid P to get into a shell that shows what postfix sees.

mapo

Thank you for your help.
Ok, I fixed ACLs (my fault). But still no luck. :(
Directory has full access (777) now (for testing):

root@srv3:/var/spool/kopano# ls -al
total 8
drwxrwxrwx+ 2 kopano kopano 4096 Nov 30 21:56 .
drwxr-xr-x  6 root   root   4096 Nov 30 21:37 ..
srwxrwxrwx  1 root   root      0 Nov 30 21:56 dagent.sock

Tried also with nsenter - spawned shell from postfix PID and directory is accessibile & readable under postfix PID.
Will try to play around with this over the weekend.

Caldwell

For my part, I ran the commands as listed in the documentation on Ubuntu 18.x, and the socket file NEVER gets created. I had to revert to *:2003 config style.

Whether using “run_as” kopano or root, the socket file never gets created.

Any details on how to make that happen?

thctlo

Why not…

dpkg-statoverride --add kopano postfix 770 /var/spool/kopano
and you on Debian with systemd.

see: systemctl cat kopano-dagent

fix it with : systemctl edit kopano-dagent

add:

[Unit]
# optional, but helps is the start up process. 
After=kopano-server.service
Wants=kopano-server.service

[Service]
LimitNOFILE=8192:16384
User=kopano
Group=kopano

and try again

BMWfan

I have the same problem as mapo.

Dec 30 20:32:07 servername postfix/error[11706]: DB1844C1F50: to=<max@mustermann.de>, relay=none, delay=0.01, delays=0.01/0/0/0, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to servername.server.de[/var/spool/kopano/dagent.sock]: No such file or directory)

The problem is not fixed after the suggested doings from thctlo.

jengelh

Ubuntu may be using AppArmor.

BMWfan

@jengelh and what do you want to tell me with this information?
I’am using Debian 9 as mapo.

jengelh

Well, that the LSM may interfere? Investigation needs shells, since no one has crystal balls (and won’t for the—ha—foreseeable future!)

pks57

Hi,

similar problem on ubuntu 18.04

The postfix/lmtp process runs chrooted in /var/spool/postfix and can therefore not access the socket in /var/spool/kopano.

my solution:
create the kopano spooldir in /var/spool/postfix instead of /var/spool (same chown, chmod and setfacl as in original instructions apply)

in dagent.conf:

lmtp_listen = unix:/var/spool/postfix/kopano/dagent.sock

In postfix/main.cf:

virtual_transport = lmtp:unix:/kopano/dagent.sock

worked for me…

jengelh

similar problem on ubuntu 18.04
The postfix/lmtp process runs chrooted in /var/spool/postfix and can therefore not access the socket in /var/spool/kopano.

Yep. Just as I postulated on 2018-11-30:

The other idea is that, because postfix reports “No such file or directory”, that it might be running in some kind of mount namespace.

crankshaft

@pks57 said in LMTP with unix socket (core 8.7.8, Debian 9.6):

/var/spool/postfix/kopano/dagent.sock

I have the same problem with a fresh install on Ubuntu 18.

connect to kopano[/var/spool/kopano/dagent.sock]: No such file or directory

So as suggested, I created: /var/spool/postfix/kopano/

And set permissions and facl, and updated main.cf and dagent.cfg etc etc and rebooted.

The dagent.sock file is never created and postfix now errors with:

connect to kopano[/var/spool/postfix/kopano/dagent.sock]: No such file or directory

Any suggestions ??

jengelh

Look at the dagent log and see what it says about dagent.sock.