From owner-freebsd-questions@FreeBSD.ORG Wed May 6 20:13:02 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E90968AE; Wed, 6 May 2015 20:13:02 +0000 (UTC) Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42]) by mx1.freebsd.org (Postfix) with ESMTP id D4F5B17CB; Wed, 6 May 2015 20:13:02 +0000 (UTC) Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128]) (authenticated bits=0) by shell1.rawbw.com (8.14.9/8.14.9) with ESMTP id t46KBh0H092026 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 6 May 2015 13:11:44 -0700 (PDT) (envelope-from yuri@rawbw.com) X-Authentication-Warning: shell1.rawbw.com: Host c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be yuri.doctorlan.com Message-ID: <554A757E.2060909@rawbw.com> Date: Wed, 06 May 2015 13:11:42 -0700 From: Yuri User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0 MIME-Version: 1.0 To: dweimer@dweimer.net CC: FreeBSD Questions , owner-freebsd-questions@freebsd.org Subject: Re: BSDstats-6.0 has been released References: <5549BAA1.4070000@rawbw.com> <1e2855e2cbad8dbe45786773b64dc2da@dweimer.net> In-Reply-To: <1e2855e2cbad8dbe45786773b64dc2da@dweimer.net> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 06 May 2015 20:13:03 -0000 On 05/06/2015 05:43, dweimer wrote: > It seems to fail its manual send after updating my system from the old > port, I didn't chose the TOR option when I built the script if that > matters on this issue. > > # bsdstats-send > BSDstats failed: token enabling request failed > > Any Ideas? Actually, I got the word that this was the server bug that is now fixed. So please try again, and confirm that this is fixed for you. Thanks, Yuri