Delivery-Date: Mon, 02 Mar 2015 14:19:21 -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.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	T_RP_MATCHES_RCVD,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 C4B2E1E0CFA
	for <archiver@seul.org>; Mon,  2 Mar 2015 14:19:19 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6B88034108;
	Mon,  2 Mar 2015 19:19:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AD58234107
 for <tor-talk@lists.torproject.org>; Mon,  2 Mar 2015 19:19:13 +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 pE5w6I6BWky0 for <tor-talk@lists.torproject.org>;
 Mon,  2 Mar 2015 19:19:13 +0000 (UTC)
Received: from mail.confidantmail.org (mail.confidantmail.org [54.213.166.118])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 851F734105
 for <tor-talk@lists.torproject.org>; Mon,  2 Mar 2015 19:19:13 +0000 (UTC)
Received: from [192.168.1.176] (rrcs-24-43-0-6.west.biz.rr.com [24.43.0.6])
 (Authenticated sender: mike)
 by mail.confidantmail.org (Postfix) with ESMTPSA id 3C426A131A
 for <tor-talk@lists.torproject.org>; Mon,  2 Mar 2015 19:18:38 +0000 (UTC)
Message-ID: <54F4B7AC.4080507@confidantmail.org>
Date: Mon, 02 Mar 2015 11:19:08 -0800
From: Mike Ingle <mike@confidantmail.org>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <54F47E8E.6040908@infosecurity.ch>
In-Reply-To: <54F47E8E.6040908@infosecurity.ch>
Subject: Re: [tor-talk] Fixing the problem of sending email from Tor: Proof
 of Work based system
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

That email system, with built in Tor support and proof of work based 
anti-spam, has already been built.
Get it here:
http://www.confidantmail.org
Mike Ingle <mike@confidantmail.org> d2b89e6f95e72e26e0c917d02d1847dfecfcd0c2


On 3/2/2015 7:15 AM, Fabio Pietrosanti (naif) - lists wrote:
> Hi all,
>
> at GlobaLeaks we're encountering a lot of issues related to sending of
> email notification behind Tor, with almost any email provider.
>
> If the sender provider don't block you today, it will block you tomorrow
> at random.
> If the recipient's provider don't mark you as Spam today, it will do it
> tomorrow at random.
>
> That's a known Tor's outgoing email problem, still unfixed.
>
> That's because any provider that's used continuously behind Tor, before
> or later get abused/will block you (including Google), and because the
> IP reputation of any Tor Exit Relay on the internet is very bad.
>
> So, thinking on how to fix it, why don't create an outbound email system
> that's based on proof of work to heavily disincentive spammer/fraudster,
> enabling a Tor user to send email to general Internet users without
> major problems?
>
> If my Tor client computer had to run heavy computations for 15-30s to
> send a single email, i think that spammer and fraudster will be KO, but
> an average user could still find it acceptable because a single user is
> "low volume" but any automated systems are high-volume.
>
> A Tor Exit node could require such a "proof of work" from a Tor Client
> in order to enable a single outgoing connection for that "highly
> sensible exit port" (25, 465, 587).
>
> If this method work, it should be required to improve Tor to run a
> dedicated "Per Port  Exit OutBoundAddress" that would enable to have a
> dedicated IP address for outgoing connections trough port 25/465/587.
> This IP address will have a good reputation on the internet, because
> will be only used by real-users to send a relatively limited amount of
> emails.
>
> That way it would be transparent for the end-user to send outgoing email
> trough Tor.
>
> If this would be in place, the Tor2web inbound SMTP feature #LINKTICKET,
> to be developed before or later, will complement this picture allowing
> full inbound/outbound SMTP email traffic.
>
>
> Beware: I'm pro-compatibility, i don't like any "let's make/use a new
> protocol, Email is dead, SMTP is dead, PGP is dead!" and i concretely
> think that we shall improve the existing internet-standards to fulfill
> new requirements, rather than create new ones.
>
>
>   

-- 
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

