Re: Restricting the list
Robert Moskowitz <rgm3@is.chrysler.com> Thu, 08 February 1996 12:24 UTC
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10251;
8 Feb 96 7:24 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id ab10247;
8 Feb 96 7:24 EST
Received: from list.cren.net by CNRI.Reston.VA.US id aa05115; 8 Feb 96 7:24 EST
Received: from localhost (localhost [127.0.0.1]) by list.cren.net
(8.6.12/8.6.12) with SMTP id HAA09157; Thu, 8 Feb 1996 07:17:14 -0500
Received: from dimacs.rutgers.edu (root@dimacs.rutgers.edu [128.6.75.16]) by
list.cren.net (8.6.12/8.6.12) with ESMTP id HAA09113 for
<ietf-smtp@list.cren.net>; Thu, 8 Feb 1996 07:16:17 -0500
Received: from relay6.UU.NET (relay6.UU.NET [192.48.96.16]) by
dimacs.rutgers.edu (8.6.12+bestmx+oldruq+newsunq+grosshack/8.6.12) with ESMTP
id HAA14957 for <ietf-smtp@dimacs.rutgers.edu>; Thu, 8 Feb 1996 07:16:17 -0500
Received: from pilotx.firewall.is.chrysler.com by relay6.UU.NET with SMTP
id QQacaj19691; Thu, 8 Feb 1996 07:16:15 -0500 (EST)
Received: by pilotx.firewall.is.chrysler.com; id HAA11299;
Thu, 8 Feb 1996 07:35:48 -0500
Received: from clhubgw1.is.chrysler.com(172.29.128.203) by
pilotx.is.chrysler.com via smap (g3.0.1)
id sma011270; Thu, 8 Feb 96 07:35:44 -0500
Received: from rgm3.is.chrysler.com by clhubgw1.is.chrysler.com (5.x/SMI-4.1)
id AB23057; Thu, 8 Feb 1996 07:17:42 -0500
Message-Id: <2.2.32.19960208121522.00612358@pop3hub.is.chrysler.com>
Date: Thu, 08 Feb 1996 07:15:22 -0500
X-Orig-Sender: owner-ietf-smtp@list.cren.net
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Robert Moskowitz <rgm3@is.chrysler.com>
To: Jay <jay@aol.com>, info-ietf-smtp@uunet.uu.net
Subject: Re: Restricting the list
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Sender: t3125rm@pop3hub.is.chrysler.com
X-Mailer: Windows Eudora Pro Version 2.2 (32)
X-Listprocessor-Version: 8.0(beta) -- ListProcessor by CREN
At 10:05 AM 2/6/96 -0500, Jay wrote: >This raises the question.. is there already an IETF group thinking abouut >the general problems/solutions of commercial mailings? If not, should >there be? It's becoming a major issue for the online services, and I >assume for the ISPs and listserv owners as well. You can't assume that >they're being sent from a known account anymore, so the simple threat of >punishment isn't enough.. > >I don't want to take this thread too off-topic, but it's a subject of >great interest to me. Jay, do you follow com-priv? There your company is accused of encouraging spams, as you benefit in the turn of $5k per typical spam in connect costs for your users. There is a draft by John Myers for an ESMTP AUTH command to help control this.... Robert Moskowitz Chrysler Corporation (810) 758-8212
- Restricting the list Jim Conklin
- Re: Restricting the list Ned Freed
- Re: Restricting the list Donald E. Eastlake 3rd
- Re: Restricting the list Roger Fajman
- Re: Restricting the list John W. Noerenberg
- PS -- Re: Restricting the list Nathaniel Borenstein
- Re: Restricting the list Nathaniel Borenstein
- Re: Restricting the list Jay
- Re: Restricting the list Ben Nowlin
- Re: PS -- Re: Restricting the list Ned Freed
- Re: Restricting the list Ned Freed
- Re: Restricting the list John W. Noerenberg
- Re: Restricting the list RANDY
- Re: Restricting the list Robert Moskowitz
- Re: Restricting the list keld
- Re: Restricting the list Lindsay
- Re: Restricting the list Einar Stefferud
- Re: Restricting the list Jim Conklin
- Re: Restricting the list Tim Kehres