We have been using IPv6 with Surge for quite some time. In order for
Surge to use IPv6 you have to bind it to that appropriate IP just like a
multi-homed IPv4 server. We send quite a bit of IPv6 email actually.
As for the ffff: thing, I think you can use g_dns_system=true but be
warned, they broke some other things like PTR lookups in later versions
when that's on.
--Ed
On 07/05/2012 06:08 PM, VinnyHIDDEN@@Dell.com wrote:
> While on the topic, does Surgemail default to sending on IPv6 if
> enabled? I just flipped it on after configuring IPv6 (Windows 2003) and
> all major functionality seems to work fine, but when I sent an email to
> my gmail address whose MX records have AAAA records, it seemed to talk
> to Gmail on IPv4 for some reason.
>
> -Vinny
>
> *From:*Frank Bulk [mailtoHIDDEN@mypremieronline.com]
> *Sent:* Thursday, July 05, 2012 6:03 PM
> *To:* 'surgemailHIDDEN@etwinsite.com'
> *Subject:* RE: [SurgeMail List] re: ipv6 support
>
> We saw the same thing here. Any chance you can update the matching
> check o that ::ffff:<IPv4 address> is auto-added?
>
> Frank
>
> *From:*Support [mailto:surgemailHIDDEN@t@netwinsite.com]
> <mailto:[mailto:surgemailHIDDEN@t@netwinsite.com]>
> *Sent:* Wednesday, July 04, 2012 11:25 PM
> *To:* surgemailHIDDEN@etwinsite.com <mailto:surgemail-list@netwinsite.com>
> *Subject:* Re: [SurgeMail List] re: ipv6 support
>
> Support <surgemailHIDDEN@t@netwinsite.com
> <mailto:surgemailHIDDEN@t@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) "
>
> This is what linux reports as the actual address, we do try and cope
> with this but it doesn't cope with an ipv4 cidr, it will accept a wild
> card, e.g.
>
> You can do this...
>
> g_admin_ip "127.*,72.20.181.*"
>
> so if you avoid cidr notation the problem will go away.
>
> ChrisP.
>
> 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
>
> ------------------------------------------------------------------------
>
> Sent with YesImOnline email client http://yesimonline.com/yes (free client)
>
--
-----------------------------------------------------------
EAS Enterprises LLC
World Class Web and Email Hosting Solutions
IPv6 ready today for your needs of tomorrow!
Ask us about dual-stacking your site
www.easent.net
|
