Clashing port numbers POP3/IMAP

theboy

After running for a while, I've now hit a snag since the last minor update a couple of days ago.

If POP3 is running, IMAP won't start, and if IMAP is running, POP3 won't start. After a bit of digging, it looks like port 143 (which I believe should be IMAP only) is conflicting:

With POP3 stopped and IMAP running:
test-mail:/etc # ss -tlnp sport = :143 State Recv-Q Send-Q Local Address:Port Peer Address:Port Process LISTEN 0 512 *:143 *:* users:(("imap",pid=16635,fd=3))

With IMAP stopped and POP3 running:
test-mail:/etc # ss -tlnp sport = :143 State Recv-Q Send-Q Local Address:Port Peer Address:Port Process LISTEN 0 512 *:143 *:* users:(("pop3",pid=30298,fd=3))

Errors in the imap or pop3 logs are similar to:
[2026-02-07 11:21:55.863152]: gromox-pop3 3.4.50.m7fdf9e3 (pid 31788 uid 0) [2026-02-07 11:21:55.863624]: [system]: host ID is test-mail [2026-02-07 11:21:55.863624]: [system]: one thread is in charge of 20 contexts [2026-02-07 11:21:55.863624]: [system]: threads pool initial threads number is 5 [2026-02-07 11:21:55.863624]: [pop3]: context average memory is 512k [2026-02-07 11:21:55.863624]: [pop3]: context maximum memory is 2048k [2026-02-07 11:21:55.863829]: [pop3]: context average units number is 5000 [2026-02-07 11:21:55.863829]: [pop3]: pop3 socket read write timeout is 3min [2026-02-07 11:21:55.863829]: [pop3]: maximum authentication failure times is 10 [2026-02-07 11:21:55.863829]: [pop3]: block client 1min when authentication failure count is exceeded [2026-02-07 11:21:55.863829]: [pop3]: TLS support enabled [2026-02-07 11:21:55.863928]: gromox::errno_t gromox::listener_ctx::add_inet(const char*, uint16_t, uint32_t)([::]:143): Address already in use

I am unable to find where the port values are set, but this does appear to be either the opensuse updates or the latest gromox that has caused this.

Any clues?

WalterH

Can you post the content of this two files: /etc/gromox/pop3.cfg and /etc/gromox/imap.cfg ?

WalterH

BTW, this is the output of my system:

# ss -tlnp sport = :143
State             Recv-Q            Send-Q                         Local Address:Port                         Peer Address:Port            Process
LISTEN            0                 512                                        *:143                                     *:*                users:(("imap",pid=20827,fd=3))
# ss -tlnp sport = :110
State             Recv-Q            Send-Q                         Local Address:Port                         Peer Address:Port            Process
LISTEN            0                 512                                        *:110                                     *:*                users:(("pop3",pid=20938,fd=3))
#

umgfoin

imap, pop3 (and others') socket-binding configurations have changed (location and name):
They're now defined in gromox.cfg whereas according directives in pop3.cfgand imap.cfg have been deprecated.

now:

[gromox.cfg]
imap_listen = [::]:143
imap_listen_tls = [::]:993
pop3_listen = [::]:110
pop3_listen_tls = [::]:995

before:

[imap.cfg]
imap_listen_addr = ::
imap_listen_port = 143
imap_listen_tls_port = 993

[pop3.cfg]
pop3_listen_addr = ::
pop3_listen_port = 110
pop3_listen_tls_port = 995

The new implementation allows for finer grained configurations like:
imap_listen = 192.168.2.34:143 [1a2b:3f7:10b:a2c::2]:143 127.0.0.1:144

umgfoin

Compatibility with "old" configuration defaults is fixed, now with commit 3319bdb
.

WalterH

umgfoin
Will the configuration in imap.cfg continue to be supported? There are configurations where a second IMAP service runs, e.g., without a login prompt.

umgfoin

WalterH Will the configuration in imap.cfg continue to be supported? There are configurations where a second IMAP service runs, e.g., without a login prompt.

Right now and imho (reading from the sourcebook), this is still possible:
1) deprecated binding directives in imap.cfg are still parsed and supported (as of today), but do generate a warning.
2) The ability to start the imap-daemon with an alternate config-path (option -c) is unaffected of these changes:
The new binding directives (set in the context of gromox.cfg) are parsed in an alternate config-file, too (together with directives otherwise expected in imap.cfg).

bdimitrov

It would also be cool to update the manual core docu

https://docs.grommunio.com/admin/manual_core.html

so that new instances use the new configuration and not the old style

WalterH

I guess ,the documentation will be updated when this version is in the released channel.