Angel wrote: > Hi > > Ive just downloaded and compile 2.2.11-rc3 (statically) > > Firts i just stopped my current 2.2.11-rc2 deamons and then i tired to test > the new one 2.2.11-rc3 > > running "./dbmail-imapd -nv" > > states > > Oct 30 12:12:10 quasar dbmail-imapd[13631]: Debug:[serverparent] > serverparent.c,LoadServerConfig(+308): socket [] > Oct 30 12:12:10 quasar dbmail-imapd[13631]: Debug:[serverparent] > serverparent.c,LoadServerConfig(+320): binding to PORT [143]
That message is incorrect. It should read something like 'configured to bind to PORT [143]' since it merely describes what is read from dbmail.conf. > Oct 30 12:12:10 quasar dbmail-imapd[13631]: Debug:[serverparent] > serverparent.c,LoadServerConfig(+341): binding to IP [*] > Oct 30 12:12:10 quasar dbmail-imapd[13631]: Debug:[serverparent] > serverparent.c,LoadServerConfig(+348): no value for BACKLOG in config file. > Using default value [16] > > but netstat -atnp (as root) doesnt show any TCP/143 opened dbmail-imapd -n will run in stdin/stdout mode, aka inetd-mode. It won't open a network socket because it listens and talks to stdin/stdout only. > So i suspect the -nv mode of operation has some problem. dbmail-2.3 adds another mode: foreground network mode. Maybe that is what you were expecting here. But dbmail-2.2 doesn't support that. -- ________________________________________________________________ Paul Stevens paul at nfg.nl NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31 The Netherlands________________________________http://www.nfg.nl _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
