Support <surgemail-support@netwinsite.com> wrote:

Sorry that comment is out of date I will update. It is functional already and has

been for some time, let me know if you strike any serious trouble with it. (be sure to >install the latest release of course)

 

Thank you, one thing I have noticed is that turning on IPv6 seems to break IPv4 address matching, when connecting via the webui; a "::ffff" shows up in front of the IP address. The error that shows up says "Sorry you are not connecting from a valid ip address (::ffff:72.20.181.8) "

When I have configured g_admin_ip "127.*,72.20.181.0/24" in surgemail.ini

 

So the IPv4 CIDR match rule doesn't match and it shows me coming from an IPv6 mapped IPv4 address, as soon as v6 is turned on in surgemail.

 

 

And a similar thing happens with g_relay_allow_ip

Client IP addresses show up with the embedded ::ffff:*

 

I have noted the problem goes away when setting kernel sysctl

 

echo 1 >/proc/sys/net/ipv6/bindv6only

 

And restarting surgemail; afterwards, Surgemail seems to accept connection on both IPv4 and IPv6 addresses and show no spurious ::ffff for IPv4 addresses.

 

I assume surgemail's not binding the IPv6 listening port with IPV6_V6ONLY; so under Linux defaults, an IPv4 connection can be accepted on the IPv6 listening socket, and "look" like an ipv6 peer with the ::ffff address to the application?

 

--

Regards,

Jimmy