RE: 6. Solutions - Longterm - Replacing SMTP (Re: [Asrg] Bogus reasoning)

"Elric Pedder" <elric@novitraq.com> Wed, 02 July 2003 22:10 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23649 for <asrg-archive@odin.ietf.org>; Wed, 2 Jul 2003 18:10:28 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xpng-0000cj-5U for asrg-archive@odin.ietf.org; Wed, 02 Jul 2003 18:10:04 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h62MA4fY002393 for asrg-archive@odin.ietf.org; Wed, 2 Jul 2003 18:10:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xpng-0000cW-2Z for asrg-web-archive@optimus.ietf.org; Wed, 02 Jul 2003 18:10:04 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23499; Wed, 2 Jul 2003 18:09:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Xpnb-0002h8-00; Wed, 02 Jul 2003 18:09:59 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19Xpna-0002h5-00; Wed, 02 Jul 2003 18:09:58 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xpnd-0000Z2-FZ; Wed, 02 Jul 2003 18:10:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19Xpmz-0000Y1-Qq for asrg@optimus.ietf.org; Wed, 02 Jul 2003 18:09:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23257 for <asrg@ietf.org>; Wed, 2 Jul 2003 18:09:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Xpmu-0002f1-00 for asrg@ietf.org; Wed, 02 Jul 2003 18:09:16 -0400
Received: from dns.novitraq.com ([204.92.85.2]) by ietf-mx with smtp (Exim 4.12) id 19Xpmt-0002ep-00 for asrg@ietf.org; Wed, 02 Jul 2003 18:09:15 -0400
Received: from kensington (kensington [204.92.85.4]) by novitraq.com with SMTP (Mailtraq/2.3.0.1402) id NVTRD8320C74 for asrg@ietf.org; Wed, 02 Jul 2003 18:05:48 -0400
From: Elric Pedder <elric@novitraq.com>
To: asrg@ietf.org
Subject: RE: 6. Solutions - Longterm - Replacing SMTP (Re: [Asrg] Bogus reasoning)
Organization: Novitraq Inc
Message-ID: <009901c340e6$802a08c0$04555ccc@kensington>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <3F03428E.2010401@garbagedump.com>
X-Hops: 1
Content-Transfer-Encoding: 7bit
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Wed, 02 Jul 2003 18:08:36 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On 
> Behalf Of C. Wegrzyn
> Sent: July 2, 2003 16:38
> To: Barry Shein
> Cc: gep2@terabites.com; Yakov Shafranovich; asrg@ietf.org
> Subject: Re: 6. Solutions - Longterm - Replacing SMTP (Re: 
> [Asrg] Bogus reasoning)

> I believe the only real alternative is for every ISP (and 
> this can be done I believe) to take on a per-email 
> transaction fee.

This proposal is made quite often, but I cannot see how it
would work.

SMTP does not require the participation of any ISP other than
for the transmission of packets.  In order to levy a charge,
the ISP would have to monitor your traffic, detect SMTP 
usage, detect actual e-mail delivery, and bill you for it.

What you create is an incentive for users to avoid the
detection of SMTP delivery -- a whole new problem.

Without getting in to the "big brother" concepts or using
some sort of "centralised register of authorised e-mail
delivery agents" perhaps ISPs could bill a higher rate for 
port 25-destined traffic than other traffic, and require that 
every SMTP transaction contain only one RCPT address.

Unfortunately port 25-destined traffic does not actually
cost any more than other-port-destined traffic.  Therefore
in a competitive marketplace prices will be driven down to
cost+margin.

The only weapon I can think of against market competition is
the government.  So... would you accept a government tax on
e-mail?  

Ultimately, I just don't see how you could charge for e-mail.

-- 
Elric Pedder
Mailtraq Development (www.mailtraq.com)


_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg