From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UapZW-0004h5-Sh for bitcoin-development@lists.sourceforge.net; Fri, 10 May 2013 15:49:26 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bluematt.me designates 173.246.101.161 as permitted sender) client-ip=173.246.101.161; envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me; Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me) by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1UapZW-0007SQ-0J for bitcoin-development@lists.sourceforge.net; Fri, 10 May 2013 15:49:26 +0000 Received: from [192.168.157.243] (unknown [74.125.61.18]) by mail.bluematt.me (Postfix) with ESMTPSA id BC6336082 for ; Fri, 10 May 2013 15:49:19 +0000 (UTC) User-Agent: K-9 Mail for Android MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----5VPR9P0QGBH42KHSGPW02RLUE68AR7" From: bitcoin-list@bluematt.me Date: Fri, 10 May 2013 17:49:16 +0200 To: bitcoin-development@lists.sourceforge.net Message-ID: X-Spam-Score: -1.8 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record -1.3 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 1.0 HTML_MESSAGE BODY: HTML included in message X-Headers-End: 1UapZW-0007SQ-0J Subject: [Bitcoin-development] Automated Weekly Testnet Alerts X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 May 2013 15:49:27 -0000 ------5VPR9P0QGBH42KHSGPW02RLUE68AR7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable In order to provide developers with a reasonable way to test their alert-= handling code, starting next Thursday, automated weekly alerts will be ma= de on testnet. They will contain the message "[TEST] This is a test alert broadcast at $= TIMESTAMP" (where $TIMESTAMP is the unix timestamp of initial broadcast),= will expire in between 2 and 4 hours and will have varying prioriry. Th= ey will be announced at 13:00 UTC (currently 9am EST). ------5VPR9P0QGBH42KHSGPW02RLUE68AR7 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable In order to provide developers with a reasonable way t= o test their alert-handling code, starting next Thursday, automated weekl= y alerts will be made on testnet.
They will contain the message "[TEST] This is a test alert broadcast= at $TIMESTAMP" (where $TIMESTAMP is the unix timestamp of initial b= roadcast), will expire in between 2 and 4 hours and will have varying pri= oriry. They will be announced at 13:00 UTC (currently 9am EST). ------5VPR9P0QGBH42KHSGPW02RLUE68AR7--