kopano-gateway listen only on ipv6

BusinessTux

Hello everybody,

I want to migrate an Univention Corporate Server (UCS) with Zarafa to Kopano. For this I installed a fresh UCS with Kopano to check all functions. Web- and Deskapp are working. But I cannot connect via IMAP(S), because the kopano-gateway only listens on IPv6, not on IPv4 :-(.

:~# netstat -tulpen | grep -i kopano
tcp        0      0 0.0.0.0:236             0.0.0.0:*               LISTEN      0          807632      3337/kopano-server
tcp        0      0 0.0.0.0:237             0.0.0.0:*               LISTEN      0          807635      3337/kopano-server
tcp6       0      0 :::110                  :::*                    LISTEN      0          7996412     23468/kopano-gatewa
tcp6       0      0 :::143                  :::*                    LISTEN      0          8002562     23468/kopano-gatewa
tcp6       0      0 :::8080                 :::*                    LISTEN      0          15093       773/kopano-ical
tcp6       0      0 :::2003                 :::*                    LISTEN      0          16005       778/kopano-dagent
tcp6       0      0 :::8443                 :::*                    LISTEN      0          15113       773/kopano-ical
tcp6       0      0 :::993                  :::*                    LISTEN      0          8002565     23468/kopano-gatewa
tcp6       0      0 :::995                  :::*                    LISTEN      0          7996415     23468/kopano-gatewa

My UCS info:

:~# univention-app info
UCS: 4.2-2 errata189
App Center compatibility: 4
Installed: dhcp-server=11.0.0 kopano-core=8.3.1.32 kopano-webapp=3.3.0.610 nagios=3.5 pkgdb=10 samba4=4.6 squid=3.4 z-push-kopano=2.3.7
Upgradable:

Where can I configure, that the ports on IPv4 are opened too?

Thanks
Ulf

fbartels

Hello @businesstux ,

for me the deamons are listed for ipv6 in netstat as well, but still react to ipv4 adresses:

root@ucs-3635 ~
$ nc 127.0.0.1 143
* OK [CAPABILITY IMAP4rev1 LITERAL+ STARTTLS AUTH=PLAIN] IMAP gateway ready
^C

BusinessTux

Hi Felix,

you’re so right. From the Windows client per telnet I’ve got the same output like you. Then I have to search, why my Thunderbird won’t connect.

Thanks
Ulf

IPv6 sockets generally also allow IPv4 connections transparently unless explicitly deactivated by something like IPV6_V6ONLY setsockopt.