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...@spamassassin.apache.org on 2020/09/16 14:11:12 UTC
[Bug 7856] New: Can't connect to sa-update.secnap.net:80 (connect:
No route to host): 500
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7856
Bug ID: 7856
Summary: Can't connect to sa-update.secnap.net:80 (connect: No
route to host): 500
Product: Spamassassin
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: major
Priority: P2
Component: Website/Infrastructure
Assignee: dev@spamassassin.apache.org
Reporter: admin@servmysite.net
Target Milestone: Undefined
It appears access to sa-update.secnap.net:80 is not available. Can you check
this domain? see below.
/etc/cron.daily/spamassassin:
http: GET http://sa-update.secnap.net/1881731.tar.gz request failed: 500 Can't
connect to sa-update.secnap.net:80 (connect: No route to host): 500 Can't
connect to sa-update.secnap.net:80 (connect: No route to host)
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7856] Can't connect to sa-update.secnap.net:80 (connect: No
route to host): 500
Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7856
Kevin A. McGrail <km...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
CC| |kmcgrail@apache.org
--- Comment #2 from Kevin A. McGrail <km...@apache.org> ---
Disabled with Committed revision 1881807.
Thanks to SecNap for their many years of donated update service.
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 7856] Can't connect to sa-update.secnap.net:80 (connect: No
route to host): 500
Posted by bu...@spamassassin.apache.org.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7856
Bill Cole <bi...@apache.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |billcole@apache.org
--- Comment #1 from Bill Cole <bi...@apache.org> ---
We're aware of this. It has been down for a few days, and we don't have working
contact information for anyone able to revive it. Efforts continue
The sa-update script should recover from this by trying another mirror. Is that
not working for you?
--
You are receiving this mail because:
You are the assignee for the bug.