> Hum there is something not 100% yet. > > Imapd crashed, and I started it again, and it could not bind again, > only > after a few time. > telnet localhost 143 was refused so nothing was binding on it. > My guess is, imapd was unable to bind 'cause of alive connections, > could > this be possible? > I didn't checked it 100% but it seems that, next time I'll confirm > this!
Paul & Jon, I just confirmed this. After the change to support IPv6, IMAPD+POP3D can't start when there are connections in any other state than ESTABLISHED. I was monitoring this: tcp 0 1 192.168.1.222:143 192.168.1.29:1138 LAST_ACK tcp 0 1 195.23.114.76:143 84.91.32.171:1110 LAST_ACK tcp 0 1 195.23.114.76:143 81.193.16.3:1082 LAST_ACK tcp 0 1 195.23.114.76:143 84.91.32.171:1113 LAST_ACK tcp 0 1 195.23.114.76:143 81.193.16.3:1092 LAST_ACK tcp 0 1 195.23.114.76:143 84.91.224.11:1353 LAST_ACK tcp 0 1 192.168.0.222:143 85.244.91.38:19576 LAST_ACK IMAPD complains that "address is in use" which is not. A simple telnet localhost 143, turns into a connection refused. And only when this connections disappeared, IMAPD was able to start. Can you give a hand on this? Jorge, _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
