Milter-greylist

Hi,

>>>>> On Fri, 15 May 2009 11:15:28 +0200
>>>>> attila.bruncsak@... <attila.bruncsak@...> said:

attila> On my Tru64 UNIX system it looks working but I get
attila> "milter-greylist: cannot start MX sync, bind failed: Address already in
attila> use"
attila> message for every envelop recipient,
attila> practically flooded with that message.

I suspect you got the message in question even before you tried to fix
the problem, and you get "cannot set IPV6_V6ONLY:" message as well,
right? 
If so, your system uses IPv4-mapped IPv6 address and we cannot disable
use of it.  In that case, your system listen IPv4 by IPv6 socket.  So,
you don't need to listen on IPv4 separately.

attila> Probably with SO_REUSEPORT that message would go away.

If is is your case, the error is expected behavior, and use of
SO_REUSEPORT is not good way, IMHO.  Just disabling the message is
enough.

Index: sync.c
diff -u -p sync.c.orig sync.c
--- sync.c.orig	2009-05-15 16:55:20.000000000 +0900
+++ sync.c	2009-05-15 18:42:14.249372861 +0900
@@ -961,15 +961,19 @@ sync_listen(addr, port, sms)
 		optval = 1;
 		if ((setsockopt(s, IPPROTO_IPV6, IPV6_V6ONLY,
 		    &optval, sizeof(optval))) != 0) {
+#if 0
 			mg_log(LOG_ERR, "cannot set IPV6_V6ONLY: %s",
 			    strerror(errno));
+#endif
 		}
 	}
 #endif
 
 	if (bind(s, SA(&laddr), laddrlen) != 0) {
+#if 0
 		mg_log(LOG_ERR, "cannot start MX sync, bind failed: %s",
 		    strerror(errno));
+#endif
 		sms->runs = 0;
 		close(s);
 		return;


Sincerely,

--
Hajimu UMEMOTO @ Internet Mutual Aid Society Yokohama, Japan
ume@...  ume@{,jp.}FreeBSD.org
http://www.imasy.org/~ume/