Re: [Asrg] Need to know

Scott Nelson <scott@spamwolf.com> Tue, 27 May 2003 07:54 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02645 for <asrg-archive@odin.ietf.org>; Tue, 27 May 2003 03:54:37 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4R7sYV26647 for asrg-archive@odin.ietf.org; Tue, 27 May 2003 03:54:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4R7sXB26641 for <asrg-web-archive@optimus.ietf.org>; Tue, 27 May 2003 03:54:33 -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 DAA02607; Tue, 27 May 2003 03:53:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19KZFq-0001fi-00; Tue, 27 May 2003 03:52:18 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19KZFp-0001ff-00; Tue, 27 May 2003 03:52:17 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4R7pVB26507; Tue, 27 May 2003 03:51:31 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4R7o4B26464 for <asrg@optimus.ietf.org>; Tue, 27 May 2003 03:50: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 DAA02438 for <asrg@ietf.org>; Tue, 27 May 2003 03:49:38 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19KZBl-0001cZ-00 for asrg@ietf.org; Tue, 27 May 2003 03:48:05 -0400
Received: from adsl-66-120-64-133.dsl.snfc21.pacbell.net ([66.120.64.133] helo=magic1.org) by ietf-mx with smtp (Exim 4.12) id 19KZBk-0001cL-00 for asrg@ietf.org; Tue, 27 May 2003 03:48:04 -0400
Message-Id: <aT5vaIe86J8qbrFzc02@x>
To: asrg@ietf.org
From: Scott Nelson <scott@spamwolf.com>
Subject: Re: [Asrg] Need to know
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: Tue, 27 May 2003 00:49:41 -0700

At 01:24 AM 5/27/03 +0200, Markus Stumpf wrote:
>On Sat, May 24, 2003 at 11:27:15PM -0700, Scott Nelson wrote:
>> >Why would limiting number of recipients make a difference? With today's 
>> >computers and Internet connections cheap, additional SMTP sessions will be 
>> >initiated just increasing Internet traffic.
>> 
>> That's an interesting theory you've posited.
>> How, I wonder, could we prove it?
>
>qmail only does one recipient delivery.
>Statistics show (haven't an URL ready, sorry) that the overall "overhead"
>against multi-recipient systems is nearly unmeasurable. Of course there ARE
>situations, were it is a big gain to use multi-recipient strategy.
>
>Most of the time recipient sorting on the sender site is rather CPU and
>DNS expensive so in the same time some mailservers spend sorting
>other actually finish the deliveries.
>

I'm guessing, but I think the qmail sorting problem is quite different 
from the spammer sorting problem.  Spammers don't have to sort on the
fly - they can sort their lists well before hand, and the list only 
needs to be sorted once.

Still, if we knew the average number of recipients for spam 
messages currently, and the average number for non-spam,
then we could at least make a reasonable estimate of the effects 
of limiting it, in terms of number of connections, and total bandwidth.  
If it turns out the average number of recipients
is less than 1.1, then clearly limiting it to one wouldn't
have much effect at all.  If it's 50, then that's nearly a
50 to 1 increase in raw network cost.  To fully understand
the ultimate effect we'd still need to know what effect raising
the cost of sending has on spam and non-spam, but "the average
number of recipients" is at least one of the things we "need to know".


It occurs to me that if the SMTP protocol was changed so that it 
didn't /guarantee/ 100 recipients, it could still allow more than
one for trusted senders.  (local policy would dictate of course,
but the I'd make the wording "SHOULD limit to one, unless the 
sender is trusted") Established mailing lists wouldn't be affected
as much, since they would probably be whitelisted relatively 
quickly by the big ISPs.  

Scott Nelson <scott@spamwolf.com>
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg