IETF Logo Mail Archive

Re: [Asrg] Email service assumptions and making system-wide changes

Barry Shein <bzs@world.std.com> Wed, 18 January 2006 23:45 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EzMzV-0008IZ-Cd; Wed, 18 Jan 2006 18:45:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EzMzU-0008IU-T7 for asrg@megatron.ietf.org; Wed, 18 Jan 2006 18:45:24 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21467 for <asrg@ietf.org>; Wed, 18 Jan 2006 18:43:59 -0500 (EST)
Received: from pcls1.std.com ([192.74.137.141] helo=TheWorld.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EzN7v-0004Ov-0o for asrg@ietf.org; Wed, 18 Jan 2006 18:54:07 -0500
Received: from world.std.com (world.std.com [192.74.137.5]) by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id k0INhW5P012407 for <asrg@ietf.org>; Wed, 18 Jan 2006 18:43:37 -0500
Received: (from bzs@localhost) by world.std.com (8.12.8p1/8.12.8) id k0INf54I003995; Wed, 18 Jan 2006 18:41:05 -0500 (EST)
From: Barry Shein <bzs@world.std.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <17358.53777.280181.751442@world.std.com>
Date: Wed, 18 Jan 2006 18:41:05 -0500
To: asrg@ietf.org
Subject: Re: [Asrg] Email service assumptions and making system-wide changes
In-Reply-To: <OFFE10648F.FD8AB2E7-ON802570FA.0035C93C-802570FA.0035EABB@slc.co.uk>
References: <17356.38171.951736.912706@world.std.com> <OFFE10648F.FD8AB2E7-ON802570FA.0035C93C-802570FA.0035EABB@slc.co.uk>
X-Mailer: VM 7.07 under Emacs 21.2.2
X-Spam-Status: No, score=-4.2 required=10.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.1.0
X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pcls1.std.com
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
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>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

On January 18, 2006 at 09:48 Danny_Angus@slc.co.uk (Danny Angus) wrote:
 > 
 > 
 > 
 > > So by your reasoning we shouldn't have bothered to close the open
 > > relays?
 > 
 > A truly effective solution to the real problem would not *require* that
 > open relays be closed, it would involve a transaction between the sender
 > and the recipient, not impose a constraint on the transport layer.
 > 

In other words, it'd find some other way to achieve the same effect of
closing open relays.

I suppose one could argue that simply forbidding unauthorized
third-party email to be forwarded through their system seems a
heavy-handed way to accomplish the desired effect.

But then again it's not clear how any other solution could allow
forwarding of unauthorized third-party mail w/o problem, though I
suppose variations on the basic theme could arise.

-- 
        -Barry Shein

The World              | bzs@TheWorld.com           | http://www.TheWorld.com
Purveyors to the Trade | Voice: 800-THE-WRLD        | Login: Nationwide
Software Tool & Die    | Public Access Internet     | SINCE 1989     *oo*

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

v2.23.0 | Report a Bug | By Email