Anyone have a thought?
-------- Forwarded Message -------- Subject: [Bug 7706] New: Connection to spamassassin.apache.org times out Date: Thu, 11 Apr 2019 13:44:14 +0000 From: bugzilla-dae...@spamassassin.apache.org To: d...@spamassassin.apache.org https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7706 Bug ID: 7706 Summary: Connection to spamassassin.apache.org times out Product: Spamassassin Version: 3.4.0 Hardware: Other OS: Linux Status: NEW Severity: normal Priority: P2 Component: sa-update Assignee: d...@spamassassin.apache.org Reporter: ma...@entekadesign.com Target Milestone: Undefined I am running spamassassin 3.4.0 on Centos 7.6 in a DigitalOcean VPS. The following cronjob runs nightly, returning the following error: /usr/share/spamassassin/sa-update.cron error: unable to refresh mirrors file for channel updates.spamassassin.org, using old file Apparently, my droplet isn't reaching the relevant servers. Testing connection with telnet: [root@mail ~]# telnet -d spamassassin.apache.org 443 Trying 95.216.24.32... telnet: connect to address 95.216.24.32: Connection timed out Trying 40.79.78.1... telnet: connect to address 40.79.78.1: Connection timed out Trying 2a01:4f9:2a:185f::2... telnet: connect to address 2a01:4f9:2a:185f::2: Network is unreachable Testing connection with curl: [root@mail ~]# curl -v -I spamassassin.apache.org * About to connect() to spamassassin.apache.org port 80 (#0) * Trying 95.216.24.32... * Connection timed out * Trying 40.79.78.1... * After 86336ms connect time, move on! * Trying 2a01:4f9:2a:185f::2... * Failed to connect to 2a01:4f9:2a:185f::2: Network is unreachable * Failed connect to spamassassin.apache.org:80; Network is unreachable * Closing connection 0 curl: (7) Failed to connect to 2a01:4f9:2a:185f::2: Network is unreachable Testing with traceroute: [root@mail ~]# traceroute -T spamassassin.apache.org traceroute to spamassassin.apache.org (40.79.78.1), 30 hops max, 60 byte packets 1 67.205.144.253 (67.205.144.253) 0.868 ms 67.205.144.254 (67.205.144.254) 0.848 ms 0.827 ms 2 138.197.251.98 (138.197.251.98) 2.929 ms 138.197.248.86 (138.197.248.86) 0.870 ms 138.197.251.98 (138.197.251.98) 2.903 ms 3 138.197.248.70 (138.197.248.70) 0.780 ms nyc-76e-1.ntwk.msn.net (198.32.118.18) 1.097 ms 138.197.248.70 (138.197.248.70) 0.757 ms 4 nyc-76e-1.ntwk.msn.net (198.32.118.18) 0.998 ms be-75-0.ibr02.nyc30.ntwk.msn.net (104.44.10.99) 11.754 ms nyc-76e-1.ntwk.msn.net (198.32.118.18) 1.064 ms 5 be-75-0.ibr02.nyc30.ntwk.msn.net (104.44.10.99) 11.856 ms 11.838 ms 11.744 ms 6 be-5-0.ibr01.bn6.ntwk.msn.net (104.44.16.47) 11.726 ms be-7-0.ibr02.bn6.ntwk.msn.net (104.44.16.49) 11.283 ms be-5-0.ibr01.bn6.ntwk.msn.net (104.44.16.47) 11.205 ms 7 be-5-0.ibr01.bn6.ntwk.msn.net (104.44.16.47) 11.310 ms ae163-0.icr04.bn6.ntwk.msn.net (104.44.21.76) 13.312 ms be-5-0.ibr01.bn6.ntwk.msn.net (104.44.16.47) 11.101 ms 8 * ae160-0.icr01.bn6.ntwk.msn.net (104.44.21.70) 10.754 ms ae143-0.icr04.bn6.ntwk.msn.net (104.44.21.68) 10.744 ms 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * DigitalOcean support can't help. Could my IP be blocked? What else could explain this behavior? Thanks! -- You are receiving this mail because: You are the assignee for the bug.