spamassassin-dev December 2011 archive
Main Archive Page > Month Archives  > spamassassin-dev archives
spamassassin-dev: [Bug 6712] IPv6 DNS Work

[Bug 6712] IPv6 DNS Work

From: <bugzilla-daemon_at_nospam>
Date: Thu Dec 01 2011 - 20:18:12 GMT
To: dev@spamassassin.apache.org

https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6712

--- Comment #7 from Mark Martinec <Mark.Martinec@ijs.si> 2011-12-01 20:18:12 UTC ---
> During the past few days I have prepared another fresh node
> with inet6 connectivity only, for testing SpamAssassin. Looks fine.
> I only need NAT64 to access Razor servers (not sure about DCC)
> and to be able to fetch SA source update from svn.apache.org.
>
> The DNS64 is running fine (available since bind 9.8),
> but the NAT64 is still giving me hard time.

Just a short progress report:

Ditched the ecdysis-fedora-14-x86_64-20101117.iso and went for
ecdysis-openbsd-4.6-amd64-20100226.iso on a virtual box, now
finally the NAT64 works!

On an IPv6-only host I'm now able to fetch SpamAssassin sources from SVN!
Also also the bootstraping of MIRRORED.BY works through NAT64.
Can also ssh to people.apache.org .

The t/dcc.t test is successful (just mutters an unnecessary warning
about a broken Razor!? )

The only test (that I know of) that is failing is Razor.
The NAT64 would provide it with a connectivity to an IPv4-only razor
server, but the razor agent perl module is unable to use an inet6 socket
and gives up, claiming that the protocol is not supported:

$ razor-admin -discover -d
  [ 5] Connecting to discovery.razor.cloudmark.com ...
  [ 3] Unable to connect to discovery.razor.cloudmark.com:2703;
    Reason: Protocol not supported.
  [ 5] Razor Discovery Server discovery.razor.cloudmark.com is unreachable

All the rest seems fine, all the tests (except razor) pass,
including the long and the network tests:
t/config:
  run_long_tests=y
  run_net_tests=y
  run_dcc_tests=y
  run_spamd_prefork_stress_test=y

-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.