Delivery-Date: Fri, 02 Jan 2015 14:29:17 -0500
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,UNPARSEABLE_RELAY,
	URIBL_BLOCKED autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 78C151E0443
	for <archiver@seul.org>; Fri,  2 Jan 2015 14:29:15 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 3D7493284B;
	Fri,  2 Jan 2015 19:29:13 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 42C0932838
 for <tor-talk@lists.torproject.org>; Fri,  2 Jan 2015 19:29:09 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id mkVy0npniJnr for <tor-talk@lists.torproject.org>;
 Fri,  2 Jan 2015 19:29:09 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 214AC325F0
 for <tor-talk@lists.torproject.org>; Fri,  2 Jan 2015 19:29:09 +0000 (UTC)
Received: from plantcutter.riseup.net (plantcutter-pn.riseup.net [10.0.1.121])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 4A12A41E2E
 for <tor-talk@lists.torproject.org>; Fri,  2 Jan 2015 19:29:06 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1420226946; bh=KLqS0QXXvCsCwC0mEag9Snm8kLxa/ILjlOy2ThrNvuQ=;
 h=Date:From:To:Subject:From;
 b=f2SRUs/z4jygkUfpQdMNGsvHiQqwkOQsTXEE1tCPLGkcgMf+bmaYEitWm85nTQ+e7
 x/vl9K9jwJv7x+nVpD/wQDZiAfG6L13UJNYDTKDxjB1TAs2YtNKCriEPWIRYZbaW2b
 gWddvzf2LtDsL+QJmkU2/KLLvk4ZzJXqmG7IdrZU=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: cyrus_the_great) with ESMTPSA id 0E8A722505
Message-ID: <54A6F179.1090608@riseup.net>
Date: Fri, 02 Jan 2015 19:28:57 +0000
From: Cyrus <cyrus_the_great@riseup.net>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
X-Virus-Scanned: clamav-milter 0.98.5 at mx1
X-Virus-Status: Clean
Subject: [tor-talk] Unexpected SMTP
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

My server is behind a Tor transparent proxy on a separate machine.
Customers have just started reporting getting email from their sites,
and the headers show this to be coming from exit nodes. I can't see any
update news that the policy on SMTP has changed.

It might just be bad exit nodes, but according to one of these customers
emails have been coming constantly since Dec 31. For a lot of idiots
this means their sites are now leaking information. This can include
information on password resets, account activities, and even private
messages.

I can't find any mention of this change in the blog. It is possible some
exit nodes are not following the rules. This is an interesting
occurrence. It scared the crap out of me when I first heard about it.

-- 
CYRUSERV Onionland Hosting: http://cyruservvvklto2l.onion/
PGP public key: http://cyruservvvklto2l.onion/contact
This email is just for mailing lists and private correspondence.
Please use cyrus_the_great@lelantos.org for business inquiries.
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

