Unable to get into spamassassin2.zones.apache.org

2017-08-12 Thread Dave Jones
Kevin I am not able to login to this server like we did a few weeks ago with: ssh -p 80 r...@spamassassin-vm.apache.org spamassassin2.zones.apache.org It appears the special sshd setup you did is no longer listening on port 80. I tried various combinations to get in and no luck. -- Dave Jone

Re: Unable to get into spamassassin2.zones.apache.org

2017-08-12 Thread Kevin A. McGrail
I thought I turned that off after you were in normally. Give me a few. Regards, KAM On August 12, 2017 9:56:48 AM EDT, Dave Jones wrote: >Kevin >I am not able to login to this server like we did a few weeks ago with: > >ssh -p 80 r...@spamassassin-vm.apache.org >spamassassin2.zones.apache.org >

Re: Unable to get into spamassassin2.zones.apache.org

2017-08-12 Thread Kevin A. McGrail
Zones is an old Solaris box with nothing special as far as ssh or leap integration like the newer boxes. Use the normal port 22 as root. The alt port was for the old spamassassin-vm box wasn't it? What's a number I can call you on? Regards, KAM On August 12, 2017 9:56:48 AM EDT, Dave Jones wr

Re: Unable to get into spamassassin2.zones.apache.org

2017-08-12 Thread Kevin A. McGrail
On 8/12/2017 9:56 AM, Dave Jones wrote: Kevin I am not able to login to this server like we did a few weeks ago with: ssh -p 80 r...@spamassassin-vm.apache.org spamassassin2.zones.apache.org It appears the special sshd setup you did is no longer listening on port 80. I tried various combinati

Re: Unable to get into spamassassin2.zones.apache.org

2017-08-12 Thread Kevin A. McGrail
On 8/12/2017 10:36 AM, Kevin A. McGrail wrote: On 8/12/2017 9:56 AM, Dave Jones wrote: Kevin I am not able to login to this server like we did a few weeks ago with: ssh -p 80 r...@spamassassin-vm.apache.org spamassassin2.zones.apache.org It appears the special sshd setup you did is no longer l

checkMasscheckContribs.sh on sa-vm1.apache.org - not enough contributors for SVN 1804861

2017-08-12 Thread root
Corpus total: 148, Old: 84, Recent: 12, New: 20 SVN tagged rev in weekly_mass_check: 1804861 New masscheck submission listings in the past day: SVN rev (Match) File Name (Date) 1804861 (Yes) - spam-net-axb-ninja.log (Aug 12 12:10) 1804861 (Yes) - spam-net-grenier.log (Aug 12 09:04)

checkMasscheckContribs.sh on sa-vm1.apache.org - not enough contributors for SVN 1804861

2017-08-12 Thread root
Corpus total: 148, Old: 86, Recent: 10, New: 20 SVN tagged rev in weekly_mass_check: 1804861 New masscheck submission listings in the past day: SVN rev (Match) File Name (Date) 1804861 (Yes) - spam-net-axb-ninja.log (Aug 12 12:10) 1804861 (Yes) - spam-net-grenier.log (Aug 12 09:04)

pushDNStoSVN.sh on sa-vm1.apache.org - 0 DNS zones updated

2017-08-12 Thread root
spamassassin.org: pdnsutil list-zone spamassassin.org OK (use 'load-zone spamassassin.org FILE' to restore) svn status /usr/local/spamassassin/automc/svn/dns OK

updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-12 Thread noreply
2.3.3.updates (TXT) -> \"1804861\" File /usr/local/bin/updateDNS.disabled exists, not updating DNS.

updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-12 Thread noreply
0.4.3.updates (TXT) -> \"1804861\" File /usr/local/bin/updateDNS.disabled exists, not updating DNS.

updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-12 Thread noreply
0.3.3.updates (TXT) -> \"1804861\" File /usr/local/bin/updateDNS.disabled exists, not updating DNS.

updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-12 Thread noreply
1.3.3.updates (TXT) -> \"1804861\" File /usr/local/bin/updateDNS.disabled exists, not updating DNS.

updateDNS.sh on sa-vm1.apache.org - DNS updates disabled

2017-08-12 Thread noreply
3.3.3.updates (TXT) -> \"1804861\" File /usr/local/bin/updateDNS.disabled exists, not updating DNS.