/etc/cron.weekly/update-notifier-common:
New release '18.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.
spamassassin.org:
pdnsutil list-zone spamassassin.org
OK (use 'load-zone spamassassin.org FILE' to restore)
svn status /usr/local/spamassassin/automc/svn/dns
M /usr/local/spamassassin/automc/svn/dns/spamassassin.org
OK
On 9/1/2018 1:03 PM, Dave Jones wrote:
> On 09/01/2018 10:24 AM, Kevin A. McGrail wrote:
>> Hi all,
>>
>> Q: is http://automc.spamassassin.org/updates/ the replacement for
>> http://buildbot.spamassassin.org/updatestage/?
>>
>> I'm working to update some scripts.
>>
>>
>> Regards,
>>
>> KAM
>>
>
>
On 09/01/2018 10:24 AM, Kevin A. McGrail wrote:
Hi all,
Q: is http://automc.spamassassin.org/updates/ the replacement for
http://buildbot.spamassassin.org/updatestage/?
I'm working to update some scripts.
Regards,
KAM
I believe this is correct. When I went through the previous Apache
ht
I found the previous source of the spam for incoming.spamassassin.org
It's some tags hidden on SA's website.
--
*Kevin A. McGrail*
703-798-0171 (wireless)
https://www.linkedin.com/in/kmcgrail
Hi all,
Q: is http://automc.spamassassin.org/updates/ the replacement for
http://buildbot.spamassassin.org/updatestage/?
I'm working to update some scripts.
Regards,
KAM
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.link
+ 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
HTTP get: http://ruleqa.spamassassin.org/3-days-ago?xml=1
+ mv rul