Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
+ promote_active_rules
+ pwd
+ /usr/bin/perl build/mkupdates/listpromotable
/usr/local/spamassassin/automc/svn/trunk
HTTP get: http://ruleqa.spamassassin.org/1-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/2-days-ago?xml=1
day 2 contains a --net mass-check! offsetting by an extra day
Use
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
On 9/24/18 5:33 AM, Sidney Markowitz wrote:
I was updating links on one of our wiki pages to https when I discovered
that
http://ruleqa.spamassassin.org does not take a https link.
Chrome reports ruleqa.spamassassin.org sent an invalid response.
ERR_SSL_PROTOCOL_ERROR
Firefox reports SSL
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
I was updating links on one of our wiki pages to https when I discovered that
http://ruleqa.spamassassin.org does not take a https link.
Chrome reports ruleqa.spamassassin.org sent an invalid response.
ERR_SSL_PROTOCOL_ERROR
Firefox reports SSL received a record that exceeded the maximum
On 9/24/2018 7:06 AM, Dave Jones wrote:
> On 9/24/18 5:33 AM, Sidney Markowitz wrote:
>> I was updating links on one of our wiki pages to https when I
>> discovered that
>> http://ruleqa.spamassassin.org does not take a https link.
>>
>> Chrome reports ruleqa.spamassassin.org sent an invalid
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
On 9/23/18 11:40 PM, Dave Warren wrote:
Looks like I got dropped again? I had a low disk space warning for a few
hours until more space was provisioned, I suspect I was out of date for
a few hours.
I just added back sa-update.razx.cloud.
Dave
On 9/24/18 8:30 AM, Kevin A. McGrail wrote:
On 9/24/2018 7:06 AM, Dave Jones wrote:
On 9/24/18 5:33 AM, Sidney Markowitz wrote:
I was updating links on one of our wiki pages to https when I
discovered that
http://ruleqa.spamassassin.org does not take a https link.
Chrome reports
On 9/24/18 8:30 AM, Kevin A. McGrail wrote:
On 9/24/2018 7:06 AM, Dave Jones wrote:
On 9/24/18 5:33 AM, Sidney Markowitz wrote:
I was updating links on one of our wiki pages to https when I
discovered that
http://ruleqa.spamassassin.org does not take a https link.
Chrome reports
On 9/24/2018 11:59 AM, Dave Jones wrote:
> Everything should be going to LE certs now with Chrome's push toward
> HTTPS everywhere and now that LE is doing wildcard certs. You can
> setup certbot easily then forget about it. Now if you are on Windows
> and IIS then it's a different story but I
Dear Supporter of Digital Freedom,
I want to thank you for using the Electronic Frontier Foundation’s Certbot to
enable HTTPS on your webserver. Each cert brings us closer to our goal of
encrypting the entire Internet and defending user privacy and free expression.
I also want to thank you for
19 matches
Mail list logo
