http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5388
[EMAIL PROTECTED] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From [EMAIL PROTECTED] 2007-03-24 23:32 -------
Figured out the issue with the ipv4 version - I have an additional local
loopback address that is part of an LVS/keepalived scheme, and that address was
accept()ing connections on tcp783 every second as part of LVS' tcpcheck. At the
initiation of these connections, the socket object returns a null ->peername()
in peer_info_from_socket(), which causes the error messages I listed above. As
a workaround, we will configure LVS/keepalived to perform health status checks
via the correct interface at both ends, but also teach it to ping spamd with a
proper ping header.
I have not tested it, but I assume the ipv6 version error messages are caused
similarly.
I would also like to take this opportunity to request an additional flag for
spamd (--bind-ipv4-only) that would override/condition the eval{} in the second
BEGIN{}, since in our case, I would like to keep the debian package
libio-socket-inet6-perl installed, but still force spamd to bind to ipv4 only.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
