You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2013/03/06 11:42:11 UTC

[Bug 6914] sa-update problem probably on ipv6

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

Kevin A. McGrail <km...@pccc.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
                 CC|                            |kmcgrail@pccc.com
         Resolution|---                         |WORKSFORME

--- Comment #1 from Kevin A. McGrail <km...@pccc.com> ---
Checking http://ipv6-test.com/validate.php for
spamassassin.apache.org/updates/MIRRORED.BY appears to work.

On the system, what does dig -t AAAA spamassassin.apache.org, show?

Also, what does ping6 2001:610:1:80bc:192:87:106:229, show?

After that, 

What do these commands give you?

curl -g "http://[2001:610:1:80bc:192:87:106:229]/updates/MIRRORED.BY"    

curl -g spamassassin.apache.org/updates/MIRRORED.BY


For the record, with the ipv6 address, that should fail because they are using
named virtual hosting.

So testing manually:

telnet 2001:610:1:80bc:192:87:106:229 80
Trying 2001:610:1:80bc:192:87:106:229...
Connected to 2001:610:1:80bc:192:87:106:229 (2001:610:1:80bc:192:87:106:229).
Escape character is '^]'.
GET /updates/MIRRORED.BY http/1.1
Host: spamassassin.apache.org

HTTP/1.1 200 OK
Date: Wed, 06 Mar 2013 10:40:26 GMT
Server: Apache/2.4.4 (Unix) OpenSSL/1.0.0g
Last-Modified: Tue, 09 Oct 2012 19:47:42 GMT
ETag: "12b-4cba59c781380"
Accept-Ranges: bytes
Content-Length: 299

# test mirror: zone, cached via Coral
#http://buildbot.spamassassin.org.nyud.net:8090/updatestage/
#Removed on 2012-09-26 per bug 6838
#http://daryl.dostech.ca/sa-update/asf/ weight=5
http://sa-update.dnswl.org/ weight=1
http://www.sa-update.pccc.com/ weight=5
http://sa-update.secnap.net/ weight=5

So I think you might have a networking issue.

It is NOT uncommon with ipv6 not to have all ipv6 routable and accessible.  You
might have to talk to your ISP.

-- 
You are receiving this mail because:
You are the assignee for the bug.