From exim@www1.ietf.org  Mon Mar  1 01:35:59 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08918
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 01:35:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axh1W-0004c7-H3
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 01:35:30 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i216ZUL4017730
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 01:35:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axh1W-0004br-B2
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 01:35:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08909
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 01:35:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axh1T-0001Ao-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 01:35:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axh0U-00016X-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 01:34:27 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axh0L-00012N-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 01:34:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axh06-0004Rq-0u; Mon, 01 Mar 2004 01:34:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxgeF-0002VD-HA
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 01:11:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA08272
	for <asrg@ietf.org>; Mon, 1 Mar 2004 01:11:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxgeC-000715-00
	for asrg@ietf.org; Mon, 01 Mar 2004 01:11:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxgdF-0006x6-00
	for asrg@ietf.org; Mon, 01 Mar 2004 01:10:25 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axgd0-0006t9-00
	for asrg@ietf.org; Mon, 01 Mar 2004 01:10:10 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1Axgd1-0000sf-00
	for asrg@ietf.org; Mon, 01 Mar 2004 01:10:11 -0500
Received: from [68.244.153.112] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1Axgd0-0002jp-00
	for asrg@ietf.org; Mon, 01 Mar 2004 01:10:11 -0500
Message-ID: <4042D3BA.3080903@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 3b. LMAP BoF - Chat channel available for the BoF
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 01:10:02 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

There will be a Jabber channel for the BoF and hopefully a scribe. The 
channel is:

marid@ietf.xmpp.org

The BoF is also going to be multicasted, those who want to watch can use 
RealPlayer or other software, and follow instructions here:

http://www.ietf.org/meetings/multicast_59.html
http://videolab.uoregon.edu/events/ietf/ietf59.html

Yakov

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



From exim@www1.ietf.org  Mon Mar  1 02:24:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24442
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 02:24:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axhm5-00078o-Hr
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 02:23:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i217NbE9027428
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 02:23:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axhm4-00078J-7i
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 02:23:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24396
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 02:23:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axhm0-0006NR-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 02:23:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axhl6-0006I7-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 02:22:36 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axhkh-0006Cq-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 02:22:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxhkX-0006Zo-V0; Mon, 01 Mar 2004 02:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axhk7-0006Q4-8N
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 02:21:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24217
	for <asrg@ietf.org>; Mon, 1 Mar 2004 02:21:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axhk3-0006Aq-00
	for asrg@ietf.org; Mon, 01 Mar 2004 02:21:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxhjH-00065I-00
	for asrg@ietf.org; Mon, 01 Mar 2004 02:20:44 -0500
Received: from mail.chariot.net.au ([203.87.95.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axhir-0005zC-00
	for asrg@ietf.org; Mon, 01 Mar 2004 02:20:17 -0500
Received: from localhost (avs1.sa.chariot.net.au [203.87.94.5])
	by mail.chariot.net.au (Postfix) with ESMTP id 7824A61D25
	for <asrg@ietf.org>; Mon,  1 Mar 2004 17:50:07 +1030 (CST)
Received: from mail.chariot.net.au ([203.87.95.38])
 by localhost (avs1.sa.chariot.net.au [203.87.94.5]) (amavisd-new, port 10024)
 with LMTP id 21750-04-6 for <asrg@ietf.org>;
 Mon,  1 Mar 2004 17:50:07 +1030 (CST)
Received: from rebel (ppp-065.cust203-87-126.ghr.chariot.net.au [203.87.126.65])
	by mail.chariot.net.au (Postfix) with SMTP id 31E305FBE5
	for <asrg@ietf.org>; Mon,  1 Mar 2004 17:50:03 +1030 (CST)
From: "Chris" <rebel@rebel.com.au>
To: "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Message-ID: <GPEMJLCHICHEGPOKJHHDMEKLGPAA.rebel@rebel.com.au>
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 IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <019e01c3ff36$212b7980$5b00005a@moregarlic.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Virus-Scanned: by amavisd-new at chariot.net.au
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 17:48:59 +1030
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> >>Trojaned machines - by their nature authenticated
>
> No, not actually. The authentication process is SMTP server to
> server,

No when I say trojaned machine I mean someone places a trojan on my machine
and then sends email on my account

my server will of course authenticate the email as having come from me (and
itself)
the server doesn't know my machine has been compromised.

I didn't send it, some spammer who took over my machine did.


> so unless the trojaned system has access to an open relay which is,
> nevertheless, properly accounted
> for in the SPF/Caller ID DNS entries, the trojan will need to
> have proper SMTP AUTH
> credentials to some server. They don't currently work this way,
> and it seems unlikely
> that an administrator would leave relays open but implement
> domain-level SMTP
> authentication.

just because an ISP upgrades to the latest version of Sendmail does not
automatically make him security wise
many open relays are created by inept or lazy managers, and like spammers
they wont go away.

> >>Open Scripts - Authenticated by the insecure server (sendmail)
>
> See first answer

Same answer as trojaned

If my website had an insecure script on it (formmail) and someone uses it to
send e-mail. again it is authenticated as coming from my account.

sendmail says "yeah I know that guy" so I will authenticate the email.

> but there would still be IP-based blacklisting and the
> fact that would have to
> operate out in the open.

I am personally against blacklists

but at least with server identification blacklists can narrow their targets
to the actual offending server, as opposed to the scattergun approach they
have now.

If "Blocklists" were to become viable in my opinion they would have to be
formalised

and again the argument arises that one mans spam is another mans erectile
enhancer

People actually use spam the same as my wife uses junkmail.

Just because someone personally won't accept any form of spam does not mean
the next person has to bow to their wishes.
this is effectivally censorship which I am totally against.


Regards
Chris



> -----Original Message-----
> From: Larry Seltzer [mailto:larry@larryseltzer.com]
> Sent: Monday, 1 March 2004 1:07 PM
> To: 'Chris'; 'ASRG'
> Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
>
>
>
> >>Uncloseted spammers - eg sheck-buy, authenticated cause they don't care
> >>Third world spammers - sender authenticated but legally out of reach
>
> Yes, definitely, and this is why blacklists (or the new PC term
> "blocklists") are
> important in an SMTP authenticated world. Unlike now, such lists
> could be accurate and
> authoritative. It's possible that spammers could buy and use
> large numbers of throwaway
> domains, but there would still be IP-based blacklisting and the
> fact that would have to
> operate out in the open.
>
> >>Open Scripts - Authenticated by the insecure server (sendmail)
>
> See first answer
>
> Larry Seltzer
> eWEEK.com Security Center Editor
> http://security.eweek.com/
> larryseltzer@ziffdavis.com
>
>


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



From exim@www1.ietf.org  Mon Mar  1 06:18:20 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10693
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 06:18:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxlQn-0008DK-Gt
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 06:17:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21BHrCZ031573
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 06:17:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxlQn-0008DA-Cj
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 06:17:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10672
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 06:17:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxlQj-0007Zp-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 06:17:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxlPq-0007TW-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 06:16:55 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxlPP-0007MP-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 06:16:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxlP3-0007k2-JH; Mon, 01 Mar 2004 06:16:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxlOw-0007jM-80
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 06:15:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10512
	for <asrg@ietf.org>; Mon, 1 Mar 2004 06:15:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxlOs-0007KB-00
	for asrg@ietf.org; Mon, 01 Mar 2004 06:15:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxlNi-0007E9-00
	for asrg@ietf.org; Mon, 01 Mar 2004 06:14:43 -0500
Received: from mail2.speakeasy.net ([216.254.0.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxlN0-00078j-00
	for asrg@ietf.org; Mon, 01 Mar 2004 06:13:58 -0500
Received: (qmail 27790 invoked from network); 1 Mar 2004 11:13:58 -0000
Received: from dsl081-214-187.nyc2.dsl.speakeasy.net (HELO elliot) (lseltzer@[64.81.214.187])
          (envelope-sender <larry@larryseltzer.com>)
          by mail2.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <asrg@ietf.org>; 1 Mar 2004 11:13:58 -0000
From: "Larry Seltzer" <larry@larryseltzer.com>
To: "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Message-ID: <020901c3ff7e$10307840$5b00005a@moregarlic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <GPEMJLCHICHEGPOKJHHDMEKLGPAA.rebel@rebel.com.au>
Importance: Normal
Content-Transfer-Encoding: quoted-printable
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 06:12:09 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

>>No when I say trojaned machine I mean someone places a trojan on my =
machine and then
sends email on my account

None of these trojans work that way, at least not since Melissa or =
sometime about then.
They all use built-in SMTP code to send mail on behalf of the user. The =
reason is that
Microsoft closed this hole in Outlook and Outlook Express several years =
ago, and any
version of either (since Outlook 98) that's been patched since about =
2000 or 2001 blocks
external programmatic access and access to the address book without =
explicit end-user
approval. If you'll read the analyses of how these things work you'll =
see that they
don't use the MUA, they *are* an MUA.=20

If you know of a trojan that does what you claim please give me a =
specific example, or
tell me how it would work. But they don't bother with the user's =
credentials because
they don't have to.

Larry Seltzer
eWEEK.com Security Center Editor
http://security.eweek.com/
larryseltzer@ziffdavis.com=20



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



From exim@www1.ietf.org  Mon Mar  1 11:44:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19588
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 11:42:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxqUs-0007ks-JX
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 11:42:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21GgQHw029804
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 11:42:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxqUr-0007kc-Gv
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 11:42:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18948
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 11:42:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxqFu-0003Uh-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 11:26:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxqDB-0002L2-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 11:24:10 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxqAr-0001Vs-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 11:21:45 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Axpxn-0000pQ-Vy
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 11:08:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axpwh-0002zF-Dm; Mon, 01 Mar 2004 11:07:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxpwJ-0002qv-HW
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 11:06:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14544
	for <asrg@ietf.org>; Mon, 1 Mar 2004 11:06:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxpwB-0005M9-00
	for asrg@ietf.org; Mon, 01 Mar 2004 11:06:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axppg-0002ff-00
	for asrg@ietf.org; Mon, 01 Mar 2004 10:59:55 -0500
Received: from mail5.speakeasy.net ([216.254.0.205])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxpiB-0007ZW-00
	for asrg@ietf.org; Mon, 01 Mar 2004 10:52:07 -0500
Received: (qmail 14284 invoked from network); 1 Mar 2004 15:52:05 -0000
Received: from dsl081-214-187.nyc2.dsl.speakeasy.net (HELO elliot) (lseltzer@[64.81.214.187])
          (envelope-sender <larry@larryseltzer.com>)
          by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <asrg@ietf.org>; 1 Mar 2004 15:52:05 -0000
From: "Larry Seltzer" <larry@larryseltzer.com>
To: "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Message-ID: <02a601c3ffa4$e45f5c00$5b00005a@moregarlic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <20040301143416.GA12966@teal.hjp.at>
Importance: Normal
Content-Transfer-Encoding: quoted-printable
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 10:49:34 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

>>The trojan could always read this data [[address book?]] directly. I =
don't think they
can block that.

And that's what they do, although the typical pattern is that they read =
.wab, .htm*,
.txt, maybe .doc files, and scan them for e-mail addresses. Interesting, =
but not
relevant to the main issue of authentication, except that to the extent =
that these worms
read these addresses to determine from: addresses for their propagation, =
they are even
less likely to spread through SMTP authentication.

>>Swen. But I don't think it uses data from Outlook or Outlook Express. =
It simply pops
up a Window asking the user for his credentials.=20

A copy of this dialog box may be found at
http://securityresponse.symantec.com/avcenter/graphics/w32.swen.a@mm.5.gi=
f. I have a
hard time believing. I doubt many people remember their SMTP server =
credentials offhand,
since they are usually stored by the MUA for automatic use.=20

But anyway, if that's the best they can come up with I'm still sure that =
worm spreading
would be cut dramatically. What they'd really need to do is to find ways =
to crack the
SMTP AUTH credentials from the various MUAs that might be on a system.

Larry Seltzer
eWEEK.com Security Center Editor
http://security.eweek.com/
larryseltzer@ziffdavis.com=20



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



From exim@www1.ietf.org  Mon Mar  1 13:01:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25215
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 13:01:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axrj6-0005sg-RY
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 13:01:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21I1CZU022600
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 13:01:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axrj6-0005sR-Mo
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 13:01:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25164
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 13:01:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axrj5-0002sU-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 13:01:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxriF-0002ie-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 13:00:20 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxrhE-0002X9-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 12:59:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axrgz-0005Xe-At; Mon, 01 Mar 2004 12:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxrgA-0005Le-Tl
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 12:58:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24789
	for <asrg@ietf.org>; Mon, 1 Mar 2004 12:58:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axrg9-0002Jq-00
	for asrg@ietf.org; Mon, 01 Mar 2004 12:58:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axrf1-00029n-00
	for asrg@ietf.org; Mon, 01 Mar 2004 12:57:00 -0500
Received: from teal.hjp.at ([62.99.236.98])
	by ietf-mx with smtp (Exim 4.12)
	id 1AxreC-0001uo-00
	for asrg@ietf.org; Mon, 01 Mar 2004 12:56:08 -0500
Received: (qmail 14471 invoked by uid 500); 1 Mar 2004 17:55:32 -0000
From: "Peter J. Holzer" <hjp-asrg@hjp.at>
To: "'ASRG'" <asrg@ietf.org>
Subject: Re: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Message-ID: <20040301175532.GA14270@teal.hjp.at>
Mail-Followup-To: 'ASRG' <asrg@ietf.org>
References: <20040301143416.GA12966@teal.hjp.at> <02a601c3ffa4$e45f5c00$5b00005a@moregarlic.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="wRRV7LY7NUeQGEoC"
Content-Disposition: inline
In-Reply-To: <02a601c3ffa4$e45f5c00$5b00005a@moregarlic.com>
User-Agent: Mutt/1.4.1i
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 18:55:32 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--wRRV7LY7NUeQGEoC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2004-03-01 10:49:34 -0500, Larry Seltzer wrote:
> >>The trojan could always read this data [[address book?]] directly. I do=
n't think they
> can block that.
>=20
> And that's what they do, although the typical pattern is that they read .=
wab, .htm*,
> .txt, maybe .doc files, and scan them for e-mail addresses.

Yes, but I was thinking of configuration data and credentials.

> >>Swen. But I don't think it uses data from Outlook or Outlook Express. I=
t simply pops
> up a Window asking the user for his credentials.=20
>=20
> A copy of this dialog box may be found at
> http://securityresponse.symantec.com/avcenter/graphics/w32.swen.a@mm.5.gi=
f. I have a
> hard time believing. I doubt many people remember their SMTP server crede=
ntials offhand,
> since they are usually stored by the MUA for automatic use.=20
>=20
> But anyway, if that's the best they can come up with I'm still sure that =
worm spreading
> would be cut dramatically.

Before Swen I would have agreed. But Swen spread quite rapidly, so
apparently there are enough people who don't get suspicious if the get
asked to enter their credentials out of the blue, and either remember
them offhand or hunt down that piece of paper they noted it on (or call
their ISP's hotline to find out).

> What they'd really need to do is to find ways to crack the
> SMTP AUTH credentials from the various MUAs that might be on a system.

Which probably isn't that hard for some MUAs. Netscape 4 just stored
them in the preferences file (base64-encoded). Older versions of Eudora
did the same (don't know about current ones). I don't know about Outlook
and Outlook Express, but I would not be surprised if the information was
stored somewhere in an easily decodable format. Mozilla is as good as
you can possibly get: The credentials are stored encrypted (IF the user
entered a "master password") and are only decrypted if needed. But while
the MUA is running, it keeps the master password in memory, so another
process running as the same user could get it and then decrypt the
passwords. (disabling the ptrace system call or its equivalent on
non-unix platforms might help).

	hp

--=20
   _  | Peter J. Holzer    | I think we need two definitions:
|_|_) | Sysadmin WSR       | 1) The problem the *users* want us to solve
| |   | hjp@hjp.at         | 2) The problem our solution addresses.
__/   | http://www.hjp.at/ |    -- Phillip Hallam-Baker on spam

--wRRV7LY7NUeQGEoC
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQFAQ3kUfZ+RkG8quy0RAsHgAJ9pv010RBFFAlXQadQdOaWugAOO5gCgggNF
WDWN8I/9t1hpsUuuZNyg+5o=
=kBFo
-----END PGP SIGNATURE-----

--wRRV7LY7NUeQGEoC--

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



From exim@www1.ietf.org  Mon Mar  1 13:58:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27948
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 13:58:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axsc5-0000iP-T3
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 13:58:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21Iw177002742
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 13:58:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axsc5-0000i9-M0
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 13:58:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27895
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 13:57:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axsc3-0001lN-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 13:57:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxsbB-0001cY-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 13:57:07 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxsaJ-0001Td-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 13:56:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axsa8-0000XB-VY; Mon, 01 Mar 2004 13:56:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxsZE-0000Vf-9b
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 13:55:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27648
	for <asrg@ietf.org>; Mon, 1 Mar 2004 13:55:00 -0500 (EST)
From: gep2@terabites.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxsZB-0001KL-00
	for asrg@ietf.org; Mon, 01 Mar 2004 13:55:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxsYH-0001DC-00
	for asrg@ietf.org; Mon, 01 Mar 2004 13:54:06 -0500
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxsXT-0000zM-00
	for asrg@ietf.org; Mon, 01 Mar 2004 13:53:15 -0500
Received: from WinProxy.anywhere (c-24-0-183-151.client.comcast.net[24.0.183.151])
          by comcast.net (rwcrmhc13) with SMTP
          id <200403011852430150046na3e>; Mon, 1 Mar 2004 18:52:44 +0000
Received: from 192.168.0.30 by 192.168.0.1 (WinProxy); Mon, 1 Mar 2004 12:53:41 -0600
Received: from 192.168.0.240 (unverified [192.168.0.240]) by nts1.terabites.com
 (EMWAC SMTPRS 0.83) with SMTP id <B0000029432@nts1.terabites.com>;
 Mon, 01 Mar 2004 12:57:12 -0600
Message-ID: <B0000029432@nts1.terabites.com>
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
To: dave@farber.net
Cc: asrg@ietf.org, wishlist@microsoft.com
X-Mailer: SPRY Mail Version: 04.00.06.17
Content-Transfer-Encoding: 7bit
Subject: [Asrg] [IP] CNN covers Meng's SPF
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 12:57:12 -0600
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=2.0 required=5.0 tests=AWL,NO_REAL_NAME,RATWARE_EMWAC 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



> NEW YORK (AP) -- With a simple adjustment in your e-mail software, you can
pretend to be anyone. You can send messages marked as coming from
BillGates@microsoft.com.

Surprise surprise!!!  This should have been common knowledge for a long time.

> The trick, known as spoofing, is a popular method for spammers to hide
their tracks -- you'd blame Microsoft Corp. chairman Bill Gates and not
the actual perpetrator of junk mail.

> To close that loophole, Microsoft and Yahoo! Inc. are each developing
systems aimed at authenticating senders of e-mail. America Online Inc. is
testing a third.

Funny thing that each of these folks are ISPs... and each is trying to make sure 
you use THEM for everything you do. :-((  

> "Having e-mail come in, and not really being able to identify where it
comes from, this is a huge security hole," Gates said this week in
announcing specifications for his proposal.

Actually, the "Received" headers give one a pretty decent trace of "where it 
comes from", at least once it leaves the hands of those who counterfeit headers 
or otherwise attempt to deceive.  And one could certainly imagine a system 
whereby mail recipients systems could go back to the claimed originating system 
of the E-mail message and ask for confirmation that the specific E-mail message 
actually originated at that system.

> Many software engineers are concerned, however, that these systems could
end up causing more problems than they solve.

And, in fact, that is precisely the problem.  Many of these systems, SPECFICALLY 
INCLUDING Wong's SPF (and as a member of the IETF's Anti-Spam Research Group was 
on Wong's SPF mailing list for a while, before I concluded that it was probably 
fatally flawed), have a number of very serious problems in them if they were 
ever to be widely adopted.

> Microsoft's proposal, known as Caller ID for E-mail, calls for Internet
service providers to submit lists of unique numeric addresses for their
mail servers. On the receiving end, software would check a database to
verify that a message said to come from an e-mail provider actually
originated at one of its registered machines.

The problem with this one of course is that not all E-mail messages originate at 
mail servers run by ISPs.  Some of the more sophisticated business customers 
(and indeed, some of the more sophisticated USERS, myself among them) actually 
use their own outgoing E-mail servers... for a whole variety of perfectly valid 
reasons.  It's outrageous and offensive that ISPs are trying to prevent users 
from being able to bypass the ISP's (hoped-for) monopoly provision of (sometimes 
unwanted and often gotcha-laden) "ISP services".

> In January, AOL began testing a similar system called Sender Policy
Framework, or SPF, which checks a different part of the message.

> Yahoo's proposed solution is a different animal. It would use encryption
to digitally sign messages. If the sender or message content is altered,
the signature gets rejected. Yahoo announced its proposal, DomainKeys, in
December but has yet to make details public.

There are a lot of such systems and most of them work at least in the scenario 
they are designed for.  Unfortunately, when you start looking at the less 
obvious but still HIGHLY important situations... such as personally-owned 
domains, mailing lists, corporate "vanity domains", roaming use (mailing from 
cruise ships, airport waiting lounge kiosks, etc)... not even to mention 
"anonymous remailers" required by whistleblowers etc... you usually find that 
these proposals have very serious flaws that have terrible implications to many 
customers with legitimate needs and concerns.

> The big three e-mail providers are not alone in trying to tackle address
spoofing. Leading e-mail software vendor Sendmail Inc., spam-filtering
company Brightmail Inc. and frequent e-mailer Amazon.com are also at it,
each planning to test one or more systems.

> All these competing proposals are enough to get the Internet's
standards-setting bodies in a lather.

> One of them, the Internet Engineering Task Force, has scheduled a session
on authentication next Thursday in South Korea. Experts predict some
combination of the techniques will be ready for use later this year,
though formal standards will take longer.

> There's much work to be done in the meantime, including proving the
systems can actually work beyond controlled, laboratory environments.

> Caller ID and SPF, at least, are likely to disrupt mail-forwarding
services that colleges and companies offer to let alumni and subscribers
route e-mail through a domain name other than their own service
provider's.

> They also could break "send to a friend" features in which someone clicks
on a Web link to pass an interesting item to someone else.

THOSE *need* to be broken.  They are often more just a pleasant-looking ruse to 
collect an E-mail address of the "someone else" victim and later use that for 
spamming or other unwelcome purpose.  (Electronic "greeting cards" of course 
suffer from the same fault.)

> Issues to be worked out for all three systems include how to properly send
e-mail from cybercafes, hotels and public Wi-Fi hotspots...

Indeed, and (as mentioned) airport waiting lounge kiosks, cruise ships, and 
other "temporary/away" situations.  Mailing lists are another such serious 
problem.

> and how to preserve privacy when using anonymous re-mailers, which are used by
whistleblowers and others to intentionally mask the origin of messages.

Absolutely.

> "A lot of people have said that e-mail today is broken, and now we're
going to break it a little more," Meng Weng Wong, lead developer of SPF,
acknowledged. "Some of the things people are used to doing, they won't be
able to do it in quite the same way."

In fact, Wong (based on E-mail exchanges he and I have had) basically just 
doesn't care about the important flaws in his approach, he is fully aware of 
them and has been forging ahead with it regardless.  I consider his approach and 
attitude to be irresponsible and objectionable.

> But the gain in fighting spam outweighs any pain from change, Wong argues.

Except that it doesn't.  NOTHING in SPF in any way prevents spam whatsoever... 
all it does is to authenticate the sender.  Spammer-friendly ISPs, new "vanity" 
domains (and spammers are creating "disposable" vanity domains with seemingly 
randomly generated domain names at a breathtaking rate... sometimes using the 
domain name just once for a single mass mailing and figuring the less-than-$50 
domain registration fee just a small part of the cost of doing their spamming 
business.)

Spammers can also continue hijacking (with viruses and worms) the systems of 
legitimate (if naive or careless) users and use those to generate spam E-mails 
using absolutely "legitimate" (if inadvertent) and authenticated users and valid 
sender ISPs.  This of course is one of the problems with the "cyberpayments" 
schemes for E-mails, too (quite apart from that being a slippery slope to the 
"pay for each E-mail" scheme that monopoly ISPs would LOVE to see become the 
norm).  In each case, the spammer simply shifts the costs to an inadvertent 
third-party victim.

So in fact, Wong's system creates MUCH pain, requires changes to systems 
literally everywhere in the world, hugely inconveniences (or even disables 
entirely) many types of users with highly legitimate needs, and still doesn't 
really do much of anything to actually solve the problem.  It still leaves 
people sending and receiving spam, with about the only improvement being that 
you maybe know who to send complaints about it to (usually an ISP, whose user is 
themself an unwitting and usually unwilling victim).  So what is the ISP 
supposed to do, punish the victim?  And even if they throw the victimized user 
off their system, eventually ALL such users will have been victimized, and 
NOBODY is left still on the Net.  :-(

> Authentication also can help limit the spread of e-mail viruses...

Again, NO IT DOESN'T.  It only helps identify where they actually came from.  
Maybe.  (And often, that trail will end up leading back to someone who is a 
pathetic and beleaguered victim themselves).  This ultimately is NOT very 
helpful.

A **far** better approach... simpler, easier, rapid to implement, hard to 
disable or to evade... and one which IMMEDIATELY benefits the folks who 
INDIVIDUALLY put it in place, without requiring literally worldwide changes and 
consensus to be effective... is for E-mail client software companies to simply 
discard ALL incoming attachments (including alternative HTML-burdened ones) 
unless the recipient had previously whitelisted the sender and authorized THAT 
sender to send THAT recipient attachments of THAT specified type.  (Example:  
Your Aunt Gertrude *might* actually send you an electronic photo JPG of her 
adorable poodle Fifi, but she probably NEVER needs to send you an .EXE, script, 
PIF, or other type of executable file.)  Likewise, even if you're some kind of 
consumer products company (say, Proctor and Gamble) that needs to receive 
unsolicited messages from previously-unknown users, it's very hard to argue that 
people need to send *attachments* (at least not as an initial contact message) 
rather than simply safe, plain ASCII text.

So E-MAIL CLIENT SOFTWARE SHOULD STRIP ALL ATTACHMENTS UNLESS THE RECIPIENT HAS 
SPECIFICALLY WHITELISTED THE INDIVIDUAL SENDER TO SEND THEM THAT SPECIFIC TYPE 
OR CLASS OF ATTACHMENT.

That single, simple, highly effective strategy would OVERNIGHT result in a 
near-total-elimination of 85-95% (maybe more) of all viruses and worms.  The 
GREAT majority of them would find their propagation rate reduced to well below 
the minimum "survival" rate.

> and, with Caller ID and DomainKeys, help flag fraudulent "phishing" messages 
that try to trick people into revealing passwords and credit card information.

A far more effective strategy THERE, TOO, is to STRIP ALL HTML CONTENT OUT OF 
MESSAGES unless the recipient has specifically authorized (by whitelisting) the 
specific sender in question to send the recipient HTML-burdened E-mail.

The great majority of spam and fraudulent "phishing" messages use tricks based 
on HTML to deceive, obscure, and defraud.  This can include obscured URLs, links 
that claim to be one thing but in fact point somewhere else (e.g. claim to be 
"http://security.ebay.com" but in fact when you click on them they point to a 
rogue server in Romania or somewhere), Web bugs, malicious scripting, malicious 
ActiveX content, text-as-image in order to evade antispam content filters, and 
so forth.  

If ONLY AUTHORIZED WHITELISTED-BY-EACH-RECIPIENT SENDERS were able to send them 
HTML-burdened E-mail content, then (and in conjunction with good antispam 
content filters, which would then be HUGELY more effective) we'd also get rid of 
the great majority of spam and other fraudulent E-mail, too.

Again, this doesn't require any great worldwide consensus, doesn't require any 
sweeping and disruptive change to the world's online systems, and doesn't 
needlessly or seriously disrupt legitimate users.  Moreover, IT IS EFFECTIVE 
FROM DAY ONE AND TO THE VERY FIRST ADOPTERS, which means that people are 
immediately gratified by the change they make to THEIR systems.  This ought to 
result in a rapid adoption rate, and minimize the long time it takes to move 
complex and ultimately unsatisfactory standards through worldwide standards 
organizations.

Note also that BOTH the changes I propose... simply whitelisting attachments and 
HTML at the recipient end, on a sender-by-sender basis... are SINGLE-ENDED 
schemes which do not require ANY changes at the sender ends at all (other than 
implying that they cannot send attachments or HTML-burdened mail unsolicited or 
unwanted, and expect to actually get it through!).  And, once whitelisted, 
EVERYTHING we can do today (vanity domains, roaming, mailing lists, 
send-from-cruise-ship, and so forth) all still work, too.

> The proposals require no changes to existing protocols for e-mail or the
domain name system, and developers of all three pledge to eventually seek
standards status (Wong has already submitted SPF for review).

Actually, almost all of these other approaches (INCLUDING Wong's) DO involve the 
need for worldwide changes and consensus, they prevent legitimate users from 
doing things they sometimes truly NEED to do, most DO involve changes to the DNS 
system (or else the construction of a wasteful parallel to it), and in fact NONE 
of them seem to ACTUALLY solve the problem.  They do NOT prevent the sending of 
Spam, they do NOT prevent the propagation of viruses, they do NOT prevent 
"phishing" and similar deceptions.  They only inconvenience people everywhere 
and disable exceedingly useful and important features.

> For now, the three can coexist, although adoption could be limited until a
consensus emerges around one or a combination.

The reason there has not been (and is not LIKELY to be) a consensus around these 
proposals anytime soon is because they each have very nasty problems that many 
people strongly dislike, and generally the payback even upon widespread 
implementation simply isn't worth the implmentation costs and other 
disadvantages.

> But these solutions alone will not stop spammers.

ABSOLUTELY, and that is at the root of the delay and dissatisfaction with all of 
them.  Nobody that seriously looks at these proposals is truly convinced that 
any of them ACTUALLY solve the problem.  It only makes folks (arguably) 
identifiable or traceable, and while that sounds good on the surface, it simply 
doesn't achieve much in the end analysis.  I don't think it makes much sense to 
uproot and mess up the entire Internet worldwide, just to give the bogus 
APPEARANCE of "we have to [appear to] do SOMETHING".

Meanwhile, the simple single-ended solution I propose (in conjunction with a 
suitable content filter at the recipient end) would be cheap and fast, HIGHLY 
effective against worms, viruses, spams, and "phishing" spoofs, is rapidly 
implementable, and would have negligible negative impact on legitimate, 
responsible users (both senders and recipients).  It moreover requires **no** 
changes whatsoever to the critical underlying Internet infrastructure.

> Systems will have to be established to evaluate the reputation of domains
that relay e-mail, and that raises questions about who would develop such
lists and who would arbitrate disputes.

Again, that's simply NOT NECESSARY.  All that does is to establish trackability, 
it does **nothing** to actually prevent the sending (or receipt!) of spam, 
viruses, worms, and the like.

> In the short term, authentication will be useful mostly for verifying
newsletters and other bulk mailings that are often misidentified as spam
today, said Margaret Olson, co-chairman of the Email Service Provider
Coalition's technology committee.

This can easily enough be handled, if necessary, with normal public-key 
signature technology.  Again, no infrastructure changes are required or even 
indicated.

> Once enough service and software providers adopt the technology, "getting
unauthenticated mail delivered will be extremely difficult," she said.

And that's part of the problem with such changes.  They require worldwide 
consensus to work effectively, and the earliest adopters gain little or nothing 
from making the changes.  They are expensive (because they have to be done 
EVERYWHERE) and in the end, when all is said and done, THEY DON'T SOLVE THE 
PROBLEM!

> And that could hurt e-mailers in other countries where adoption of
English-language specifications tend to lag, and smaller service providers
may be forced to accept whatever the giants decide, critics warn.

Right, it could take years or even decades, and many Net users (including 
businesses with embedded mail handlers built into their related applications) 
might in some cases not even *ever* be able to adhere to the changed 
specifications.

> At EarthLink Inc., which is experimenting with authentication, chief
architect Robert Sanders said no service provider wants to suddenly stop
e-mail from non-participants.

Right.  The authentication approach isn't really very effective unless and until 
EVERYONE is "authenticated", and the way the schemes are generally conceived, 
that mythical state of eternal bliss is NEVER in practice achieved.  And again, 
even after EVERYONE is authenticated, that STILL doesn't prevent them being a 
victim and sending out "fully authenticated" viruses, worms, and "my system was 
hijacked" spams!

> But he likened the technology to telephone's caller ID: "You may still get
a phone call with caller ID, but you may not choose to answer it."

There are a LOT of ways we can potentially "break" the world's E-mail system.  
My position is that we shouldn't do that unless the actual payback we'd achieve 
by doing so is truly compelling.  I still feel that the approach I'm proposing 
has the fastest payback to adopters, the lowest worldwide cost, the best 
effectiveness against worms, viruses, spams, spoofing, and "phishing", and the 
least unwanted and undesired downside costs to existing users, systems and 
applications.

Gordon Peterson                  http://personal.terabites.com/
1977-2002  Twenty-fifth anniversary year of Local Area Networking!
Support free and fair US elections!  http://stickers.defend-democracy.org
12/19/98: Partisan Republicans scornfully ignore the voters they "represent".
12/09/00: the date the Republican Party took down democracy in America.



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



From exim@www1.ietf.org  Mon Mar  1 14:12:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28541
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 14:12:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axspu-0001lM-5f
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 14:12:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21JCITN006770
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 14:12:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axspt-0001l5-Vh
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 14:12:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28524
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 14:12:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axspr-0003Kt-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:12:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axsox-0003Cp-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:11:20 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxsoM-000349-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:10:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axsni-0001S1-NO; Mon, 01 Mar 2004 14:10:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axsmn-0001Qb-JV
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 14:09:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28371
	for <asrg@ietf.org>; Mon, 1 Mar 2004 14:09:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axsml-0002vD-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:09:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axslj-0002oh-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:08:00 -0500
Received: from mail4.speakeasy.net ([216.254.0.204])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axsl8-0002jE-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:07:22 -0500
Received: (qmail 18588 invoked from network); 1 Mar 2004 19:07:16 -0000
Received: from dsl081-214-187.nyc2.dsl.speakeasy.net (HELO elliot) (lseltzer@[64.81.214.187])
          (envelope-sender <larry@larryseltzer.com>)
          by mail4.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <asrg@ietf.org>; 1 Mar 2004 19:07:16 -0000
From: "Larry Seltzer" <larry@larryseltzer.com>
To: "'Peter J. Holzer'" <hjp-asrg@hjp.at>, "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Message-ID: <036601c3ffc0$2bd09700$5b00005a@moregarlic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <20040301175532.GA14270@teal.hjp.at>
Importance: Normal
Content-Transfer-Encoding: quoted-printable
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 14:04:47 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

>>Yes, but I was thinking of configuration data and credentials.

Right, but this information isn't sitting in plaintext files waiting to =
be read. It's
not obvious how you'd get it if you were a worm.

>>Before Swen I would have agreed. But Swen spread quite rapidly, so =
apparently there
are enough people who don't get suspicious if the get asked to enter =
their credentials
out of the blue, and either remember them offhand or hunt down that =
piece of paper they
noted it on (or call their ISP's hotline to find out).

Swen doesn't need this information to spread. Apart from sprading =
through
non-authenticated SMTP servers, it uses network shares, KaZaA, IRC and =
Usenet. It's not
at all clear a lot of people entered that information.

>>>> What they'd really need to do is to find ways to crack the SMTP =
AUTH=20
>>>> credentials from the various MUAs that might be on a system.
>>Which probably isn't that hard for some MUAs. Netscape 4 just stored =
them in the
preferences file (base64-encoded). Older versions of Eudora did the same =
(don't know
about current ones). I don't know about Outlook and Outlook Express, but =
I would not be
surprised if the information was stored somewhere in an easily decodable =
format. Mozilla
is as good as you can possibly get: The credentials are stored encrypted =
(IF the user
entered a "master password") and are only decrypted if needed. But while =
the MUA is
running, it keeps the master password in memory, so another process =
running as the same
user could get it and then decrypt the passwords. (disabling the ptrace =
system call or
its equivalent on non-unix platforms might help).

Both Outlook and OE store the data in the registry in some sort of =
obscured format. I
don't know the scheme and I doubt they're telling.

Bear in mind, if a worm were to spread itself this way, it would be =
completely
traceable. This too would help to stop them.



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



From exim@www1.ietf.org  Mon Mar  1 14:47:45 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01320
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 14:47:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtNn-0004aw-Hu
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 14:47:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21JlJB7017656
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 14:47:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtNn-0004ah-Cr
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 14:47:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01310
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 14:47:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtNk-0007e0-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:47:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxtMp-0007W1-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:46:21 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtM1-0007Mo-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:45:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtKb-0004Kg-Dc; Mon, 01 Mar 2004 14:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtK1-0004JF-KS
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 14:43:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01057
	for <asrg@ietf.org>; Mon, 1 Mar 2004 14:43:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtJy-000768-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:43:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxtIx-0006xz-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:42:21 -0500
Received: from mail3.panix.com ([166.84.1.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtII-0006pR-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:41:38 -0500
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail3.panix.com (Postfix) with ESMTP id 15C7E9880C
	for <asrg@ietf.org>; Mon,  1 Mar 2004 14:41:36 -0500 (EST)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i21JfaU23193;
	Mon, 1 Mar 2004 14:41:36 -0500 (EST)
Message-Id: <200403011941.i21JfaU23193@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <B0000029432@nts1.terabites.com> (gep2@terabites.com)
Subject: Re: [Asrg] [IP] CNN covers Meng's SPF
References: <B0000029432@nts1.terabites.com>
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 14:41:36 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

gep2@terabites.com wrote:

> Actually, the "Received" headers give one a pretty decent trace of
> "where it comes from", at least once it leaves the hands of those
> who counterfeit headers or otherwise attempt to deceive.  And one
> could certainly imagine a system whereby mail recipients systems
> could go back to the claimed originating system of the E-mail
> message and ask for confirmation that the specific E-mail message
> actually originated at that system.

Which is better than SPF exactly how?

> The problem with this one of course is that not all E-mail messages
> originate at mail servers run by ISPs.  Some of the more
> sophisticated business customers (and indeed, some of the more
> sophisticated USERS, myself among them) actually use their own
> outgoing E-mail servers... for a whole variety of perfectly valid
> reasons.

You're confusing a news article with reality.  In the actual
proposals, any domain owner gets to specify which IP addresses can
send mail "from" that domain.

> There are a lot of such systems and most of them work at least in
> the scenario they are designed for.  Unfortunately, when you start
> looking at the less obvious but still HIGHLY important
> situations... such as personally-owned domains, mailing lists,
> corporate "vanity domains", roaming use (mailing from cruise ships,
> airport waiting lounge kiosks, etc)... not even to mention
> "anonymous remailers" required by whistleblowers etc... you usually
> find that these proposals have very serious flaws that have terrible
> implications to many customers with legitimate needs and concerns.

You need to be specific.  Anonymous remailers claim that the mail came
 from them, and they will certify that fact, so what's the problem?

Mailing list hosts will claim that the mail came from them and certify
that fact.

Personally-owned and corporate domains will likewise certify that the
mail came from them.

Roaming users who get random IP addresses will have several options.
One is to use the mailserver of whatever domain they _claim_ to be
sending from.  Another is to register their current IP with the domain
owner so that the domain will certify it (for some time period).

If I'm at an airport lounge kiosk and I send email, it can either
admit that it came from airportloungekiosk.wherever, or I can connect
to Panix and send mail from there.  Otherwise, if _I_ can send mail
claiming to be from <sethb@panix.com> from the kiosk, so could you (or
a spammer), and I don't want that.

The actual problem is "requested remailers" (such as acm.org, or many
colleges that forward email for graduates).  That fails under many
current implementations, so either the remailer has to be specially
trusted, or it will have to rewrite headers in a specific way.

>> But the gain in fighting spam outweighs any pain from change, Wong argues.
>
> Except that it doesn't.  NOTHING in SPF in any way prevents spam whatsoever... 
> all it does is to authenticate the sender.

Spammers forge, so rejecting mail from anti-authenticated senders will
reject spam.

>  Spammer-friendly ISPs,

Can be blocked by _name_ if they can't forge.

> new "vanity" domains (and spammers are creating "disposable" vanity
> domains with seemingly randomly generated domain names at a
> breathtaking rate... sometimes using the domain name just once for a
> single mass mailing and figuring the less-than-$50 domain
> registration fee just a small part of the cost of doing their
> spamming business.)

There are ways to catch those, too, which I don't want to reveal in an
open mailing list.  I will suggest greylisting a new domain (new="I
haven't seen much email from it yet") as a start.

> Spammers can also continue hijacking (with viruses and worms) the
> systems of legitimate (if naive or careless) users and use those to
> generate spam E-mails using absolutely "legitimate" (if inadvertent)
> and authenticated users and valid sender ISPs.

Then pressure will be put on their ISPs (partly by being blocked for
emitting spam).  Note that the spam will have to come through the
ISP's mailserver, because the ISP won't certify random cable modem IP
addresses as authorized senders.

> So in fact, Wong's system creates MUCH pain,

and avoids more

> requires changes to systems literally everywhere in the world,

Only those that do authorized forwarding, or their receivers.

> hugely inconveniences (or even disables 
> entirely) many types of users with highly legitimate needs,

You may consider their "needs" to be "highly legitimate" but I don't
have to, and if there's nothing preventing a spammer from acting just
like one of them, I don't want to, either.

> and still doesn't really do much of anything to actually solve the
> problem.

It would cut way down on the spam I receive.  That's a good thing.

>  It still leaves people sending and receiving spam,

Sending yes, receiving no.

>  And even if they throw the victimized user off their system,
> eventually ALL such users will have been victimized, and NOBODY is
> left still on the Net.  :-(

Except the clueful and those with good ISPs (that can prevent their
victims from actually getting spam out).  I don't see a problem with
that.

>> Authentication also can help limit the spread of e-mail viruses...
>
> Again, NO IT DOESN'T.  It only helps identify where they actually came from.  

Which means it's easier to disinfect, limiting the spread.

> A **far** better approach... simpler, easier, rapid to implement,
> hard to disable or to evade... and one which IMMEDIATELY benefits
> the folks who INDIVIDUALLY put it in place, without requiring
> literally worldwide changes and consensus to be effective... is for
> E-mail client software companies to simply discard ALL incoming
> attachments (including alternative HTML-burdened ones) unless the
> recipient had previously whitelisted the sender and authorized THAT
> sender to send THAT recipient attachments of THAT specified type.

Earlier, you were objecting to things that required changes all over
the world.  There are a lot more clients than servers, and they change
more slowly.

Besides, there's plenty of plaintext spam, and if that were the only
sort that got through, spammers would just switch to it.

> That single, simple, highly effective strategy would OVERNIGHT
> result in a near-total-elimination of 85-95% (maybe more) of all
> viruses and worms.  The GREAT majority of them would find their
> propagation rate reduced to well below the minimum "survival" rate.

For a value of "OVERNIGHT" that includes the multiple years before a
majority of client software is upgraded.

It also does absolutely nothing to stop non-email viruses and worms,
such as those spread directly through flaws in operating systems.

> Again, this doesn't require any great worldwide consensus, doesn't
> require any sweeping and disruptive change to the world's online
> systems, and doesn't needlessly or seriously disrupt legitimate
> users.  Moreover, IT IS EFFECTIVE FROM DAY ONE AND TO THE VERY FIRST
> ADOPTERS, which means that people are immediately gratified by the
> change they make to THEIR systems.

So why don't you just do it and stop yelling about it?

>  And, once whitelisted, EVERYTHING we can do today (vanity domains,
> roaming, mailing lists, send-from-cruise-ship, and so forth) all
> still work, too.

So if a spammer can figure out or guess somebody you have whitelisted,
he can still get your machine infected by forging that sender's
address.  In fact, this becomes _more_ likely to work, due to the
false belief that only safe attachments can get through.

> Actually, almost all of these other approaches (INCLUDING Wong's) DO
> involve the need for worldwide changes and consensus,

They help those who use them, and have no effect on those who don't.

> they prevent legitimate users from 
> doing things they sometimes truly NEED to do,

Those are things that spammers want to do, and in your world there's
no way to tell the spammers from the legitimate users.  (They also
don't prevent the needed things, as I've shown above.)

> most DO involve changes to the DNS 
> system (or else the construction of a wasteful parallel to it),

You mean adding a few records?  Big deal.

> and in fact NONE of them seem to ACTUALLY solve the problem.  They
> do NOT prevent the sending of Spam, they do NOT prevent the
> propagation of viruses, they do NOT prevent "phishing" and similar
> deceptions.

Neither does your proposal.

>  They only inconvenience people everywhere 
> and disable exceedingly useful and important features.

Those "useful and important features" are that way primarily to
spammers, others have easy workarounds.

If I'm travelling and need to send email claiming to be from
me@my.company, I should connect back to my.company's mailserver to
send it; otherwise, what prevents the guy in the next hotel room from
claiming to be me@my.company in his forged email?

> Meanwhile, the simple single-ended solution I propose (in
> conjunction with a suitable content filter at the recipient end)
> would be cheap and fast, HIGHLY effective against worms, viruses,
> spams, and "phishing" spoofs, is rapidly implementable, and would
> have negligible negative impact on legitimate, responsible users
> (both senders and recipients).

It would likewise have little impact on spammers.  It is not at all
effective against phishing spoofs (since spammers could forge
"security@yourbank.com" as the sender and put the URL to go to in
plaintext, coding it in a way that will fool enough people into
thinking it's real).  It is not at all effective against plaintext
spam.  It works a little against email-borne viruses and worms, but
not against others.

>> In the short term, authentication will be useful mostly for verifying
>> newsletters and other bulk mailings that are often misidentified as spam
>> today, said Margaret Olson, co-chairman of the Email Service Provider
>> Coalition's technology committee.
>
> This can easily enough be handled, if necessary, with normal public-key 
> signature technology.  Again, no infrastructure changes are required or even 
> indicated.

Strange how "normal public-key signature technology" is "easy" when
you want it to be, but even simpler techniques are infeasible when
they aren't your proposal.

>> Once enough service and software providers adopt the technology, "getting
>> unauthenticated mail delivered will be extremely difficult," she said.
>
> And that's part of the problem with such changes.  They require worldwide 
> consensus to work effectively, and the earliest adopters gain little or nothing 
> from making the changes.

They don't require consensus, just enough adoption.  The earliest
adopters apparently do think it's worth doing, that's why so many
large email senders are publishing SPF records _now_.  Some of the
large (and, for that matter, tiny) receivers are checking them, too.

>  They are expensive (because they have to be done EVERYWHERE)

They're providing benefit now, even when not done everywhere.

> and in the end, when all is said and done, THEY DON'T SOLVE THE
> PROBLEM!

It has been suggested that nothing short of hangings will do that,
although others believe that public floggings may suffice.

>> And that could hurt e-mailers in other countries where adoption of
>> English-language specifications tend to lag, and smaller service providers
>> may be forced to accept whatever the giants decide, critics warn.
>
> Right, it could take years or even decades, and many Net users (including 
> businesses with embedded mail handlers built into their related applications) 
> might in some cases not even *ever* be able to adhere to the changed 
> specifications.

If you can't distinguish yourself from a spammer, that's not my
problem.

>> At EarthLink Inc., which is experimenting with authentication, chief
>> architect Robert Sanders said no service provider wants to suddenly stop
>> e-mail from non-participants.
>
> Right.  The authentication approach isn't really very effective unless and until 
> EVERYONE is "authenticated", and the way the schemes are generally conceived, 
> that mythical state of eternal bliss is NEVER in practice achieved.

Look up the word "suddenly".  There are many effective partial
solutions (including such things as rate-limiting unauthenticated
email to increase the pressure to authenticate, without blocking it
entirely).

> There are a LOT of ways we can potentially "break" the world's
> E-mail system.

My toys, my rules.  If you don't abide by the requirements I set for
sending email to me, then your email won't get through to me.

>  I still feel that the approach I'm proposing has the fastest
> payback to adopters, the lowest worldwide cost, the best
> effectiveness against worms, viruses, spams, spoofing, and
> "phishing", and the least unwanted and undesired downside costs to
> existing users, systems and applications.

How much has it benefited you so far?

Seth

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



From exim@www1.ietf.org  Mon Mar  1 14:54:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01627
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 14:54:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtUV-0004wT-1g
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 14:54:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21JsF0X018991
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 14:54:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtUU-0004wE-Mv
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 14:54:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01620
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 14:54:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtUR-0000h0-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:54:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxtTR-0000ZS-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:53:10 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtSi-0000SA-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:52:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtRN-0004hu-Qg; Mon, 01 Mar 2004 14:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtQT-0004gB-5P
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 14:50:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01462
	for <asrg@ietf.org>; Mon, 1 Mar 2004 14:50:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtQQ-0000BM-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:50:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxtPX-00004r-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:49:08 -0500
Received: from mailbox.onlinepolicy.net ([64.62.161.194])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtPD-0007lc-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:48:47 -0500
Received: by mailbox.onlinepolicy.net (Postfix, from userid 504)
	id C106C1681A5; Mon,  1 Mar 2004 10:44:15 -0800 (PST)
Received: from roger (dsl081-190-082.sea1.dsl.speakeasy.net [64.81.190.82])
	by mailbox.onlinepolicy.net (Postfix) with ESMTP id 34B7A1681A3;
	Mon,  1 Mar 2004 10:44:15 -0800 (PST)
From: "Roger B.A. Klorese" <rogerk@queernet.org>
To: "'Seth Breidbart'" <sethb@panix.com>, <asrg@ietf.org>
Subject: RE: [Asrg] [IP] CNN covers Meng's SPF
Message-ID: <7CEFA9CA4D5BE74586551915EC9C9C33805C11@consera1.corpnet.consera.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <200403011941.i21JfaU23193@panix5.panix.com>
Importance: Normal
Content-Transfer-Encoding: quoted-printable
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 11:48:15 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> If I'm at an airport lounge kiosk and I send email, it can either
> admit that it came from airportloungekiosk.wherever, or I can connect
> to Panix and send mail from there.  Otherwise, if _I_ can send mail
> claiming to be from <sethb@panix.com> from the kiosk, so could you (or
> a spammer), and I don't want that.

Um, why?

If I authenticate to Panix.com, you should trust that I'm sending legit =
mail
through you, whatever domain I'm using to send it, or you should revoke =
my
ability to authenticate.=20

Trust the people you contract service for.  Don't contract service for =
the
untrustworthy.


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



From exim@www1.ietf.org  Mon Mar  1 14:59:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01857
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 14:59:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtZ0-0005EY-8I
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 14:58:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21JwsaX020112
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 14:58:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtZ0-0005EJ-4p
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 14:58:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01852
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 14:58:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtYx-0001BK-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:58:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxtY5-00016p-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:57:58 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtXZ-00011r-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 14:57:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtWE-00050e-HU; Mon, 01 Mar 2004 14:56:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxtWC-000509-Ql
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 14:56:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01707
	for <asrg@ietf.org>; Mon, 1 Mar 2004 14:55:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtWA-0000uI-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:55:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxtVL-0000os-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:55:08 -0500
Received: from mail1.panix.com ([166.84.1.72])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxtV0-0000i9-00
	for asrg@ietf.org; Mon, 01 Mar 2004 14:54:46 -0500
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail1.panix.com (Postfix) with ESMTP id 1A5204884E
	for <asrg@ietf.org>; Mon,  1 Mar 2004 14:54:45 -0500 (EST)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i21Jsj424806;
	Mon, 1 Mar 2004 14:54:45 -0500 (EST)
Message-Id: <200403011954.i21Jsj424806@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: 
	<7CEFA9CA4D5BE74586551915EC9C9C33805C11@consera1.corpnet.consera.com>
	(rogerk@queernet.org)
Subject: Re: [Asrg] [IP] CNN covers Meng's SPF
References: <7CEFA9CA4D5BE74586551915EC9C9C33805C11@consera1.corpnet.consera.com>
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 14:54:45 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

"Roger B.A. Klorese" <rogerk@queernet.org> wrote:

>> If I'm at an airport lounge kiosk and I send email, it can either
>> admit that it came from airportloungekiosk.wherever, or I can connect
>> to Panix and send mail from there.  Otherwise, if _I_ can send mail
>> claiming to be from <sethb@panix.com> from the kiosk, so could you (or
>> a spammer), and I don't want that.
>
> Um, why?
>
> If I authenticate to Panix.com, you should trust that I'm sending legit mail
> through you, whatever domain I'm using to send it, or you should revoke my
> ability to authenticate. 

I'm a user here, not speaking for Panix.

I meant if I can send email to a random recipient (e.g. hotmail)
claiming to be <sethb@panix.com> but I don't authenticate myself to
Panix in the process, then you can do the same.  (There's no way for
me to authenticate to hotmail, because they don't know anything about
me.)

If I authenticate myself to Panix, then I can either send email
through them (in which case SPF works fine, Panix's outbound
mailservers are listed) or I can persuade them to temporarily list the
IP I'm using (if their software works that way) so hotmail will
believe me.

Seth


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



From exim@www1.ietf.org  Mon Mar  1 15:00:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01929
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 15:00:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axta1-0005Fn-Ms
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 14:59:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21JxvfF020187
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 14:59:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxqU5-0007HU-9W
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 11:41:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16709
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 11:25:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axq21-0007MY-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 11:12:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axpz6-0006V2-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 11:09:37 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axpus-0004e3-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 11:05:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axpuj-0001z3-J0; Mon, 01 Mar 2004 11:05:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxpuX-0001wD-JX
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 11:04:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12948
	for <asrg@ietf.org>; Mon, 1 Mar 2004 11:04:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxpsJ-0003a9-00
	for asrg@ietf.org; Mon, 01 Mar 2004 11:02:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axplc-000142-00
	for asrg@ietf.org; Mon, 01 Mar 2004 10:55:42 -0500
Received: from mail3.panix.com ([166.84.1.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxpdV-0005us-00
	for asrg@ietf.org; Mon, 01 Mar 2004 10:47:17 -0500
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail3.panix.com (Postfix) with ESMTP id 27541986FA
	for <asrg@ietf.org>; Mon,  1 Mar 2004 10:47:04 -0500 (EST)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i21Fl4611911;
	Mon, 1 Mar 2004 10:47:04 -0500 (EST)
Message-Id: <200403011547.i21Fl4611911@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <GPEMJLCHICHEGPOKJHHDMEKLGPAA.rebel@rebel.com.au>
Subject: Re: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
References: <GPEMJLCHICHEGPOKJHHDMEKLGPAA.rebel@rebel.com.au>
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 10:47:04 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

"Chris" <rebel@rebel.com.au> wrote:

>> >>Trojaned machines - by their nature authenticated
>> No, not actually. The authentication process is SMTP server to
>> server,
>
> No when I say trojaned machine I mean someone places a trojan on my machine
> and then sends email on my account
>
> my server will of course authenticate the email as having come from me (and
> itself) the server doesn't know my machine has been compromised.
>
> I didn't send it, some spammer who took over my machine did.

That depends on your configuration.  I don't store keys or passwords
anywhere Windoze can get hold of them.

Even for those who do, this makes detecting and blocking them easier,
since the ISP can filter its own email servers.

> If "Blocklists" were to become viable in my opinion they would have to be
> formalised

They are viable: they exist and are used.  They aren't perfect, but
those who use them choose to do so anyway.

> and again the argument arises that one mans spam is another mans erectile
> enhancer

You shouldn't use a blocklist that you don't want to.

> Just because someone personally won't accept any form of spam does not mean
> the next person has to bow to their wishes.

The next person doesn't have to use my mailserver, he can buy service
 from someone else or run his own.

> this is effectivally censorship which I am totally against.

My toys, my rules.

Seth

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



From exim@www1.ietf.org  Mon Mar  1 15:41:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA05407
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 15:41:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxuDj-0000uz-3A
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 15:40:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21KewtX003519
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 15:40:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axq8d-0004uK-Br
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 11:19:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13633
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 11:05:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxpkT-0000c6-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 10:54:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axpbh-0005N1-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 10:45:29 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxpEc-00062B-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 10:21:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxpE6-0007ws-GR; Mon, 01 Mar 2004 10:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxpDv-0007pC-Jy
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 10:20:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01880
	for <asrg@ietf.org>; Mon, 1 Mar 2004 10:20:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxpDt-0005pT-00
	for asrg@ietf.org; Mon, 01 Mar 2004 10:20:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axoe2-0005SA-00
	for asrg@ietf.org; Mon, 01 Mar 2004 09:43:50 -0500
Received: from teal.hjp.at ([62.99.236.98])
	by ietf-mx with smtp (Exim 4.12)
	id 1AxoVM-00033j-00
	for asrg@ietf.org; Mon, 01 Mar 2004 09:34:48 -0500
Received: (qmail 13084 invoked by uid 500); 1 Mar 2004 14:34:16 -0000
From: "Peter J. Holzer" <hjp-asrg@hjp.at>
To: "'ASRG'" <asrg@ietf.org>
Subject: Re: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Message-ID: <20040301143416.GA12966@teal.hjp.at>
Mail-Followup-To: 'ASRG' <asrg@ietf.org>
References: <GPEMJLCHICHEGPOKJHHDMEKLGPAA.rebel@rebel.com.au> <020901c3ff7e$10307840$5b00005a@moregarlic.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK"
Content-Disposition: inline
In-Reply-To: <020901c3ff7e$10307840$5b00005a@moregarlic.com>
User-Agent: Mutt/1.4.1i
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 15:34:16 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--YZ5djTAD1cGYuMQK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2004-03-01 06:12:09 -0500, Larry Seltzer wrote:
> >>No when I say trojaned machine I mean someone places a trojan on my mac=
hine and then
> sends email on my account
>=20
> None of these trojans work that way, at least not since Melissa or someti=
me about then.
> They all use built-in SMTP code to send mail on behalf of the user. The r=
eason is that
> Microsoft closed this hole in Outlook and Outlook Express several years a=
go, and any
> version of either (since Outlook 98) that's been patched since about 2000=
 or 2001 blocks
> external programmatic access and access to the address book without expli=
cit end-user
> approval.

The trojan could always read this data directly. I don't think they can
block that.

> If you'll read the analyses of how these things work you'll see that they
> don't use the MUA, they *are* an MUA.=20

They are also the MTA.

> If you know of a trojan that does what you claim please give me a
> specific example, or tell me how it would work.

Swen. But I don't think it uses data from Outlook or Outlook Express. It
simply pops up a Window asking the user for his credentials.=20

> But they don't bother with the user's credentials because
> they don't have to.

They don't have to, currently. But if LMAP, MTA-Mark or blocking of port
25 becomes widespread, they will have to.=20

	hp

--=20
   _  | Peter J. Holzer    | I think we need two definitions:
|_|_) | Sysadmin WSR       | 1) The problem the *users* want us to solve
| |   | hjp@hjp.at         | 2) The problem our solution addresses.
__/   | http://www.hjp.at/ |    -- Phillip Hallam-Baker on spam

--YZ5djTAD1cGYuMQK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQFAQ0nofZ+RkG8quy0RAnAiAJ9j+YJ+G469FntD9FCVvbNc3MUXrQCfUwn5
EAfYLxt8QX581ih5trJFfZI=
=laAz
-----END PGP SIGNATURE-----

--YZ5djTAD1cGYuMQK--

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



From exim@www1.ietf.org  Mon Mar  1 17:18:01 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09605
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 17:18:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxvjB-00065s-Ks
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 17:17:34 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21MHXVr023418
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 17:17:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxvjB-00065d-7q
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 17:17:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09400
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 17:17:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axvj9-0001Zn-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:17:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axvi2-0001Kr-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:16:23 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axvh9-0001C1-05
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:15:27 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Axvbp-0004i0-4x
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:09:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxvZy-0005JA-3Q; Mon, 01 Mar 2004 17:08:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxkeK-0002Ek-8n
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 05:27:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07841
	for <asrg@ietf.org>; Mon, 1 Mar 2004 05:27:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxkeG-0002Fj-00
	for asrg@ietf.org; Mon, 01 Mar 2004 05:27:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxkdM-0002A4-00
	for asrg@ietf.org; Mon, 01 Mar 2004 05:26:49 -0500
Received: from gizmo10bw.bigpond.com ([144.140.70.20])
	by ietf-mx with smtp (Exim 4.12)
	id 1Axkci-00020E-00
	for asrg@ietf.org; Mon, 01 Mar 2004 05:26:08 -0500
Received: (qmail 18189 invoked from network); 1 Mar 2004 10:22:41 -0000
Received: from unknown (HELO bwmam10.bigpond.com) (144.135.24.97)
  by gizmo10bw.bigpond.com with SMTP; 1 Mar 2004 10:22:41 -0000
Received: from 144.138.220.115 ([144.138.220.115]) by bwmam10.bigpond.com(MAM REL_3_4_2 165/109533725) with SMTP id 109533725; Mon, 01 Mar 2004 20:25:34 +1000
Reply-To: <sami.suomalainen@bigpond.com>
From: "Sami Suomalainen" <sami.suomalainen@bigpond.com>
To: "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Message-ID: <003001c3ff77$685778e0$73dc8a90@SUOMALAINEN>
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.2727.1300
In-reply-to: <GPEMJLCHICHEGPOKJHHDMEKLGPAA.rebel@rebel.com.au>
Importance: Normal
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 20:24:26 +1000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> People actually use spam the same as my wife uses junkmail.
> 
> Just because someone personally won't accept any form of spam 
> does not mean
> the next person has to bow to their wishes.
> this is effectivally censorship which I am totally against.

This is one thing I have been thinking lately. We want to get rid of
spam - sure - but surely there is a place for legitimate advertising on
the net. I am wholeheartedly for increased authentication so that we
know at least better than now who has sent each email. That way we can
start better targeting the worst spammers.

As you can guess from the above comment, my background is in marketing.
However, I am totally against Martha Siegel type of spammers who care
about nothing else but themselves and money, who cares if you clog the
whole net in the process?? That's how these guys think. I believe there
is a place for marketing on the net, even via email, and I believe we
could make it more acceptable too. A simple solution would be to add a
'marketing tag' (and possibly other tags showing what kind of product is
offered) into emails so that these emails could be bounced back to the
sender automatically if the recipient has indicated that s/he doesn't
want that kind of advertising. Idealistic? Perhaps.

In addition, I believe marketing messages should be made at the same
time subject to charges, and these charges would be used for getting
better stuff for users, similarly to TV advertising bringing better
programmes.

I know this is idealistic but I just wanted to bring a responsible
marketing view into this discussion (most of the people here are
probably more technical?). I believe all of the above would be great for
both users and marketers if it could be implemented. There is a minority
of marketers who would ever even consider spamming, but unfortunately
those few who do make the whole industry's reputation bad.

Cheers
Sami



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



From exim@www1.ietf.org  Mon Mar  1 17:25:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10005
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 17:25:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxvqU-0006Yw-GG
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 17:25:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21MP6Eh025220
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 17:25:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxvqU-0006Yh-BC
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 17:25:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09984
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 17:25:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxvqS-0002W0-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:25:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxvpS-0002Px-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:24:03 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axvou-0002KU-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:23:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxvnV-0006MR-Ae; Mon, 01 Mar 2004 17:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axvmg-0006LB-B9
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 17:21:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09860
	for <asrg@ietf.org>; Mon, 1 Mar 2004 17:21:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axvme-00027l-00
	for asrg@ietf.org; Mon, 01 Mar 2004 17:21:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axvln-00021g-00
	for asrg@ietf.org; Mon, 01 Mar 2004 17:20:16 -0500
Received: from mail2.speakeasy.net ([216.254.0.202])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxvlF-0001uB-00
	for asrg@ietf.org; Mon, 01 Mar 2004 17:19:41 -0500
Received: (qmail 20999 invoked from network); 1 Mar 2004 22:19:40 -0000
Received: from dsl081-214-187.nyc2.dsl.speakeasy.net (HELO elliot) (lseltzer@[64.81.214.187])
          (envelope-sender <larry@larryseltzer.com>)
          by mail2.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <asrg@ietf.org>; 1 Mar 2004 22:19:40 -0000
From: "Larry Seltzer" <larry@larryseltzer.com>
To: <sami.suomalainen@bigpond.com>, "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Message-ID: <041e01c3ffdb$0e65d020$5b00005a@moregarlic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <003001c3ff77$685778e0$73dc8a90@SUOMALAINEN>
Importance: Normal
Content-Transfer-Encoding: quoted-printable
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 17:17:49 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

>>...responsible marketing view ...

Nothing in SPF, CID or DK would stop a legitimate marketer from sending =
e-mail that
authenticates properly. Actually, nothing stops them from sending it =
unsolicited either,
but since the addresses would be verifiable users would be able to block =
them
effectively. If they didn't block you, they would get your mail.

Larry Seltzer
eWEEK.com Security Center Editor
http://security.eweek.com/
larryseltzer@ziffdavis.com=20



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



From exim@www1.ietf.org  Mon Mar  1 17:39:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10352
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 17:39:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axw3w-0007Ps-FI
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 17:39:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21Md0xT028502
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 17:39:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axw3w-0007Pd-A9
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 17:39:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10345
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 17:38:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axw3t-0003jY-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:38:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axw2x-0003eo-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:38:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axw2S-0003a4-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:37:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axw14-0006rE-W9; Mon, 01 Mar 2004 17:36:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axw10-0006qa-Sx
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 17:35:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10277
	for <asrg@ietf.org>; Mon, 1 Mar 2004 17:35:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axw0y-0003TB-00
	for asrg@ietf.org; Mon, 01 Mar 2004 17:35:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axw06-0003Oh-00
	for asrg@ietf.org; Mon, 01 Mar 2004 17:35:03 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxvzC-0003Jq-00
	for asrg@ietf.org; Mon, 01 Mar 2004 17:34:06 -0500
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (mailer3.verisign.com [65.205.251.55])
        by peacock.verisign.com (8.12.11/) with ESMTP id i21MY2c9021068;
        Mon, 1 Mar 2004 14:34:02 -0800 (PST)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <F2HVVT84>; Mon, 1 Mar 2004 14:34:02 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A18FA@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'gep2@terabites.com'" <gep2@terabites.com>, dave@farber.net
Cc: asrg@ietf.org, wishlist@microsoft.com
Subject: RE: [Asrg] [IP] CNN covers Meng's SPF
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 14:33:58 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60


> Funny thing that each of these folks are ISPs... and each is 
> trying to make sure 
> you use THEM for everything you do. :-((  

It is not a surprise to me that ISPs want to reduce spam. The
surprise to me is that the IETF appears unable to treat the
issue with more than casual interest.


> Actually, the "Received" headers give one a pretty decent 
> trace of "where it 
> comes from", at least once it leaves the hands of those who 
> counterfeit headers 
> or otherwise attempt to deceive. 

The received headers provide an end user absolutely no information
of value. Most end users would not even know they existed.

The problem with approches of this sort is that they are based
on the false assumption that the Internet still belongs to
a small inner circle of geeks who have no responsibility at
all to the wider public.

How do we know the point at which the counterfeiting
occurs without the ability to authenticate any of the links 
in the chain?

> And one could certainly imagine a system 

Imagined systems will form no part of the solution, only running
code will.

> > Many software engineers are concerned, however, that these 
> systems could
> end up causing more problems than they solve.
> 
> And, in fact, that is precisely the problem. 

No, the problem is that nobody will state what those dire
consequences are and as a result little notice is being taken
of the would be Cassandras.

Vague intonations of doom such as 'this system is so broken 
I won't tell you what is wrong with it' deserve to be ignored.

Also deserving of being igonred are the people who say to me
that there are dire consequences to any Internet change and so
there should be a period of total inaction lasting six months
in the first instance and with repeated renewals.

If there is such a threat to the Internet then the IAB and
the IESG will kindly produce a document stating what those
threats are. People who shout the sky is falling but don't
have the time to explain the basis for their claim have zero
credibility with me - regardless of the office they hold
or the illustriousness of their predecessors.

> Many of these 
> systems, SPECFICALLY 
> INCLUDING Wong's SPF (and as a member of the IETF's Anti-Spam 
> Research Group was 
> on Wong's SPF mailing list for a while, before I concluded 
> that it was probably 
> fatally flawed), have a number of very serious problems in 
> them if they were 
> ever to be widely adopted.

Again, same old sky is falling routine, no details.

Doing something to the Internet that would set a precedent
for acting without IESG or IANA approval is not a disaster
in my view, quite the contrary.

I want the use of the SRV style _ep or _spf record tagging
to set a precedent for extending the DNS outside the control
of the IESG. 


> The problem with this one of course is that not all E-mail 
> messages originate at mail servers run by ISPs. 

So, take your chances with the spam filter.

> Some of the more sophisticated  business customers 
> (and indeed, some of the more sophisticated USERS, myself 
> among them) actually 
> use their own outgoing E-mail servers... for a whole variety 
> of perfectly valid reasons.  

State them, if you want them to be likely to remain true in
future.

There are many ways to adapt SPF to the various corner case
scenarios. Use dynamic DNS to set your mail records on the fly
for example.

Sure they require people to get off their butt and do something,
but the fact is that there is much too much spam and people who 
care about their email being received are going to have to work 
to convince recipients that it is not spam.

> It's outrageous and offensive that ISPs are trying 
> to prevent users 
> from being able to bypass the ISP's (hoped-for) monopoly 
> provision of (sometimes 
> unwanted and often gotcha-laden) "ISP services".

It is inevitable. Port 25 blocking is largely the effect of the
blacklists. 

How many ISPs block outgoing SUBMIT? 

> There are a lot of such systems and most of them work at 
> least in the scenario 
> they are designed for.  Unfortunately, when you start looking 
> at the less 
> obvious but still HIGHLY important situations...

The problem is that these 'highly important situations' get
used as an excuse for doing nothing by people whose real 
intention was to block progress all along.

If you want to influence the outcome in a positive way
you have to give positive criticism.

Blocking these proposals in the IETF will not affect their
deployment. Nobody is waiting for the IETF for a permission
slip to defend the country.

> > They also could break "send to a friend" features in which 
> someone clicks
> on a Web link to pass an interesting item to someone else.

Actually CallerID and SPF need not break these schemes. The core
idea here is accountability. 

The problem with 'send to a friend' is that the messages are
forged so they appear to come from the requester, they don't,
they come from the web site, that is the name that should
appear in the from address.

> In fact, Wong (based on E-mail exchanges he and I have had) 
> basically just 
> doesn't care about the important flaws in his approach, he is 
> fully aware of 
> them and has been forging ahead with it regardless.  I 
> consider his approach and 
> attitude to be irresponsible and objectionable.

More duck speak.

If you have a problem with the proposals then express it with
greater clarity than has happened thus far. 


> > But the gain in fighting spam outweighs any pain from 
> change, Wong argues.
> 
> Except that it doesn't.  NOTHING in SPF in any way prevents 
> spam whatsoever... 
> all it does is to authenticate the sender.  Spammer-friendly 
> ISPs, new "vanity" 
> domains (and spammers are creating "disposable" vanity 
> domains with seemingly 
> randomly generated domain names at a breathtaking rate... 

Authentication + Accreditation + Consequences = Spam Solution

> Spammers can also continue hijacking (with viruses and worms) 
> the systems of 
> legitimate (if naive or careless) users and use those to 
> generate spam E-mails 

Sure, more problems to solve, but we have to solve this
problem anyway.

> A **far** better approach... simpler, easier, rapid to 
> implement, hard to 
> disable or to evade... and one which IMMEDIATELY benefits the 
> folks who 
> INDIVIDUALLY put it in place, without requiring literally 
> worldwide changes and 
> consensus to be effective... is for E-mail client software 
> companies to simply 
> discard ALL incoming attachments 

Sorry, you don't understand the Internet, we are not retreating
here.

Those HTMl messages are much more important to me than any
of the problems you imagine are important.

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



From exim@www1.ietf.org  Mon Mar  1 17:56:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10825
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 17:56:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwKO-00007f-88
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 17:56:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21Mu03T000465
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 17:56:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwKO-00007Q-3W
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 17:56:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10819
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 17:55:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwKL-0005G3-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:55:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxwJP-0005Af-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:55:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwIY-00055x-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 17:54:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwIT-0008NK-KN; Mon, 01 Mar 2004 17:54:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwIS-0008N9-NV
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 17:54:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10771
	for <asrg@ietf.org>; Mon, 1 Mar 2004 17:53:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwIQ-00054q-00
	for asrg@ietf.org; Mon, 01 Mar 2004 17:53:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxwHY-0004zh-00
	for asrg@ietf.org; Mon, 01 Mar 2004 17:53:04 -0500
Received: from sc1.scconsult.com ([66.73.230.190] helo=toaster.scconsult.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwGw-0004uY-00
	for asrg@ietf.org; Mon, 01 Mar 2004 17:52:26 -0500
Received: from [192.168.254.12] (localhost [127.0.0.1])
	by toaster.scconsult.com (Postfix) with ESMTP id 98409F1DF0
	for <asrg@ietf.org>; Mon,  1 Mar 2004 17:52:25 -0500 (EST)
Mime-Version: 1.0
X-Sender: bill@fireproof.scconsult.com
Message-Id: <p0600204dbc69136d1759@[192.168.254.12]>
In-Reply-To: <02a601c3ffa4$e45f5c00$5b00005a@moregarlic.com>
References: <02a601c3ffa4$e45f5c00$5b00005a@moregarlic.com>
To: <asrg@ietf.org>
From: Bill Cole <grsa@billmail.scconsult.com>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 17:52:15 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

At 10:49 AM -0500 3/1/04, Larry Seltzer wrote:
>>>The trojan could always read this data [[address book?]] directly. 
>>>I don't think they
>can block that.
>
>And that's what they do, although the typical pattern is that they 
>read .wab, .htm*,
>.txt, maybe .doc files, and scan them for e-mail addresses. 
>Interesting, but not
>relevant to the main issue of authentication, except that to the 
>extent that these worms
>read these addresses to determine from: addresses for their 
>propagation, they are even
>less likely to spread through SMTP authentication.
>
>>>Swen. But I don't think it uses data from Outlook or Outlook 
>>>Express. It simply pops
>up a Window asking the user for his credentials.
>
>A copy of this dialog box may be found at
>http://securityresponse.symantec.com/avcenter/graphics/w32.swen.a@mm.5.gif. 
>I have a
>hard time believing. I doubt many people remember their SMTP server 
>credentials offhand,
>since they are usually stored by the MUA for automatic use.
>
>But anyway, if that's the best they can come up with I'm still sure 
>that worm spreading
>would be cut dramatically. What they'd really need to do is to find 
>ways to crack the
>SMTP AUTH credentials from the various MUAs that might be on a system.

Are you unfamiliar with Swen?

Since 9/19/03 I have received 3621 copies of Swen from over 1700 
unique IP addresses carrying 1651 unique envelope senders, and that 
only counts the ones aimed at my 'main' account. That number of held 
down by the fact that mail to that account has a very draconian 
SMTP-level blacklist in front of it as well as router-level 
protections which together shun mail from most of Asia and large 
pieces of the rest of the world, and I also use a number of the more 
conservative public blacklists. It is a rare day when I do not see a 
handful of new Swen sources. At one point the rate of Swen coming out 
of Charter's mailservers was so high  that my only defense to keep my 
mail server usable for anything I wanted was to block that part of 
their network at the router level. It took less than2 days for their 
user population to reach that level of infection from the initial 
sightings of Swen.

Swen arrives with the real address of the infected user in the SMTP 
envelope and a bogus address that often claims to be from Microsoft 
in the From header. It arrives NOT from the actually infected 
machine, but from the normal outbound mailserver of that user's ISP 
or employer (or wherever they normally pass their mail.) That dialog 
you saw, as incredible as it may seem to you, demonstrably does its 
job quite well. The only other explanation would be that Swen is 
instead managing to dig credentials out of wherever Outlook Express 
stores them OR that it is using some programmatic means of getting 
the OS to send mail for it using the OE config and saved credentials, 
and that it is only presenting the dialog as a bit of misdirection 
for anti-virus folks. Unless a couple of ISP's have been lying to me 
without prompting (both volunteered that they require SMTP AUTH in 
asking me to stop blocking their servers,) Swen does indeed get 
through machines that require SMTP authentication.

Swen and more recent worms have provided rather solid proof that the 
most vulnerable attack point is between the keyboard and the chair.

-- 
Bill Cole
bill@scconsult.com


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



From exim@www1.ietf.org  Mon Mar  1 18:13:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12013
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 18:13:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axwaw-0005ll-MU
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 18:13:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21ND6Q7022171
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 18:13:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axwaw-0005lR-Hm
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 18:13:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11955
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 18:13:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axwat-0006ot-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:13:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axwa1-0006ik-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:12:10 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwZ8-0006cc-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:11:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwYv-0004zL-E7; Mon, 01 Mar 2004 18:11:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwY4-0004aj-Tg
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 18:10:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11620
	for <asrg@ietf.org>; Mon, 1 Mar 2004 18:10:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwY1-0006Vk-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:10:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxwXC-0006QB-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:09:15 -0500
Received: from mail.chariot.net.au ([203.87.95.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwWi-0006Jo-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:08:45 -0500
Received: from localhost (avs1.sa.chariot.net.au [203.87.94.5])
	by mail.chariot.net.au (Postfix) with ESMTP id CFC826408E
	for <asrg@ietf.org>; Tue,  2 Mar 2004 09:38:41 +1030 (CST)
Received: from mail.chariot.net.au ([203.87.95.38])
 by localhost (avs1.sa.chariot.net.au [203.87.94.5]) (amavisd-new, port 10024)
 with LMTP id 17391-03-5 for <asrg@ietf.org>;
 Tue,  2 Mar 2004 09:38:41 +1030 (CST)
Received: from rebel (ppp-086.cust203-87-123.ghr.chariot.net.au [203.87.123.86])
	by mail.chariot.net.au (Postfix) with SMTP id 747B167377
	for <asrg@ietf.org>; Tue,  2 Mar 2004 09:38:40 +1030 (CST)
From: "Chris" <asrg@rebel.com.au>
To: <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Message-ID: <GPEMJLCHICHEGPOKJHHDOELBGPAA.asrg@rebel.com.au>
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 IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <p0600204dbc69136d1759@[192.168.254.12]>
X-Virus-Scanned: by amavisd-new at chariot.net.au
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/mail-archive/working-groups/asrg/>
Date: Tue, 2 Mar 2004 09:37:40 +1030
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi Guys

thanks for all the input

But bogged down in detail here!!!!!

the point of my email is Spammers don't give up and die (die die die)

they mutate into something else

if the world is about to adopt yahoo and M$ authentication systems I say
great.

BUT

Spammers will persist. if we are one step ahead it makes their life a lot
harder

So we should look at what spammers will be doing post authentication.

the examples I included were just that examples. They may not have been all
that accurate.


Regards
Chris



> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org]On Behalf Of Bill
> Cole
> Sent: Tuesday, 2 March 2004 9:22 AM
> To: asrg@ietf.org
> Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
>
>
> At 10:49 AM -0500 3/1/04, Larry Seltzer wrote:
> >>>The trojan could always read this data [[address book?]] directly.
> >>>I don't think they
> >can block that.
> >
> >And that's what they do, although the typical pattern is that they
> >read .wab, .htm*,
> >.txt, maybe .doc files, and scan them for e-mail addresses.
> >Interesting, but not
> >relevant to the main issue of authentication, except that to the
> >extent that these worms
> >read these addresses to determine from: addresses for their
> >propagation, they are even
> >less likely to spread through SMTP authentication.
> >
> >>>Swen. But I don't think it uses data from Outlook or Outlook
> >>>Express. It simply pops
> >up a Window asking the user for his credentials.
> >
> >A copy of this dialog box may be found at
> >http://securityresponse.symantec.com/avcenter/graphics/w32.swen.a
> @mm.5.gif.
> >I have a
> >hard time believing. I doubt many people remember their SMTP server
> >credentials offhand,
> >since they are usually stored by the MUA for automatic use.
> >
> >But anyway, if that's the best they can come up with I'm still sure
> >that worm spreading
> >would be cut dramatically. What they'd really need to do is to find
> >ways to crack the
> >SMTP AUTH credentials from the various MUAs that might be on a system.
>
> Are you unfamiliar with Swen?
>
> Since 9/19/03 I have received 3621 copies of Swen from over 1700
> unique IP addresses carrying 1651 unique envelope senders, and that
> only counts the ones aimed at my 'main' account. That number of held
> down by the fact that mail to that account has a very draconian
> SMTP-level blacklist in front of it as well as router-level
> protections which together shun mail from most of Asia and large
> pieces of the rest of the world, and I also use a number of the more
> conservative public blacklists. It is a rare day when I do not see a
> handful of new Swen sources. At one point the rate of Swen coming out
> of Charter's mailservers was so high  that my only defense to keep my
> mail server usable for anything I wanted was to block that part of
> their network at the router level. It took less than2 days for their
> user population to reach that level of infection from the initial
> sightings of Swen.
>
> Swen arrives with the real address of the infected user in the SMTP
> envelope and a bogus address that often claims to be from Microsoft
> in the From header. It arrives NOT from the actually infected
> machine, but from the normal outbound mailserver of that user's ISP
> or employer (or wherever they normally pass their mail.) That dialog
> you saw, as incredible as it may seem to you, demonstrably does its
> job quite well. The only other explanation would be that Swen is
> instead managing to dig credentials out of wherever Outlook Express
> stores them OR that it is using some programmatic means of getting
> the OS to send mail for it using the OE config and saved credentials,
> and that it is only presenting the dialog as a bit of misdirection
> for anti-virus folks. Unless a couple of ISP's have been lying to me
> without prompting (both volunteered that they require SMTP AUTH in
> asking me to stop blocking their servers,) Swen does indeed get
> through machines that require SMTP authentication.
>
> Swen and more recent worms have provided rather solid proof that the
> most vulnerable attack point is between the keyboard and the chair.
>
> --
> Bill Cole
> bill@scconsult.com
>
>
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg


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



From exim@www1.ietf.org  Mon Mar  1 18:28:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12841
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 18:28:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwpR-0008Jy-Bc
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 18:28:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21NS5ml031978
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 18:28:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwpR-0008Jg-5P
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 18:28:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12826
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 18:28:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwpO-0000Vl-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:28:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxwoS-0000Po-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:27:04 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axwnd-0000K5-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:26:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwnS-00085m-JR; Mon, 01 Mar 2004 18:26:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axwmj-00083u-Nk
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 18:25:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12723
	for <asrg@ietf.org>; Mon, 1 Mar 2004 18:25:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axwmg-0000D2-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:25:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axwlj-00005h-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:24:15 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwlA-0007lx-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:23:40 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i21NNVdW022756;
        Mon, 1 Mar 2004 15:23:31 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <F2HV1DXA>; Mon, 1 Mar 2004 15:23:31 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A18FC@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Larry Seltzer'" <larry@larryseltzer.com>, sami.suomalainen@bigpond.com,
        "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 15:23:24 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60


> Nothing in SPF, CID or DK would stop a legitimate marketer 
> from sending e-mail that
> authenticates properly. Actually, nothing stops them from 
> sending it unsolicited either,
> but since the addresses would be verifiable users would be 
> able to block them
> effectively. If they didn't block you, they would get your mail.

I agree with the response to the specific issue, but I think
it misses the big picture here. 


I think the problem here is that some people don't understand 
engineering. The way you solve a big problem like spam is
you break it down into a collection of smaller problems and then 
address those in turn.

Saying that SPF or Caller ID does not bring peace on earth
does not mean they have no value. They are not an end in
themselves, they are a starting point. Of course this type 
of talk is being used in an attempt to talk the proposals out,
a strategy that assumes a veto power that does not exist.


Everyone understands that there has to be more than just
authentication to 'solve' the spam problem. But authentication
is the first step in any of the comprehensive strategies.

Once you know who sent the message you have a different
response depending on the type of spam it is. 

	Impersonation spam (aka joe job) - discard

	Intentional spam - affects the reputation of the sender,
			may lead to civil, criminal sanctions

	Hijacked Machine spam - We locate the machine and shut it 
			down.

The different responses require different strategies but they
are all soluble. It is simply a matter of case analysis. 

At a recent anti-phishing meeting we discussed a mechanism to
address the hijacked machine issue. Lets just define a simple
way that you can contact me when you think someone is using a 
machine I am responsible for in a malicious fashion.

_contact.example.com 	TXT 
			"email:abuse.example.com tel:+44012440102031"
_contact.example.com	SRV
			"http://contact.example.com/"
_contact.1.0.0.10		TXT
			"include:example.com"

So when someone launches a DDoS against my machines with source 
address 10.0.0.1 I know where to go, I have an email address,
telephone number, more usefully though I have the address of
a web service I can connect to and send a report of the incident.

If I am operating an ISP I am not going to turn off users 
automatically in response to unauthenticated requests from outside,
but I could easily automate much of the response loop:

	* Report of spam or virus attack from IP address
		AND IP address is making lots of connections to port 25
		ACTION - warn operator, possibly shut down site.

	* Report of DDoS from source address
		AND IP address is engaged in objectionable activity
		ACTION object

Spoofed IP addresses could be addressed by similar means but here 
I need to connect via the contact addresses of my ISPs :-

	Report of DDoS against IP address 10.9.9.9 
		AND abnormal activity connecting to 10.9.9.9
			Respond

Response consists of tracking the attack back to the source, same
way a human operator would. For each router you look to see which
incomming ports have abnormal levels of packets routed to the 
targetted address, if so you kick the contact report back down
to the next NOC in the chain. If the source is in your own network
you disable the machines behaving unacceptably (like SYN flooding).




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



From exim@www1.ietf.org  Mon Mar  1 18:34:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13061
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 18:34:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwvN-0000HV-6A
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 18:34:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21NYDs1001075
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 18:34:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwvN-0000HG-1x
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 18:34:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13054
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 18:34:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwvK-0001AF-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:34:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxwuQ-000143-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:33:15 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwtR-0000x9-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:32:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwtG-0008Q9-9T; Mon, 01 Mar 2004 18:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxwsP-0008Ov-JD
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 18:31:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12911
	for <asrg@ietf.org>; Mon, 1 Mar 2004 18:31:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwsM-0000pC-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:31:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxwrO-0000jA-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:30:07 -0500
Received: from mail.chariot.net.au ([203.87.95.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axwqi-0000dP-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:29:25 -0500
Received: from localhost (avs1.sa.chariot.net.au [203.87.94.5])
	by mail.chariot.net.au (Postfix) with ESMTP id 574ED6746F
	for <asrg@ietf.org>; Tue,  2 Mar 2004 09:59:18 +1030 (CST)
Received: from mail.chariot.net.au ([203.87.95.38])
 by localhost (avs1.sa.chariot.net.au [203.87.94.5]) (amavisd-new, port 10024)
 with LMTP id 10108-05-6 for <asrg@ietf.org>;
 Tue,  2 Mar 2004 09:59:17 +1030 (CST)
Received: from rebel (ppp-086.cust203-87-123.ghr.chariot.net.au [203.87.123.86])
	by mail.chariot.net.au (Postfix) with SMTP id 6A2F2674DF
	for <asrg@ietf.org>; Tue,  2 Mar 2004 09:59:13 +1030 (CST)
From: "Chris" <asrg@rebel.com.au>
To: "'ASRG'" <asrg@ietf.org>
Message-ID: <GPEMJLCHICHEGPOKJHHDEELDGPAA.asrg@rebel.com.au>
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 IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <4043C310.7070105@solidmatrix.com>
X-Virus-Scanned: by amavisd-new at chariot.net.au
Content-Transfer-Encoding: 7bit
Subject: [Asrg] RE: 2a .BCP -  Handling Trojaned machines
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/mail-archive/working-groups/asrg/>
Date: Tue, 2 Mar 2004 09:58:13 +1030
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> under a restricted access account, chances are he will be running
> Windows with administrative access and Outlook or Outlook Express.
> Nothing against Microsoft, but statistically most desktops in the world
> run Windows. Chances are that the use is stupid enough to click on the
> MyDoom virus in his inbox. At this point the virus has full
> administrative access to his machine.


Micro$ofts security model is so badly broken that it is nigh impossible for
a regular user to set up his machine in anything other than Administrative
access

If you don't registry access is blocked to most programs and they die, often
horribly.

I gave up securing a M$2000 machine because all her programs broke.

I now regularly clean the machine from virus's and I hope I have convinced
her to stop using Kazaa


trojans are here to stay!


It would also be fair to say that we could solve spam overnight by outlawing
Micro$oft bloatware (TIC)


Regards
Chris

OT

Microsofts biggest problem is the registry. A great idea that went horribly
wrong. They have invested so much into it they won't change it.


> -----Original Message-----
> From: Yakov Shafranovich [mailto:research@solidmatrix.com]
> Sent: Tuesday, 2 March 2004 9:41 AM
> To: Larry Seltzer
> Cc: 'Chris'; 'ASRG'
> Subject: 2a .BCP - Handling Trojaned machines
>
>
> Larry Seltzer wrote:
> >>>Trojaned machines - by their nature authenticated
> >
> > No, not actually. The authentication process is SMTP server to
> server, so unless the
> > trojaned system has access to an open relay which is,
> nevertheless, properly accounted
> > for in the SPF/Caller ID DNS entries, the trojan will need to
> have proper SMTP AUTH
> > credentials to some server. They don't currently work this way,
> and it seems unlikely
> > that an administrator would leave relays open but implement
> domain-level SMTP
> > authentication.
>
> One of the big ISPs I spoke to claims that 80% over their incoming
> traffic is coming from other ISPs' MTAs, which are used by trojaned
> machines to send mail, NOT by trojaned machines sending mail directly.
> No SMTP AUTH is used - the mail is send directly to the ISP's MTA and
> the ISP trusts the incoming connection because they know they our IPs.
> The question is why aren't they doing rate limiting, and I will
> get to that.
>
> But you should step back for a second. There is a basic principle in
> security - if you have physical access to the machine, then you cannot
> secure it. Unless the user is running some old copy of MS-DOS or Linux
> under a restricted access account, chances are he will be running
> Windows with administrative access and Outlook or Outlook Express.
> Nothing against Microsoft, but statistically most desktops in the world
> run Windows. Chances are that the use is stupid enough to click on the
> MyDoom virus in his inbox. At this point the virus has full
> administrative access to his machine. If the virus writer is smart
> enough, he might even make it a root kit, so the virus will have full
> access to all layers of the operating system.
>
> Now the user  will be using some form of authentication method be it
> SMTP AUTH with passwords, Verisign's or RSA's hardware tokens, smart
> cards, etc. Now we assume that the user does not have to do the
> authentication process every time he does his email, but rather his
> client or OS caches the password. The virus having full control of the
> machine, can very easily "piggy back" on that authentication process and
> send spam via the user's regular account.
>
> LMAP proposals do stop trojaned machines from sending email to other
> machines and claiming to be from someone else's domain. That's all they
> do - they do not stop spammers from using their own domains, or relaying
> via user's credentials. Granted this narrows down the playing field, but
> we still need to look at ways to be able to detect a malicious machine
> relaying email via a throwaway domain or via the user's own account. At
> this point all of the LMAP proposals are going to be discussed at the
> BoF, and if the IETF creates a WG for them after this week's meeting,
> than it will be out of scope for the ASRG.
>
> Now going back, how do you detect malicious machines relaying mail for
> throwaway domains or via the user's account. One way is via MTA MARK
> which does cause problems for users who want to run their own MTAs. But
> the argument is - if you want to run your own MTA, you must take
> responsibility for it. Another way is via reputation/accrediation
> schemes, but it remains to be seen if they will be administrated
> properly and fair unlike many of today's blacklists.
>
> However, we must not lose the sight of the fact that the one known fact
> about spam coming from the hijacked machine is the IP. The network
> hosting the IP should also be responsible for implementing some kind of
> scheme to deal with trojaned machines. One way to approach this issue is
> to detect large spikes in email traffic and queue the mail temporarily
> alerting the user. In regards to this specific method, we are currently
> looking for volunteers to write a BCP on this and other methods of
> dealing with hijacked machines from the originating network's point of
> view.
>
> Yakov
>


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



From exim@www1.ietf.org  Mon Mar  1 18:38:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13240
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 18:38:30 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axwz6-0000nK-5c
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 18:38:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21Nc35T003046
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 18:38:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axwz5-0000n1-P7
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 18:38:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13206
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 18:37:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axwz2-0001aX-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:38:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxwyC-0001Th-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:37:09 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwxB-0001Mu-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:36:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axwx9-0000QT-Dj; Mon, 01 Mar 2004 18:36:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axwb1-0005my-Ay
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 18:13:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11976
	for <asrg@ietf.org>; Mon, 1 Mar 2004 18:13:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axway-0006pd-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:13:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axwa6-0006jb-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:12:15 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxwZh-0006d8-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:11:49 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AxwZb-0007hh-00; Mon, 01 Mar 2004 18:11:43 -0500
Received: from [68.24.248.250] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AxwZa-0005ZQ-00; Mon, 01 Mar 2004 18:11:43 -0500
Message-ID: <4043C310.7070105@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Larry Seltzer <larry@larryseltzer.com>
CC: "'Chris'" <asrg@rebel.com.au>, "'ASRG'" <asrg@ietf.org>
References: <019e01c3ff36$212b7980$5b00005a@moregarlic.com>
In-Reply-To: <019e01c3ff36$212b7980$5b00005a@moregarlic.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 2a .BCP -  Handling Trojaned machines
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 18:11:12 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Larry Seltzer wrote:
>>>Trojaned machines - by their nature authenticated
> 
> No, not actually. The authentication process is SMTP server to server, so unless the
> trojaned system has access to an open relay which is, nevertheless, properly accounted
> for in the SPF/Caller ID DNS entries, the trojan will need to have proper SMTP AUTH
> credentials to some server. They don't currently work this way, and it seems unlikely
> that an administrator would leave relays open but implement domain-level SMTP
> authentication.

One of the big ISPs I spoke to claims that 80% over their incoming 
traffic is coming from other ISPs' MTAs, which are used by trojaned 
machines to send mail, NOT by trojaned machines sending mail directly. 
No SMTP AUTH is used - the mail is send directly to the ISP's MTA and 
the ISP trusts the incoming connection because they know they our IPs. 
The question is why aren't they doing rate limiting, and I will get to that.

But you should step back for a second. There is a basic principle in 
security - if you have physical access to the machine, then you cannot 
secure it. Unless the user is running some old copy of MS-DOS or Linux 
under a restricted access account, chances are he will be running 
Windows with administrative access and Outlook or Outlook Express. 
Nothing against Microsoft, but statistically most desktops in the world 
run Windows. Chances are that the use is stupid enough to click on the 
MyDoom virus in his inbox. At this point the virus has full 
administrative access to his machine. If the virus writer is smart 
enough, he might even make it a root kit, so the virus will have full 
access to all layers of the operating system.

Now the user  will be using some form of authentication method be it 
SMTP AUTH with passwords, Verisign's or RSA's hardware tokens, smart 
cards, etc. Now we assume that the user does not have to do the 
authentication process every time he does his email, but rather his 
client or OS caches the password. The virus having full control of the 
machine, can very easily "piggy back" on that authentication process and 
send spam via the user's regular account.

LMAP proposals do stop trojaned machines from sending email to other 
machines and claiming to be from someone else's domain. That's all they 
do - they do not stop spammers from using their own domains, or relaying 
via user's credentials. Granted this narrows down the playing field, but 
we still need to look at ways to be able to detect a malicious machine 
relaying email via a throwaway domain or via the user's own account. At 
this point all of the LMAP proposals are going to be discussed at the 
BoF, and if the IETF creates a WG for them after this week's meeting, 
than it will be out of scope for the ASRG.

Now going back, how do you detect malicious machines relaying mail for 
throwaway domains or via the user's account. One way is via MTA MARK 
which does cause problems for users who want to run their own MTAs. But 
the argument is - if you want to run your own MTA, you must take 
responsibility for it. Another way is via reputation/accrediation 
schemes, but it remains to be seen if they will be administrated 
properly and fair unlike many of today's blacklists.

However, we must not lose the sight of the fact that the one known fact 
about spam coming from the hijacked machine is the IP. The network 
hosting the IP should also be responsible for implementing some kind of 
scheme to deal with trojaned machines. One way to approach this issue is 
to detect large spikes in email traffic and queue the mail temporarily 
alerting the user. In regards to this specific method, we are currently 
looking for volunteers to write a BCP on this and other methods of 
dealing with hijacked machines from the originating network's point of 
view.

Yakov


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



From exim@www1.ietf.org  Mon Mar  1 18:52:30 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13759
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 18:52:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxCd-0002PN-OK
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 18:52:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i21Nq3CX009251
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 18:52:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxCd-0002P8-KC
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 18:52:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13750
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 18:51:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxCa-00036u-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:52:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxxBd-00031q-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:51:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxAp-0002xA-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 18:50:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxAf-00028r-U0; Mon, 01 Mar 2004 18:50:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axx9j-00025t-4r
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 18:49:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13728
	for <asrg@ietf.org>; Mon, 1 Mar 2004 18:48:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axx9g-0002sQ-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:49:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axx8r-0002ne-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:48:10 -0500
Received: from mail.chariot.net.au ([203.87.95.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axx8C-0002hs-00
	for asrg@ietf.org; Mon, 01 Mar 2004 18:47:28 -0500
Received: from localhost (avs1.sa.chariot.net.au [203.87.94.5])
	by mail.chariot.net.au (Postfix) with ESMTP id 2D7A36B6A9
	for <asrg@ietf.org>; Tue,  2 Mar 2004 10:17:21 +1030 (CST)
Received: from mail.chariot.net.au ([203.87.95.38])
 by localhost (avs1.sa.chariot.net.au [203.87.94.5]) (amavisd-new, port 10024)
 with LMTP id 32331-03-7 for <asrg@ietf.org>;
 Tue,  2 Mar 2004 10:17:20 +1030 (CST)
Received: from rebel (ppp-086.cust203-87-123.ghr.chariot.net.au [203.87.123.86])
	by mail.chariot.net.au (Postfix) with SMTP id 4D8C7675F0
	for <asrg@ietf.org>; Tue,  2 Mar 2004 10:15:43 +1030 (CST)
From: "Chris" <asrg@rebel.com.au>
To: "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Message-ID: <GPEMJLCHICHEGPOKJHHDKELEGPAA.asrg@rebel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A18FC@mou1wnexm05.vcorp.ad.vrsn.com>
X-Virus-Scanned: by amavisd-new at chariot.net.au
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/mail-archive/working-groups/asrg/>
Date: Tue, 2 Mar 2004 10:14:43 +1030
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

to quote my original response

"It is my firm belief that no single system will do the job, a toolkit is
required each tool tackling a different type of spam source."


Regards
Chris



> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org]On Behalf Of
> Hallam-Baker, Phillip
> Sent: Tuesday, 2 March 2004 9:53 AM
> To: 'Larry Seltzer'; sami.suomalainen@bigpond.com; 'ASRG'
> Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
> 
> 
> 
> > Nothing in SPF, CID or DK would stop a legitimate marketer 
> > from sending e-mail that
> > authenticates properly. Actually, nothing stops them from 
> > sending it unsolicited either,
> > but since the addresses would be verifiable users would be 
> > able to block them
> > effectively. If they didn't block you, they would get your mail.
> 
> I agree with the response to the specific issue, but I think
> it misses the big picture here. 
> 
> 
> I think the problem here is that some people don't understand 
> engineering. The way you solve a big problem like spam is
> you break it down into a collection of smaller problems and then 
> address those in turn.
> 
> Saying that SPF or Caller ID does not bring peace on earth
> does not mean they have no value. They are not an end in
> themselves, they are a starting point. Of course this type 
> of talk is being used in an attempt to talk the proposals out,
> a strategy that assumes a veto power that does not exist.
> 
> 
> Everyone understands that there has to be more than just
> authentication to 'solve' the spam problem. But authentication
> is the first step in any of the comprehensive strategies.
> 
> Once you know who sent the message you have a different
> response depending on the type of spam it is. 
> 
> 	Impersonation spam (aka joe job) - discard
> 
> 	Intentional spam - affects the reputation of the sender,
> 			may lead to civil, criminal sanctions
> 
> 	Hijacked Machine spam - We locate the machine and shut it 
> 			down.
> 
> The different responses require different strategies but they
> are all soluble. It is simply a matter of case analysis. 
> 
> At a recent anti-phishing meeting we discussed a mechanism to
> address the hijacked machine issue. Lets just define a simple
> way that you can contact me when you think someone is using a 
> machine I am responsible for in a malicious fashion.
> 
> _contact.example.com 	TXT 
> 			"email:abuse.example.com tel:+44012440102031"
> _contact.example.com	SRV
> 			"http://contact.example.com/"
> _contact.1.0.0.10		TXT
> 			"include:example.com"
> 
> So when someone launches a DDoS against my machines with source 
> address 10.0.0.1 I know where to go, I have an email address,
> telephone number, more usefully though I have the address of
> a web service I can connect to and send a report of the incident.
> 
> If I am operating an ISP I am not going to turn off users 
> automatically in response to unauthenticated requests from outside,
> but I could easily automate much of the response loop:
> 
> 	* Report of spam or virus attack from IP address
> 		AND IP address is making lots of connections to port 25
> 		ACTION - warn operator, possibly shut down site.
> 
> 	* Report of DDoS from source address
> 		AND IP address is engaged in objectionable activity
> 		ACTION object
> 
> Spoofed IP addresses could be addressed by similar means but here 
> I need to connect via the contact addresses of my ISPs :-
> 
> 	Report of DDoS against IP address 10.9.9.9 
> 		AND abnormal activity connecting to 10.9.9.9
> 			Respond
> 
> Response consists of tracking the attack back to the source, same
> way a human operator would. For each router you look to see which
> incomming ports have abnormal levels of packets routed to the 
> targetted address, if so you kick the contact report back down
> to the next NOC in the chain. If the source is in your own network
> you disable the machines behaving unacceptably (like SYN flooding).
> 
> 
> 
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg

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



From exim@www1.ietf.org  Mon Mar  1 19:21:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14838
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 19:21:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axxer-0004Lp-Dn
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 19:21:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i220LDrv016719
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 19:21:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axxer-0004La-6l
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 19:21:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14825
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 19:21:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axxep-0006EO-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:21:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axxdm-00065g-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:20:07 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axxcx-0005xX-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:19:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axxcj-00042D-BS; Mon, 01 Mar 2004 19:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxMX-0002zY-7q
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 19:02:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13954
	for <asrg@ietf.org>; Mon, 1 Mar 2004 19:02:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxMU-00043A-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:02:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxxLY-0003w6-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:01:16 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxKq-0003om-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:00:32 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AxxKl-00029h-00; Mon, 01 Mar 2004 19:00:27 -0500
Received: from [68.24.248.250] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AxxKi-0007M0-00; Mon, 01 Mar 2004 19:00:27 -0500
Message-ID: <4043CE8E.5020809@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: "'Larry Seltzer'" <larry@larryseltzer.com>, sami.suomalainen@bigpond.com,
        "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
References: <C6DDA43B91BFDA49AA2F1E473732113E0A18FC@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A18FC@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 19:00:14 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hallam-Baker, Phillip wrote:
> 
> Everyone understands that there has to be more than just
> authentication to 'solve' the spam problem. But authentication
> is the first step in any of the comprehensive strategies.
> 

I want to clarify - IMHO a more correct statement is that 
"authentication is the first step in any of the comprehensive strategies 
BY THE RECEIVER". There is a host of other technical strategies that can 
be adopted by the sender's network to detect spam. There are also other 
means to make the spam problem decrease which are technical in nature 
but are meant for non-technical purposes. Example of these are standards 
or measures for cooperation among ISPs, BCPs, something like the 
NO-SOLICIT extension combined with laws, etc. We must remember to look 
at the entire picture, not just the receiver's end.

> At a recent anti-phishing meeting we discussed a mechanism to
> address the hijacked machine issue. Lets just define a simple
> way that you can contact me when you think someone is using a 
> machine I am responsible for in a malicious fashion.
> 
> _contact.example.com 	TXT 
> 			"email:abuse.example.com tel:+44012440102031"
> _contact.example.com	SRV
> 			"http://contact.example.com/"
> _contact.1.0.0.10		TXT
> 			"include:example.com"
> 

I believe that RFC 1183 defines an RP RR for a similar purpose. But in 
most cases it is already known who the owner of the network is either 
via abuse.net or WHOIS information for the IP addresses. When spam is 
reported, most of the time it is reported to the right responsible party.

Nevertheless, standards for abuse reporting including possible DNS 
implications would be very useful assuming that the ISPs will take 
action on it and actually do something. That has not always been the case.

(and we do have a subgroup on abuse standards, which is looking for 
volunteers)

Yakov

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



From exim@www1.ietf.org  Mon Mar  1 19:28:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15264
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 19:28:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxlU-0005Yf-TB
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 19:28:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i220S4mA021322
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 19:28:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxlU-0005Xb-CM
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 19:28:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15248
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 19:28:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxlS-000747-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:28:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxxkW-0006y4-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:27:05 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axxji-0006rL-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:26:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxjV-0005Fk-N2; Mon, 01 Mar 2004 19:26:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axxgl-0004VX-0K
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 19:23:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14997
	for <asrg@ietf.org>; Mon, 1 Mar 2004 19:23:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axxgj-0006VL-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:23:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axxg4-0006Pi-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:22:28 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxfM-0006Hb-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:21:44 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AxxfI-0004GC-00; Mon, 01 Mar 2004 19:21:40 -0500
Received: from [68.24.248.250] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AxxfH-0008IQ-00; Mon, 01 Mar 2004 19:21:40 -0500
Message-ID: <4043D389.7040104@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: "'gep2@terabites.com'" <gep2@terabites.com>, dave@farber.net,
        asrg@ietf.org, wishlist@microsoft.com
References: <C6DDA43B91BFDA49AA2F1E473732113E0A18FA@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A18FA@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 3b. SMTP Session Verification - LMAP
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 19:21:29 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hallam-Baker, Phillip wrote:
>>Funny thing that each of these folks are ISPs... and each is 
>>trying to make sure you use THEM for everything you do. :-((  
> 
> 
> It is not a surprise to me that ISPs want to reduce spam. The
> surprise to me is that the IETF appears unable to treat the
> issue with more than casual interest.
> 

As for the IETF, the BoF will take place this Thursday. If anyone have 
specific objections, pros and cons regarding LMAP proposals, then the 
BoF mailing list would be the appropriate place to address them, since 
the BoF is where the IETF will actually take action NOT the ASRG. The 
mailing list is  at:

http://www.imc.org/ietf-mxcomp/

As a reminder there will be a chat channel, and multicast video and 
audio feeds.

> The problem with approches of this sort is that they are based
> on the false assumption that the Internet still belongs to
> a small inner circle of geeks who have no responsibility at
> all to the wider public.
> 

The problem is not the end users or the cabal of inner circle of geeks, 
but rather the developers of the MUAs. There are multiple measures such 
as disabling JavaScript, displaying the "Return Path" headers and 
others, that can be done to let end users know. The commercial companies 
that make the MUAs have not been willing to make these changes so far.

> 
>>And one could certainly imagine a system 
> 
> Imagined systems will form no part of the solution, only running
> code will.

This is a research group, and for most of the time research does not 
start with working code. While both are important, we have free license 
to discuss possible systems as long as working code will come out of them.

Yakov

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



From exim@www1.ietf.org  Mon Mar  1 19:33:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15672
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 19:33:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxqN-00064o-I1
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 19:33:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i220X7sh023352
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 19:33:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxqN-00064X-DU
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 19:33:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15600
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 19:33:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxqL-0007eQ-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:33:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxxpQ-0007Xo-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:32:09 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axxoc-0007RI-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:31:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxoN-0005oL-TV; Mon, 01 Mar 2004 19:31:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axxjj-0005N6-CG
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 19:26:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15156
	for <asrg@ietf.org>; Mon, 1 Mar 2004 19:26:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axxjh-0006rA-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:26:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axxio-0006kJ-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:25:18 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxiF-0006d3-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:24:43 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1Axxi7-0004U3-00; Mon, 01 Mar 2004 19:24:35 -0500
Received: from [68.24.248.250] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1Axxi6-0008QR-00; Mon, 01 Mar 2004 19:24:35 -0500
Message-ID: <4043D436.8070801@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: "'Larry Seltzer'" <larry@larryseltzer.com>, sami.suomalainen@bigpond.com,
        "'ASRG'" <asrg@ietf.org>
Subject: Re: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
References: <C6DDA43B91BFDA49AA2F1E473732113E0A1900@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A1900@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 19:24:22 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hallam-Baker, Phillip wrote:
> Thanks for the pointer, it may not be exactly what I am after, I 
> will look further.
> 
> 
>>I believe that RFC 1183 defines an RP RR for a similar 
>>purpose. But in 
>>most cases it is already known who the owner of the network is either 
>>via abuse.net or WHOIS information for the IP addresses. When spam is 
>>reported, most of the time it is reported to the right 
>>responsible party.
> 
> 
> The issue came up in the context of phishing at a meeting attending
> by leading banks. It can take a substantial length of time to get
> a site taken down even with the full assistance of the FBI etc.
> 
> Some of these issues are jurisdictional, but others are pure
> communication issues.
> 

The communication issues is one area where common standards would help 
and this is why we are looking into such standards for abuse reporting 
including multiple ways to communicate and lookup such data.

> 
>>Nevertheless, standards for abuse reporting including possible DNS 
>>implications would be very useful assuming that the ISPs will take 
>>action on it and actually do something. That has not always 
>>been the case.
> 
> I think what has to happen here is to give people a real value 
> prpoposition. people are now very concerned about the problem 
> of having hijacked machines on their networks. I don't think those
> were at all common back in 1990.

I agree. The question is what kind of value proposition can we give 
them? Simply blocking them might be a crude weapon.

Yakov

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



From exim@www1.ietf.org  Mon Mar  1 19:38:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16044
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 19:38:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxvE-0007F1-ED
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 19:38:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i220c8DY027825
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 19:38:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxvD-0007Ed-UP
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 19:38:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15903
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 19:38:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxvC-0000Td-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:38:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxxuC-0000JS-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:37:05 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxtE-0000Ad-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:36:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxtC-0006Jw-K0; Mon, 01 Mar 2004 19:36:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxsF-0006GN-SS
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 19:35:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15774
	for <asrg@ietf.org>; Mon, 1 Mar 2004 19:35:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxsE-00003S-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:35:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxxrH-0007ku-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:34:03 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxqM-0007eR-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:33:06 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i220X4sv029297;
        Mon, 1 Mar 2004 16:33:04 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <F2HV1NFA>; Mon, 1 Mar 2004 16:33:04 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A1902@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Yakov Shafranovich'" <research@solidmatrix.com>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'Larry Seltzer'" <larry@larryseltzer.com>, sami.suomalainen@bigpond.com,
        "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 16:33:01 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

> The communication issues is one area where common standards 
> would help 
> and this is why we are looking into such standards for abuse 
> reporting 
> including multiple ways to communicate and lookup such data.

The reporting issues need not be spam related

DDoS is a big enough issue here to justify a notification mechanism.
If there is a hijacked machine on the net then the ISP resonsible needs
to know ASAP.

> I agree. The question is what kind of value proposition can we give 
> them? Simply blocking them might be a crude weapon.

	"A machine on your network may be causing grief in my network,
		please fix"
	"You are being impersonated by spam from this address"

Value to notifier	
	* May cause attack to stop
	* Can hold source accountable

Value to receiver
	* Public interest
	* Avoid more intrusive contact attempts
	* Reduce value of capturing machines on the receiver's network
	* Deter attacks
	* Shut down attacks faster
	* Reduce liabilities

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



From exim@www1.ietf.org  Mon Mar  1 19:49:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16882
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 19:49:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axy5u-0000sV-Ma
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 19:49:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i220nAdb003376
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 19:49:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axy5u-0000sN-Ee
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 19:49:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16844
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 19:49:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axy5s-0001yR-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:49:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axy4z-0001rQ-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:48:14 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axy49-0001lX-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:47:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axy3r-000089-3A; Mon, 01 Mar 2004 19:47:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axxoa-0005up-VH
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 19:31:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15472
	for <asrg@ietf.org>; Mon, 1 Mar 2004 19:31:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxoZ-0007Qh-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:31:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axxne-0007Jp-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:30:18 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axxn9-0007CQ-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:29:47 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1Axxn7-0000ik-00; Mon, 01 Mar 2004 19:29:45 -0500
Received: from [68.24.248.250] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1Axxn6-0000Fx-00; Mon, 01 Mar 2004 19:29:45 -0500
Message-ID: <4043D567.7050901@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Yakov Shafranovich <research@solidmatrix.com>
CC: "Hallam-Baker, Phillip" <pbaker@verisign.com>,
        "'gep2@terabites.com'" <gep2@terabites.com>, dave@farber.net,
        asrg@ietf.org
Subject: Re: [Asrg] 3b. SMTP Session Verification - LMAP
References: <C6DDA43B91BFDA49AA2F1E473732113E0A18FA@mou1wnexm05.vcorp.ad.vrsn.com> <4043D389.7040104@solidmatrix.com>
In-Reply-To: <4043D389.7040104@solidmatrix.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 19:29:27 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yakov Shafranovich wrote:
> Hallam-Baker, Phillip wrote:
...
>> The problem with approches of this sort is that they are based
>> on the false assumption that the Internet still belongs to
>> a small inner circle of geeks who have no responsibility at
>> all to the wider public.
>>
> 
> The problem is not the end users or the cabal of inner circle of geeks, 
> but rather the developers of the MUAs. There are multiple measures such 
> as disabling JavaScript, displaying the "Return Path" headers and 
> others, that can be done to let end users know. The commercial companies 
> that make the MUAs have not been willing to make these changes so far.
> 

Let me clarify - the problem is that the MUA developers do not have 
enough incentive to implement any of these changes. There is also a 
problem of warped thinking - thinking that regular end users can do 
whatever geeks can do, and therefore such measures that geeks can use 
should be implemented. However, there are many measures which are not 
"geeky" and are still useful, yet not enough incentive exists for MUA 
developers to make them.

Yakov


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



From exim@www1.ietf.org  Mon Mar  1 19:50:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17016
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 19:50:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axy6m-0000xZ-Iv
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 19:50:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i220o4XH003683
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 19:50:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axy6m-0000xJ-CC
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 19:50:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16924
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 19:50:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axy6k-000264-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:50:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axy5l-0001xJ-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:49:02 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axy4o-0001qI-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:48:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axy4o-0000bx-Py; Mon, 01 Mar 2004 19:48:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axy35-00005p-S7
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 19:46:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16647
	for <asrg@ietf.org>; Mon, 1 Mar 2004 19:46:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axy34-0001bH-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:46:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axy24-0001TJ-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:45:12 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axy1H-0001M5-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:44:23 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1Axy1C-0004ek-00; Mon, 01 Mar 2004 19:44:18 -0500
Received: from [68.24.248.250] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1Axy1A-0000pf-00; Mon, 01 Mar 2004 19:44:18 -0500
Message-ID: <4043D8D4.4070203@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: "'Larry Seltzer'" <larry@larryseltzer.com>, sami.suomalainen@bigpond.com,
        "'ASRG'" <asrg@ietf.org>
Subject: Re: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
References: <C6DDA43B91BFDA49AA2F1E473732113E0A1902@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A1902@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 19:44:04 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hallam-Baker, Phillip wrote:
>>The communication issues is one area where common standards 
>>would help and this is why we are looking into such standards for abuse 
>>reporting including multiple ways to communicate and lookup such data.
> 
> The reporting issues need not be spam related
> 
> DDoS is a big enough issue here to justify a notification mechanism.
> If there is a hijacked machine on the net then the ISP resonsible needs
> to know ASAP.

I agree. We gave a subgroup setup for this 
(http://asrg.sp.am/subgroups/abuse_reports.shtml) and soliciting 
volunteers. However, we haven't gotten much response so far, which makes 
me think that people might not as interested in this kind of stuff as we 
think they would be.

Yakov

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



From exim@www1.ietf.org  Mon Mar  1 20:34:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20231
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 20:34:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxynX-0007VW-M5
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 20:34:20 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i221YFBV028852
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 20:34:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxynX-0007VH-Fv
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 20:34:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20196
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 20:34:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxynV-0000Z8-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 20:34:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxymY-0000Rt-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 20:33:14 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axylf-0000KK-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 20:32:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxylO-0007B6-IB; Mon, 01 Mar 2004 20:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axyks-00077c-2k
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 20:31:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20025
	for <asrg@ietf.org>; Mon, 1 Mar 2004 20:31:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axykp-0000CF-00
	for asrg@ietf.org; Mon, 01 Mar 2004 20:31:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axyjq-000023-00
	for asrg@ietf.org; Mon, 01 Mar 2004 20:30:27 -0500
Received: from [131.107.8.3] (helo=exchange.microsoft.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxyjI-0007gJ-00
	for asrg@ietf.org; Mon, 01 Mar 2004 20:29:52 -0500
Received: from DF-VRS-01.redmond.corp.microsoft.com ([157.54.4.14]) by exchange.microsoft.com with Microsoft SMTPSVC(6.0.3790.1069);
	 Mon, 1 Mar 2004 17:29:22 -0800
Received: from 10.197.0.83 by DF-VRS-01.redmond.corp.microsoft.com (InterScan E-Mail VirusWall NT); Mon, 01 Mar 2004 17:29:22 -0800
Received: from DF-CHOPPER.platinum.corp.microsoft.com ([10.197.0.81]) by DF-BEG.platinum.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 1 Mar 2004 17:29:22 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5.7195.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Asrg] [IP] CNN covers Meng's SPF
Message-ID: <27C4E14288DB344FBA10705D57A9BB0401831FEB@DF-CHOPPER.platinum.corp.microsoft.com>
Thread-Topic: [Asrg] [IP] CNN covers Meng's SPF
Thread-Index: AcP/vv74b3Q8Y8iVQiKaBgNKmrgQJwANpFQw
X-Priority: 5
Priority: Non-Urgent
Importance: low
From: "Bob Atkinson" <bobatk@exchange.microsoft.com>
To: <gep2@terabites.com>, <dave@farber.net>
Cc: <asrg@ietf.org>
X-OriginalArrivalTime: 02 Mar 2004 01:29:22.0295 (UTC) FILETIME=[CA520870:01C3FFF5]
Content-Transfer-Encoding: quoted-printable
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 17:29:20 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On Behalf Of
> gep2@terabites.com
> To: dave@farber.net

> > NEW YORK (AP) -- With a simple adjustment in your e-mail software,
you
> can
> pretend to be anyone. You can send messages marked as coming from
> BillGates@microsoft.com.
>=20
> Surprise surprise!!!  This should have been common knowledge for a
long
> time.

Actually, the correct address to forge in this case is
billg@microsoft.com, not BillGates@microsoft.com.=20

	:-)
	Bob Atkinson
	Microsoft Exchange Server


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



From exim@www1.ietf.org  Mon Mar  1 20:46:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21142
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 20:46:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axyz3-0001pg-97
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 20:46:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i221k9Iv007037
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 20:46:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axyz3-0001pQ-28
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 20:46:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21119
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 20:46:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axyz0-00025N-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 20:46:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axyy3-0001yB-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 20:45:08 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxyxC-0001pu-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 20:44:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axywz-0001VZ-5O; Mon, 01 Mar 2004 20:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxywN-0001Ug-Dk
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 20:43:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20840
	for <asrg@ietf.org>; Mon, 1 Mar 2004 20:43:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxywL-0001h5-00
	for asrg@ietf.org; Mon, 01 Mar 2004 20:43:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxyvO-0001Yc-00
	for asrg@ietf.org; Mon, 01 Mar 2004 20:42:23 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxyuZ-0001Qe-00
	for asrg@ietf.org; Mon, 01 Mar 2004 20:41:32 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i221fOG4019678;
        Mon, 1 Mar 2004 17:41:24 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <F2HV1XY1>; Mon, 1 Mar 2004 17:41:22 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A1904@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Yakov Shafranovich'" <research@solidmatrix.com>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'Larry Seltzer'" <larry@larryseltzer.com>, sami.suomalainen@bigpond.com,
        "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 17:41:21 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

> I agree. We gave a subgroup setup for this 
> (http://asrg.sp.am/subgroups/abuse_reports.shtml) and soliciting 
> volunteers. However, we haven't gotten much response so far, 
> which makes 
> me think that people might not as interested in this kind of 
> stuff as we 
> think they would be.

The people I am talking to are very interested in the concept.
But they may not be interested in persuing the idea in this forum.

	Phill

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



From exim@www1.ietf.org  Mon Mar  1 21:12:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22947
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 21:12:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzOH-0005Ky-Ma
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 21:12:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i222CDje020510
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 21:12:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzOH-0005Kj-G1
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 21:12:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22919
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 21:12:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzOE-0005hF-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:12:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzNC-0005Ym-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:11:07 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzMG-0005QY-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:10:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzM9-00050t-K2; Mon, 01 Mar 2004 21:10:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzLX-0004w9-Q7
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 21:09:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22781
	for <asrg@ietf.org>; Mon, 1 Mar 2004 21:09:19 -0500 (EST)
From: nazgul@somewhere.com
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzLV-0005Jv-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:09:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzKd-0005CW-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:08:28 -0500
Received: from bgp983818bgs.stclar01.mi.comcast.net ([68.43.3.79] helo=7p2h10b)
	by ietf-mx with smtp (Exim 4.12)
	id 1AxzKA-00054g-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:07:58 -0500
To: asrg@ietf.org
Message-ID: <sbjwodbwvancoolioym@somewhere.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------wvutubyncjtualeuvntd"
Subject: [Asrg] Hello my friend
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 21:35:27 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=1.6 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60

----------wvutubyncjtualeuvntd
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_BAGLE.E in file jxkvqqhl.exe (in edabaced.zip)
The file is deleted.

---------------------------------------------------------

----------wvutubyncjtualeuvntd
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

Empty

----------wvutubyncjtualeuvntd
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

edabaced.zip is removed from here because it contains a virus.

---------------------------------------------------------
----------wvutubyncjtualeuvntd--


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



From exim@www1.ietf.org  Mon Mar  1 21:17:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23288
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 21:17:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzT2-0005sy-Tf
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 21:17:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i222H81Q022618
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 21:17:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzT2-0005sj-OB
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 21:17:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23227
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 21:17:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzT0-0006LI-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:17:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzRz-0006Cl-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:16:04 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzR0-00065C-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:15:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzQz-0005US-Rl; Mon, 01 Mar 2004 21:15:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzQE-0005SL-50
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 21:14:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23098
	for <asrg@ietf.org>; Mon, 1 Mar 2004 21:14:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzQB-0005yc-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:14:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzPK-0005qk-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:13:19 -0500
Received: from mail3.panix.com ([166.84.1.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzOU-0005i7-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:12:26 -0500
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail3.panix.com (Postfix) with ESMTP id 3931099322
	for <asrg@ietf.org>; Mon,  1 Mar 2004 21:12:20 -0500 (EST)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i222CK817559;
	Mon, 1 Mar 2004 21:12:20 -0500 (EST)
Message-Id: <200403020212.i222CK817559@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: 
	<C6DDA43B91BFDA49AA2F1E473732113E0A1902@mou1wnexm05.vcorp.ad.vrsn.com>
	(pbaker@verisign.com)
Subject: Re: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
References: <C6DDA43B91BFDA49AA2F1E473732113E0A1902@mou1wnexm05.vcorp.ad.vrsn.com>
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 21:12:20 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

"Hallam-Baker, Phillip" <pbaker@verisign.com> wrote:

>	"You are being impersonated by spam from this address"

Thanks but no thanks, until you have a way to limit the number of
notifications I get to the log10 of the number of spams sent out.

Feel free to tell the network-owner of the spamming machine about it,
that's who can take action to stop the spam (and the notifications).

Seth

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



From exim@www1.ietf.org  Mon Mar  1 21:24:48 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23745
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 21:24:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axza2-0006s5-4n
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 21:24:22 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i222OMqV026407
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 21:24:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axza1-0006rq-Vr
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 21:24:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23662
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 21:24:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzZz-0007Lg-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:24:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzZ3-0007B5-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:23:22 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzY1-00070Q-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:22:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzXm-0006Py-86; Mon, 01 Mar 2004 21:22:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzX2-0006Nl-7w
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 21:21:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23461
	for <asrg@ietf.org>; Mon, 1 Mar 2004 21:21:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzWz-0006qB-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:21:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzVu-0006hg-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:20:07 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzUx-0006aa-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:19:07 -0500
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (mailer3.verisign.com [65.205.251.55])
        by peacock.verisign.com (8.12.11/) with ESMTP id i222J7sS012257;
        Mon, 1 Mar 2004 18:19:07 -0800 (PST)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <F2HVW4G7>; Mon, 1 Mar 2004 18:19:07 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A1906@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Seth Breidbart'" <sethb@panix.com>, asrg@ietf.org
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 18:19:00 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60


> "Hallam-Baker, Phillip" <pbaker@verisign.com> wrote:
> 
> >	"You are being impersonated by spam from this address"
> 
> Thanks but no thanks, until you have a way to limit the number of
> notifications I get to the log10 of the number of spams sent out.
> 
> Feel free to tell the network-owner of the spamming machine about it,
> that's who can take action to stop the spam (and the notifications).

That was the idea :-)

And thats where they can send the anti-virus company spam as well
(that or /dev/null)

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



From exim@www1.ietf.org  Mon Mar  1 21:48:04 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24946
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 21:48:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzwW-0000SP-QP
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 21:47:36 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i222lafM001751
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 21:47:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzwW-0000SA-J8
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 21:47:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24783
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 21:47:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzwT-0002TP-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:47:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzvM-0002GX-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:46:25 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axzut-00028H-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:45:55 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AxznN-0007bk-9G
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:38:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxznF-0008H9-PX; Mon, 01 Mar 2004 21:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzlQ-0007xk-3q
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 21:36:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24540
	for <asrg@ietf.org>; Mon, 1 Mar 2004 21:36:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzlN-0001JZ-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:36:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxzkN-0001CQ-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:35:04 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxzjN-00011X-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:34:01 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AxzjO-00017x-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:34:02 -0500
Received: from [68.24.248.250] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AxzjN-0004yv-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:34:02 -0500
Message-ID: <4043F28B.3070300@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 0. General - Soliciting Volunteers for Subgroups
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 21:33:47 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

We are still soliciting volunteers for ASRG subgroups. A list of current 
subgroups can be found on our website 
(http://asrg.sp.am/about/subgroups.shtml):

* Abuse Reporting Standards - researches standard formats and protocols 
for reporting email and network abuse
* Analysis & Characterization (A&C) - applies empirical and quantitative 
methods to problems and issues surrounding spam.
* Best Current Practices (BCP) - researches and documents best practices 
for spam management
* Filtering Standards (FILTERING) - researches filtering standards for 
dynamic updating and interaction with MTAs
* Inventory of Problems - research problems with the current email 
architechture that facilitate spam
* Message Verification (MSG-VERIFY) - researches solutions dealing with 
verification and authetication in the email messages and headers
* SMTP Session Verification (SMTP-VERIFY) - researches solutions dealing 
with authetication and verification of the SMTP session

Interested parties should contact the ASRG chairs off-list.

Yakov

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



From exim@www1.ietf.org  Mon Mar  1 21:48:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25073
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 21:48:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axzwo-0000VV-0s
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 21:48:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i222lrpn001943
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 21:47:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axzwn-0000VG-TH
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 21:47:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24869
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 21:47:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axzwl-0002W7-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:47:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axzvd-0002JV-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:46:42 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axzux-00028H-01
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:45:59 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Axzhe-0007Uc-Ff
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:32:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxzhS-0007I9-3E; Mon, 01 Mar 2004 21:32:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axzgo-0007FJ-JA
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 21:31:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24337
	for <asrg@ietf.org>; Mon, 1 Mar 2004 21:31:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axzgl-0000lq-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:31:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axzfr-0000cE-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:30:24 -0500
Received: from mail.chariot.net.au ([203.87.95.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axzex-0000Sq-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:29:27 -0500
Received: from localhost (avs1.sa.chariot.net.au [203.87.94.5])
	by mail.chariot.net.au (Postfix) with ESMTP id 0B42C6C44D
	for <asrg@ietf.org>; Tue,  2 Mar 2004 12:59:22 +1030 (CST)
Received: from mail.chariot.net.au ([203.87.95.38])
 by localhost (avs1.sa.chariot.net.au [203.87.94.5]) (amavisd-new, port 10024)
 with LMTP id 16532-02-8 for <asrg@ietf.org>;
 Tue,  2 Mar 2004 12:59:22 +1030 (CST)
Received: from rebel (ppp-086.cust203-87-123.ghr.chariot.net.au [203.87.123.86])
	by mail.chariot.net.au (Postfix) with SMTP id AB0D86C4DD
	for <asrg@ietf.org>; Tue,  2 Mar 2004 12:55:03 +1030 (CST)
From: "Chris" <asrg@rebel.com.au>
To: <asrg@ietf.org>
Subject: FW: [Asrg] Hello my friend
Message-ID: <GPEMJLCHICHEGPOKJHHDKELHGPAA.asrg@rebel.com.au>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="----=_NextPart_000_0066_01C40055.715A9B00"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-Virus-Scanned: by amavisd-new at chariot.net.au
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/mail-archive/working-groups/asrg/>
Date: Tue, 2 Mar 2004 12:54:04 +1030
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

This is a multi-part message in MIME format.

------=_NextPart_000_0066_01C40055.715A9B00
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


Take a close look at the subject line....

Regards
Chris



-----Original Message-----
From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org]On Behalf Of
nazgul@somewhere.com
Sent: Tuesday, 2 March 2004 1:05 PM
To: asrg@ietf.org
Subject: [Asrg] Hello my friend


------------------  Virus Warning Message (on ietf-mx)

Found virus WORM_BAGLE.E in file jxkvqqhl.exe (in edabaced.zip)
The file is deleted.

---------------------------------------------------------

------=_NextPart_000_0066_01C40055.715A9B00
Content-Type: text/plain;
	name="ATT00097.txt"
Content-Disposition: attachment;
	filename="ATT00097.txt"
Content-Transfer-Encoding: 7bit

Empty

------=_NextPart_000_0066_01C40055.715A9B00
Content-Type: text/plain;
	name="ATT00100.txt"
Content-Disposition: attachment;
	filename="ATT00100.txt"
Content-Transfer-Encoding: 7bit


------------------  Virus Warning Message (on ietf-mx)

edabaced.zip is removed from here because it contains a virus.

---------------------------------------------------------
------=_NextPart_000_0066_01C40055.715A9B00--


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



From exim@www1.ietf.org  Mon Mar  1 21:54:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25358
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 21:54:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay02u-0000zz-Pl
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 21:54:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i222sCIh003833
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 21:54:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay02u-0000zk-MA
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 21:54:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25341
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 21:54:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay02r-0003Ma-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:54:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay020-0003Gb-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:53:17 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay015-0003A6-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 21:52:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay00n-0000mU-9T; Mon, 01 Mar 2004 21:52:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay005-0000fG-5Q
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 21:51:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA25221
	for <asrg@ietf.org>; Mon, 1 Mar 2004 21:51:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay002-00032G-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:51:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axzz8-0002wD-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:50:19 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axzyp-0002pW-00
	for asrg@ietf.org; Mon, 01 Mar 2004 21:49:59 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id 94EB3170C1
	for <asrg@ietf.org>; Mon,  1 Mar 2004 21:53:05 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID 
In-Reply-To: Your message of "Mon, 01 Mar 2004 17:52:15 EST."
             <p0600204dbc69136d1759@[192.168.254.12]> 
Message-Id: <20040302025305.94EB3170C1@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 21:53:05 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Bill Cole <grsa@billmail.scconsult.com> wrote:
> .. Swen does indeed get 
> through machines that require SMTP authentication.

  Yup.  But look at it from this point of view:

  a) You now have a small number of MTAs to block, versus a large
     number of MUAs (if the virus had it's own SMTP engine)
  b) the MTA owners who care fix the problem, and it stops.
  c) The MTA owners who don't care are either blocked, or spend
     thousands of dollars upgrading their system to handle the load.
     So they're being punished for being idiots.  Nice.
  d) If they don't spend the money to upgrade their MTAs, then *their*
     MTA goes down when a new virus comes out, and *mine* doesn't.


  Everybody wins.

  As for the issue that spammers can register more domains, and
publish LMAP information:

  a) it costs them money
  b) the domains have to be relatively long-lived to be useful, and
     long-lived domains can be discovered, and blocked
  c) If they register a huge number of domains, it's incentive to
     block *all* domains which are hosted on a particular DNS server
     (IP or network).

  It's also possible to use rDNS to grab LMAP-style information for an
IP.  One useful piece of information is a list of domains (or DNS
servers) whic are allowed to publish LMAP information for that IP.  If
LAMP for a domain in the SMTP envelope says "This IP is OK to send
messages!", and the rDNS owner says "I don't know who the heck that
domain is", the recipient can treat the message with great suspicion.

  That concept negates a lot of the objections to LMAP.

  Of course, it requires cooperating parties.  But if no one agrees to
cooperate to fight spam, then we'll never address the problem.

  Alan DeKok.

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



From exim@www1.ietf.org  Mon Mar  1 23:20:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28913
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 23:20:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1NV-0005oO-Oq
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 23:19:33 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i224JXmF022337
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 23:19:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1NV-0005oC-9n
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 23:19:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28805
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 23:19:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1NT-0005XA-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 23:19:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay1MU-0005Kh-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 23:18:30 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1Ly-0005CL-01
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 23:17:58 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Ay1HV-0000J9-Pa
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 23:13:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1HA-00058v-Kk; Mon, 01 Mar 2004 23:13:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1Gp-00058X-3r
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 23:12:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA28582
	for <asrg@ietf.org>; Mon, 1 Mar 2004 23:12:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1Gm-0004gn-00
	for asrg@ietf.org; Mon, 01 Mar 2004 23:12:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay1G0-0004ZC-00
	for asrg@ietf.org; Mon, 01 Mar 2004 23:11:50 -0500
Received: from mail3.asianet.co.th ([203.144.222.231] helo=mail.asianet.co.th)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1EB-0004BO-00
	for asrg@ietf.org; Mon, 01 Mar 2004 23:09:55 -0500
Received: from virscan2.asianet.co.th (HELO mail.asianet.co.th) ([203.144.222.198])
          (envelope-sender <jrace@attglobal.net>)
          by mail3.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <asrg@ietf.org>; 2 Mar 2004 11:09:16 +0700
Received: from ppp-203.144.203.164.revip.asianet.co.th (HELO localhost) ([203.144.203.164])
          (envelope-sender <jrace@attglobal.net>)
          by mx1.asianet.co.th (qmail-ldap-1.03) with SMTP
          for <jrace@attglobal.net>; 2 Mar 2004 10:56:18 +0700
From: "Dr. Jeffrey Race" <jrace@attglobal.net>
To: "Jeffrey Race" <jrace@attglobal.net>
Cc: "ASRG" <asrg@ietf.org>
Reply-To: "Dr. Jeffrey Race" <jrace@attglobal.net>
Priority: Normal
X-Mailer: PMMail 1.96a For OS/2
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] 2a .BCP -  Handling Trojaned machines
Message-Id: <E1Ay1EB-0004BO-00@ietf-mx>
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/mail-archive/working-groups/asrg/>
Date: Tue, 02 Mar 2004 10:56:15 +0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.9 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Mon, 01 Mar 2004 18:11:12 -0500, Yakov Shafranovich wrote:
> In regards to this specific method, we are currently 
>looking for volunteers to write a BCP on this and other methods of 
>dealing with hijacked machines from the originating network's point of 
>view

It's done already :)

  <http://www.camblab.com/misc/univ_std.txt> 
   
    based upon

  <http://www.camblab.com/nugget/spam_03.pdf>

Jeffrey Race


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



From exim@www1.ietf.org  Mon Mar  1 23:54:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA01092
	for <asrg-archive@odin.ietf.org>; Mon, 1 Mar 2004 23:54:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1v4-00038p-0T
	for asrg-archive@odin.ietf.org; Mon, 01 Mar 2004 23:54:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i224sDp3012069
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 23:54:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1v3-00038a-SI
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 23:54:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00979
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 23:54:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1v1-0002Cc-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 23:54:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay1u0-00022g-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 23:53:09 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1t2-0001ur-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 23:52:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1su-0002wV-TF; Mon, 01 Mar 2004 23:52:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay1qO-0002ny-1T
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 23:49:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00715
	for <asrg@ietf.org>; Mon, 1 Mar 2004 23:49:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1qL-0001YE-00
	for asrg@ietf.org; Mon, 01 Mar 2004 23:49:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay1pQ-0001Rn-00
	for asrg@ietf.org; Mon, 01 Mar 2004 23:48:24 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay1oa-0001L4-00
	for asrg@ietf.org; Mon, 01 Mar 2004 23:47:32 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1Ay1ob-0000uY-00; Mon, 01 Mar 2004 23:47:33 -0500
Received: from [68.24.248.250] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1Ay1oZ-0001tC-00; Mon, 01 Mar 2004 23:47:33 -0500
Message-ID: <404411D1.4030302@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Dr. Jeffrey Race" <jrace@attglobal.net>
CC: ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 2a .BCP -  Handling Trojaned machines
References: <E1Ay1EB-0004BO-00@ietf-mx>
In-Reply-To: <E1Ay1EB-0004BO-00@ietf-mx>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Mar 2004 23:47:13 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Dr. Jeffrey Race wrote:
> On Mon, 01 Mar 2004 18:11:12 -0500, Yakov Shafranovich wrote:
> 
>>In regards to this specific method, we are currently 
>>looking for volunteers to write a BCP on this and other methods of 
>>dealing with hijacked machines from the originating network's point of 
>>view
> 
> 
> It's done already :)
> 
>   <http://www.camblab.com/misc/univ_std.txt> 
>    
>     based upon
> 
>   <http://www.camblab.com/nugget/spam_03.pdf>
> 

Jeffrey,

Its a good document but what I had been thinking of is a BCP for 
specific measures such as detecting mail spikes and queing the mail, 
rate limiting, etc. in combination with a document such as the one you 
wrote. Your document defines general policy guidelines which are good, 
but we would still need a set of BCPs documentating the best current 
practices that are used by ISPs today for this purpose.

Yakov



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



From exim@www1.ietf.org  Tue Mar  2 05:58:51 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02694
	for <asrg-archive@odin.ietf.org>; Tue, 2 Mar 2004 05:58:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay7bU-0004U8-Ig
	for asrg-archive@odin.ietf.org; Tue, 02 Mar 2004 05:58:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i22AwOTG017239
	for asrg-archive@odin.ietf.org; Tue, 2 Mar 2004 05:58:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay7bU-0004Td-1s
	for asrg-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 05:58:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02631
	for <asrg-web-archive@ietf.org>; Tue, 2 Mar 2004 05:58:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay7bQ-0002L6-00
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 05:58:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay7aR-0002DK-00
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 05:57:20 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay7ZW-00025p-00
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 05:56:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay7ZA-0004DC-Qo; Tue, 02 Mar 2004 05:56:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ay7Yk-0004CY-VU
	for asrg@optimus.ietf.org; Tue, 02 Mar 2004 05:55:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02525
	for <asrg@ietf.org>; Tue, 2 Mar 2004 05:55:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay7Yh-0001xx-00
	for asrg@ietf.org; Tue, 02 Mar 2004 05:55:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ay7Xt-0001pz-00
	for asrg@ietf.org; Tue, 02 Mar 2004 05:54:42 -0500
Received: from host217-35-105-169.in-addr.btopenworld.com ([217.35.105.169] helo=mail.neosinteractive.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ay7Wy-0001h2-00
	for asrg@ietf.org; Tue, 02 Mar 2004 05:53:45 -0500
Received: from tthomson ([217.35.105.173] unverified) by mail.neosinteractive.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 2 Mar 2004 09:58:45 +0000
From: "Tom Thomson" <tthomson@neosinteractive.com>
To: "Larry Seltzer" <larry@larryseltzer.com>, "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
Message-ID: <IOEPKAPPDKHPENCKFNNGKEPODBAA.tthomson@neosinteractive.com>
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 IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <02a601c3ffa4$e45f5c00$5b00005a@moregarlic.com>
X-OriginalArrivalTime: 02 Mar 2004 09:58:45.0062 (UTC) FILETIME=[F3262E60:01C4003C]
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/mail-archive/working-groups/asrg/>
Date: Tue, 2 Mar 2004 10:53:45 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> A copy of this dialog box may be found at
>
http://securityresponse.symantec.com/avcenter/graphics/w32.swen.a@mm.5.gif.
I have a
> hard time believing. I doubt many people remember their SMTP server
credentials offhand,
> since they are usually stored by the MUA for automatic use.

I don't agree with you.  People don't bother to remember credentials for
machines behind adequate firewalls, having no publicly meaningful IP
address, with anti-virus and anti-intrusion stuff mounted on the Exchange
server (or non-MS equivalent), and good anti-virus stuff running on the
desktop.  In less secure environments, a lot of people do remember
credentials (and most people I know have desktops in both secure and
insecure environments, and let the MUA store credentials in one and not in
the other).

It is even possible to set up Outlook Express so that it CAN'T remember
credentials even if you ask it to (I did this on some machines, and can't
remember how to turn it off to allow the MUA to remember credentials - which
is a pity as some of those machines are now in clean envirenments).


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



From exim@www1.ietf.org  Tue Mar  2 14:25:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25790
	for <asrg-archive@odin.ietf.org>; Tue, 2 Mar 2004 14:25:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyFVa-0003Mj-Eg
	for asrg-archive@odin.ietf.org; Tue, 02 Mar 2004 14:24:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i22JOoZ4012931
	for asrg-archive@odin.ietf.org; Tue, 2 Mar 2004 14:24:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyFVa-0003MU-68
	for asrg-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 14:24:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25786
	for <asrg-web-archive@ietf.org>; Tue, 2 Mar 2004 14:24:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyFVX-0000Ks-00
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 14:24:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyFUj-0000Du-00
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 14:23:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyFUB-00005e-00
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 14:23:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyFTp-00038L-1l; Tue, 02 Mar 2004 14:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyFTg-00037p-T9
	for asrg@optimus.ietf.org; Tue, 02 Mar 2004 14:22:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25732
	for <asrg@ietf.org>; Tue, 2 Mar 2004 14:22:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyFTe-00004l-00
	for asrg@ietf.org; Tue, 02 Mar 2004 14:22:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyFSs-0007kL-00
	for asrg@ietf.org; Tue, 02 Mar 2004 14:22:02 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyFS1-0007aY-00
	for asrg@ietf.org; Tue, 02 Mar 2004 14:21:09 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id D1574170BB
	for <asrg@ietf.org>; Tue,  2 Mar 2004 14:24:21 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID 
In-Reply-To: Your message of "Mon, 01 Mar 2004 16:33:01 PST."
             <C6DDA43B91BFDA49AA2F1E473732113E0A1902@mou1wnexm05.vcorp.ad.vrsn.com> 
Message-Id: <20040302192421.D1574170BB@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Tue, 02 Mar 2004 14:24:21 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

"Hallam-Baker, Phillip" <pbaker@verisign.com> wrote:
> The reporting issues need not be spam related
> 
> DDoS is a big enough issue here to justify a notification mechanism.

  If anyone who disagrees, please post the IP of their main MTA on
this list.  I'll point the MX for my "death by spam" domain to it.

  The best-case scenario is then that you block port 25 or shut the
machine down.  But your routers will still be dealing with ~100 TCP
SYN's a second to port 25 from 10's of 1000's of IP's.

  If that's not a DDoS, I don't know what is.

> If there is a hijacked machine on the net then the ISP resonsible needs
> to know ASAP.

  Or, everyone else needs to know, so that they can block the machine
if the ISP won't.

  Alan DeKok.

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



From exim@www1.ietf.org  Tue Mar  2 15:23:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29361
	for <asrg-archive@odin.ietf.org>; Tue, 2 Mar 2004 15:23:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyGPi-0005y0-88
	for asrg-archive@odin.ietf.org; Tue, 02 Mar 2004 15:22:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i22KMoxF022929
	for asrg-archive@odin.ietf.org; Tue, 2 Mar 2004 15:22:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyGPh-0005xk-Jq
	for asrg-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 15:22:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29341
	for <asrg-web-archive@ietf.org>; Tue, 2 Mar 2004 15:22:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyGPg-0000MX-00
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 15:22:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyGOm-0000FH-00
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 15:21:53 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyGOK-00007K-00
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 15:21:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyGNy-00057u-T1; Tue, 02 Mar 2004 15:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyGNh-00050a-S8
	for asrg@optimus.ietf.org; Tue, 02 Mar 2004 15:20:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29236
	for <asrg@ietf.org>; Tue, 2 Mar 2004 15:20:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyGNg-00005H-00
	for asrg@ietf.org; Tue, 02 Mar 2004 15:20:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyGMf-0007ld-00
	for asrg@ietf.org; Tue, 02 Mar 2004 15:19:42 -0500
Received: from [216.226.168.57] (helo=sv-IAS2.fjcs.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyGLh-0007Ys-00
	for asrg@ietf.org; Tue, 02 Mar 2004 15:18:41 -0500
Received: from goui815 ([172.16.75.250]) by sv-IAS2.fjcs.net with Microsoft SMTPSVC(6.0.3790.0);
	 Tue, 2 Mar 2004 12:23:03 -0800
Message-ID: <000701c40093$7bcf1d20$fa4b10ac@fpcad.fujitsupc.com>
From: "George Ou" <george_ou@netzero.com>
To: "Tom Thomson" <tthomson@neosinteractive.com>,
        "Larry Seltzer" <larry@larryseltzer.com>, "'ASRG'" <asrg@ietf.org>
References: <IOEPKAPPDKHPENCKFNNGKEPODBAA.tthomson@neosinteractive.com>
Subject: Re: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 02 Mar 2004 20:23:03.0013 (UTC) FILETIME=[29D3E950:01C40094]
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/mail-archive/working-groups/asrg/>
Date: Tue, 2 Mar 2004 12:18:10 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> I don't agree with you.  People don't bother to remember credentials for
> machines behind adequate firewalls, having no publicly meaningful IP
> address, with anti-virus and anti-intrusion stuff mounted on the Exchange
> server (or non-MS equivalent), and good anti-virus stuff running on the
> desktop.  In less secure environments, a lot of people do remember
> credentials (and most people I know have desktops in both secure and
> insecure environments, and let the MUA store credentials in one and not in
> the other).

Although I definitely agree with the security precautions that you take, I
think it is extremely unlikely that the average user will be as
knowledgeable and diligent as you and computer savvy friends.  The average
person is clueless that they even need a firewall at all.  The average
person stores their credentials on anything.  The average person is clueless
about security and that won't ever change.  The solution to any of these
problems is to attack the problem at the gateway, server, and standards
level.

I can't believe in 2004 we're still even talking about email viruses when
anti-virus gateway technology has been available for many years.  It's
amazing that people are still under the illusion that somehow if they scream
enough that they'll be able to convince the average user to not open
attachments when it's impossible for the computer masses to comply.  I've
not seen a single virus in any of my user's mail boxes in nearly 4 years
because of anti-virus gateway and server measures we took, yet people still
spend all their time attacking the problem from the end user's perspective.
It's about time all mail gateways and servers scan for viruses inbound and
outbound.  That is the only way to eliminate the virus problem.  I know MSN
and Yahoo already do this, and I never see viruses in my MSN account.

As for worm propagation, hopefully XP Service Pack 2 with it's simple
stateful firewall turned on by default will be implemented across all
Windows XP machines soon.  It will go a long ways to eliminate the DDoS
threat if 80% of the world's computers block all inbound traffic by default,
just like any of these SMTP authentication schemes if adopted will help in
the battle against SPAM.  At this point, I don't even care who's standard
wins, just as long as some kind of authentication scheme is standardized and
adopted by a critical mass.

Sorry for being slightly off topic.


George Ou


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



From exim@www1.ietf.org  Tue Mar  2 22:12:08 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24648
	for <asrg-archive@odin.ietf.org>; Tue, 2 Mar 2004 22:12:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyMnN-0008AC-GC
	for asrg-archive@odin.ietf.org; Tue, 02 Mar 2004 22:11:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i233Bfa8031376
	for asrg-archive@odin.ietf.org; Tue, 2 Mar 2004 22:11:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyMnN-00089z-C2
	for asrg-web-archive@optimus.ietf.org; Tue, 02 Mar 2004 22:11:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24482
	for <asrg-web-archive@ietf.org>; Tue, 2 Mar 2004 22:11:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyMnK-0007hK-00
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 22:11:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyMkz-00078a-00
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 22:09:14 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyMk0-0006zr-02
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 22:08:12 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AyMh5-0000lS-M6
	for asrg-web-archive@ietf.org; Tue, 02 Mar 2004 22:05:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyMfw-0006cg-QL; Tue, 02 Mar 2004 22:04:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyMfI-0006aW-Rm
	for asrg@optimus.ietf.org; Tue, 02 Mar 2004 22:03:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24003
	for <asrg@ietf.org>; Tue, 2 Mar 2004 22:03:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyMfF-0006BR-00
	for asrg@ietf.org; Tue, 02 Mar 2004 22:03:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyMeG-00061H-00
	for asrg@ietf.org; Tue, 02 Mar 2004 22:02:17 -0500
Received: from mail3.panix.com ([166.84.1.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyMdY-0005rY-00
	for asrg@ietf.org; Tue, 02 Mar 2004 22:01:32 -0500
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail3.panix.com (Postfix) with ESMTP id 0DB779842B
	for <asrg@ietf.org>; Tue,  2 Mar 2004 22:01:26 -0500 (EST)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i2331PK19868;
	Tue, 2 Mar 2004 22:01:25 -0500 (EST)
Message-Id: <200403030301.i2331PK19868@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <6.0.1.1.0.20040204013312.01c05ec0@mail.uniwares.com> (message
	from Andreas Saurwein on Wed, 04 Feb 2004 01:36:00 -0200)
Subject: Re: [Asrg] Its all over for Challenge Response
References: <2A1D4C86842EE14CA9BC80474919782E0356EF80@mou1wnexm02.vcorp.ad.vrsn.com>
 <200402040327.i143R6216657@panix5.panix.com> <6.0.1.1.0.20040204013312.01c05ec0@mail.uniwares.com>
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/mail-archive/working-groups/asrg/>
Date: Tue, 2 Mar 2004 22:01:25 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Andreas Saurwein <saurwein@uniwares.com> wrote:
> At 4/2/2004 01:27 Wednesday, Seth wrote:

>>That can always be done by selecting a different ISP.  Therefore, any
>>problem is self-limiting.
>
> Not always you have to choice of ISP. There are still lots of places where 
> you have to be thankful that you HAVE internet access.

If I can run ssh on my own computer, I can use my chosen ISP.  I
haven't dialed in to Panix this century.

>>Would you also want to limit the ability of a church that provides
>>email accounts for its members to limit the ability of opposing
>>religions to send mail to its members?
>
> Yes

Why won't you let the owner of the equipment decide how it may be
used?

>>Would you also want to limit the ability of a company to limit the
>>ability of headhunters to solicit its employees?
>
> Again Yes.
> Thats what we call "policy". As a member or employee you accept the policy 
> or you go somewhere else.

So why are you _limiting_ the ability of the company?  You mean the
company has to allow the employees to do whatever they want, and just
fire them if it doesn't like it?

Seth

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



From exim@www1.ietf.org  Wed Mar  3 10:18:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03779
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 10:18:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyY7u-0003yo-5N
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 10:17:39 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23FHcUH015291
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 10:17:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyY7t-0003yS-RK
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 10:17:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03657
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 10:17:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyY7r-0007K6-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 10:17:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyY70-000772-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 10:16:42 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyY6I-0006ue-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 10:15:58 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyY5O-0003DM-Bo; Wed, 03 Mar 2004 10:15:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyY4X-0002y6-2k
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 10:14:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03209
	for <asrg@ietf.org>; Wed, 3 Mar 2004 10:14:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyY4U-0006Sn-00
	for asrg@ietf.org; Wed, 03 Mar 2004 10:14:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyY3k-0006GC-00
	for asrg@ietf.org; Wed, 03 Mar 2004 10:13:21 -0500
Received: from bsdsgr04.sagres.com.br ([200.140.134.134])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyY2o-0005zf-00
	for asrg@ietf.org; Wed, 03 Mar 2004 10:12:22 -0500
Received: from ntsgr07.sagres.com.br (NTsgr07.sagres.com.br [10.0.17.7])
	by BSDsgr04.sagres.com.br (8.12.8p1/8.12.10) with ESMTP id i23FBiDd023525;
	Wed, 3 Mar 2004 15:11:49 GMT
	(envelope-from saurwein@uniwares.com)
Received: from leonone.uniwares.com ([200.163.14.212])
          by ntsgr07.sagres.com.br (Lotus Domino Release 5.0.12)
          with ESMTP id 2004030312200730:26039 ;
          Wed, 3 Mar 2004 12:20:07 -0300 
Message-Id: <6.0.3.0.0.20040303120840.01df0ec0@mail.uniwares.com>
X-Sender: saurwein.uniwares@mail.uniwares.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
To: Seth Breidbart <sethb@panix.com>, asrg@ietf.org
From: Andreas Saurwein <saurwein@uniwares.com>
Subject: Re: [Asrg] Its all over for Challenge Response
In-Reply-To: <200403030301.i2331PK19868@panix5.panix.com>
References: <2A1D4C86842EE14CA9BC80474919782E0356EF80@mou1wnexm02.vcorp.ad.vrsn.com>
 <200402040327.i143R6216657@panix5.panix.com>
 <6.0.1.1.0.20040204013312.01c05ec0@mail.uniwares.com>
 <200403030301.i2331PK19868@panix5.panix.com>
Mime-Version: 1.0
X-MIMETrack: Itemize by SMTP Server on ntsgr07/SAGRES(Release 5.0.12  |February 13, 2003) at
 03/03/2004 12:20:07,
	Serialize by Router on ntsgr07/SAGRES(Release 5.0.12  |February 13, 2003) at
 03/03/2004 12:20:14,
	Serialize complete at 03/03/2004 12:20:14
Content-Type: text/plain; charset="us-ascii"; format=flowed
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 12:11:33 -0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL autolearn=no version=2.60

At 3/3/2004 00:01 Wednesday, Seth Breidbart wrote:
>Andreas Saurwein <saurwein@uniwares.com> wrote:
> > At 4/2/2004 01:27 Wednesday, Seth wrote:
>
> >>That can always be done by selecting a different ISP.  Therefore, any
> >>problem is self-limiting.
> >
> > Not always you have to choice of ISP. There are still lots of places where
> > you have to be thankful that you HAVE internet access.
>
>If I can run ssh on my own computer, I can use my chosen ISP.  I
>haven't dialed in to Panix this century.

How many average users you'll find able to use ssh? Forget for a moment 
that there are some people (about 0.01% of the internet users?) who know 
what the heck they are doing.

> >>Would you also want to limit the ability of a company to limit the
> >>ability of headhunters to solicit its employees?
> >
> > Again Yes.
> > Thats what we call "policy". As a member or employee you accept the policy
> > or you go somewhere else.
>
>So why are you _limiting_ the ability of the company?  You mean the
>company has to allow the employees to do whatever they want, and just
>fire them if it doesn't like it?

Quite the other way round: the company sets the policy and the employees 
have to accept it, if they dont like it, they are free to go.
So, where is that limiting?

Andreas


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



From exim@www1.ietf.org  Wed Mar  3 14:19:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19483
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 14:19:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aybta-0001nQ-Pw
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 14:19:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23JJ6EQ006898
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 14:19:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aybta-0001nB-K9
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 14:19:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19453
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 14:19:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AybtY-0000nJ-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 14:19:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aybsf-0000bt-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 14:18:10 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aybrr-0000QQ-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 14:17:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aybrb-0001To-Ej; Wed, 03 Mar 2004 14:17:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AybrV-0001Sa-EH
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 14:16:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19276
	for <asrg@ietf.org>; Wed, 3 Mar 2004 14:16:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AybrT-0000Ne-00
	for asrg@ietf.org; Wed, 03 Mar 2004 14:16:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AybqU-00008O-00
	for asrg@ietf.org; Wed, 03 Mar 2004 14:15:55 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AybpF-0007aK-00
	for asrg@ietf.org; Wed, 03 Mar 2004 14:14:37 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id C6FD2170C1
	for <asrg@ietf.org>; Wed,  3 Mar 2004 14:17:50 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] Its all over for Challenge Response 
In-Reply-To: Your message of "Wed, 03 Mar 2004 12:11:33 -0300."
             <6.0.3.0.0.20040303120840.01df0ec0@mail.uniwares.com> 
Message-Id: <20040303191750.C6FD2170C1@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 14:17:50 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Andreas Saurwein <saurwein@uniwares.com> wrote:
> >If I can run ssh on my own computer, I can use my chosen ISP.  I
> >haven't dialed in to Panix this century.
> 
> How many average users you'll find able to use ssh?

  This is not an argument.  Those users are using MUAs.  The authors
of those MUAs can do the work, and add a checkbox that the idiot users
can use.

  And yes, we already know that solving the spam problem may require
software upgrades.  Saying that there will be cost and time to deploy
updated software isn't a useful argument, either.  If there is
sufficient incentive to upgrade, people will do so.

  And we already know that people who won't upgrade won't be doing
anything to help solve the spam problem.  We can ignore any arguments
about their needs, as they've already made their choice to accept the
current situation.

  Alan DeKok.

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



From exim@www1.ietf.org  Wed Mar  3 14:44:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20833
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 14:44:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AycHm-0003oM-Tr
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 14:44:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23Ji64H014644
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 14:44:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AycHm-0003o7-O5
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 14:44:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20817
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 14:44:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AycHk-0005ER-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 14:44:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AycGd-00053O-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 14:42:56 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AycFw-0004sz-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 14:42:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AycFk-0003ZC-L2; Wed, 03 Mar 2004 14:42:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AycCm-0003Rr-9C
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 14:38:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20584
	for <asrg@ietf.org>; Wed, 3 Mar 2004 14:38:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AycCj-0004OQ-00
	for asrg@ietf.org; Wed, 03 Mar 2004 14:38:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AycBo-0004FN-00
	for asrg@ietf.org; Wed, 03 Mar 2004 14:37:56 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AycBO-00045r-00
	for asrg@ietf.org; Wed, 03 Mar 2004 14:37:30 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AycBO-0008G9-00
	for asrg@ietf.org; Wed, 03 Mar 2004 14:37:30 -0500
Received: from [68.24.225.2] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AycBN-0004zw-00
	for asrg@ietf.org; Wed, 03 Mar 2004 14:37:30 -0500
Message-ID: <404633F3.2010503@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 3b. SMTP Verification - Reputation Systems and their Problems
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 14:37:23 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

In the current world the closest approximation we have to reputation 
systems that are planned with LMAP are blacklists and Senderbase. Given 
that current blacklists have numerous problems, why would any proposed 
reputation or accrediation systems of the future be any different? How 
are we planning on avoiding the same problems we have today in the 
future, if we want to deploy such systems?

Yakov

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



From exim@www1.ietf.org  Wed Mar  3 15:28:50 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24653
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 15:28:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aycya-0000GP-NC
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 15:28:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23KSKjk001007
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 15:28:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aycya-0000GA-4Y
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 15:28:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24554
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 15:28:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AycyY-00065q-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 15:28:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aycx7-0005kF-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 15:26:50 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AycwL-0005bN-01
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 15:26:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AycvZ-0005gp-44
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 15:25:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AycvO-0008So-0O; Wed, 03 Mar 2004 15:25:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aycv9-0008SO-Rm
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 15:24:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24472
	for <asrg@ietf.org>; Wed, 3 Mar 2004 15:24:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aycv8-0005SJ-00
	for asrg@ietf.org; Wed, 03 Mar 2004 15:24:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aycu9-0005K8-00
	for asrg@ietf.org; Wed, 03 Mar 2004 15:23:45 -0500
Received: from c-24-17-77-4.client.comcast.net ([24.17.77.4] helo=riddler.dyndns.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayctm-0005C8-00
	for asrg@ietf.org; Wed, 03 Mar 2004 15:23:22 -0500
Received: from mdf by riddler.dyndns.org with local (Exim 4.30 #2)
	id 1Ayctk-000AQO-J8
	for asrg@ietf.org; Wed, 03 Mar 2004 12:23:20 -0800
From: Mark Foster <mark@foster.cc>
To: ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation Systems and their Problems
Message-ID: <20040303202320.GA38846@riddler.dyndns.org>
Mail-Followup-To: Mark Foster <mark@foster.cc>, ASRG <asrg@ietf.org>
References: <404633F3.2010503@solidmatrix.com>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="KsGdsel6WgEHnImy"
Content-Disposition: inline
In-Reply-To: <404633F3.2010503@solidmatrix.com>
User-Agent: Mutt/1.4.2.1i
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/mail-archive/working-groups/asrg/>
Date: Wed, 3 Mar 2004 12:23:20 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


--KsGdsel6WgEHnImy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 03, 2004 at 02:37:23PM -0500, Yakov Shafranovich wrote:
> In the current world the closest approximation we have to reputation=20
> systems that are planned with LMAP are blacklists and Senderbase. Given=
=20
> that current blacklists have numerous problems, why would any proposed=20
> reputation or accrediation systems of the future be any different? How=20
> are we planning on avoiding the same problems we have today in the=20
> future, if we want to deploy such systems?

I've been doing some research into the use of STARTTLS and certificate
verification. The possibility exists for overlaying a
PKI trust model onto the email infrastructure... not just S/MIME and
PGP/GPG, but securing the message relay transmissions (MTA to MTA).

By enabling STARTTLS on any given email server (most of them support
STARTTLS), the server must have an x509 certificate, which
is either self-signed or signed by a public (or private) certificate
authority. By also configuring the mail servers to cough up the same
certificate when relaying (outbound), something approaching a whitelist
trust model can be achieved. Also, some mail servers automatically step-up
to TLS when they encounter the STARTTLS in transmission. So if the admins
are willing and able to turn on STARTTLS, and folks start using certificate
verification in their acceptance criteria, this could take off.

Here are some of the problems with the idea.=20
1. Most if not all of the MTAs do not support certificate=20
revocation lists (CRLs) or OSCP (although Exim will very soon).
2. The existing CAs do not sell these "types" of certificates (usually
just web server, s/mime for email and code signing).
3. The existing CAs do not fit easily into the role currently played
by the DNSBL folks. They would need to revoke certificates upon receiving
complaints from the community at large about abuse.

I don't think any of those problems are insurmountable. I haven't seen
too many folks touting this as a possible solution going forward,
either.

http://mark.foster.cc/articles/secure-email.html

I'd be interested to know what others think.
--=20
Some days it's just not worth chewing through the restraints...
Mark D. Foster, CISSP <mark@foster.cc>  http://mark.foster.cc/


--KsGdsel6WgEHnImy
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (FreeBSD)

iD8DBQFARj63sP1x4ZySqYcRAkoDAJwL78peOd2iOjoXt6+W7ce7yDSPgACgjPEa
s7GIK8nd8fGNgkURIvSf0yw=
=3N2Y
-----END PGP SIGNATURE-----

--KsGdsel6WgEHnImy--

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



From exim@www1.ietf.org  Wed Mar  3 16:04:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26249
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 16:04:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AydWy-0002bn-Do
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 16:03:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23L3qZj010010
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 16:03:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AydWy-0002bL-2I
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 16:03:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26226
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 16:03:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AydWw-0004dc-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:03:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AydW1-0004Ua-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:02:54 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AydVH-0004LR-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:02:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AydVB-0002RQ-D1; Wed, 03 Mar 2004 16:02:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AydUw-0002Qs-PF
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 16:01:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26092
	for <asrg@ietf.org>; Wed, 3 Mar 2004 16:01:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AydUv-0004JD-00
	for asrg@ietf.org; Wed, 03 Mar 2004 16:01:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AydTx-00049x-00
	for asrg@ietf.org; Wed, 03 Mar 2004 16:00:46 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AydT3-00040w-00
	for asrg@ietf.org; Wed, 03 Mar 2004 15:59:49 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id B6021170C1
	for <asrg@ietf.org>; Wed,  3 Mar 2004 16:03:03 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation Systems and their Problems 
In-Reply-To: Your message of "Wed, 03 Mar 2004 12:23:20 PST."
             <20040303202320.GA38846@riddler.dyndns.org> 
Message-Id: <20040303210303.B6021170C1@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 16:03:03 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Mark Foster <mark@foster.cc> wrote:
> I've been doing some research into the use of STARTTLS and certificate
> verification. The possibility exists for overlaying a
> PKI trust model onto the email infrastructure... not just S/MIME and
> PGP/GPG, but securing the message relay transmissions (MTA to MTA).

  A PKI trust model is very different than overlaying encryption on
top of SMTP.

> By enabling STARTTLS on any given email server (most of them support
> STARTTLS), the server must have an x509 certificate, which
> is either self-signed or signed by a public (or private) certificate
> authority.

  Which are both trivial to get, and mean nothing.

> By also configuring the mail servers to cough up the same
> certificate when relaying (outbound), something approaching a
> whitelist trust model can be achieved.

  How?  You don't say that.  That's the important piece, and the only
one worth talking about.

> 3. The existing CAs do not fit easily into the role currently played
> by the DNSBL folks. They would need to revoke certificates upon receiving
> complaints from the community at large about abuse.

  Then you're using certificates for something they were never
intended to be used for, and giving CA's additional responsibility and
authority.

> I don't think any of those problems are insurmountable. I haven't seen
> too many folks touting this as a possible solution going forward,
> either.

  That's because it's not very practical.

  This whole scheme is equivalent to publishing the web of trust in
any other format, and doesn't require STARTTLS or certificates for it
to work.

  Alan DeKok.

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



From exim@www1.ietf.org  Wed Mar  3 16:17:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26859
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 16:17:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AydjZ-0003tS-QV
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 16:16:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23LGr6R014960
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 16:16:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AydjZ-0003tD-MS
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 16:16:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26853
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 16:16:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AydjY-0006sR-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:16:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aydik-0006jJ-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:16:03 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aydi8-0006ZK-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:15:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aydhm-0003fJ-Uu; Wed, 03 Mar 2004 16:15:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aydfd-0003Gf-11
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 16:12:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26680
	for <asrg@ietf.org>; Wed, 3 Mar 2004 16:12:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aydfb-0006EX-00
	for asrg@ietf.org; Wed, 03 Mar 2004 16:12:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aydel-00066E-00
	for asrg@ietf.org; Wed, 03 Mar 2004 16:11:56 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AydeU-0005xP-00
	for asrg@ietf.org; Wed, 03 Mar 2004 16:11:38 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1Ayde5-0005et-00; Wed, 03 Mar 2004 16:11:13 -0500
Received: from [68.24.225.2] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1Ayde1-00036W-00; Wed, 03 Mar 2004 16:11:13 -0500
Message-ID: <404649E2.6020809@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Mark Foster <mark@foster.cc>
CC: ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation Systems and their Problems
References: <404633F3.2010503@solidmatrix.com> <20040303202320.GA38846@riddler.dyndns.org>
In-Reply-To: <20040303202320.GA38846@riddler.dyndns.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 16:10:58 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mark Foster wrote:
> On Wed, Mar 03, 2004 at 02:37:23PM -0500, Yakov Shafranovich wrote:
> 
>>In the current world the closest approximation we have to reputation 
>>systems that are planned with LMAP are blacklists and Senderbase. Given 
>>that current blacklists have numerous problems, why would any proposed 
>>reputation or accrediation systems of the future be any different? How 
>>are we planning on avoiding the same problems we have today in the 
>>future, if we want to deploy such systems?
> 
> 
> I've been doing some research into the use of STARTTLS and certificate
> verification. The possibility exists for overlaying a
> PKI trust model onto the email infrastructure... not just S/MIME and
> PGP/GPG, but securing the message relay transmissions (MTA to MTA).
> 

The problem with the PKI model is key distribution. If we follow the 
current SSL scheme that might work BUT then you are making Verisign and 
other CAs the gatekeepers for the Internet - and can have repercussions. 
For example, in the SSL market according to 
(http://www.securityspace.com/s_survey/sdata/200402/certca.html), 
Verisign and Thawte have 30% and 20% each. HOWEVER, according to 
(http://www.thawte.com/html/CORPORATE/today.html), Thawte is owned by 
Verisign, which implies that 50% of the SSL market is controlled by one 
company. Do you really want a few companies to choose who gets the right 
to send email? Of course, a distributed system like DomainKeys can help 
with some of these problems, but the main problems that blacklists have 
are still there.

Also, SSL certificates today only *idenfity* the site, not provide its 
reputation. Changing CAs into reputation systems, will involve a whole 
new set of challenges. These challenges are mostly present today in 
blacklists which is exactly what worries me - I don't see yet how any of 
these problems can be avoided in any reputation systems.

> Here are some of the problems with the idea. 
> 1. Most if not all of the MTAs do not support certificate 
> revocation lists (CRLs) or OSCP (although Exim will very soon).
> 2. The existing CAs do not sell these "types" of certificates (usually
> just web server, s/mime for email and code signing).
> 3. The existing CAs do not fit easily into the role currently played
> by the DNSBL folks. They would need to revoke certificates upon receiving
> complaints from the community at large about abuse.
> 

#1 and #2 can be solved (#2 especially since CAs will jump at it). 
HOWEVER, #3 is what worries me. What does "abuse" mean, how do we know 
that any of these CAs will be any more responsible than SPEWS is today? 
What about lawsuits? Dealing with different standards of spam and 
different legal standards?

Yakov

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



From exim@www1.ietf.org  Wed Mar  3 16:25:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27126
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 16:25:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AydrG-0004IM-3Z
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 16:24:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23LOoFY016504
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 16:24:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AydrF-0004I7-Re
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 16:24:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27051
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 16:24:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AydrE-0000J6-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:24:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AydqJ-0000A3-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:23:52 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aydpd-00000a-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:23:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AydpV-00047P-42; Wed, 03 Mar 2004 16:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AydpN-00046l-9V
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 16:22:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27002
	for <asrg@ietf.org>; Wed, 3 Mar 2004 16:22:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AydpL-0007nQ-00
	for asrg@ietf.org; Wed, 03 Mar 2004 16:22:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AydoT-0007eM-00
	for asrg@ietf.org; Wed, 03 Mar 2004 16:21:58 -0500
Received: from joy.songbird.com ([208.184.79.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aydni-0007KL-00
	for asrg@ietf.org; Wed, 03 Mar 2004 16:21:10 -0500
Received: from BBFUJIP.brandenburg.com (jay.songbird.com [208.184.79.253])
	by joy.songbird.com (8.11.6/8.11.6) with ESMTP id i23LTKd10234;
	Wed, 3 Mar 2004 13:29:20 -0800
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
X-Priority: 3 (Normal)
Message-ID: <194882531.20040304062025@brandenburg.com>
To: "Alan DeKok" <aland@ox.org>
CC: asrg@ietf.org
Subject: Re: [Asrg] Its all over for Challenge Response
In-Reply-To: <20040303191750.C6FD2170C1@mail.nitros9.org>
References: Your message of "Wed, 03 Mar 2004 12:11:33 -0300."
 <6.0.3.0.0.20040303120840.01df0ec0@mail.uniwares.com>
 <20040303191750.C6FD2170C1@mail.nitros9.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 4 Mar 2004 06:20:25 +0900
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,PRIORITY_NO_NAME 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Alan,

>> How many average users you'll find able to use ssh?

AD>   This is not an argument.  Those users are using MUAs.  The authors
AD> of those MUAs can do the work, and add a checkbox that the idiot users
AD> can use.

For the IETF, it is the _only_ argument.  Folks forget that we exist
to produce specifications that get used.  Not "implemented" but
actually used.

For an example of the "it got implemented" criterion that ignored the
"it gets used" criterion, please refer to the history of OSI.


AD>   And yes, we already know that solving the spam problem may require
AD> software upgrades.  Saying that there will be cost and time to deploy
AD> updated software isn't a useful argument, either.  If there is
AD> sufficient incentive to upgrade, people will do so.

That is my point.  The nature and amount of incentive needed depends
on the cost and the benefit (along with a few other factors, of
course.) Any scheme that proposed massive change needs to pay quite a
bit of attention to the both of these.  That requires detailed
thinking, not a simple handwave.


AD>   And we already know that people who won't upgrade won't be doing
AD> anything to help solve the spam problem.  We can ignore any arguments
AD> about their needs, as they've already made their choice to accept the
AD> current situation.

That line of thinking is quite popular in the technical community, and
often even in the management community.  It accounts for a massive
number of companies' failures.  As well as standards' failures.


d/
--
 Dave Crocker <dcrocker-at-brandenburg-dot-com>
 Brandenburg InternetWorking <www.brandenburg.com>
 Sunnyvale, CA  USA <tel:+1.408.246.8253>


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



From exim@www1.ietf.org  Wed Mar  3 16:35:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27655
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 16:35:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aye18-000530-Jo
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 16:35:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23LZ2rY019396
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 16:35:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aye18-00052l-Ex
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 16:35:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27629
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 16:34:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aye16-00029B-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:35:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aye0B-0001zK-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:34:04 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AydzI-0001o6-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 16:33:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AydzA-0004qM-W7; Wed, 03 Mar 2004 16:33:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aydz5-0004nv-Kq
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 16:32:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27510
	for <asrg@ietf.org>; Wed, 3 Mar 2004 16:32:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aydz3-0001mm-00
	for asrg@ietf.org; Wed, 03 Mar 2004 16:32:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AydyH-0001d3-00
	for asrg@ietf.org; Wed, 03 Mar 2004 16:32:06 -0500
Received: from mail1.panix.com ([166.84.1.72])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aydxg-0001SZ-00
	for asrg@ietf.org; Wed, 03 Mar 2004 16:31:29 -0500
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail1.panix.com (Postfix) with ESMTP id 95591491BF
	for <asrg@ietf.org>; Wed,  3 Mar 2004 16:31:06 -0500 (EST)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i23LUYx22056;
	Wed, 3 Mar 2004 16:30:34 -0500 (EST)
Message-Id: <200403032130.i23LUYx22056@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <194882531.20040304062025@brandenburg.com> (message from Dave
	Crocker on Thu, 4 Mar 2004 06:20:25 +0900)
Subject: Re: [Asrg] Its all over for Challenge Response
References: Your message of "Wed, 03 Mar 2004 12:11:33 -0300."
 <6.0.3.0.0.20040303120840.01df0ec0@mail.uniwares.com>
 <20040303191750.C6FD2170C1@mail.nitros9.org> <194882531.20040304062025@brandenburg.com>
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/mail-archive/working-groups/asrg/>
Date: Wed, 3 Mar 2004 16:30:34 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

>>> How many average users you'll find able to use ssh?
>
>AD>   This is not an argument.  Those users are using MUAs.  The authors
>AD> of those MUAs can do the work, and add a checkbox that the idiot users
>AD> can use.
>
> For the IETF, it is the _only_ argument.  Folks forget that we exist
> to produce specifications that get used.  Not "implemented" but
> actually used.

I gave ssh as an example to disprove the "I have to use the mailserver
provided by somebody who owns a wire to my house" claim.  Most MUAs
today are perfectly able to connect to arbitrary POP/IMAP servers and
MTAs, the user just fills in the boxes with the names of the machines
to use.

> That is my point.  The nature and amount of incentive needed depends
> on the cost and the benefit (along with a few other factors, of
> course.) Any scheme that proposed massive change needs to pay quite
> a bit of attention to the both of these.  That requires detailed
> thinking, not a simple handwave.

It also depends on who needs to do what.  Something done at the server
level is likely to happen sooner than something done at the client
level, because there are fewer servers, their administrators tend to
be more knowledgeable, and the benefits can be greater.

Seth

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



From exim@www1.ietf.org  Wed Mar  3 17:57:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03028
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 17:57:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfIN-0003M0-K4
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 17:56:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23Mut1K012886
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 17:56:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfIN-0003Ll-G6
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 17:56:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02996
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 17:56:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfIK-0002K9-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 17:56:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyfHP-0002Al-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 17:55:56 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfGl-00021U-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 17:55:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfGa-00031k-JR; Wed, 03 Mar 2004 17:55:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfGT-0002yf-7u
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 17:54:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02873
	for <asrg@ietf.org>; Wed, 3 Mar 2004 17:54:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfGQ-0001zq-00
	for asrg@ietf.org; Wed, 03 Mar 2004 17:54:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyfFZ-0001pj-00
	for asrg@ietf.org; Wed, 03 Mar 2004 17:54:01 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfEh-0001g5-00
	for asrg@ietf.org; Wed, 03 Mar 2004 17:53:07 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id 3FA9F170C1
	for <asrg@ietf.org>; Wed,  3 Mar 2004 17:56:21 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] Its all over for Challenge Response 
In-Reply-To: Your message of "Thu, 04 Mar 2004 06:20:25 +0900."
             <194882531.20040304062025@brandenburg.com> 
Message-Id: <20040303225621.3FA9F170C1@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 17:56:21 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Dave Crocker <dhc@dcrocker.net> wrote:
> For the IETF, it is the _only_ argument.  Folks forget that we exist
> to produce specifications that get used.  Not "implemented" but
> actually used.

  I believe the original point was about roaming users sending mail
via SSH tunnels in an LMAP-aware world, where their dynamic IP wasn't
listed in LMAP.  They could then use SMTP over an SSH tunnel to send
mail via a machine in the domain, versus using naked SMTP themselves.

  SSH exists and has been widely deployed for years.  SMTP exists and
has been widely deployed for years.  There is no need for additional
standards work.  There is only a need for MUA authors to implement and
deploy existing protocols.

  Nothing in that process requires input from the IETF or any other
standards body.

> > [ incentive to upgrade ]
> 
> That is my point.  The nature and amount of incentive needed depends
> on the cost and the benefit (along with a few other factors, of
> course.)  Any scheme that proposed massive change needs to pay quite a bit of
> attention to the both of these.  That requires detailed thinking,
> not a simple handwave.

  I agree.  But when a proposal is being opposed, we similarly need a
cost/benefit reason for opposition, not a simple hand-waving of "it
will cost more than most people think."  Such arguments don't help
move the discussion forward, either.

> AD>   And we already know that people who won't upgrade won't be doing
> AD> anything to help solve the spam problem.  We can ignore any arguments
> AD> about their needs, as they've already made their choice to accept the
> AD> current situation.
> 
> That line of thinking is quite popular in the technical community, and
> often even in the management community.  It accounts for a massive
> number of companies' failures.  As well as standards' failures.

  I'm not sure how that comment is relevant to what I said.  I'm not
saying we deny them their needs, I'm saying that their anti-spam needs
aren't really relevant for input to the design of an anti-spam system,
as they chose not to participate in that system.

  In simple steps:

  a) If we design an anti-spam system which, by design, has zero
     impact on non-implementors when they interact with implementors,
     then it will also have zero impact on spammers.  (Who, by
     definition, won't implement it, or will implement it solely to
     abuse it.)

  b) If we design an anti-spam system which DOES require people to
     participate to get its benefits, then people who DON'T participate
     may not reap its benefits.

  c) That's OK, because they chose not to participate.

  d) People who don't implement an anti-spam system shouldn't be
     affected by it, unless they choose to interact with someone who
     does implement it.

  e) In that case we already know that communication is solely by
     mutual consent.

  f) Any anti-spam system MUST permit the implementor to choose to
     communicate with non-implementors, otherwise it is a draconian
     system, and will not be implemented by anyone.

  g) In which case, everyone is happy.  People who implement it will
     reap the benefits with other implementors.  People who don't
     implement it won't have their interaction with non-implementors be
     affected.

  The interaction between the two groups is solely at their own
discretion, which means local policy, which means it's outside of the
scope of ASRG & the IETF.

  I hope that makes my intentions clearer.

  Alan DeKok.

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



From exim@www1.ietf.org  Wed Mar  3 18:00:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03169
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 18:00:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfLL-0003t4-57
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 17:59:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23Mxxn9014942
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 17:59:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfLL-0003sv-0a
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 17:59:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03114
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 17:59:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfLI-0002ny-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 17:59:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyfKG-0002dF-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 17:58:53 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfJT-0002UM-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 17:58:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfJS-0003Nt-Ej; Wed, 03 Mar 2004 17:58:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfJJ-0003Ms-KG
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 17:57:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03060
	for <asrg@ietf.org>; Wed, 3 Mar 2004 17:57:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfJG-0002TX-00
	for asrg@ietf.org; Wed, 03 Mar 2004 17:57:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyfIR-0002L4-00
	for asrg@ietf.org; Wed, 03 Mar 2004 17:56:59 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfHn-0002BU-00
	for asrg@ietf.org; Wed, 03 Mar 2004 17:56:19 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i23MuHjM002736;
        Wed, 3 Mar 2004 14:56:17 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GHS761N1>; Wed, 3 Mar 2004 14:56:17 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A1912@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Dave Crocker'" <dhc@dcrocker.net>, Alan DeKok <aland@ox.org>
Cc: asrg@ietf.org
Subject: RE: [Asrg] Its all over for Challenge Response
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Wed, 3 Mar 2004 14:56:14 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

> AD>   This is not an argument.  Those users are using MUAs.  
> The authors
> AD> of those MUAs can do the work, and add a checkbox that 
> the idiot users
> AD> can use.
> 
> For the IETF, it is the _only_ argument.  Folks forget that we exist
> to produce specifications that get used.  Not "implemented" but
> actually used.

The IETF has been spectacularly unsucessful by this criteria. The
vast majority of the 'IETF' specifications predate the first meeting.
HTTP, SSL, LDAP were all successful before work started in the IETF.

Only in a very small number of cases has there been any success in
changing an already deployed protocol. This is not intrinsic to the
problem though, it is a fixable feature of the way the Internet is put
together. 


Thinking about deployment is important, but there is not a single
specification that does not require some change somewhere - otherwise
there would be no need for the spec.


> For an example of the "it got implemented" criterion that ignored the
> "it gets used" criterion, please refer to the history of OSI.

The history of OSI shows less than many claim. OSI came into existence
because European computer makers and the US government feared that 
IBM's SNA would become a defacto proprietary standard in the same way 
that the IBM PC did.

OSI failed for one reason alone, it missed the window of opportunity by
a couple of years. The Web killed OSI, the Internet and the IETF had
nothing to do with it. Once the Internet became the 'anyone but IBM'
candidate the support of pretty much everyone apart from the US
civil service switched to it. And yes there are folk in the USG
still plotting the deployment of X.500

The Internet is under-engineered, OSI is over-engineered. Neither has
any real impact on the success of a computer protocol. The second,
third and even fourth rate succeed all the time. OSI is tame 
compared to the protocols used in telephony.

 
> That is my point.  The nature and amount of incentive needed depends
> on the cost and the benefit (along with a few other factors, of
> course.) Any scheme that proposed massive change needs to pay quite a
> bit of attention to the both of these.  That requires detailed
> thinking, not a simple handwave.

It is not the benefit that matters, it is the perceived benefit. The
potential benefit does not move the market unless people have a very strong
belief that it will succeed and that there is an advantage to being 
an early adopter.


> AD>   And we already know that people who won't upgrade won't be doing
> AD> anything to help solve the spam problem.  We can ignore 
> any arguments
> AD> about their needs, as they've already made their choice 
> to accept the
> AD> current situation.
> 
> That line of thinking is quite popular in the technical community, and
> often even in the management community.  It accounts for a massive
> number of companies' failures.  As well as standards' failures.

The spam problem will not drive the deployment of any authentication
mechanism. That is not the problem they are designed to solve.

The problem they do solve is the 'get my email through' problem. This
is at least as large as the spam problem. I just got an email from someone
who owes me $1390 I did not know had not been paid. It had been marked
as spam.

		Phill


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



From exim@www1.ietf.org  Wed Mar  3 18:14:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04410
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 18:14:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfYp-0001D2-7h
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 18:13:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23NDtnb004642
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 18:13:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfYp-0001Cn-1l
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 18:13:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04358
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 18:13:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfYm-00059w-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 18:13:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyfXq-00050q-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 18:12:55 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfX4-0004rl-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 18:12:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfWz-0000P2-Au; Wed, 03 Mar 2004 18:12:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfWu-0000Ni-N0
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 18:11:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04165
	for <asrg@ietf.org>; Wed, 3 Mar 2004 18:11:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfWr-0004qm-00
	for asrg@ietf.org; Wed, 03 Mar 2004 18:11:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyfVz-0004hN-00
	for asrg@ietf.org; Wed, 03 Mar 2004 18:10:59 -0500
Received: from pigeon.verisign.com ([65.205.251.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfVP-0004Xp-00
	for asrg@ietf.org; Wed, 03 Mar 2004 18:10:23 -0500
Received: from mou1wnexc01.vcorp.ad.vrsn.com (verisign.com [65.205.251.53])
        by pigeon.verisign.com (8.12.11/) with ESMTP id i23NAM8I027300;
        Wed, 3 Mar 2004 15:10:22 -0800 (PST)
Received: by mou1wnexc01.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GHS7SYVK>; Wed, 3 Mar 2004 15:10:22 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A1913@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Alan DeKok'" <aland@ox.org>, asrg@ietf.org
Subject: RE: [Asrg] Its all over for Challenge Response 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Wed, 3 Mar 2004 15:10:21 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

>   SSH exists and has been widely deployed for years.  SMTP exists and
> has been widely deployed for years.  There is no need for additional
> standards work.  There is only a need for MUA authors to implement and
> deploy existing protocols.

STARTLS exists, is an approved standard and has been implemented in
Microsoft exchange along with pretty much every other mail server for 
years.

Incidentally STARTTLS is the most commonly used email encryption scheme
in use today. It is vastly more successful than PGP or S/MIME combined.

>   Nothing in that process requires input from the IETF or any other
> standards body.

Using SSH would require input. You have to know the other endpoint
supports SSH.


Digital certificates provide the accreditation component that is the
principle value in the only two cryptography schemes that have been
an unqualified success - SSL driven e-commerce and the authenticode scheme.

Sure there are people who claim there is no value from certificates 
that cannot be provided through a web of trust. The real issue is 
accountability. I designed my procedures so that each employee in the 
CA center is accountable for their actions, as a company we agree to
be held accountable within the bounds of predefined limits to the
parties relying on our certificates.


Sure you can build peer-to-peer type networks. But peer-to-peer trust
networks are complex and unweildy. That is why pretty much every 
B2B scheme that starts as bilateral relationships quickly moves
to a Value Added Network model, you authenticate to the hub and
then you can talk to anyone.

The Web has peer to peer aspects, eliminating the central hub was 
what made the network hypertext model work. But look at Google and
you will see that the search model is not peer to peer. 

		Phill

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



From exim@www1.ietf.org  Wed Mar  3 18:29:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06285
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 18:29:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfnN-0003uW-MS
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 18:28:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23NSvOs015026
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 18:28:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyfnM-0003uC-6t
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 18:28:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06243
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 18:28:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfnJ-0000Tr-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 18:28:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyfmN-0000LK-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 18:27:56 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayflg-0000CM-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 18:27:12 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Ayflg-0000Qt-Vk
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 18:27:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyflV-0003dt-4M; Wed, 03 Mar 2004 18:27:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyflM-0003d3-1h
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 18:26:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06183
	for <asrg@ietf.org>; Wed, 3 Mar 2004 18:26:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyflJ-0000Ah-00
	for asrg@ietf.org; Wed, 03 Mar 2004 18:26:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyfkL-00000G-00
	for asrg@ietf.org; Wed, 03 Mar 2004 18:25:49 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyfjQ-0007Ri-00
	for asrg@ietf.org; Wed, 03 Mar 2004 18:24:52 -0500
Received: from mbaugher-w2k07.cisco.com (sjc-vpn1-782.cisco.com [10.21.99.14])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i23NOJLN024949;
	Wed, 3 Mar 2004 15:24:20 -0800 (PST)
Message-Id: <6.0.0.22.2.20040303152239.038acd78@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Mark Baugher <mbaugher@cisco.com>
Subject: RE: [Asrg] Its all over for Challenge Response 
Cc: asrg@ietf.org
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A1913@mou1wnexm05.vcorp.a
 d.vrsn.com>
References: <C6DDA43B91BFDA49AA2F1E473732113E0A1913@mou1wnexm05.vcorp.ad.vrsn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 15:24:17 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

Phillip,

At 03:10 PM 3/3/2004, Hallam-Baker, Phillip wrote:
> >   SSH exists and has been widely deployed for years.  SMTP exists and
> > has been widely deployed for years.  There is no need for additional
> > standards work.  There is only a need for MUA authors to implement and
> > deploy existing protocols.
>
>STARTLS exists, is an approved standard and has been implemented in
>Microsoft exchange along with pretty much every other mail server for
>years.
>
>Incidentally STARTTLS is the most commonly used email encryption scheme
>in use today. It is vastly more successful than PGP or S/MIME combined.

How could that be since STARTLS is hop-by-hop and not end-to-end?  This is 
comparing apples and oranges, isn't it?

Mark


> >   Nothing in that process requires input from the IETF or any other
> > standards body.
>
>Using SSH would require input. You have to know the other endpoint
>supports SSH.
>
>
>Digital certificates provide the accreditation component that is the
>principle value in the only two cryptography schemes that have been
>an unqualified success - SSL driven e-commerce and the authenticode scheme.
>
>Sure there are people who claim there is no value from certificates
>that cannot be provided through a web of trust. The real issue is
>accountability. I designed my procedures so that each employee in the
>CA center is accountable for their actions, as a company we agree to
>be held accountable within the bounds of predefined limits to the
>parties relying on our certificates.
>
>
>Sure you can build peer-to-peer type networks. But peer-to-peer trust
>networks are complex and unweildy. That is why pretty much every
>B2B scheme that starts as bilateral relationships quickly moves
>to a Value Added Network model, you authenticate to the hub and
>then you can talk to anyone.
>
>The Web has peer to peer aspects, eliminating the central hub was
>what made the network hypertext model work. But look at Google and
>you will see that the search model is not peer to peer.
>
>                 Phill
>
>_______________________________________________
>Asrg mailing list
>Asrg@ietf.org
>https://www1.ietf.org/mailman/listinfo/asrg



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



From exim@www1.ietf.org  Wed Mar  3 19:11:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08740
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 19:11:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AygSG-0007vs-0x
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 19:11:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i240BBV4030488
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 19:11:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AygSF-0007vf-P1
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 19:11:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA08598
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 19:11:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AygSC-0000Pk-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 19:11:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AygQz-00005x-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 19:09:54 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AygPw-0007WX-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 19:08:48 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AygHg-0001V2-Ec
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 19:00:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AygHU-0006cx-55; Wed, 03 Mar 2004 19:00:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AygCc-0006BL-9v
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 18:55:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08163
	for <asrg@ietf.org>; Wed, 3 Mar 2004 18:54:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AygCZ-0005bL-00
	for asrg@ietf.org; Wed, 03 Mar 2004 18:54:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AygBa-0005Ry-00
	for asrg@ietf.org; Wed, 03 Mar 2004 18:53:59 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AygAn-0005H2-00
	for asrg@ietf.org; Wed, 03 Mar 2004 18:53:09 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AygAl-0003rz-00; Wed, 03 Mar 2004 18:53:07 -0500
Received: from [68.24.225.2] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AygAi-0005yS-00; Wed, 03 Mar 2004 18:53:07 -0500
Message-ID: <40466FD9.70801@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: "'Alan DeKok'" <aland@ox.org>, asrg@ietf.org
Subject: Re: [Asrg] Its all over for Challenge Response
References: <C6DDA43B91BFDA49AA2F1E473732113E0A1913@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A1913@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 18:52:57 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> Digital certificates provide the accreditation component that is the
> principle value in the only two cryptography schemes that have been
> an unqualified success - SSL driven e-commerce and the authenticode scheme.
> 
> Sure there are people who claim there is no value from certificates 
> that cannot be provided through a web of trust. The real issue is 
> accountability. I designed my procedures so that each employee in the 
> CA center is accountable for their actions, as a company we agree to
> be held accountable within the bounds of predefined limits to the
> parties relying on our certificates.
> 
> Sure you can build peer-to-peer type networks. But peer-to-peer trust
> networks are complex and unweildy. That is why pretty much every 
> B2B scheme that starts as bilateral relationships quickly moves
> to a Value Added Network model, you authenticate to the hub and
> then you can talk to anyone.
> 
> The Web has peer to peer aspects, eliminating the central hub was 
> what made the network hypertext model work. But look at Google and
> you will see that the search model is not peer to peer. 
> 

If so, what kind of trust systems would work in email?

Yakov


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



From exim@www1.ietf.org  Wed Mar  3 21:01:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15156
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 21:01:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyiAf-0002OO-0D
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 21:01:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i242188I009190
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 21:01:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyiAe-0002O9-RP
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 21:01:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15005
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 21:01:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyiAc-0004t3-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 21:01:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayi8q-0004Pe-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 20:59:17 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayi7k-0004Dl-01
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 20:58:08 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Ayi45-0003mx-2C
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 20:54:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayi3m-0001hZ-41; Wed, 03 Mar 2004 20:54:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayi38-0001bl-3M
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 20:53:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14438
	for <asrg@ietf.org>; Wed, 3 Mar 2004 20:53:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayi35-0003GR-00
	for asrg@ietf.org; Wed, 03 Mar 2004 20:53:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayi2D-00033F-00
	for asrg@ietf.org; Wed, 03 Mar 2004 20:52:25 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayi1X-0002qb-00
	for asrg@ietf.org; Wed, 03 Mar 2004 20:51:43 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i241pf7u028041;
        Wed, 3 Mar 2004 17:51:41 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GHS76X2M>; Wed, 3 Mar 2004 17:51:41 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A1918@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Mark Baugher'" <mbaugher@cisco.com>,
        "Hallam-Baker, Phillip"
	 <pbaker@verisign.com>
Cc: asrg@ietf.org
Subject: RE: [Asrg] Its all over for Challenge Response 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Wed, 3 Mar 2004 17:51:36 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

> How could that be since STARTLS is hop-by-hop and not 
> end-to-end?  This is comparing apples and oranges, isn't it?

No, end-to-end security is a bogus concept. 

Sure it looks great in theory, but the cost of deploying all
those end user certificates is simply beyond most enterprises.

If you look at the problem from a risk assement point of view
it is entirely reasonable to secure email internaly by using
SSL to secure communication with the email server and then to use
SSL to secure the hop over the Internet where the email is 
most likely to be intercepted.

Sure there is a residual risk, my mail server can be compromised.
But the cost of deploying SSL based encryption is small, the
benefit is huge. It does not hurt to deploy both. The big downside
of SSL is not that it is hop-by-hop, the real problem is that
you cannot be confident it will be applied.

Sure they might be apples and oranges. But if you put apples 
and oranges together you have a fruit salad.

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



From exim@www1.ietf.org  Wed Mar  3 21:11:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15952
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 21:11:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyiKO-0003dy-Nn
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 21:11:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i242BCSf014000
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 21:11:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyiKO-0003dj-Iv
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 21:11:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15804
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 21:11:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyiKL-0006uy-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 21:11:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyiJS-0006gB-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 21:10:15 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyiIT-0006U4-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 21:09:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyiIH-0003M0-89; Wed, 03 Mar 2004 21:09:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyiEU-0002qg-7F
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 21:05:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15571
	for <asrg@ietf.org>; Wed, 3 Mar 2004 21:05:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyiER-0005pY-00
	for asrg@ietf.org; Wed, 03 Mar 2004 21:05:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyiDZ-0005fw-00
	for asrg@ietf.org; Wed, 03 Mar 2004 21:04:10 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyiCu-0005Vl-00
	for asrg@ietf.org; Wed, 03 Mar 2004 21:03:28 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AyiCr-0006aF-00; Wed, 03 Mar 2004 21:03:25 -0500
Received: from [68.24.225.2] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AyiCp-0001Fi-00; Wed, 03 Mar 2004 21:03:25 -0500
Message-ID: <40468E63.5080403@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: "'Mark Baugher'" <mbaugher@cisco.com>, asrg@ietf.org
Subject: Re: [Asrg] Its all over for Challenge Response
References: <C6DDA43B91BFDA49AA2F1E473732113E0A1918@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A1918@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 21:03:15 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hallam-Baker, Phillip wrote:
>>How could that be since STARTLS is hop-by-hop and not 
>>end-to-end?  This is comparing apples and oranges, isn't it?
> 
> 
> No, end-to-end security is a bogus concept. 
> 
> Sure it looks great in theory, but the cost of deploying all
> those end user certificates is simply beyond most enterprises.
> 

You could do end to end between MTAs via multiple hops as per RFC 3183. 
But STARTTLS is *always* hop-to-hop between MTAs.

Yakov

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



From exim@www1.ietf.org  Wed Mar  3 21:37:52 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18543
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 21:37:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayijk-0000lo-6u
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 21:37:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i242bNwi002951
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 21:37:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayijj-0000lU-9D
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 21:37:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18483
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 21:37:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayijg-00055y-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 21:37:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayiic-0004qH-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 21:36:15 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayihb-0004ZX-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 21:35:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyihV-0008Qf-IY; Wed, 03 Mar 2004 21:35:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayih5-0008NQ-2f
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 21:34:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18198
	for <asrg@ietf.org>; Wed, 3 Mar 2004 21:34:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayih2-0004Mh-00
	for asrg@ietf.org; Wed, 03 Mar 2004 21:34:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayig9-000470-00
	for asrg@ietf.org; Wed, 03 Mar 2004 21:33:41 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyifD-0003qJ-00
	for asrg@ietf.org; Wed, 03 Mar 2004 21:32:43 -0500
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (mailer3.verisign.com [65.205.251.55])
        by peacock.verisign.com (8.12.11/) with ESMTP id i242Wfcp016599;
        Wed, 3 Mar 2004 18:32:41 -0800 (PST)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GHS83QJF>; Wed, 3 Mar 2004 18:32:41 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A191B@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Yakov Shafranovich'" <research@solidmatrix.com>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'Mark Baugher'" <mbaugher@cisco.com>, asrg@ietf.org
Subject: RE: [Asrg] Its all over for Challenge Response
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Wed, 3 Mar 2004 18:32:34 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

> You could do end to end between MTAs via multiple hops as per 
> RFC 3183. 
> But STARTTLS is *always* hop-to-hop between MTAs.

If you were going to do end-to-end you would do S/MIME.

But then you have all those headers in the clear anyway so there
is still real value to using SSL.

		Phill

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



From exim@www1.ietf.org  Wed Mar  3 22:32:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21790
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 22:32:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayjan-00068P-5u
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 22:32:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i243WDlt023580
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 22:32:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayjan-00068F-0l
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 22:32:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21770
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 22:32:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayjaj-0000D1-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 22:32:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyjZu-00001h-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 22:31:18 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyjZ3-0007eW-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 22:30:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyjYh-0005v7-39; Wed, 03 Mar 2004 22:30:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyjV4-0005Vu-Uh
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 22:26:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21435
	for <asrg@ietf.org>; Wed, 3 Mar 2004 22:26:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyjV1-0006nV-00
	for asrg@ietf.org; Wed, 03 Mar 2004 22:26:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyjU2-0006cH-00
	for asrg@ietf.org; Wed, 03 Mar 2004 22:25:15 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyjTX-0006Rh-00
	for asrg@ietf.org; Wed, 03 Mar 2004 22:24:43 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AyjTY-0005ls-00
	for asrg@ietf.org; Wed, 03 Mar 2004 22:24:44 -0500
Received: from [68.24.225.2] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AyjTX-0007aw-00
	for asrg@ietf.org; Wed, 03 Mar 2004 22:24:44 -0500
Message-ID: <4046A16F.7010408@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 3b. SMTP Session Verification - LMAP BOF Jabber Logs posted
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 22:24:31 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The BoF took place this morning (or evening in US). The Jabber log is 
available here:

http://www.xmpp.org/ietf-logs/marid@ietf.xmpp.org/2004-03-03.html

Yakov

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



From exim@www1.ietf.org  Wed Mar  3 22:43:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22308
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 22:43:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyjlT-0007ev-DD
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 22:43:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i243hFp1029435
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 22:43:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyjlT-0007eg-4a
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 22:43:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22289
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 22:43:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyjlP-0002Aj-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 22:43:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyjkT-00020H-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 22:42:13 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayjjg-0001q1-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 22:41:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyjjJ-0007Rm-Gs; Wed, 03 Mar 2004 22:41:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyjEQ-0003lu-P2
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 22:09:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA20514
	for <asrg@ietf.org>; Wed, 3 Mar 2004 22:09:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyjEN-0003Ka-00
	for asrg@ietf.org; Wed, 03 Mar 2004 22:09:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyjDW-0003Az-00
	for asrg@ietf.org; Wed, 03 Mar 2004 22:08:11 -0500
Received: from pcls2.std.com ([192.74.137.142] helo=TheWorld.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyjCf-00031t-00
	for asrg@ietf.org; Wed, 03 Mar 2004 22:07:17 -0500
Received: from world.std.com (root@world-e.std.com [69.38.147.5])
	by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id i2437HV7027303;
	Wed, 3 Mar 2004 22:07:17 -0500
Received: (from bzs@localhost)
	by world.std.com (8.9.3/8.9.3) id WAA01816;
	Wed, 3 Mar 2004 22:07:17 -0500 (EST)
Message-Id: <200403040307.WAA01816@world.std.com>
From: Barry Shein <bzs@world.std.com>
To: asrg@ietf.org
Subject: [Asrg] Request for MS CID XML samples...
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/mail-archive/working-groups/asrg/>
Date: Wed, 3 Mar 2004 22:07:17 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


I realize that the "Caller ID for E-Mail" paper has some contrived
examples but I was hoping I could prod Microsoft and/or Sendmail to
work up and publish current examples of what their actual MS CID XML
records would look like right this minute if MS CID were in use.

It'd be interesting to see real-life examples for msn.net,
microsoft.com, and sendmail.com for study.

Thank you.

-- 
        -Barry Shein

Software Tool & Die    | bzs@TheWorld.com           | http://www.TheWorld.com
Purveyors to the Trade | Voice: 617-739-0202        | Login: 617-739-WRLD
The World              | Public Access Internet     | Since 1989     *oo*

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



From exim@www1.ietf.org  Wed Mar  3 23:06:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23964
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 23:06:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayk7g-0001oy-UW
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 23:06:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2446C85006994
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 23:06:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayk7g-0001oj-Eq
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 23:06:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23927
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 23:06:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayk7a-0006XC-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 23:06:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayk4z-000619-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 23:03:26 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayk3j-0005md-03
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 23:02:07 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1Ayjw2-0005Om-BV
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 22:54:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayjvs-0000Gm-JP; Wed, 03 Mar 2004 22:54:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayju7-0008Ne-T5
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 22:52:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23286
	for <asrg@ietf.org>; Wed, 3 Mar 2004 22:52:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayju4-0004FL-00
	for asrg@ietf.org; Wed, 03 Mar 2004 22:52:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyjtG-00045Z-00
	for asrg@ietf.org; Wed, 03 Mar 2004 22:51:18 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyjsZ-0003uj-00
	for asrg@ietf.org; Wed, 03 Mar 2004 22:50:35 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AyjsZ-0008RJ-00; Wed, 03 Mar 2004 22:50:35 -0500
Received: from [68.24.225.2] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AyjsY-0000HJ-00; Wed, 03 Mar 2004 22:50:35 -0500
Message-ID: <4046A77F.8020300@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Barry Shein <bzs@world.std.com>
CC: asrg@ietf.org
References: <200403040307.WAA01816@world.std.com>
In-Reply-To: <200403040307.WAA01816@world.std.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: Request for MS CID XML samples...
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 22:50:23 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Barry Shein wrote:
> I realize that the "Caller ID for E-Mail" paper has some contrived
> examples but I was hoping I could prod Microsoft and/or Sendmail to
> work up and publish current examples of what their actual MS CID XML
> records would look like right this minute if MS CID were in use.
> 
> It'd be interesting to see real-life examples for msn.net,
> microsoft.com, and sendmail.com for study.
> 
> Thank you.
> 

Barry,

Welcome back. The key is to look for "_ep.domain..." - the following are 
real life examples (as of 5 minutes ago):

1. For Hotmail:

_ep.hotmail.com text =

"<ep xmlns='http://ms.net/1' testing='true'><out><m><indirect>list1._ep.
hotmail.com</indirect><indirect>list2._ep.hotmail.com</indirect><indirect>list3.
_ep.hotmail.com</indirect></m></out></ep>"


2. For Microsoft:

_ep.microsoft.com       text =

"<ep xmlns='http://ms.net/1' testing='true'><out><m>"

"<mx/><a>213.199.128.160</a><a>213.199.128.145</a><a>207.46.71.29</a><a>
194.121.59.20</a><a>157.60.216.10</a><a>131.107.3.116</a><a>131.107.3.117</a><a>
131.107.3.100</a>"

"</m></out></ep>"

3. For Amazon:

_ep.amazon.com  text =

"<ep xmlns='http://ms.net/1' 
testing='true'><out><m><r>207.171.160.0/19</r></m></out></ep>"

Yakov

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



From exim@www1.ietf.org  Wed Mar  3 23:31:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25457
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 23:31:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AykVv-0004Pr-5q
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 23:31:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i244VFaB016969
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 23:31:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AykVu-0004Pc-W0
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 23:31:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25379
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 23:31:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AykVt-0003az-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 23:31:13 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AykUz-0003Mx-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 23:30:18 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AykU0-0003A0-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 23:29:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AykTl-00045t-Kl; Wed, 03 Mar 2004 23:29:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AykSy-00045J-LP
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 23:28:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25189
	for <asrg@ietf.org>; Wed, 3 Mar 2004 23:28:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AykSw-0002yN-00
	for asrg@ietf.org; Wed, 03 Mar 2004 23:28:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AykRz-0002on-00
	for asrg@ietf.org; Wed, 03 Mar 2004 23:27:12 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AykRg-0002es-00
	for asrg@ietf.org; Wed, 03 Mar 2004 23:26:52 -0500
Received: from mbaugher-w2k07.cisco.com (sjc-vpn3-56.cisco.com [10.21.64.56])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i244QJLN015447;
	Wed, 3 Mar 2004 20:26:20 -0800 (PST)
Message-Id: <6.0.0.22.2.20040303201031.03c8e910@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Mark Baugher <mbaugher@cisco.com>
Subject: RE: [Asrg] Its all over for Challenge Response 
Cc: asrg@ietf.org
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A1918@mou1wnexm05.vcorp.a
 d.vrsn.com>
References: <C6DDA43B91BFDA49AA2F1E473732113E0A1918@mou1wnexm05.vcorp.ad.vrsn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 20:26:17 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

Phill,

At 05:51 PM 3/3/2004, Hallam-Baker, Phillip wrote:
> > How could that be since STARTLS is hop-by-hop and not
> > end-to-end?  This is comparing apples and oranges, isn't it?
>
>No, end-to-end security is a bogus concept.

This statement is in the spirit of the list.


>Sure it looks great in theory, but the cost of deploying all
>those end user certificates is simply beyond most enterprises.

It seems to me that your pinning the apparent failure of X.509
PKI on the end-to-end security concept.

I use PGP Mail whenever I need authentication and encryption.
I consider it to be successful for my personal use.


>If you look at the problem from a risk assement point of view
>it is entirely reasonable to secure email internaly by using
>SSL to secure communication with the email server and then to use
>SSL to secure the hop over the Internet where the email is
>most likely to be intercepted.

There are two problems with this notion.  The first is that
various intermediate systems have access to the communication
to read and alter.  The second is that there is no guarantee
that any pair of intermediate systems actually secure the
hop between them.  The secure connection established by the
two systems is appropriate for their own security needs rather
than for the end-to-end traffic they convey over that connection.


>Sure there is a residual risk, my mail server can be compromised.
>But the cost of deploying SSL based encryption is small, the
>benefit is huge. It does not hurt to deploy both. The big downside
>of SSL is not that it is hop-by-hop, the real problem is that
>you cannot be confident it will be applied.

Yes, I agree.  And it would be completely unacceptable for
two communicating endpoints wanting integrity and confidentiality
of their communication.


>Sure they might be apples and oranges. But if you put apples
>and oranges together you have a fruit salad.

I do think STARTLS might have a role to play in antispam if
there were some scalable way to do the authorization.

Mark




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



From exim@www1.ietf.org  Wed Mar  3 23:56:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27481
	for <asrg-archive@odin.ietf.org>; Wed, 3 Mar 2004 23:56:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AykuA-0008Ce-LU
	for asrg-archive@odin.ietf.org; Wed, 03 Mar 2004 23:56:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i244uIEY031526
	for asrg-archive@odin.ietf.org; Wed, 3 Mar 2004 23:56:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AykuA-0008CP-F5
	for asrg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 23:56:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27373
	for <asrg-web-archive@ietf.org>; Wed, 3 Mar 2004 23:56:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayku8-000147-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 23:56:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayks9-0000W7-00
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 23:54:14 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aykr9-0000KL-01
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 23:53:11 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AykqL-0006Dd-Qt
	for asrg-web-archive@ietf.org; Wed, 03 Mar 2004 23:52:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aykq1-0007jO-3t; Wed, 03 Mar 2004 23:52:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aykp9-0007b6-8v
	for asrg@optimus.ietf.org; Wed, 03 Mar 2004 23:51:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA27236
	for <asrg@ietf.org>; Wed, 3 Mar 2004 23:51:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aykp7-00000g-00
	for asrg@ietf.org; Wed, 03 Mar 2004 23:51:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AykoA-0007eO-00
	for asrg@ietf.org; Wed, 03 Mar 2004 23:50:07 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyknG-0007Tv-00
	for asrg@ietf.org; Wed, 03 Mar 2004 23:49:10 -0500
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (mailer3.verisign.com [65.205.251.55])
        by peacock.verisign.com (8.12.11/) with ESMTP id i244n8MW005777;
        Wed, 3 Mar 2004 20:49:08 -0800 (PST)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GHS835SW>; Wed, 3 Mar 2004 20:49:08 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A191F@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Mark Baugher'" <mbaugher@cisco.com>,
        "Hallam-Baker, Phillip"
	 <pbaker@verisign.com>
Cc: asrg@ietf.org
Subject: RE: [Asrg] Its all over for Challenge Response 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
MIME-Version: 1.0
Content-Type: multipart/signed;
	micalg=SHA1;
	boundary="----=_NextPart_000_0040_01C4017A.1A5B5E90";
	protocol="application/x-pkcs7-signature"
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Wed, 3 Mar 2004 20:49:02 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

------=_NextPart_000_0040_01C4017A.1A5B5E90
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit


> >Sure it looks great in theory, but the cost of deploying all
> >those end user certificates is simply beyond most enterprises.
> 
> It seems to me that your pinning the apparent failure of X.509
> PKI on the end-to-end security concept.

No, SSL and Authenticode are tremendously successful, the best 
security we have on the Internet in fact. It is the email area
where we have failed - until we started to use STARTTLS.
 
> I use PGP Mail whenever I need authentication and encryption.
> I consider it to be successful for my personal use.

I don't consider PGP to be any more successfull, i get far more
S/MIME signed messages than PGP and that is ignoring the S/MIME
bias from PKIX and S/MIMe list membership. The vast majority
of MUAs support S/MIME and have done for years.

The failure has been getting the end users to participate.
it was just too hard.

> >If you look at the problem from a risk assement point of view
> >it is entirely reasonable to secure email internaly by using
> >SSL to secure communication with the email server and then to use
> >SSL to secure the hop over the Internet where the email is
> >most likely to be intercepted.
> 
> There are two problems with this notion.  The first is that
> various intermediate systems have access to the communication
> to read and alter.  

Sure, but that is irrelevant. Almost none of the email on the
internet is encrypted in any form. The vast majority of messages
that are encrypted use STARTTLS.

> The second is that there is no guarantee
> that any pair of intermediate systems actually secure the
> hop between them.  The secure connection established by the
> two systems is appropriate for their own security needs rather
> than for the end-to-end traffic they convey over that connection.

Again, wrong comparison. STARTTLS is a bicycle. It has nowhere 
near the power and capabilities that a tank offers. But it will
get you to your destination far faster than walking.

> >Sure they might be apples and oranges. But if you put apples
> >and oranges together you have a fruit salad.
> 
> I do think STARTLS might have a role to play in antispam if
> there were some scalable way to do the authorization.

The problem is advertising the fact you support STARTTLS in
the DNS.

it is not an authorization problem.

------=_NextPart_000_0040_01C4017A.1A5B5E90
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Disposition: attachment;
	filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIILizCCA6Yw
ggMPoAMCAQICEHWNgosXAgaqes2nmr0jsCgwDQYJKoZIhvcNAQEFBQAwgcExCzAJBgNVBAYTAlVT
MRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjE8MDoGA1UECxMzQ2xhc3MgMiBQdWJsaWMgUHJpbWFy
eSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEcyMTowOAYDVQQLEzEoYykgMTk5OCBWZXJpU2ln
biwgSW5jLiAtIEZvciBhdXRob3JpemVkIHVzZSBvbmx5MR8wHQYDVQQLExZWZXJpU2lnbiBUcnVz
dCBOZXR3b3JrMB4XDTk5MDIyNTAwMDAwMFoXDTA5MDIyNDIzNTk1OVowga0xFzAVBgNVBAoTDlZl
cmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUkwRwYDVQQLE0BV
c2UgaXMgc3ViamVjdCB0byB0ZXJtcyBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhLWty
IChjKTk5MSYwJAYDVQQDEx1WZXJpU2lnbiBDbGFzcyAyIFBlcnNvbm5lbCBDQTCBnzANBgkqhkiG
9w0BAQEFAAOBjQAwgYkCgYEApwRsD6Jyt0oGLvjXKSw0nYK8SJFKx6z56fy5WXixVcBTWLHPbxY7
wUnVy/RuzOHMy7XHLk6IqjTpttBbfD4VVzThGLz/3fWvZ1kgCuU96oiKQNKaiRMpqbbV26d+4ec3
JJP9lHRNeuQybUzoXBaXr92S2WaKFGbk6loDqD1f+wsCAwEAAaOBsDCBrTARBglghkgBhvhCAQEE
BAMCAQYwDwYDVR0TBAgwBgEB/wIBATALBgNVHQ8EBAMCAQYwRAYDVR0gBD0wOzA5BgtghkgBhvhF
AQcXAjAqMCgGCCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMDQGA1UdHwQt
MCswKaAnoCWGI2h0dHA6Ly9jcmwudmVyaXNpZ24uY29tL3BjYTItZzIuY3JsMA0GCSqGSIb3DQEB
BQUAA4GBAFJetpXbb3ymfgX2VIU72RqKRVlffMJl7vlA3lRux5ASgCQ8QKNj7IUf9R4bico9juNL
Lt+cG+6O51S5VpP+29HERPjLnECdkqzFzgTxEUbsiLyYyIwhfTeczGu9NKWTjL2cOR3qp5wazfVH
bSxzE2NqIS5afYd9vEy+8scDwoy2MIIDwDCCAymgAwIBAgIQSsgAA2Nh1BUDFvGGNpu3zTANBgkq
hkiG9w0BAQUFADCBrTEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWdu
IFRydXN0IE5ldHdvcmsxSTBHBgNVBAsTQFVzZSBpcyBzdWJqZWN0IHRvIHRlcm1zIGF0IGh0dHBz
Oi8vd3d3LnZlcmlzaWduLmNvbS9ycGEta3IgKGMpOTkxJjAkBgNVBAMTHVZlcmlTaWduIENsYXNz
IDIgUGVyc29ubmVsIENBMB4XDTk5MDIyNTAwMDAwMFoXDTA5MDIyMzIzNTk1OVowgawxFzAVBgNV
BAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUkwRwYD
VQQLE0BVc2UgaXMgc3ViamVjdCB0byB0ZXJtcyBhdCBodHRwczovL3d3dy52ZXJpc2lnbi5jb20v
cnBhLWtyIChjKTk5MSUwIwYDVQQDExxWZXJpU2lnbiBDbGFzcyAyIEVtcGxveWVlIENBMIGfMA0G
CSqGSIb3DQEBAQUAA4GNADCBiQKBgQDAitGHYaLqMANVawg28Jf6GlQ1JB/ofZ3Iw3PT2Eb1kS3Z
OO2U17Amcyrel1BN/yIcvXAAmAxYKrGkco+lufctfGDjtd/pfU4hIWHV/DtUyaQJnLsi+aK6cGFP
hkai/QVk7Ao/plh2V7sWc0R88KUNl8BspvFjCCWxBBeVoI3+fwIDAQABo4HfMIHcMCkGA1UdEQQi
MCCkHjAcMRowGAYDVQQDExFQcml2YXRlTGFiZWwxLTExODARBglghkgBhvhCAQEEBAMCAQYwDwYD
VR0TBAgwBgEB/wIBADALBgNVHQ8EBAMCAQYwRAYDVR0gBD0wOzA5BgtghkgBhvhFAQcXAjAqMCgG
CCsGAQUFBwIBFhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vcnBhMDgGA1UdHwQxMC8wLaAroCmG
J2h0dHA6Ly9jcmwudmVyaXNpZ24uY29tL1ZTQ2xhc3MySW50LmNybDANBgkqhkiG9w0BAQUFAAOB
gQA2GP0zYNYX0wS12FRfUhrlkggo9KJA2sNbjBqGl++uohX+bMTOL8gByjO+8nlYM5eXkkVwWk4o
Hd33wYhOG4dXAj2TJdl+TnI1iUkXs7l3L20O+aSIJcHOdnNlaQWTd+f9k5YYOE1YbHqd6NKb6NDb
if1JwnUEA5el1JaB2CNB8DCCBBkwggOCoAMCAQICED71tdHM9i4jiA298PD00EgwDQYJKoZIhvcN
AQEEBQAwgawxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVz
dCBOZXR3b3JrMUkwRwYDVQQLE0BVc2UgaXMgc3ViamVjdCB0byB0ZXJtcyBhdCBodHRwczovL3d3
dy52ZXJpc2lnbi5jb20vcnBhLWtyIChjKTk5MSUwIwYDVQQDExxWZXJpU2lnbiBDbGFzcyAyIEVt
cGxveWVlIENBMB4XDTAzMDMwNjAwMDAwMFoXDTA0MDMwNTIzNTk1OVowbTERMA8GA1UEChMIVkVS
SVNJR04xCzAJBgNVBAsTAkhRMRMwEQYDVQQDEwpSZWNpcGllbnRzMTYwNAYDVQQDEy1wYmFrZXIg
KEhhbGxhbS1CYWtlciBQaGlsbGlwLCBWZXJpU2lnbiwgSW5jLikwgZ8wDQYJKoZIhvcNAQEBBQAD
gY0AMIGJAoGBALnb2fFyN844Cl9FoNaBDI8P+O4JliUWbYoS/H5ebiL9BiGWuVAXoo1TAaB/SHU6
Sw12kMz9z7gL+HW09pG9kofKMikS3baa49tG5t/Ap7wOnVNmLgelD5d/JuYi3d5J94N9qh2krJqP
auD5FjEbnTQ/Op2NHQzivxnE+g0cdDLJAgMBAAGjggF4MIIBdDAJBgNVHRMEAjAAMFkGA1UdHwRS
MFAwTqBMoEqGSGh0dHA6Ly9vbnNpdGVjcmwudmVyaXNpZ24uY29tL1ZlcmlTaWduSW5jRXhjaGFu
Z2VFbXBsb3llZXMvTGF0ZXN0Q1JMLmNybDALBgNVHQ8EBAMCBaAwHgYDVR0RBBcwFYETcGJha2Vy
QHZlcmlzaWduLmNvbTCBrAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcC
ARYcaHR0cHM6Ly93d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWdu
LCBJbmMuMAMCAQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0
ZC4gKGMpOTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMB0GA1UdJQQWMBQGCCsGAQUFBwME
BggrBgEFBQcDAjANBgkqhkiG9w0BAQQFAAOBgQCi33oiw4urer1XI46PtYSjUD2W43Q+Ez8T9XJo
Ewtc3mfUOuEw/PAH7VU3pLjUm6QfGe6W3xRzedAhAWzG1mWKK5vAq4Nnu8tpIV14PdxeXfKWM1Z0
Jw/1MHijGcoqLU9i3a1HYz/pF2A7/mibKe8Le+nJXV5q+XSAaL7K1ZcV3zGCAvgwggL0AgEBMIHB
MIGsMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0
d29yazFJMEcGA1UECxNAVXNlIGlzIHN1YmplY3QgdG8gdGVybXMgYXQgaHR0cHM6Ly93d3cudmVy
aXNpZ24uY29tL3JwYS1rciAoYyk5OTElMCMGA1UEAxMcVmVyaVNpZ24gQ2xhc3MgMiBFbXBsb3ll
ZSBDQQIQPvW10cz2LiOIDb3w8PTQSDAJBgUrDgMCGgUAoIIBjDAYBgkqhkiG9w0BCQMxCwYJKoZI
hvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0wNDAzMDQwNDQ5MDFaMCMGCSqGSIb3DQEJBDEWBBQBmPX3
N/m6LUfDVqWvCHtku+ZZ+TBYBgkqhkiG9w0BCQ8xSzBJMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMC
AgIAgDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDAHBgUrDgMCGjAKBggqhkiG9w0CBTCB0gYJKwYB
BAGCNxAEMYHEMIHBMIGsMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFJMEcGA1UECxNAVXNlIGlzIHN1YmplY3QgdG8gdGVybXMgYXQgaHR0
cHM6Ly93d3cudmVyaXNpZ24uY29tL3JwYS1rciAoYyk5OTElMCMGA1UEAxMcVmVyaVNpZ24gQ2xh
c3MgMiBFbXBsb3llZSBDQQIQPvW10cz2LiOIDb3w8PTQSDANBgkqhkiG9w0BAQEFAASBgDsYqyZx
o0CKMeOzv0FMo5tKQ8+RlQnaN91x0xfUJwLXCyoHTsqSnR0aOCUa5BPevN+JmKBXgWMRTE1uI/xa
YpCRpsTJ7RVmp57jGCFMC2gEew28qoKq7BcJJgv6qGZNj1kZwdSxayO0jKsJjLebihIU3qE3PGJl
G6TGsLPLfxIEAAAAAAAA

------=_NextPart_000_0040_01C4017A.1A5B5E90--


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



From exim@www1.ietf.org  Thu Mar  4 01:13:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03724
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 01:13:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aym64-0001zD-N1
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 01:12:40 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i246Cevc007629
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 01:12:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aym64-0001yy-FO
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 01:12:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA03691
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 01:12:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aym61-0001Gc-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 01:12:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aym4r-00010d-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 01:11:26 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aym3k-0000lG-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 01:10:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aym3X-00011i-3i; Thu, 04 Mar 2004 01:10:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aylvy-00081c-8k
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 01:02:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02314
	for <asrg@ietf.org>; Thu, 4 Mar 2004 01:02:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aylvv-0006LS-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:02:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayluq-000660-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:01:05 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayltp-0005oD-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:00:01 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1Ayltl-0004U6-00; Thu, 04 Mar 2004 00:59:57 -0500
Received: from [68.24.225.2] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1Ayltk-0004N9-00; Thu, 04 Mar 2004 00:59:57 -0500
Message-ID: <4046C5CF.3090206@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: "'Mark Baugher'" <mbaugher@cisco.com>, asrg@ietf.org
References: <C6DDA43B91BFDA49AA2F1E473732113E0A191F@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A191F@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 3b. SMTP Session Verification - STARTTLS
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/mail-archive/working-groups/asrg/>
Date: Thu, 04 Mar 2004 00:59:43 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

[was Re: [Asrg] Its all over for Challenge Response]

Hallam-Baker, Phillip wrote:
>>>Sure they might be apples and oranges. But if you put apples
>>>and oranges together you have a fruit salad.
>>
>>I do think STARTLS might have a role to play in antispam if
>>there were some scalable way to do the authorization.
> 
> 
> The problem is advertising the fact you support STARTTLS in
> the DNS.
> 
> it is not an authorization problem.

The SMTP clients and servers exchange that information during the EHLO 
session of the SMTP transaction. Why do you need to advertise that via DNS?

Leaving all of this aside, how will the use of TLS with SMTP help 
resolve the spam problem?

Yakov

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



From exim@www1.ietf.org  Thu Mar  4 01:55:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06818
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 01:55:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AymlG-0007LB-I9
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 01:55:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i246tEtm028211
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 01:55:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AymlG-0007Kw-DI
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 01:55:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06795
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 01:55:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AymlD-0002Hh-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 01:55:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AymkG-00026V-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 01:54:12 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AymjI-0001v1-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 01:53:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aymj7-00078x-EM; Thu, 04 Mar 2004 01:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aymie-00077q-UW
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 01:52:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06632
	for <asrg@ietf.org>; Thu, 4 Mar 2004 01:52:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aymib-0001kW-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:52:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aymhi-0001YL-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:51:34 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aymgu-0001K4-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:50:44 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
  by sj-iport-5.cisco.com with ESMTP; 03 Mar 2004 22:50:28 -0800
Received: from mbaugher-w2k07.cisco.com (sjc-vpn1-905.cisco.com [10.21.99.137])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i246oCD2015077;
	Wed, 3 Mar 2004 22:50:13 -0800 (PST)
Message-Id: <6.0.0.22.2.20040303223327.03a7bf68@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Mark Baugher <mbaugher@cisco.com>
Subject: RE: [Asrg] Its all over for Challenge Response 
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>, asrg@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 22:50:10 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

At 10:32 PM 3/3/2004, Mark Baugher wrote:
>At 08:49 PM 3/3/2004, Hallam-Baker, Phillip wrote:
>>
>> > >Sure it looks great in theory, but the cost of deploying all
>> > >those end user certificates is simply beyond most enterprises.
>> >
>> > It seems to me that your pinning the apparent failure of X.509
>> > PKI on the end-to-end security concept.
>>
>>No, SSL and Authenticode are tremendously successful, the best
>>security we have on the Internet in fact.

You shifted the argument.  I said "PKI" and you said "SSL" and
they are not the same thing, are they?

>>It is the email area
>>where we have failed - until we started to use STARTTLS.
>>
>> > I use PGP Mail whenever I need authentication and encryption.
>> > I consider it to be successful for my personal use.
>>
>>I don't consider PGP to be any more successfull, i get far more
>>S/MIME signed messages than PGP and that is ignoring the S/MIME
>>bias from PKIX and S/MIMe list membership. The vast majority
>>of MUAs support S/MIME and have done for years.

So what?  The vast majority of MUAs support PGP as well. And I don't
think you get far more S/MIME signed messages than PGP signed messages
from the ASRG lists.


>>The failure has been getting the end users to participate.
>>it was just too hard.
>>
>> > >If you look at the problem from a risk assement point of view
>> > >it is entirely reasonable to secure email internaly by using
>> > >SSL to secure communication with the email server and then to use
>> > >SSL to secure the hop over the Internet where the email is
>> > >most likely to be intercepted.
>> >
>> > There are two problems with this notion.  The first is that
>> > various intermediate systems have access to the communication
>> > to read and alter.
>>
>>Sure, but that is irrelevant. Almost none of the email on the
>>internet is encrypted in any form. The vast majority of messages
>>that are encrypted use STARTTLS.

RFC 3207 did not intend STARTLS to serve to protect user's email.
That's not what it's for.  Users who need email confidentiality
need confidentiality from interlopers who are most likely to have access
to their messages such as the mail operator.


>> > The second is that there is no guarantee
>> > that any pair of intermediate systems actually secure the
>> > hop between them.  The secure connection established by the
>> > two systems is appropriate for their own security needs rather
>> > than for the end-to-end traffic they convey over that connection.
>>
>>Again, wrong comparison. STARTTLS is a bicycle. It has nowhere
>>near the power and capabilities that a tank offers. But it will
>>get you to your destination far faster than walking.
>>
>> > >Sure they might be apples and oranges. But if you put apples
>> > >and oranges together you have a fruit salad.
>> >
>> > I do think STARTLS might have a role to play in antispam if
>> > there were some scalable way to do the authorization.
>>
>>The problem is advertising the fact you support STARTTLS in
>>the DNS.

See section 3 of RFC 3207.


>>it is not an authorization problem.

There is always an authorization problem.

Mark






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



From exim@www1.ietf.org  Thu Mar  4 01:58:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06999
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 01:58:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aymo8-0007fy-VU
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 01:58:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i246wCG2029500
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 01:58:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aymo8-0007fj-R6
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 01:58:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06973
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 01:58:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aymo5-0002o5-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 01:58:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aymn5-0002cs-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 01:57:08 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aymm5-0002NJ-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 01:56:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aymm0-0007N5-He; Thu, 04 Mar 2004 01:56:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AymlE-0007Kr-KG
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 01:55:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06792
	for <asrg@ietf.org>; Thu, 4 Mar 2004 01:55:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AymlB-0002HP-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:55:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AymkD-000264-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:54:09 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AymjF-0001li-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:53:09 -0500
Received: from mbaugher-w2k07.cisco.com (sjc-vpn1-905.cisco.com [10.21.99.137])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i246qaLN014934;
	Wed, 3 Mar 2004 22:52:37 -0800 (PST)
Message-Id: <6.0.0.22.2.20040303223327.03a7bf68@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Mark Baugher <mbaugher@cisco.com>
Subject: RE: [Asrg] Its all over for Challenge Response 
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>, asrg@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 22:50:10 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

Phill,

At 10:32 PM 3/3/2004, Mark Baugher wrote:
>At 08:49 PM 3/3/2004, Hallam-Baker, Phillip wrote:
>>
>> > >Sure it looks great in theory, but the cost of deploying all
>> > >those end user certificates is simply beyond most enterprises.
>> >
>> > It seems to me that your pinning the apparent failure of X.509
>> > PKI on the end-to-end security concept.
>>
>>No, SSL and Authenticode are tremendously successful, the best
>>security we have on the Internet in fact.

You shifted the argument.  I said "PKI" and you said "SSL" and
they are not the same thing, are they?

>>It is the email area
>>where we have failed - until we started to use STARTTLS.
>>
>> > I use PGP Mail whenever I need authentication and encryption.
>> > I consider it to be successful for my personal use.
>>
>>I don't consider PGP to be any more successfull, i get far more
>>S/MIME signed messages than PGP and that is ignoring the S/MIME
>>bias from PKIX and S/MIMe list membership. The vast majority
>>of MUAs support S/MIME and have done for years.

So what?  The vast majority of MUAs support PGP as well. And I don't
think you get far more S/MIME signed messages than PGP signed messages
from the ASRG lists.


>>The failure has been getting the end users to participate.
>>it was just too hard.
>>
>> > >If you look at the problem from a risk assement point of view
>> > >it is entirely reasonable to secure email internaly by using
>> > >SSL to secure communication with the email server and then to use
>> > >SSL to secure the hop over the Internet where the email is
>> > >most likely to be intercepted.
>> >
>> > There are two problems with this notion.  The first is that
>> > various intermediate systems have access to the communication
>> > to read and alter.
>>
>>Sure, but that is irrelevant. Almost none of the email on the
>>internet is encrypted in any form. The vast majority of messages
>>that are encrypted use STARTTLS.

RFC 3207 did not intend STARTLS to serve to protect user's email.
That's not what it's for.  Users who need email confidentiality
need confidentiality from interlopers who are most likely to have access
to their messages such as the mail operator.


>> > The second is that there is no guarantee
>> > that any pair of intermediate systems actually secure the
>> > hop between them.  The secure connection established by the
>> > two systems is appropriate for their own security needs rather
>> > than for the end-to-end traffic they convey over that connection.
>>
>>Again, wrong comparison. STARTTLS is a bicycle. It has nowhere
>>near the power and capabilities that a tank offers. But it will
>>get you to your destination far faster than walking.
>>
>> > >Sure they might be apples and oranges. But if you put apples
>> > >and oranges together you have a fruit salad.
>> >
>> > I do think STARTLS might have a role to play in antispam if
>> > there were some scalable way to do the authorization.
>>
>>The problem is advertising the fact you support STARTTLS in
>>the DNS.

See section 3 of RFC 3207.


>>it is not an authorization problem.

There is always an authorization problem.

Mark






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



From exim@www1.ietf.org  Thu Mar  4 02:07:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA16350
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 02:07:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aymwx-0002KD-HV
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 02:07:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2477JLr008923
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 02:07:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aymwv-0002Jd-VE
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 02:07:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA15660
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 02:07:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aymws-0004rt-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 02:07:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aymvw-0004ea-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 02:06:16 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aymv1-0004R7-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 02:05:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aymuk-0001D5-Uy; Thu, 04 Mar 2004 02:05:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AymtI-0000eO-0J
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 02:03:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11307
	for <asrg@ietf.org>; Thu, 4 Mar 2004 02:03:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AymtE-00040q-00
	for asrg@ietf.org; Thu, 04 Mar 2004 02:03:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AymsG-0003nz-00
	for asrg@ietf.org; Thu, 04 Mar 2004 02:02:28 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AymrI-0003aY-00
	for asrg@ietf.org; Thu, 04 Mar 2004 02:01:28 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AymrF-0002Kx-00; Thu, 04 Mar 2004 02:01:25 -0500
Received: from [68.24.225.2] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AymrD-0006Rg-00; Thu, 04 Mar 2004 02:01:25 -0500
Message-ID: <4046D43A.4070308@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Mark Baugher <mbaugher@cisco.com>
CC: "Hallam-Baker, Phillip" <pbaker@verisign.com>, asrg@ietf.org
References: <C6DDA43B91BFDA49AA2F1E473732113E0A191F@mou1wnexm05.vcorp.ad.vrsn.com> <4046C5CF.3090206@solidmatrix.com> <6.0.0.22.2.20040303225250.037ddef0@mira-sjc5-6.cisco.com>
In-Reply-To: <6.0.0.22.2.20040303225250.037ddef0@mira-sjc5-6.cisco.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: 3b. SMTP Session Verification - STARTTLS
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/mail-archive/working-groups/asrg/>
Date: Thu, 04 Mar 2004 02:01:14 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mark Baugher wrote:

> At 09:59 PM 3/3/2004, Yakov Shafranovich wrote:
> 
>> [was Re: [Asrg] Its all over for Challenge Response]
>>
>> Hallam-Baker, Phillip wrote:
>>
>>>>> Sure they might be apples and oranges. But if you put apples
>>>>> and oranges together you have a fruit salad.
>>>>
>>>>
>>>> I do think STARTLS might have a role to play in antispam if
>>>> there were some scalable way to do the authorization.
>>>
>>>
>>> The problem is advertising the fact you support STARTTLS in
>>> the DNS.
>>> it is not an authorization problem.
>>
>>
>> The SMTP clients and servers exchange that information during the EHLO 
>> session of the SMTP transaction. Why do you need to advertise that via 
>> DNS?
>>
>> Leaving all of this aside, how will the use of TLS with SMTP help 
>> resolve the spam problem?
> 
> 
> In principle, it could have a role to play by authenticating the MTA 
> sender.
> 

What would you do with that information? Why is IP address insufficient 
(aside from the fact there are dynamic IPs)?

If this is going to be combined with reputation/accreditation systems, 
then we need to answer the questions of why future systems for 
reputation would be any different than today's.

(I am not attacking here, just trying to narrow down the solution)

Yakov

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



From exim@www1.ietf.org  Thu Mar  4 03:55:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00920
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 03:55:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyodE-0005ma-41
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 03:55:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i248t3aq022197
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 03:55:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayod9-0005lw-Jy
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 03:54:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00773
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 03:54:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayod7-0005ny-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 03:54:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayobf-0005Rz-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 03:53:28 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyobG-0005HD-04
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 03:53:02 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AyoYc-0001ow-4T
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 03:50:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyoYM-0005SL-Ps; Thu, 04 Mar 2004 03:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyoXl-0005MJ-S2
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 03:49:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA00472
	for <asrg@ietf.org>; Thu, 4 Mar 2004 03:49:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyoXj-0004ge-00
	for asrg@ietf.org; Thu, 04 Mar 2004 03:49:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyoWn-0004Qx-00
	for asrg@ietf.org; Thu, 04 Mar 2004 03:48:26 -0500
Received: from smtp.rol.ru ([194.67.21.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyoVh-0003vd-00
	for asrg@ietf.org; Thu, 04 Mar 2004 03:47:17 -0500
Received: from ariel.sovam.com ([194.67.3.216]:55942 "EHLO ariel.sovam.com"
	smtp-auth: "egc@online.ru" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits
	256/256 version TLSv1/SSLv3" TLS-PEER-CN1: <none>)
	by gnome07.net.rol.ru with ESMTP id S9756367AbUCDIqq (ORCPT
	<rfc822;asrg@ietf.org>); Thu, 4 Mar 2004 11:46:46 +0300
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation Systems and their
	Problems
From: Eugene Crosser <crosser@rol.ru>
To: Yakov Shafranovich <research@solidmatrix.com>
Cc: Mark Foster <mark@foster.cc>, ASRG <asrg@ietf.org>
In-Reply-To: <404649E2.6020809@solidmatrix.com>
References: <404633F3.2010503@solidmatrix.com>
	 <20040303202320.GA38846@riddler.dyndns.org>
	 <404649E2.6020809@solidmatrix.com>
Content-Type: text/plain
Organization: Sovintel
Message-Id: <1078389816.31519.18.camel@ariel.sovam.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 04 Mar 2004 11:43:36 +0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Thu, 2004-03-04 at 00:10, Yakov Shafranovich wrote:
> Mark Foster wrote:
> > On Wed, Mar 03, 2004 at 02:37:23PM -0500, Yakov Shafranovich wrote:
> > 
> >>In the current world the closest approximation we have to reputation 
> >>systems that are planned with LMAP are blacklists and Senderbase. Given 
> >>that current blacklists have numerous problems, why would any proposed 
> >>reputation or accrediation systems of the future be any different? How 
> >>are we planning on avoiding the same problems we have today in the 
> >>future, if we want to deploy such systems?
> > 
> > 
> > I've been doing some research into the use of STARTTLS and certificate
> > verification. The possibility exists for overlaying a
> > PKI trust model onto the email infrastructure... not just S/MIME and
> > PGP/GPG, but securing the message relay transmissions (MTA to MTA).
> > 
> 
> The problem with the PKI model is key distribution. If we follow the 
> current SSL scheme that might work BUT then you are making Verisign and 
> other CAs the gatekeepers for the Internet - and can have repercussions. 
> For example, in the SSL market according to 
> (http://www.securityspace.com/s_survey/sdata/200402/certca.html), 
> Verisign and Thawte have 30% and 20% each. HOWEVER, according to 
> (http://www.thawte.com/html/CORPORATE/today.html), Thawte is owned by 
> Verisign, which implies that 50% of the SSL market is controlled by one 
> company. Do you really want a few companies to choose who gets the right 
> to send email? Of course, a distributed system like DomainKeys can help 
> with some of these problems, but the main problems that blacklists have 
> are still there.
> 
> Also, SSL certificates today only *idenfity* the site, not provide its 
> reputation. Changing CAs into reputation systems, will involve a whole 
> new set of challenges. These challenges are mostly present today in 
> blacklists which is exactly what worries me - I don't see yet how any of 
> these problems can be avoided in any reputation systems.

I would say, authentication and reputation can be done by completely
unrelated parties.  Reputation lists could use servers' certificates the
same way they use their IP addresses now.

Otherwise, I agree that there is too much contraversy and "political"
uncertainty surrounding x509.  Primarily due to its strictly
hierarchical model, not well suitable for today's world.

Eugene


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



From exim@www1.ietf.org  Thu Mar  4 09:45:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22496
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 09:45:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayu64-0003OL-Ht
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 09:45:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24EjCvi013032
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 09:45:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayu64-0003O5-Ad
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 09:45:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22484
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 09:45:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayu62-00054z-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 09:45:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayu4z-0004qU-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 09:44:05 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayu4I-0004bQ-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 09:43:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayu3w-00038B-Qf; Thu, 04 Mar 2004 09:43:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayu33-00033C-14
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 09:42:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA22081
	for <asrg@ietf.org>; Thu, 4 Mar 2004 09:42:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayu31-0004Gv-00
	for asrg@ietf.org; Thu, 04 Mar 2004 09:42:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayu1T-0003kG-00
	for asrg@ietf.org; Thu, 04 Mar 2004 09:40:27 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayu04-0003KZ-00
	for asrg@ietf.org; Thu, 04 Mar 2004 09:39:00 -0500
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (mailer3.verisign.com [65.205.251.55])
        by peacock.verisign.com (8.12.11/) with ESMTP id i24EcuUt007465;
        Thu, 4 Mar 2004 06:38:56 -0800 (PST)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GHS8QVP7>; Thu, 4 Mar 2004 06:38:56 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A1921@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Yakov Shafranovich'" <research@solidmatrix.com>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'Mark Baugher'" <mbaugher@cisco.com>, asrg@ietf.org
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Asrg] RE: 3b. SMTP Session Verification - STARTTLS
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/mail-archive/working-groups/asrg/>
Date: Thu, 4 Mar 2004 06:38:53 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

> The SMTP clients and servers exchange that information during 
> the EHLO 
> session of the SMTP transaction. Why do you need to advertise 
> that via DNS?

There is a downgrade attack. The parties do not know
that the other accepts TLS. This means that an active man
in the middle attack could be used to prevent the session
upgrading to TLS

Of course if you do not have DNSSEC the same argument 
could be made against DNS

> Leaving all of this aside, how will the use of TLS with SMTP help 
> resolve the spam problem?

It is just another authentication mechanism, very similar to
CallerID/SPF in features offered. But it does have a much higher
barrier to entry - for the authentication to be useful you need
trustworthy third parties.

		Phill

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



From exim@www1.ietf.org  Thu Mar  4 11:43:07 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01244
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 11:43:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayvvk-0005dE-6c
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 11:42:40 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24GgebE021642
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 11:42:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayvvj-0005cz-IT
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 11:42:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01215
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 11:42:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayvvi-0007P8-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 11:42:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayvun-0007EH-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 11:41:41 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyvuG-00074L-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 11:41:09 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AyvuG-0002Qq-A1
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 11:41:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyvtK-0005K7-Fu; Thu, 04 Mar 2004 11:40:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayvt8-0005Hn-6q
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 11:39:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01089
	for <asrg@ietf.org>; Thu, 4 Mar 2004 11:39:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayvt6-0006r3-00
	for asrg@ietf.org; Thu, 04 Mar 2004 11:39:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyvsR-0006dL-00
	for asrg@ietf.org; Thu, 04 Mar 2004 11:39:16 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyvrG-0006LW-00
	for asrg@ietf.org; Thu, 04 Mar 2004 11:38:03 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id 42BE616D00
	for <asrg@ietf.org>; Thu,  4 Mar 2004 11:41:17 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] Its all over for Challenge Response 
In-Reply-To: Your message of "Wed, 03 Mar 2004 15:10:21 PST."
             <C6DDA43B91BFDA49AA2F1E473732113E0A1913@mou1wnexm05.vcorp.ad.vrsn.com> 
Message-Id: <20040304164117.42BE616D00@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Thu, 04 Mar 2004 11:41:17 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

"Hallam-Baker, Phillip" <pbaker@verisign.com> wrote:
> STARTLS exists, is an approved standard and has been implemented in
> Microsoft exchange along with pretty much every other mail server for 
> years.

  Sure.  But how many MUAs implement SUBMIT?

> Using SSH would require input. You have to know the other endpoint
> supports SSH.

  If you're roaming, you can potentially use SSH (or SUBMIT +
STARTTLS) to submit messages to the MTA for your domain.
Functionally, they're the same thing.

  Where SSH got it right, and SUBMIT got it wrong, was that with SSH,
you just do port forwarding, and authentication is seperate from
SMTP.  So you don't need to change your SMTP clients to effectively
use a "SUBMIT + STARTTLS" work-alike.

> The Web has peer to peer aspects, eliminating the central hub was 
> what made the network hypertext model work. But look at Google and
> you will see that the search model is not peer to peer. 

  Communication is peer to peer, discovery is not.  Most protocols
work this way.  Discovery through DNS, peer to peer via SMTP.

  Creating a trust system using that model should be relatively easy.

  Alan DeKok.

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



From exim@www1.ietf.org  Thu Mar  4 11:43:10 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01261
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 11:43:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayvvm-0005dg-Af
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 11:42:42 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24Ggg2Q021670
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 11:42:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayvvm-0005dR-5G
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 11:42:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01228
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 11:42:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayvvl-0007PV-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 11:42:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayvuq-0007Eo-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 11:41:46 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyvuM-00074R-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 11:41:14 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AyvuF-0002Qr-VF
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 11:41:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyvtF-0005Io-Lv; Thu, 04 Mar 2004 11:40:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayvsy-0005HK-Cj
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 11:39:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01059
	for <asrg@ietf.org>; Thu, 4 Mar 2004 11:39:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayvsx-0006ph-00
	for asrg@ietf.org; Thu, 04 Mar 2004 11:39:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayvrz-0006Zk-00
	for asrg@ietf.org; Thu, 04 Mar 2004 11:38:48 -0500
Received: from bay2-dav44.bay2.hotmail.com ([65.54.246.16] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayvqp-00066E-00
	for Asrg@ietf.org; Thu, 04 Mar 2004 11:37:35 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 4 Mar 2004 08:37:04 -0800
Received: from 67.21.251.73 by bay2-dav44.bay2.hotmail.com with DAV;
	Thu, 04 Mar 2004 16:37:04 +0000
X-Originating-IP: [67.21.251.73]
X-Originating-Email: [joe_kern_1001@hotmail.com]
X-Sender: joe_kern_1001@hotmail.com
From: "joe" <joe_kern_1001@hotmail.com>
To: <Asrg@ietf.org>
Subject: RE: [Asrg] [IP] CNN covers Meng's SPF
Message-ID: <001b01c40206$ec460e50$0b00000a@teledeal>
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
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <B0000029432@nts1.terabites.com>
X-OriginalArrivalTime: 04 Mar 2004 16:37:04.0481 (UTC) FILETIME=[ED239D10:01C40206]
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/mail-archive/working-groups/asrg/>
Date: Thu, 4 Mar 2004 11:37:03 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.0 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS,
	FROM_HAS_ULINE_NUMS autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


I fully concur with Gordon's analysis and suggestions. 
I would argue that another single ended solution could be used to
further dramatically reduce spam. i.e. disposable email addresses or
DEA.
With DEA you no longer advertise your email by giving it away when you
sign up to web sites.

I specifically like Protecteer's product SignupShield which integrates
DEA with form filling for automatic sign-up to Web sites.

No single solution is going to do it!



-----Original Message-----
From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On Behalf Of
gep2@terabites.com
Sent: Monday, March 01, 2004 1:57 PM
To: dave@farber.net
Cc: asrg@ietf.org; wishlist@microsoft.com
Subject: [Asrg] [IP] CNN covers Meng's SPF




> NEW YORK (AP) -- With a simple adjustment in your e-mail software, you

> can
pretend to be anyone. You can send messages marked as coming from
BillGates@microsoft.com.

Surprise surprise!!!  This should have been common knowledge for a long
time.

> The trick, known as spoofing, is a popular method for spammers to hide
their tracks -- you'd blame Microsoft Corp. chairman Bill Gates and not
the actual perpetrator of junk mail.

> To close that loophole, Microsoft and Yahoo! Inc. are each developing
systems aimed at authenticating senders of e-mail. America Online Inc.
is testing a third.

Funny thing that each of these folks are ISPs... and each is trying to
make sure 
you use THEM for everything you do. :-((  

> "Having e-mail come in, and not really being able to identify where it
comes from, this is a huge security hole," Gates said this week in
announcing specifications for his proposal.

Actually, the "Received" headers give one a pretty decent trace of
"where it 
comes from", at least once it leaves the hands of those who counterfeit
headers 
or otherwise attempt to deceive.  And one could certainly imagine a
system 
whereby mail recipients systems could go back to the claimed originating
system 
of the E-mail message and ask for confirmation that the specific E-mail
message 
actually originated at that system.

> Many software engineers are concerned, however, that these systems 
> could
end up causing more problems than they solve.

And, in fact, that is precisely the problem.  Many of these systems,
SPECFICALLY 
INCLUDING Wong's SPF (and as a member of the IETF's Anti-Spam Research
Group was 
on Wong's SPF mailing list for a while, before I concluded that it was
probably 
fatally flawed), have a number of very serious problems in them if they
were 
ever to be widely adopted.

> Microsoft's proposal, known as Caller ID for E-mail, calls for 
> Internet
service providers to submit lists of unique numeric addresses for their
mail servers. On the receiving end, software would check a database to
verify that a message said to come from an e-mail provider actually
originated at one of its registered machines.

The problem with this one of course is that not all E-mail messages
originate at 
mail servers run by ISPs.  Some of the more sophisticated business
customers 
(and indeed, some of the more sophisticated USERS, myself among them)
actually 
use their own outgoing E-mail servers... for a whole variety of
perfectly valid 
reasons.  It's outrageous and offensive that ISPs are trying to prevent
users 
from being able to bypass the ISP's (hoped-for) monopoly provision of
(sometimes 
unwanted and often gotcha-laden) "ISP services".

> In January, AOL began testing a similar system called Sender Policy
Framework, or SPF, which checks a different part of the message.

> Yahoo's proposed solution is a different animal. It would use 
> encryption
to digitally sign messages. If the sender or message content is altered,
the signature gets rejected. Yahoo announced its proposal, DomainKeys,
in December but has yet to make details public.

There are a lot of such systems and most of them work at least in the
scenario 
they are designed for.  Unfortunately, when you start looking at the
less 
obvious but still HIGHLY important situations... such as
personally-owned 
domains, mailing lists, corporate "vanity domains", roaming use (mailing
from 
cruise ships, airport waiting lounge kiosks, etc)... not even to mention

"anonymous remailers" required by whistleblowers etc... you usually find
that 
these proposals have very serious flaws that have terrible implications
to many 
customers with legitimate needs and concerns.

> The big three e-mail providers are not alone in trying to tackle 
> address
spoofing. Leading e-mail software vendor Sendmail Inc., spam-filtering
company Brightmail Inc. and frequent e-mailer Amazon.com are also at it,
each planning to test one or more systems.

> All these competing proposals are enough to get the Internet's
standards-setting bodies in a lather.

> One of them, the Internet Engineering Task Force, has scheduled a 
> session
on authentication next Thursday in South Korea. Experts predict some
combination of the techniques will be ready for use later this year,
though formal standards will take longer.

> There's much work to be done in the meantime, including proving the
systems can actually work beyond controlled, laboratory environments.

> Caller ID and SPF, at least, are likely to disrupt mail-forwarding
services that colleges and companies offer to let alumni and subscribers
route e-mail through a domain name other than their own service
provider's.

> They also could break "send to a friend" features in which someone 
> clicks
on a Web link to pass an interesting item to someone else.

THOSE *need* to be broken.  They are often more just a pleasant-looking
ruse to 
collect an E-mail address of the "someone else" victim and later use
that for 
spamming or other unwelcome purpose.  (Electronic "greeting cards" of
course 
suffer from the same fault.)

> Issues to be worked out for all three systems include how to properly 
> send
e-mail from cybercafes, hotels and public Wi-Fi hotspots...

Indeed, and (as mentioned) airport waiting lounge kiosks, cruise ships,
and 
other "temporary/away" situations.  Mailing lists are another such
serious 
problem.

> and how to preserve privacy when using anonymous re-mailers, which are

> used by
whistleblowers and others to intentionally mask the origin of messages.

Absolutely.

> "A lot of people have said that e-mail today is broken, and now we're
going to break it a little more," Meng Weng Wong, lead developer of SPF,
acknowledged. "Some of the things people are used to doing, they won't
be able to do it in quite the same way."

In fact, Wong (based on E-mail exchanges he and I have had) basically
just 
doesn't care about the important flaws in his approach, he is fully
aware of 
them and has been forging ahead with it regardless.  I consider his
approach and 
attitude to be irresponsible and objectionable.

> But the gain in fighting spam outweighs any pain from change, Wong 
> argues.

Except that it doesn't.  NOTHING in SPF in any way prevents spam
whatsoever... 
all it does is to authenticate the sender.  Spammer-friendly ISPs, new
"vanity" 
domains (and spammers are creating "disposable" vanity domains with
seemingly 
randomly generated domain names at a breathtaking rate... sometimes
using the 
domain name just once for a single mass mailing and figuring the
less-than-$50 
domain registration fee just a small part of the cost of doing their
spamming 
business.)

Spammers can also continue hijacking (with viruses and worms) the
systems of 
legitimate (if naive or careless) users and use those to generate spam
E-mails 
using absolutely "legitimate" (if inadvertent) and authenticated users
and valid 
sender ISPs.  This of course is one of the problems with the
"cyberpayments" 
schemes for E-mails, too (quite apart from that being a slippery slope
to the 
"pay for each E-mail" scheme that monopoly ISPs would LOVE to see become
the 
norm).  In each case, the spammer simply shifts the costs to an
inadvertent 
third-party victim.

So in fact, Wong's system creates MUCH pain, requires changes to systems

literally everywhere in the world, hugely inconveniences (or even
disables 
entirely) many types of users with highly legitimate needs, and still
doesn't 
really do much of anything to actually solve the problem.  It still
leaves 
people sending and receiving spam, with about the only improvement being
that 
you maybe know who to send complaints about it to (usually an ISP, whose
user is 
themself an unwitting and usually unwilling victim).  So what is the ISP

supposed to do, punish the victim?  And even if they throw the
victimized user 
off their system, eventually ALL such users will have been victimized,
and 
NOBODY is left still on the Net.  :-(

> Authentication also can help limit the spread of e-mail viruses...

Again, NO IT DOESN'T.  It only helps identify where they actually came
from.  
Maybe.  (And often, that trail will end up leading back to someone who
is a 
pathetic and beleaguered victim themselves).  This ultimately is NOT
very 
helpful.

A **far** better approach... simpler, easier, rapid to implement, hard
to 
disable or to evade... and one which IMMEDIATELY benefits the folks who 
INDIVIDUALLY put it in place, without requiring literally worldwide
changes and 
consensus to be effective... is for E-mail client software companies to
simply 
discard ALL incoming attachments (including alternative HTML-burdened
ones) 
unless the recipient had previously whitelisted the sender and
authorized THAT 
sender to send THAT recipient attachments of THAT specified type.
(Example:  
Your Aunt Gertrude *might* actually send you an electronic photo JPG of
her 
adorable poodle Fifi, but she probably NEVER needs to send you an .EXE,
script, 
PIF, or other type of executable file.)  Likewise, even if you're some
kind of 
consumer products company (say, Proctor and Gamble) that needs to
receive 
unsolicited messages from previously-unknown users, it's very hard to
argue that 
people need to send *attachments* (at least not as an initial contact
message) 
rather than simply safe, plain ASCII text.

So E-MAIL CLIENT SOFTWARE SHOULD STRIP ALL ATTACHMENTS UNLESS THE
RECIPIENT HAS 
SPECIFICALLY WHITELISTED THE INDIVIDUAL SENDER TO SEND THEM THAT
SPECIFIC TYPE 
OR CLASS OF ATTACHMENT.

That single, simple, highly effective strategy would OVERNIGHT result in
a 
near-total-elimination of 85-95% (maybe more) of all viruses and worms.
The 
GREAT majority of them would find their propagation rate reduced to well
below 
the minimum "survival" rate.

> and, with Caller ID and DomainKeys, help flag fraudulent "phishing" 
> messages
that try to trick people into revealing passwords and credit card
information.

A far more effective strategy THERE, TOO, is to STRIP ALL HTML CONTENT
OUT OF 
MESSAGES unless the recipient has specifically authorized (by
whitelisting) the 
specific sender in question to send the recipient HTML-burdened E-mail.

The great majority of spam and fraudulent "phishing" messages use tricks
based 
on HTML to deceive, obscure, and defraud.  This can include obscured
URLs, links 
that claim to be one thing but in fact point somewhere else (e.g. claim
to be 
"http://security.ebay.com" but in fact when you click on them they point
to a 
rogue server in Romania or somewhere), Web bugs, malicious scripting,
malicious 
ActiveX content, text-as-image in order to evade antispam content
filters, and 
so forth.  

If ONLY AUTHORIZED WHITELISTED-BY-EACH-RECIPIENT SENDERS were able to
send them 
HTML-burdened E-mail content, then (and in conjunction with good
antispam 
content filters, which would then be HUGELY more effective) we'd also
get rid of 
the great majority of spam and other fraudulent E-mail, too.

Again, this doesn't require any great worldwide consensus, doesn't
require any 
sweeping and disruptive change to the world's online systems, and
doesn't 
needlessly or seriously disrupt legitimate users.  Moreover, IT IS
EFFECTIVE 
FROM DAY ONE AND TO THE VERY FIRST ADOPTERS, which means that people are

immediately gratified by the change they make to THEIR systems.  This
ought to 
result in a rapid adoption rate, and minimize the long time it takes to
move 
complex and ultimately unsatisfactory standards through worldwide
standards 
organizations.

Note also that BOTH the changes I propose... simply whitelisting
attachments and 
HTML at the recipient end, on a sender-by-sender basis... are
SINGLE-ENDED 
schemes which do not require ANY changes at the sender ends at all
(other than 
implying that they cannot send attachments or HTML-burdened mail
unsolicited or 
unwanted, and expect to actually get it through!).  And, once
whitelisted, 
EVERYTHING we can do today (vanity domains, roaming, mailing lists, 
send-from-cruise-ship, and so forth) all still work, too.

> The proposals require no changes to existing protocols for e-mail or 
> the
domain name system, and developers of all three pledge to eventually
seek standards status (Wong has already submitted SPF for review).

Actually, almost all of these other approaches (INCLUDING Wong's) DO
involve the 
need for worldwide changes and consensus, they prevent legitimate users
from 
doing things they sometimes truly NEED to do, most DO involve changes to
the DNS 
system (or else the construction of a wasteful parallel to it), and in
fact NONE 
of them seem to ACTUALLY solve the problem.  They do NOT prevent the
sending of 
Spam, they do NOT prevent the propagation of viruses, they do NOT
prevent 
"phishing" and similar deceptions.  They only inconvenience people
everywhere 
and disable exceedingly useful and important features.

> For now, the three can coexist, although adoption could be limited 
> until a
consensus emerges around one or a combination.

The reason there has not been (and is not LIKELY to be) a consensus
around these 
proposals anytime soon is because they each have very nasty problems
that many 
people strongly dislike, and generally the payback even upon widespread 
implementation simply isn't worth the implmentation costs and other 
disadvantages.

> But these solutions alone will not stop spammers.

ABSOLUTELY, and that is at the root of the delay and dissatisfaction
with all of 
them.  Nobody that seriously looks at these proposals is truly convinced
that 
any of them ACTUALLY solve the problem.  It only makes folks (arguably) 
identifiable or traceable, and while that sounds good on the surface, it
simply 
doesn't achieve much in the end analysis.  I don't think it makes much
sense to 
uproot and mess up the entire Internet worldwide, just to give the bogus

APPEARANCE of "we have to [appear to] do SOMETHING".

Meanwhile, the simple single-ended solution I propose (in conjunction
with a 
suitable content filter at the recipient end) would be cheap and fast,
HIGHLY 
effective against worms, viruses, spams, and "phishing" spoofs, is
rapidly 
implementable, and would have negligible negative impact on legitimate, 
responsible users (both senders and recipients).  It moreover requires
**no** 
changes whatsoever to the critical underlying Internet infrastructure.

> Systems will have to be established to evaluate the reputation of 
> domains
that relay e-mail, and that raises questions about who would develop
such lists and who would arbitrate disputes.

Again, that's simply NOT NECESSARY.  All that does is to establish
trackability, 
it does **nothing** to actually prevent the sending (or receipt!) of
spam, 
viruses, worms, and the like.

> In the short term, authentication will be useful mostly for verifying
newsletters and other bulk mailings that are often misidentified as spam
today, said Margaret Olson, co-chairman of the Email Service Provider
Coalition's technology committee.

This can easily enough be handled, if necessary, with normal public-key 
signature technology.  Again, no infrastructure changes are required or
even 
indicated.

> Once enough service and software providers adopt the technology, 
> "getting
unauthenticated mail delivered will be extremely difficult," she said.

And that's part of the problem with such changes.  They require
worldwide 
consensus to work effectively, and the earliest adopters gain little or
nothing 
from making the changes.  They are expensive (because they have to be
done 
EVERYWHERE) and in the end, when all is said and done, THEY DON'T SOLVE
THE 
PROBLEM!

> And that could hurt e-mailers in other countries where adoption of
English-language specifications tend to lag, and smaller service
providers may be forced to accept whatever the giants decide, critics
warn.

Right, it could take years or even decades, and many Net users
(including 
businesses with embedded mail handlers built into their related
applications) 
might in some cases not even *ever* be able to adhere to the changed 
specifications.

> At EarthLink Inc., which is experimenting with authentication, chief
architect Robert Sanders said no service provider wants to suddenly stop
e-mail from non-participants.

Right.  The authentication approach isn't really very effective unless
and until 
EVERYONE is "authenticated", and the way the schemes are generally
conceived, 
that mythical state of eternal bliss is NEVER in practice achieved.  And
again, 
even after EVERYONE is authenticated, that STILL doesn't prevent them
being a 
victim and sending out "fully authenticated" viruses, worms, and "my
system was 
hijacked" spams!

> But he likened the technology to telephone's caller ID: "You may still

> get
a phone call with caller ID, but you may not choose to answer it."

There are a LOT of ways we can potentially "break" the world's E-mail
system.  
My position is that we shouldn't do that unless the actual payback we'd
achieve 
by doing so is truly compelling.  I still feel that the approach I'm
proposing 
has the fastest payback to adopters, the lowest worldwide cost, the best

effectiveness against worms, viruses, spams, spoofing, and "phishing",
and the 
least unwanted and undesired downside costs to existing users, systems
and 
applications.

Gordon Peterson                  http://personal.terabites.com/
1977-2002  Twenty-fifth anniversary year of Local Area Networking!
Support free and fair US elections!
http://stickers.defend-democracy.org
12/19/98: Partisan Republicans scornfully ignore the voters they
"represent".
12/09/00: the date the Republican Party took down democracy in America.



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

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



From exim@www1.ietf.org  Thu Mar  4 12:25:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02988
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 12:25:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aywb2-0001Wx-R5
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 12:25:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24HPK6S005877
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 12:25:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aywb2-0001Wi-5Y
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 12:25:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02957
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 12:25:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aywb0-0000Q7-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:25:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AywZT-0000F9-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:23:44 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AywZ6-000050-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:23:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AywYm-0001Gp-Rr; Thu, 04 Mar 2004 12:23:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AywYT-0001GI-OP
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 12:22:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02892
	for <asrg@ietf.org>; Thu, 4 Mar 2004 12:22:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AywYS-00003z-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:22:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AywXS-0007gN-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:21:39 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AywWb-0007Lr-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:20:45 -0500
Received: from sj-core-3.cisco.com (171.68.223.137)
  by sj-iport-5.cisco.com with ESMTP; 04 Mar 2004 09:20:29 -0800
Received: from mbaugher-w2k07.cisco.com (sjc-vpn3-654.cisco.com [10.21.66.142])
	by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id i24HK8LN024769;
	Thu, 4 Mar 2004 09:20:09 -0800 (PST)
Message-Id: <6.0.0.22.2.20040304083851.03d748d0@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
To: Yakov Shafranovich <research@solidmatrix.com>
From: Mark Baugher <mbaugher@cisco.com>
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>, asrg@ietf.org
In-Reply-To: <4046D43A.4070308@solidmatrix.com>
References: <C6DDA43B91BFDA49AA2F1E473732113E0A191F@mou1wnexm05.vcorp.ad.vrsn.com>
 <4046C5CF.3090206@solidmatrix.com>
 <6.0.0.22.2.20040303225250.037ddef0@mira-sjc5-6.cisco.com>
 <4046D43A.4070308@solidmatrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Asrg] Re: 3b. SMTP Session Verification - STARTTLS
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/mail-archive/working-groups/asrg/>
Date: Thu, 04 Mar 2004 09:20:01 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

Yakov,

At 11:01 PM 3/3/2004, Yakov Shafranovich wrote:
<...>
>>In principle, it could have a role to play by authenticating the MTA sender.
>
>What would you do with that information? Why is IP address insufficient 
>(aside from the fact there are dynamic IPs)?
>
>If this is going to be combined with reputation/accreditation systems, 
>then we need to answer the questions of why future systems for reputation 
>would be any different than today's.
>
>(I am not attacking here, just trying to narrow down the solution)

I don't have a spam solution but TLS can serve to authenticate one MTA to 
another.  This would be a variation on signed email whereby the smtp 
connection is signed rather than the message.  When the mail transaction is 
direct between the sending domain and the receiving domain without 
intermediaries, then this is functionally similar to signing the message 
(though much less efficient for mailing lists).  It doesn't suffer from the 
replay attack scenario that Markus Stumpf described some time ago.  When 
there is an intermediate MTA, then the receiver would need to make an 
authorization decision based on whether it trusts the intermediary to have 
an effective antispam policy, e.g. that it effectively authenticates its 
senders.

This takes us to the authorization problem and reputation seems to be a 
scalable means to do that, but I have no answer to the problems of antispam 
databases that you have mentioned previously.  (I'm not even sure what all 
the problems are with RBLs).

Mark


>Yakov



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



From exim@www1.ietf.org  Thu Mar  4 12:35:17 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03592
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 12:35:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AywkE-0002de-Ll
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 12:34:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24HYomA010136
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 12:34:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AywkE-0002dP-Dh
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 12:34:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03555
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 12:34:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AywkC-0002RH-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:34:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AywjG-0002G1-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:33:50 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AywiZ-00025I-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:33:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AywiT-0002QF-Fl; Thu, 04 Mar 2004 12:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AywiH-0002P3-N3
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 12:32:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03415
	for <asrg@ietf.org>; Thu, 4 Mar 2004 12:32:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AywiG-000234-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:32:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AywhN-0001q0-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:31:53 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AywgO-0001T8-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:30:52 -0500
Received: from mbaugher-w2k07.cisco.com (sjc-vpn3-654.cisco.com [10.21.66.142])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i24HUHD2000829;
	Thu, 4 Mar 2004 09:30:17 -0800 (PST)
Message-Id: <6.0.0.22.2.20040304092129.03d05e88@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Mark Baugher <mbaugher@cisco.com>
Cc: "'Yakov Shafranovich'" <research@solidmatrix.com>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>, asrg@ietf.org
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A1921@mou1wnexm05.vcorp.a
 d.vrsn.com>
References: <C6DDA43B91BFDA49AA2F1E473732113E0A1921@mou1wnexm05.vcorp.ad.vrsn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Asrg] RE: 3b. SMTP Session Verification - STARTTLS
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/mail-archive/working-groups/asrg/>
Date: Thu, 04 Mar 2004 09:30:15 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

Phill,

At 06:38 AM 3/4/2004, Hallam-Baker, Phillip wrote:
> > The SMTP clients and servers exchange that information during
> > the EHLO
> > session of the SMTP transaction. Why do you need to advertise
> > that via DNS?
>
>There is a downgrade attack. The parties do not know
>that the other accepts TLS. This means that an active man
>in the middle attack could be used to prevent the session
>upgrading to TLS

I don't think we should worry about active man-in-the-middle attacks 
against antispam mechanisms.  It seems like a lot of work to get a 
relatively small effect.  Besides that, even if TLS were generally used 
between MTAs, it would not be universal.  I think at best, TLS would 
introduce a new class of mail, i.e. mail from authenticated smtp 
senders.  So the m-i-m attack would serve only to downgrade particular mail 
and never succeed in upgrading it.

Mark


>Of course if you do not have DNSSEC the same argument
>could be made against DNS
>
> > Leaving all of this aside, how will the use of TLS with SMTP help
> > resolve the spam problem?
>
>It is just another authentication mechanism, very similar to
>CallerID/SPF in features offered. But it does have a much higher
>barrier to entry - for the authentication to be useful you need
>trustworthy third parties.
>
>                 Phill



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



From exim@www1.ietf.org  Thu Mar  4 12:45:15 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03903
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 12:45:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aywts-0003rD-Ij
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 12:44:48 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24HimJt014821
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 12:44:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aywts-0003qy-7b
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 12:44:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03899
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 12:44:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aywtq-0004Gv-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:44:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aywsx-00046B-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:43:52 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AywsI-0003vE-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:43:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayws9-0003cT-9v; Thu, 04 Mar 2004 12:43:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aywl7-0002g0-BP
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 12:35:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03616
	for <asrg@ietf.org>; Thu, 4 Mar 2004 12:35:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aywl5-0002cq-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:35:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aywk7-0002QR-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:34:43 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AywjD-0002Eu-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:33:47 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1Aywj8-0000dS-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:33:42 -0500
Received: from [68.244.134.55] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1Aywj7-0002Aj-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:33:42 -0500
Message-ID: <40476868.9000704@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 3b. SMTP Session Verification - LMAP BoF Preliminary minutes
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/mail-archive/working-groups/asrg/>
Date: Thu, 04 Mar 2004 12:33:28 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Preliminary minutes from the BoF can be found here:

http://www.imc.org/ietf-mxcomp/mail-archive/msg00067.html

Yakov

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



From exim@www1.ietf.org  Thu Mar  4 12:59:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04434
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 12:59:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayx7X-0005oK-RV
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 12:58:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24Hwtx6022329
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 12:58:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayx7X-0005np-KH
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 12:58:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04413
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 12:58:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayx7V-00077g-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:58:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayx6d-0006wZ-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:57:59 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayx63-0006kz-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 12:57:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayx5h-0005TL-Lg; Thu, 04 Mar 2004 12:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayx3j-00054T-0t
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 12:54:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04281
	for <asrg@ietf.org>; Thu, 4 Mar 2004 12:54:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayx3h-0006Lg-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:54:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayx2u-00068Z-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:54:08 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayx25-0005va-00
	for asrg@ietf.org; Thu, 04 Mar 2004 12:53:17 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1Ayx21-0001xC-00; Thu, 04 Mar 2004 12:53:13 -0500
Received: from [68.244.134.55] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1Ayx1y-0002qn-00; Thu, 04 Mar 2004 12:53:13 -0500
Message-ID: <40476CF8.10903@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: "'Mark Baugher'" <mbaugher@cisco.com>, asrg@ietf.org
Subject: Re: [Asrg] RE: 3b. SMTP Session Verification - STARTTLS
References: <C6DDA43B91BFDA49AA2F1E473732113E0A1921@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A1921@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 04 Mar 2004 12:52:56 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hallam-Baker, Phillip wrote:
> 
>>Leaving all of this aside, how will the use of TLS with SMTP help 
>>resolve the spam problem?
> 
> It is just another authentication mechanism, very similar to
> CallerID/SPF in features offered. But it does have a much higher
> barrier to entry - for the authentication to be useful you need
> trustworthy third parties.
> 

You can probably make a DK-like variation by storing the TLS key in DNS 
avoiding third parties. Of course that would depend on what you are 
trying to authenticate - if its just a domain then it would be 
sufficient, but if you need an address for legal process, you need a 
third party or some other mechanism.

BUT, in any case, authentication is a means to an end. From everything 
that has been discussed about authentication so far, it leads to 
authorization of some kind which has been proposed so far either via 
reputation/accreditation or "web of trust".

If the entire purpose of authentication is to lead to authorization, 
what kind of systems would we use? How would we avoid problems that 
plague existing blacklists? Would allowing CAs into doing a reputation 
service in addition to authentication wise? How will all of this reduce 
spam?

Yakov


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



From exim@www1.ietf.org  Thu Mar  4 14:06:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07982
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 14:06:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyyAJ-0003RQ-Sk
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 14:05:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24J5pT6013212
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 14:05:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyyAJ-0003R1-57
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 14:05:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07975
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 14:05:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyyAG-0004g6-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 14:05:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayy9T-0004VQ-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 14:04:59 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayy8j-0004Iu-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 14:04:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayy8X-000395-H9; Thu, 04 Mar 2004 14:04:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayy8P-00038s-4F
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 14:03:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07755
	for <asrg@ietf.org>; Thu, 4 Mar 2004 14:03:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayy8M-0004Fd-00
	for asrg@ietf.org; Thu, 04 Mar 2004 14:03:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayy7L-00040J-00
	for asrg@ietf.org; Thu, 04 Mar 2004 14:02:48 -0500
Received: from adsl-64-165-36-235.dsl.snfc21.pacbell.net ([64.165.36.235] helo=shedevil.annepmitchell.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayy6L-0003nK-00
	for asrg@ietf.org; Thu, 04 Mar 2004 14:01:45 -0500
Received: from [192.168.0.247] ([192.168.0.247])
	by shedevil.annepmitchell.com (8.11.6/8.11.4) with ESMTP id i24J1iX78569
	for <asrg@ietf.org>; Thu, 4 Mar 2004 11:01:44 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v612)
In-Reply-To: <20040304170009.30226.82939.Mailman@www1.ietf.org>
References: <20040304170009.30226.82939.Mailman@www1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <60E06C9D-6E0E-11D8-B214-000A95AC5778@isipp.com>
Content-Transfer-Encoding: 7bit
From: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
To: asrg@ietf.org
X-Mailer: Apple Mail (2.612)
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: Asrg digest, Vol 1 #552 - 30 msgs
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/mail-archive/working-groups/asrg/>
Date: Thu, 4 Mar 2004 11:01:44 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



>> why would any proposed=20
>> reputation or accrediation systems of the future be any different?

We're getting a great deal of positive response to our IADB (ISIPP 
Accreditation Database) even though we haven't publicly announced it 
yet (if you are not familiar with it you can read about it at 
http://www.isipp.com/iadb.php).  What are the problems you feel are 
innate to DNS blocklists which you feel are also ported to DNSWLs or 
other non-block DNS lists?

Anne

Anne P. Mitchell, Esq.
President/CEO
Institute for Spam and Internet Public Policy
Professor of Law, Lincoln Law School of SJ


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



From exim@www1.ietf.org  Thu Mar  4 14:07:13 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08055
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 14:07:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyyBB-0003dv-Ot
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 14:06:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24J6jsB013997
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 14:06:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyyBB-0003dg-LC
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 14:06:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08003
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 14:06:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyyB9-0004qT-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 14:06:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyyAH-0004gE-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 14:05:49 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayy9W-0004Vu-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 14:05:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayy9V-0003I0-NV; Thu, 04 Mar 2004 14:05:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Ayy9H-0003HS-4R
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 14:04:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07869
	for <asrg@ietf.org>; Thu, 4 Mar 2004 14:04:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayy9E-0004TN-00
	for asrg@ietf.org; Thu, 04 Mar 2004 14:04:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Ayy8J-0004F7-00
	for asrg@ietf.org; Thu, 04 Mar 2004 14:03:47 -0500
Received: from adsl-64-165-36-235.dsl.snfc21.pacbell.net ([64.165.36.235] helo=shedevil.annepmitchell.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayy7K-000401-00
	for asrg@ietf.org; Thu, 04 Mar 2004 14:02:46 -0500
Received: from [192.168.0.247] ([192.168.0.247])
	by shedevil.annepmitchell.com (8.11.6/8.11.4) with ESMTP id i24J2jX78578
	for <asrg@ietf.org>; Thu, 4 Mar 2004 11:02:45 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Resent-Date: Thu, 4 Mar 2004 11:02:45 -0800
Message-Id: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com>
Content-Transfer-Encoding: 7bit
Resent-To: asrg@ietf.org
Resent-Message-Id: <60E06C9D-6E0E-11D8-B214-000A95AC5778@isipp.com>
From: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
Resent-From: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
To: asrg@ietf.org
X-Mailer: Apple Mail (2.612)
Resent-Date: Thu, 04 Mar 2004 14:02:46 -0500
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.)
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/mail-archive/working-groups/asrg/>
Date: Thu, 4 Mar 2004 11:01:44 -0800
Resent-Date: Thu, 04 Mar 2004 14:05:01 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Oops...1000 apologies - resent with proper subject line:


>> why would any proposed=20
>> reputation or accrediation systems of the future be any different?

We're getting a great deal of positive response to our IADB (ISIPP 
Accreditation Database) even though we haven't publicly announced it 
yet (if you are not familiar with it you can read about it at 
http://www.isipp.com/iadb.php).  What are the problems you feel are 
innate to DNS blocklists which you feel are also ported to DNSWLs or 
other non-block DNS lists?

Anne

Anne P. Mitchell, Esq.
President/CEO
Institute for Spam and Internet Public Policy
Professor of Law, Lincoln Law School of SJ


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



From exim@www1.ietf.org  Thu Mar  4 15:35:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13069
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 15:35:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyzYT-0005ZV-ES
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 15:34:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24KYrCO021417
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 15:34:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyzYT-0005ZM-9u
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 15:34:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13065
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 15:34:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyzYS-00064e-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 15:34:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyzXW-0005uL-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 15:33:55 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyzX4-0005jw-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 15:33:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyzWe-0005KZ-Gg; Thu, 04 Mar 2004 15:33:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyzWT-0005KK-9o
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 15:32:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12991
	for <asrg@ietf.org>; Thu, 4 Mar 2004 15:32:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyzWR-0005iw-00
	for asrg@ietf.org; Thu, 04 Mar 2004 15:32:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyzVV-0005Yw-00
	for asrg@ietf.org; Thu, 04 Mar 2004 15:31:50 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AyzUe-0005Ol-00
	for asrg@ietf.org; Thu, 04 Mar 2004 15:30:56 -0500
Received: (qmail 22287 invoked by uid 1013); 4 Mar 2004 20:30:54 -0000
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
Cc: asrg@ietf.org
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.)
Message-ID: <20040304203054.GF13559@Space.Net>
References: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
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/mail-archive/working-groups/asrg/>
Date: Thu, 4 Mar 2004 21:30:54 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Thu, Mar 04, 2004 at 11:01:44AM -0800, Anne P. Mitchell, Esq. wrote:
> We're getting a great deal of positive response to our IADB (ISIPP 
> Accreditation Database)

I'm sure you get them especially for
    C. FEES ASSOCIATED WITH LISTING IN IADB
and about
    PLEASE NOTE THAT IADB IS A PRIVATE SYSTEM, AND APPROVAL IS NOT
    GUARANTEED. FINAL DECISION FOR INCLUSION IN IADB IS AT THE
    DISCRETION OF ISIPP.

How about:
   where the definition of "spam" is that generally understood in the
   email sending and receiving industries, and includes unsolicited
   commercial and bulk email.
if this RG has revealed one thing very clearly than that there is no
such thing as a 'generally understood definition of "spam"'.

We don't need another company that tries to centralize a service, take
money for it and then tries to play god with fluky rules.

Thanks, but no thanks.

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"

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



From exim@www1.ietf.org  Thu Mar  4 15:42:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13474
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 15:42:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyzfJ-0006tc-BM
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 15:41:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24KfvLJ026501
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 15:41:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyzfJ-0006tM-5V
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 15:41:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13461
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 15:41:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyzfI-0007QA-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 15:41:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyzeK-0007F7-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 15:40:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyzdX-00074D-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 15:40:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyzdT-0006UF-KD; Thu, 04 Mar 2004 15:40:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyzdK-0006SP-8L
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 15:39:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13407
	for <asrg@ietf.org>; Thu, 4 Mar 2004 15:39:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyzdJ-00072D-00
	for asrg@ietf.org; Thu, 04 Mar 2004 15:39:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyzcP-0006rs-00
	for asrg@ietf.org; Thu, 04 Mar 2004 15:38:57 -0500
Received: from adsl-64-165-36-235.dsl.snfc21.pacbell.net ([64.165.36.235] helo=shedevil.annepmitchell.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Ayzbo-0006h8-00
	for asrg@ietf.org; Thu, 04 Mar 2004 15:38:20 -0500
Received: from [192.168.0.247] ([192.168.0.247])
	by shedevil.annepmitchell.com (8.11.6/8.11.4) with ESMTP id i24KcJX80156;
	Thu, 4 Mar 2004 12:38:19 -0800 (PST)
In-Reply-To: <20040304203054.GF13559@Space.Net>
References: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com> <20040304203054.GF13559@Space.Net>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DF237F2C-6E1B-11D8-B214-000A95AC5778@isipp.com>
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
From: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.)
To: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
X-Mailer: Apple Mail (2.612)
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/mail-archive/working-groups/asrg/>
Date: Thu, 4 Mar 2004 12:38:19 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>
>     C. FEES ASSOCIATED WITH LISTING IN IADB
> and about
>     PLEASE NOTE THAT IADB IS A PRIVATE SYSTEM, AND APPROVAL IS NOT
>     GUARANTEED. FINAL DECISION FOR INCLUSION IN IADB IS AT THE
>     DISCRETION OF ISIPP.
>

To what are you objecting here (if anything?)  If we are going to do 
things like background checks, reference checks, confirming 
bricks-and-mortar address, maintain the list, keep vigilent as to 
listees, are you saying we should do that for free?  And further, 
should it *not* be the people listed therein, the senders, who provide 
those fees?

I'm just not sure to what you are objecting.

The reservation of decision is *terribly* important, so that we don't 
get a big fat spammer who techinically can say that they meet the other 
requirements, so that therefore we *have* to list them (you wouldn't 
want that, would you?)

> How about:
>    where the definition of "spam" is that generally understood in the
>    email sending and receiving industries, and includes unsolicited
>    commercial and bulk email.
> if this RG has revealed one thing very clearly than that there is no
> such thing as a 'generally understood definition of "spam"'.

Right, which is why we cover it *both* ways - we spell out "unsolicited 
commercial and bulk email", but we *also* have wiggle room so, again, a 
big ole' spammer can't come along and say "hey, this isn't *really* 
unsolicited" - but if there are legitimate spam complaints, well, that 
sure falls within the "generally understood definition of "spam"".   If 
it walks, smells, and quacks like spam, it's likely spam, and this goes 
directly back to our reservation of rights.

> We don't need another company that tries to centralize a service, take
> money for it and then tries to play god with fluky rules.
>

Clearly you're thinking of my *previous* employer. :-b

Anne



Anne P. Mitchell, Esq.
President/CEO
Institute for Spam and Internet Public Policy
Professor of Law, Lincoln Law School of SJ


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



From exim@www1.ietf.org  Thu Mar  4 17:59:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18716
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 17:59:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az1o2-00071M-LP
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 17:59:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24Mx6qC026982
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 17:59:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az1o2-000717-Gw
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 17:59:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18595
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 17:59:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Az1o0-00011O-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 17:59:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Az1n4-0000nY-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 17:58:07 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Az1mS-0000c3-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 17:57:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az1mB-0006kb-VJ; Thu, 04 Mar 2004 17:57:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az0TX-0001ox-8p
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 16:33:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14945
	for <asrg@ietf.org>; Thu, 4 Mar 2004 16:33:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Az0TV-0000cR-00
	for asrg@ietf.org; Thu, 04 Mar 2004 16:33:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Az0Sa-0000SD-00
	for asrg@ietf.org; Thu, 04 Mar 2004 16:32:53 -0500
Received: from pcls2.std.com ([192.74.137.142] helo=TheWorld.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Az0Rj-0000IK-00
	for asrg@ietf.org; Thu, 04 Mar 2004 16:31:59 -0500
Received: from world.std.com (root@world-e.std.com [69.38.147.5])
	by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id i24LVu7O011632;
	Thu, 4 Mar 2004 16:31:56 -0500
Received: (from bzs@localhost)
	by world.std.com (8.9.3/8.9.3) id QAA22450;
	Thu, 4 Mar 2004 16:31:56 -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: <16455.41035.628541.188169@world.std.com>
To: asrg@ietf.org
In-Reply-To: <4046A77F.8020300@solidmatrix.com>
References: <200403040307.WAA01816@world.std.com>
	<4046A77F.8020300@solidmatrix.com>
X-Mailer: VM 7.07 under Emacs 21.2.2
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: Request for MS CID XML samples...
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/mail-archive/working-groups/asrg/>
Date: Thu, 4 Mar 2004 16:31:55 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


me...
> It'd be interesting to see real-life examples for msn.net,
> microsoft.com, and sendmail.com for study.

Ok, teach a man to fish: dig -t txt _ep.microsoft.com

The record I get back right now from microsoft.com is (reformatted
slightly by me for ease of reading):

  <ep xmlns='http://ms.net/1' testing='true'><out><m>"
    "<mx/>
    <a>213.199.128.160</a>
    <a>213.199.128.145</a>
    <a>207.46.71.29</a>
    <a>194.121.59.20</a>
    <a>157.60.216.10</a>
    <a>131.107.3.116</a>
    <a>131.107.3.117</a>
    <a>131.107.3.100</a>"
  "</m></out></ep>"

However, looking through our logs I see that in the past 24 hours or
so we've received email from someone@microsoft.com from the following
hosts which do not appear in that list:

      207.46.248.64       delivery.pens.microsoft.com
      207.46.248.65       delivery.pens.microsoft.com
      207.46.248.66       delivery.pens.microsoft.com
      207.46.248.67       delivery.pens.microsoft.com
      207.46.248.69       delivery.pens.microsoft.com

      131.107.3.121       mail5.microsoft.com
      131.107.3.124       mail2.microsoft.com
      131.107.3.126       mail6.microsoft.com

and, perhaps an interesting case:

      209.11.164.116      mh.microsoft.m0.net

interesting because m0.net is probably being paid to send e-mail
marketing on behalf of microsoft so the only way they'd be getting
through in this new regime would be if microsoft listed them as
authorized in their _ep record.

I suppose they (m0.net) could use the Sender: or similar alternative
but looking at an actual example I see that they (m0.net) do not. So
it'd have to be in microsoft.com's list and as far as I can tell it's
not.

So, anyone want to take a reasonable stab at these discrepancies?

By reasonable, I'm hoping for something more than "maybe the _ep
record was different when those msgs flew" because that doesn't seem
likely given the actual examples, unless you know this for a fact.

Is the microsoft.com record complete or not?

Or am I misunderstanding something?

And, if it's not complete, why not and, to reiterate my original
request, what would a complete record look like?

Thank you.

-- 
        -Barry Shein

Software Tool & Die    | bzs@TheWorld.com           | http://www.TheWorld.com
Purveyors to the Trade | Voice: 617-739-0202        | Login: 617-739-WRLD
The World              | Public Access Internet     | Since 1989     *oo*

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



From exim@www1.ietf.org  Thu Mar  4 18:13:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19968
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 18:13:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az21P-0005K9-O7
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 18:12:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24NCtHP020457
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 18:12:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az21P-0005Jo-JK
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 18:12:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19911
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 18:12:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Az21N-0003pC-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 18:12:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Az20N-0003bc-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 18:11:52 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Az1zQ-0003NN-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 18:10:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az1zN-0004UO-7C; Thu, 04 Mar 2004 18:10:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az1sm-0001Sq-Am
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 18:04:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19053
	for <asrg@ietf.org>; Thu, 4 Mar 2004 18:03:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Az1sj-00023D-00
	for asrg@ietf.org; Thu, 04 Mar 2004 18:03:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Az1rv-0001t7-00
	for asrg@ietf.org; Thu, 04 Mar 2004 18:03:07 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Az1rR-0001hy-00
	for asrg@ietf.org; Thu, 04 Mar 2004 18:02:37 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1Az1rR-0003YY-00; Thu, 04 Mar 2004 18:02:37 -0500
Received: from [68.244.156.126] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1Az1rP-0003H4-00; Thu, 04 Mar 2004 18:02:37 -0500
Message-ID: <4047B581.9080405@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Barry Shein <bzs@world.std.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] Re: Request for MS CID XML samples...
References: <200403040307.WAA01816@world.std.com>	<4046A77F.8020300@solidmatrix.com> <16455.41035.628541.188169@world.std.com>
In-Reply-To: <16455.41035.628541.188169@world.std.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 04 Mar 2004 18:02:25 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Barry Shein wrote:

> me...
> 
>>It'd be interesting to see real-life examples for msn.net,
>>microsoft.com, and sendmail.com for study.
> ....

> However, looking through our logs I see that in the past 24 hours or
> so we've received email from someone@microsoft.com from the following
> hosts which do not appear in that list:
> ....

Barry,

All of these messages, did they have @microsoft.com in their MAIL FROM 
or in the "From" header of the message itself?

Yakov

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



From exim@www1.ietf.org  Thu Mar  4 18:51:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22208
	for <asrg-archive@odin.ietf.org>; Thu, 4 Mar 2004 18:51:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az2cH-0002Gv-RG
	for asrg-archive@odin.ietf.org; Thu, 04 Mar 2004 18:51:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i24Np1cb008727
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 18:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az2cH-0002GW-0H
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 18:51:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22183
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 18:50:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Az2cE-0003Kp-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 18:50:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Az2bI-00038V-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 18:50:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Az2aS-0002uU-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 18:49:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az2aK-0001zV-VC; Thu, 04 Mar 2004 18:49:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Az2ZQ-0001sq-Rp
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 18:48:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21863
	for <asrg@ietf.org>; Thu, 4 Mar 2004 18:48:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Az2ZO-0002dq-00
	for asrg@ietf.org; Thu, 04 Mar 2004 18:48:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Az2YU-0002QK-00
	for asrg@ietf.org; Thu, 04 Mar 2004 18:47:06 -0500
Received: from mail19e.dulles19-verio.com ([198.170.241.12])
	by ietf-mx with smtp (Exim 4.12)
	id 1Az2XX-0002EX-00
	for asrg@ietf.org; Thu, 04 Mar 2004 18:46:07 -0500
Received: from www1911.dulles19-verio.com (161.58.134.165)
	by mail19e.dulles19-verio.com (RS ver 1.0.91vs) with SMTP id 0-0658673965;
	Thu,  4 Mar 2004 18:46:05 -0500 (EST)
From: "Tom Bartel" <tbartel@returnpath.net>
To: "'Barry Shein'" <bzs@world.std.com>, <asrg@ietf.org>
Subject: RE: [Asrg] Re: Request for MS CID XML samples...
Message-ID: <06e201c40242$dd90adc0$1103000a@MULDER>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <16455.41035.628541.188169@world.std.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-Loop-Detect: 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/mail-archive/working-groups/asrg/>
Date: Thu, 4 Mar 2004 16:46:07 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

As I understand it, the " testing='true' " parameter in the opening tag,
as defined in the spec, indicates that the data presented in the record
is to be assumed as an incomplete listing.

Tom Bartel
303.642.4104


> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On 
> Behalf Of Barry Shein
> Sent: Thursday, March 04, 2004 2:32 PM
> To: asrg@ietf.org
> Subject: [Asrg] Re: Request for MS CID XML samples...
> 
> 
> 
> me...
> > It'd be interesting to see real-life examples for msn.net,
> > microsoft.com, and sendmail.com for study.
> 
> Ok, teach a man to fish: dig -t txt _ep.microsoft.com
> 
> The record I get back right now from microsoft.com is (reformatted
> slightly by me for ease of reading):
> 
>   <ep xmlns='http://ms.net/1' testing='true'><out><m>"
>     "<mx/>
>     <a>213.199.128.160</a>
>     <a>213.199.128.145</a>
>     <a>207.46.71.29</a>
>     <a>194.121.59.20</a>
>     <a>157.60.216.10</a>
>     <a>131.107.3.116</a>
>     <a>131.107.3.117</a>
>     <a>131.107.3.100</a>"
>   "</m></out></ep>"
> 
> However, looking through our logs I see that in the past 24 hours or
> so we've received email from someone@microsoft.com from the following
> hosts which do not appear in that list:
> 
>       207.46.248.64       delivery.pens.microsoft.com
>       207.46.248.65       delivery.pens.microsoft.com
>       207.46.248.66       delivery.pens.microsoft.com
>       207.46.248.67       delivery.pens.microsoft.com
>       207.46.248.69       delivery.pens.microsoft.com
> 
>       131.107.3.121       mail5.microsoft.com
>       131.107.3.124       mail2.microsoft.com
>       131.107.3.126       mail6.microsoft.com
> 
> and, perhaps an interesting case:
> 
>       209.11.164.116      mh.microsoft.m0.net
> 
> interesting because m0.net is probably being paid to send e-mail
> marketing on behalf of microsoft so the only way they'd be getting
> through in this new regime would be if microsoft listed them as
> authorized in their _ep record.
> 
> I suppose they (m0.net) could use the Sender: or similar alternative
> but looking at an actual example I see that they (m0.net) do not. So
> it'd have to be in microsoft.com's list and as far as I can tell it's
> not.
> 
> So, anyone want to take a reasonable stab at these discrepancies?
> 
> By reasonable, I'm hoping for something more than "maybe the _ep
> record was different when those msgs flew" because that doesn't seem
> likely given the actual examples, unless you know this for a fact.
> 
> Is the microsoft.com record complete or not?
> 
> Or am I misunderstanding something?
> 
> And, if it's not complete, why not and, to reiterate my original
> request, what would a complete record look like?
> 
> Thank you.
> 
> -- 
>         -Barry Shein
> 
> Software Tool & Die    | bzs@TheWorld.com           | 
http://www.TheWorld.com
Purveyors to the Trade | Voice: 617-739-0202        | Login:
617-739-WRLD
The World              | Public Access Internet     | Since 1989
*oo*

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

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.596 / Virus Database: 379 - Release Date: 2/26/2004
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.596 / Virus Database: 379 - Release Date: 2/26/2004
 


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



From exim@www1.ietf.org  Fri Mar  5 07:26:08 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05202
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 07:26:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzEOY-0007f6-5X
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 07:25:39 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i25CPcwk029452
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 07:25:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzEOX-0007ex-W8
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 07:25:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05187
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 07:25:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzEOX-0005oV-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 07:25:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzENR-0005dP-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 07:24:30 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzEMU-0005Rg-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 07:23:30 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzEM1-0007I8-Dw; Fri, 05 Mar 2004 07:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzELf-0007HV-V0
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 07:22:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA05098
	for <asrg@ietf.org>; Fri, 5 Mar 2004 07:22:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzELf-0005HF-00
	for asrg@ietf.org; Fri, 05 Mar 2004 07:22:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzEL1-00055r-00
	for asrg@ietf.org; Fri, 05 Mar 2004 07:21:59 -0500
Received: from mail1.nber.org ([207.113.108.7])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzEK7-0004sM-00
	for asrg@ietf.org; Fri, 05 Mar 2004 07:21:03 -0500
Received: from mail1 (root@localhost)
	by mail1.nber.org (8.12.8/8.12.8) with SMTP id i25CL2Fw006785
	for <asrg@ietf.org>; Fri, 5 Mar 2004 07:21:02 -0500
Received: from nber1.nber.org (nber1.nber.org [207.113.108.252])
	by mail1.nber.org (8.12.8/8.12.8) with ESMTP id i25CKxBb006758;
	Fri, 5 Mar 2004 07:20:59 -0500
From: Daniel Feenberg <feenberg@nber.org>
To: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
cc: "Anne P. Mitchell, Esq." <amitchell@isipp.com>, asrg@ietf.org
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their
 Problems (Modified by Anne P. Mitchell, Esq.)
In-Reply-To: <20040304203054.GF13559@Space.Net>
Message-ID: <Pine.GSO.4.10.10403050711570.25828-100000@nber1.nber.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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/mail-archive/working-groups/asrg/>
Date: Fri, 5 Mar 2004 07:20:59 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60



On Thu, 4 Mar 2004, Markus Stumpf wrote:

> On Thu, Mar 04, 2004 at 11:01:44AM -0800, Anne P. Mitchell, Esq. wrote:
> > We're getting a great deal of positive response to our IADB (ISIPP 
> > Accreditation Database)
> 
> I'm sure you get them especially for
>     C. FEES ASSOCIATED WITH LISTING IN IADB
> and about
>     PLEASE NOTE THAT IADB IS A PRIVATE SYSTEM, AND APPROVAL IS NOT
>     GUARANTEED. FINAL DECISION FOR INCLUSION IN IADB IS AT THE
>     DISCRETION OF ISIPP.
> 
> How about:
>    where the definition of "spam" is that generally understood in the
>    email sending and receiving industries, and includes unsolicited
>    commercial and bulk email.
> if this RG has revealed one thing very clearly than that there is no
> such thing as a 'generally understood definition of "spam"'.
> 
> We don't need another company that tries to centralize a service, take
> money for it and then tries to play god with fluky rules.
> 
> Thanks, but no thanks.
> 
> 	\Maex
> 

There is a difference between "centralized" and "cooperative". There is
nothing in the plan that I can see that suggests that they should be the
only service of this type, nor do I see any liklihood that any reciepient
would want to reject mail simply because the sender is not on the list. We
have many lists of bad hosts maintained cooperatively and used by multiple
mail systems. It is hardly surprising or improper for lists of
well-behaved systems to be offered in a similar manner. 

NSI had their monopoly handed to them by an inattentive government agency.
These guys will have to earn their market share - a completely different
matter.



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



From exim@www1.ietf.org  Fri Mar  5 10:11:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12235
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 10:11:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzGyL-0000UZ-Ae
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 10:10:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i25FAjNJ001888
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 10:10:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzGyL-0000UN-2i
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 10:10:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12201
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 10:10:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzGyI-0006OV-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 10:10:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzGxG-0006EF-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 10:09:39 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzGwt-00064W-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 10:09:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzGwe-0008Jb-MO; Fri, 05 Mar 2004 10:09:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzGwE-0008Cl-7O
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 10:08:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11988
	for <asrg@ietf.org>; Fri, 5 Mar 2004 10:08:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzGwC-00063Q-00
	for asrg@ietf.org; Fri, 05 Mar 2004 10:08:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzGvD-0005tJ-00
	for asrg@ietf.org; Fri, 05 Mar 2004 10:07:32 -0500
Received: from [209.216.76.58] (helo=mail.figuerres.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzGuH-0005a8-00
	for asrg@ietf.org; Fri, 05 Mar 2004 10:06:33 -0500
Received: from viper1 [65.34.96.63] by mail.figuerres.com with ESMTP
  (SMTPD32-8.02) id A72D12C4006A; Fri, 05 Mar 2004 10:05:17 -0500
From: "denny" <denny@figuerres.com>
To: <asrg@ietf.org>
Subject: RE: [Asrg] Re: Request for MS CID XML samples...
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
In-Reply-To: <06e201c40242$dd90adc0$1103000a@MULDER>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Thread-Index: AcQCQ1N9BOBwM4+KRsOQ+Lnybs8JKwAfofuA
Message-Id: <200403051005271.SM02020@viper1>
X-IMAIL-SPAM-VALHELO: (314835050)
X-IMAIL-SPAM-VALFROM: (314835050)
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/mail-archive/working-groups/asrg/>
Date: Fri, 5 Mar 2004 10:05:40 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,HTML_MESSAGE,
	MISSING_OUTLOOK_NAME autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On Behalf Of Tom
> Bartel
> Sent: Thursday, March 04, 2004 6:46 PM
> To: 'Barry Shein'; asrg@ietf.org
> Subject: RE: [Asrg] Re: Request for MS CID XML samples...
> 
> As I understand it, the " testing='true' " parameter in the opening tag,
> as defined in the spec, indicates that the data presented in the record
> is to be assumed as an incomplete listing.
> 
> Tom Bartel
> 303.642.4104
> 
> 
> > -----Original Message-----
> > From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On
> > Behalf Of Barry Shein
> > Sent: Thursday, March 04, 2004 2:32 PM
> > To: asrg@ietf.org
> > Subject: [Asrg] Re: Request for MS CID XML samples...
> >
> >
> >
> > me...
> > > It'd be interesting to see real-life examples for msn.net,
> > > microsoft.com, and sendmail.com for study.
> >
> > Ok, teach a man to fish: dig -t txt _ep.microsoft.com
> >
> > The record I get back right now from microsoft.com is (reformatted
> > slightly by me for ease of reading):
> >
> >   <ep xmlns='http://ms.net/1' testing='true'><out><m>"
> >     "<mx/>
> >     <a>213.199.128.160</a>
> >     <a>213.199.128.145</a>
> >     <a>207.46.71.29</a>
> >     <a>194.121.59.20</a>
> >     <a>157.60.216.10</a>
> >     <a>131.107.3.116</a>
> >     <a>131.107.3.117</a>
> >     <a>131.107.3.100</a>"
> >   "</m></out></ep>"
> >
> > However, looking through our logs I see that in the past 24 hours or
> > so we've received email from someone@microsoft.com from the following
> > hosts which do not appear in that list:
> >
> >       207.46.248.64       delivery.pens.microsoft.com
> >       207.46.248.65       delivery.pens.microsoft.com
> >       207.46.248.66       delivery.pens.microsoft.com
> >       207.46.248.67       delivery.pens.microsoft.com
> >       207.46.248.69       delivery.pens.microsoft.com
> >
> >       131.107.3.121       mail5.microsoft.com
> >       131.107.3.124       mail2.microsoft.com
> >       131.107.3.126       mail6.microsoft.com
> >
> > and, perhaps an interesting case:
> >
> >       209.11.164.116      mh.microsoft.m0.net
> >
> > interesting because m0.net is probably being paid to send e-mail
> > marketing on behalf of microsoft so the only way they'd be getting
> > through in this new regime would be if microsoft listed them as
> > authorized in their _ep record.
> >
> > I suppose they (m0.net) could use the Sender: or similar alternative
> > but looking at an actual example I see that they (m0.net) do not. So
> > it'd have to be in microsoft.com's list and as far as I can tell it's
> > not.
> >
> > So, anyone want to take a reasonable stab at these discrepancies?
> >
> > By reasonable, I'm hoping for something more than "maybe the _ep
> > record was different when those msgs flew" because that doesn't seem
> > likely given the actual examples, unless you know this for a fact.
> >
> > Is the microsoft.com record complete or not?
> >
> > Or am I misunderstanding something?
> >
[denny] 

Not sure if this is what the deal is but I can say that about 2 months back
I was talking to a local Microsoft rep at a tech event and I asked him about
the email that comes from MS....
He claimed that as far as he knew they had fixed the emails to all come from
*Microsoft.com
Like delivery.pens. and other hosts under the ms domain.

But for example www.gotdotnet.com which is run by ms still is not fixed and
they say that (as of about a month back) they it's going to be fixed to map
right.


So it may be in part the effect of having like 10,000 email hosting deals to
"round up" and fix....

And yea m0.net sends stuff for a bunch of legit businesses but gets in the
spam lists also....

I'd try to contact the channel that sent the *.m0.net mail and tell them to
get it moved....

About 6 months back I had a *LOT* of ms stuff in my blacklist email boxes
all the time. I'd say that now it's just a few... I think they are fixing it
as best they can given the volume of programs they run.


> > And, if it's not complete, why not and, to reiterate my original
> > request, what would a complete record look like?
> >
> > Thank you.
> >
> > --
> >         -Barry Shein
> >
> > Software Tool & Die    | bzs@TheWorld.com           |
> http://www.TheWorld.com
> Purveyors to the Trade | Voice: 617-739-0202        | Login:
> 617-739-WRLD
> The World              | Public Access Internet     | Since 1989
> *oo*
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.596 / Virus Database: 379 - Release Date: 2/26/2004
> 
> 
> ---
> Outgoing mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.596 / Virus Database: 379 - Release Date: 2/26/2004
> 
> 
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg


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



From exim@www1.ietf.org  Fri Mar  5 12:59:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20191
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 12:59:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzJb7-0001s0-5N
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 12:58:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i25Hwv8o007184
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 12:58:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzJb6-0001rn-VR
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 12:58:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20185
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 12:58:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzJb3-0000ad-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 12:58:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzJa9-0000P0-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 12:57:58 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzJZY-0000DM-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 12:57:20 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AzJZa-0004FE-Hq
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 12:57:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzJZE-0001Pc-IA; Fri, 05 Mar 2004 12:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzJYx-0001Om-VF
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 12:56:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20022
	for <asrg@ietf.org>; Fri, 5 Mar 2004 12:56:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzJYu-00009c-00
	for asrg@ietf.org; Fri, 05 Mar 2004 12:56:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzJXu-0007la-00
	for asrg@ietf.org; Fri, 05 Mar 2004 12:55:39 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AzJWw-0007Vq-00
	for asrg@ietf.org; Fri, 05 Mar 2004 12:54:38 -0500
Received: (qmail 25706 invoked by uid 1013); 5 Mar 2004 17:54:36 -0000
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
Cc: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>, asrg@ietf.org
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.)
Message-ID: <20040305175436.GA21252@Space.Net>
References: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com> <20040304203054.GF13559@Space.Net> <DF237F2C-6E1B-11D8-B214-000A95AC5778@isipp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DF237F2C-6E1B-11D8-B214-000A95AC5778@isipp.com>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
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/mail-archive/working-groups/asrg/>
Date: Fri, 5 Mar 2004 18:54:36 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Thu, Mar 04, 2004 at 12:38:19PM -0800, Anne P. Mitchell, Esq. wrote:
> >
> >    C. FEES ASSOCIATED WITH LISTING IN IADB
> >and about
> >    PLEASE NOTE THAT IADB IS A PRIVATE SYSTEM, AND APPROVAL IS NOT
> >    GUARANTEED. FINAL DECISION FOR INCLUSION IN IADB IS AT THE
> >    DISCRETION OF ISIPP.
> 
> To what are you objecting here (if anything?)  If we are going to do 
> things like background checks, reference checks, confirming 
> bricks-and-mortar address, maintain the list, keep vigilent as to 
> listees, are you saying we should do that for free?  And further, 
> should it *not* be the people listed therein, the senders, who provide 
> those fees?
> 
> I'm just not sure to what you are objecting.

I am objecting that "FINAL DECISION FOR INCLUSION IN IADB IS AT THE
DISCRETION OF ISIPP" and not whether it depends on successful passing
of the criteria. With the above sentence, even if I am the honest
man in the whole Internet it is up to your good will to be added to
the database or not.

> The reservation of decision is *terribly* important, so that we don't 
> get a big fat spammer who techinically can say that they meet the other 
> requirements, so that therefore we *have* to list them (you wouldn't 
> want that, would you?)

If you can't find any definitive term to nail him down and separate him
from the "good guys" than this is a problem with the terms.
I will NEVER trust any system that depends on the good will of some
people and that backs up goodwill decisions with their terms of service.

> sure falls within the "generally understood definition of "spam"".   If 
> it walks, smells, and quacks like spam, it's likely spam, and this goes 
> directly back to our reservation of rights.

Our abuse department receives spam complaints even for double opt-in
announcement/newsletter mailinglists of our customers for which *I
guarantee* that the only way to get an address on that list is with
double opt-in (with crypto support -> ezmlm).
Our abuse department receives spam complaints where people use a "service"
to get added to Internet lotteries and receive double opt-in confirmations
because the "service" always checks the "send me your newsletter" flag.
They claim that this is spam and unwanted.

How much time and money per complaint are you willing to spend to
investigate these cases? Are you going to hire interpreters if I am your
client (we're located in Germany) and you get complaints about "spam"
in German? Or are you making simple decisions based on your reservation
of rights?

> >We don't need another company that tries to centralize a service, take
> >money for it and then tries to play god with fluky rules.
> 
> Clearly you're thinking of my *previous* employer. :-b

No, I only said we don't need another company with the above ambitions.

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"

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



From exim@www1.ietf.org  Fri Mar  5 13:41:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22002
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 13:41:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzKFl-0006X0-9l
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 13:40:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i25IevJl025100
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 13:40:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzKFl-0006Wl-1i
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 13:40:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21987
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 13:40:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzKFh-00013l-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 13:40:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzKEo-0000tD-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 13:39:59 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzKE0-0000iR-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 13:39:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzKDs-0005pB-U8; Fri, 05 Mar 2004 13:39:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzHij-0006Zo-Vh
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 10:58:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14539
	for <asrg@ietf.org>; Fri, 5 Mar 2004 10:58:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzHih-0007Wr-00
	for asrg@ietf.org; Fri, 05 Mar 2004 10:58:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzHhn-0007NA-00
	for asrg@ietf.org; Fri, 05 Mar 2004 10:57:44 -0500
Received: from main.gmane.org ([80.91.224.249])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzHhI-0007Cg-00
	for asrg@ietf.org; Fri, 05 Mar 2004 10:57:12 -0500
Received: from list by main.gmane.org with local (Exim 3.35 #1 (Debian))
	id 1AzHhC-0005NC-00
	for <asrg@ietf.org>; Fri, 05 Mar 2004 16:57:06 +0100
Received: from footbone.midwestcs.com ([206.222.212.237])
        by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <asrg@ietf.org>; Fri, 05 Mar 2004 16:57:06 +0100
Received: from wayne by footbone.midwestcs.com with local (Gmexim 0.1 (Debian))
        id 1AlnuQ-0007hv-00
        for <asrg@ietf.org>; Fri, 05 Mar 2004 16:57:06 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: asrg@ietf.org
From: wayne <wayne@midwestcs.com>
Lines: 52
Message-ID: <x4ishjqoc0.fsf@footbone.midwestcs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: footbone.midwestcs.com
User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through
 Obscurity, linux)
Cancel-Lock: sha1:ON6WCLtHbnE0TxJhRg66gD8G9N8=
Subject: [Asrg] videos of the IETF BoF
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/mail-archive/working-groups/asrg/>
Date: Fri, 05 Mar 2004 09:57:03 -0600
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60



Hi.

There has been some discussion on the SPF-discuss mailing list about
the recent BoF on anti-spam systems.  I thought you folks might be
interested in it also.



For those that want to see this session, you can download an mpeg from:

ftp://limestone.uoregon.edu/pub/videolab/video/ietf59/ietf59-ch1-thur-am_040304_0845_5.mpg

Note that this mpeg is 1.2GB of nice high res pictures of people
talking in stereo sound at 192kbps.

I have created a smaller file (over a factor of 6 smaller) that has
almost the same quality.  The bad news is that this mpeg does not seem
to run on Windows.  It appears to work fine on Linux and *BSD using
mplayer and xine, but no one has found any program to display it on
Windows.  I'm not a video geek and I know just enough about this stuff
to be dangerous.  :-<


Sorry Windows people.  If some kind person with a clue would help me
out, or do the conversion themselves, that would be great.


The Unix mpeg is available via bittorrent at:

http://www.midwestcs.com/IETF_videos/ietf_marid.mpg.torrent

I need bittorrent users to keep their torrents up, I can not provide
that much bandwidth.  BitTorrent plugins can ben found at: 
http://bitconjurer.org/BitTorrent/

There are rumors that this video works under Win2K using the 
Videolan client.

http://www.videolan.org/vlc/

They have a MacOSX port to.

I also suspect it will work fine under Mac OS X, with the mplayerOSX
binaries.  See:

http://mplayerosx.sourceforge.net/


-wayne



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



From exim@www1.ietf.org  Fri Mar  5 14:31:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24349
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 14:31:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzL2P-0004h1-Ij
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 14:31:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i25JVDb6018033
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 14:31:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzL2P-0004gm-Da
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 14:31:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24269
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 14:31:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzL2L-0002mv-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 14:31:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzL0U-0002Ex-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 14:29:14 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzKzG-0001yl-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 14:27:58 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AzKsl-0005gl-Vd
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 14:21:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzKsY-0003Qo-6u; Fri, 05 Mar 2004 14:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzKsN-0003Q1-W0
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 14:20:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24025
	for <asrg@ietf.org>; Fri, 5 Mar 2004 14:20:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzKsJ-0000s8-00
	for asrg@ietf.org; Fri, 05 Mar 2004 14:20:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzKrT-0000ib-00
	for asrg@ietf.org; Fri, 05 Mar 2004 14:19:56 -0500
Received: from smtp.rol.ru ([194.67.21.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzKqn-0000WN-00
	for asrg@ietf.org; Fri, 05 Mar 2004 14:19:13 -0500
Received: from ariel.sovam.com ([194.67.3.216]:62091 "EHLO ariel.sovam.com"
	smtp-auth: "egc@online.ru" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits
	256/256 version TLSv1/SSLv3" TLS-PEER-CN1: <none>)
	by gnome07.net.rol.ru with ESMTP id S9770072AbUCETSl (ORCPT
	<rfc822;asrg@ietf.org>); Fri, 5 Mar 2004 22:18:41 +0300
From: Eugene Crosser <crosser@rol.ru>
To: asrg@ietf.org
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-lTyCSsg1hqdApeXZ2AAO"
Organization: Sovintel
Message-Id: <1078514131.3350.61.camel@ariel.sovam.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
Subject: [Asrg] 3b. SMTP Session Verification - old good POP before SMTP
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/mail-archive/working-groups/asrg/>
Date: Fri, 05 Mar 2004 22:15:31 +0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--=-lTyCSsg1hqdApeXZ2AAO
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

Gentlemen,

Back in 1998, when there there where still many non-SMTP-AUTH capable
MUAs around, I made up a protocol to use "POP before SMTP" style
authorization in distributed environment, and wrote software
implementing it.  It was running in production on our system until
recently (which gives 5+ years, wow!).

Nowdays, when most MUAs support SMTP AUTH, the method is probably not
relevant, but it is still within the ASRG agenda, so I thought that I'd
let you know.  At least as a historical reference.

	http://whoson.sourceforge.net/

(the draft itself is here: http://whoson.sourceforge.net/whoson.txt)

Eugene

--=-lTyCSsg1hqdApeXZ2AAO
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQBASNHTtQFsU5rTNjcRAl4CAKCuWTSHa+g5XEVYDhjMe/RnOGBrhACfZ1EG
yT4MDNAT4R+yJplohB+6gew=
=0MlY
-----END PGP SIGNATURE-----

--=-lTyCSsg1hqdApeXZ2AAO--


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



From exim@www1.ietf.org  Fri Mar  5 14:47:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25568
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 14:47:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLHv-00071Z-8g
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 14:47:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i25JlFQv026995
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 14:47:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLHv-00071K-2v
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 14:47:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25564
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 14:47:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLHq-0006rP-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 14:47:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzLGt-0006eE-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 14:46:12 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLGM-0006RQ-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 14:45:38 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AzLGO-0006ST-12
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 14:45:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLFm-0006nM-In; Fri, 05 Mar 2004 14:45:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLDg-0006Yk-3G
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 14:42:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25344
	for <asrg@ietf.org>; Fri, 5 Mar 2004 14:42:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLDb-000618-00
	for asrg@ietf.org; Fri, 05 Mar 2004 14:42:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzLCa-0005fd-00
	for asrg@ietf.org; Fri, 05 Mar 2004 14:41:45 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLAs-0005G7-00
	for asrg@ietf.org; Fri, 05 Mar 2004 14:39:58 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AzLAm-0003Dc-00; Fri, 05 Mar 2004 14:39:52 -0500
Received: from [68.244.181.67] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AzLAh-0001Gl-00; Fri, 05 Mar 2004 14:39:49 -0500
Message-ID: <4048D777.4020508@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their
 Problems (Modified by Anne P. Mitchell, Esq.)
References: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com>
In-Reply-To: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Fri, 05 Mar 2004 14:39:35 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,BAD_CREDIT autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Anne P. Mitchell, Esq. wrote:
> Oops...1000 apologies - resent with proper subject line:
> 

NP :)

>>> why would any proposed
>>> reputation or accrediation systems of the future be any different?
> 
> 
> We're getting a great deal of positive response to our IADB (ISIPP 
> Accreditation Database) even though we haven't publicly announced it yet 
> (if you are not familiar with it you can read about it at 
> http://www.isipp.com/iadb.php).  What are the problems you feel are 
> innate to DNS blocklists which you feel are also ported to DNSWLs or 
> other non-block DNS lists?
> 

Allow me to explain. There are multiple problems with reputation and 
accreditation systems, virtually all of which are non-technical in 
nature. There are a few technical problems as well: suspectibility to 
DDOS attacks unless the database is distributed and not centralized, 
whether automatic testing for things like open relays is foolproof, 
problems with protocols, etc. However I want to concentrate on the 
non-technical issues.

There are multiple types of reputation and accreditation systems (please 
feel free to correct anything). At the most basic, a reputation system 
provides information about a given organization, MTA, IP, ISP, etc. such 
as how long has this system been an MTA, average amount of outgoing 
email per day, etc. This information is not biased towards or away from 
blacklisting, but rather is provided as simply a source of statistical 
data to be used. This is similar to the statistical data provided by a 
credit agency on a credit report in the US about the accounts a person 
has, amount of credit, average balance, etc. The closest example of this 
today is SenderBase.

Then we have the various blacklist reputation systems which provide 
negative information such as this IP is an open relay, this IP is a 
spammer, this ISP hosts spammers, etc. This is the most prevalent type 
today, examples abound (SPEWS, MAPS, etc.). A real world example of this 
would be a credir agency reporting negative data about a person such as 
bankruptcy, bad credit, collections, etc. Human or community-based 
systems such as SpamCop or CloudMark would fall into this category as well.

Now we also have whitelist systems which are not reputation systems per 
se, but rather are accreditation systems. They allow parties with 
otherwise bad or unknown reputation such as new providers, IP blocks 
reassigned from spammers, email that would otherwise be caught by a 
filter, etc. to be accredited as good guys. Examples of this are 
BondedSender and your IADB. An example of this in the real world would 
be a person with bad or unknown credit coming to get a loan, and 
bringing along a letter of reference or a letter vouching for him from a 
trusted third party.

I am not saying that they are used specifically by bad guys or people 
with bad prior reputation, but the main purpose of accreditation systems 
is whitelisting email that might not get through otherwise.

There are also differences how different types of systems are managed - 
some are based on automated testing of open relays and such (SpamHaus's 
XBL, MAPS RSS and OPS, etc.), others are based on spam reports from 
people or community (SpamCop, Cloudmark, etc.), yet many are also based 
specifically on human reports and decisions by operators (SpamHaus 
ROKSO, SPEWS, etc.). The SMTP VERIFY subgroup has also discussed other 
posibilities such as reputation based on "web of trust".

The major problem with all of these is management rather than the 
technical details. Let me go through these:

1. Statistical systems - for these there are several problems. First 
problem is accuracy - the data collected by the system must be accurate 
and in order to assure that the collection process needs to be done in a 
  statistically sound matter. In particular, such system needs to cover 
a statistically significant percentage of email traffic to be accurate. 
Second, problem with statistical systems is lack of openness - the 
collection process and internal management practices must be open for 
public scrutiny and preferablly audited on a regular basis by an 
independent third party. This will preclude the operators from skewing 
the data based on their own motives. Third problem, is the "tyranny by 
the mob" - a statistical system must be able to account for the 
possibility of multiple reporting systems ganging up together and 
reporting false data in order to destroy someone's reputation. The 
fourth problem is legal, which I am not sure if it would apply. Anne, as 
a lawyer is more qualified to answer whether such statistical systems 
are likely to get sued. The fifth problem is whether such systems raise 
the bar for new MTAs on the Internet.

2. Blacklist reputation services - there are multiple problems which 
vary depending on how the list is managed. The main problem common to 
all of these is lack of open procedures about how things get added to 
the list, how long they stay on and how they can be taken off. Another 
big problem is lack of review or any kind of appeal process unlike the 
credit agencies in the US which was my real world example. There are 
also subtle differences between management types - human and community 
based systems are suspectible to the "tyranny by the mob" problem 
described above, automated systems need to deal with dynamic IPs and 
clarify the length of time spend on list and re-testing intervals (AOL 
retests once a day, not all BLs do), some BL operators tend to list 
others on the same block or ISP causing collateral damage, etc. Legal 
issues very much apply here as we saw from the various lawsuits 
surrounding blacklists. Also, in many cases blacklist operators are 
making a decision based on their beliefs which might not the same as the 
beliefs of their users. Many ISPs would rather make the decision 
themselves if they had access to the raw data that the BL operators had. 
That raw data in many cases is not exposed, or cannot be provided in an 
automated form. Lack of any appeal process, especially with SPEWS is a 
big problem as well. Lack of openness in BL operations is an issue. No 
third party audit or review to let us know that the BL operators are 
following their guidelines.

3. Whitelist and Accreditation services - less problems than others and 
more subtle. The main issue is one of a gatekeeper - if a small set of 
whitelists or one is choosen by many large ISPs, that whitelist 
effectively becomes the gatekeeper for the email system - "power 
corrupts, absolute power corrups absolutely". In order to counteract 
that, whitelists need to be very open and auditable by third parties. Of 
course, currently since we do not have too many of those, it's pretty 
earlier to say that, but the issue is important to keep in mind. DDOS 
issues come to mind as well.

In practice it is impossible for an average spam filter to utilize data 
from too many reputation systems, and therefore it is expected that only 
a few will be choosen. That would mean we must be careful with whitelist 
services to make sure that they do not raise the barrier of entry to the 
Internet community.

Yakov




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



From exim@www1.ietf.org  Fri Mar  5 14:55:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26128
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 14:55:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLPO-00082R-T7
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 14:54:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i25Jswhm030893
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 14:54:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLPO-00082C-On
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 14:54:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26093
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 14:54:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLPK-0000hs-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 14:54:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzLOT-0000Ut-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 14:54:02 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLNX-0000HE-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 14:53:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLNV-0007lj-GC; Fri, 05 Mar 2004 14:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLNQ-0007ke-67
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 14:52:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25905
	for <asrg@ietf.org>; Fri, 5 Mar 2004 14:52:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLNL-0000FG-00
	for asrg@ietf.org; Fri, 05 Mar 2004 14:52:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzLMQ-00003Q-00
	for asrg@ietf.org; Fri, 05 Mar 2004 14:51:54 -0500
Received: from adsl-64-165-36-235.dsl.snfc21.pacbell.net ([64.165.36.235] helo=shedevil.annepmitchell.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLLZ-0007gW-00
	for asrg@ietf.org; Fri, 05 Mar 2004 14:51:01 -0500
Received: from [192.168.0.247] ([192.168.0.247])
	by shedevil.annepmitchell.com (8.11.6/8.11.4) with ESMTP id i25Jp0X98470;
	Fri, 5 Mar 2004 11:51:00 -0800 (PST)
In-Reply-To: <4048D777.4020508@solidmatrix.com>
References: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com> <4048D777.4020508@solidmatrix.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <6D1485F9-6EDE-11D8-B214-000A95AC5778@isipp.com>
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
From: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.)
To: Yakov Shafranovich <research@solidmatrix.com>
X-Mailer: Apple Mail (2.612)
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/mail-archive/working-groups/asrg/>
Date: Fri, 5 Mar 2004 11:50:59 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Mar 5, 2004, at 11:39 AM, Yakov Shafranovich wrote:

> I am not saying that they are used specifically by bad guys or people 
> with bad prior reputation, but the main purpose of accreditation 
> systems is whitelisting email that might not get through otherwise.

I'm going to excise this out and answer this specifically, because so 
much of the rest of your reply is predicated on this premise.

That is not what an accreditation system (necessarily) is, and it's not 
what IADB is.  IADB is very specifically _not_ a whitelist (nor a 
blocklist) - it is, if you will, a colour-neutral list, whicih provides 
you with very specific datapoints.  It's a companion to a 
sender-authentication check.  Taking an accreditation check (such as to 
IADB) along with a sender identity check you know:

a)  who the sender is
b)  that they really are who they say they are
c)  that the source IP address is consistent with whom they say they 
are, and
c)  that they have been found to meet a certain set of standards

The real world example of an accreditation is Underwriters Labs, or the 
Good Housekeeping Seal of Approval.  Or that certificate in an elevator 
saying it has been inspected on such-and-such a date.
Or a school being accredited.

All of these, like a listing in IADB, say "the product bearing this 
accreditation has been proven to meet a certain set of standards as 
determined by the accrediting body."

It's your choice to determine what that means to you;  I know very few 
people who would accept any of the above, *alone*, as the reason to 
choose the particular product, or accept the particular email.  There 
are plenty of schools which are accredited to which I would not send my 
dog, let alone my child.  Likewise plenty of products bearing the UL 
label which I would not take if you paid me, let alone spend money on.

But taken as a datapoint, matched up with other datapoints (in this 
case sender i.d., lack of presence in a blocklist - whatever criteria 
*you* choose), it's very useful.

It is, if you will, reputation once removed.  If you trust Underwriters 
Lab then you take their seal at face value to mean "this product passes 
UL's requirements to bear this seal".  If you trust ISIPP, then you 
take a listing in the IADB at face value to mean "this sender meets the 
ISIPP criteria".

Anne






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



From exim@www1.ietf.org  Fri Mar  5 15:05:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26786
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 15:05:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLZ1-0005ZR-Mg
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 15:04:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i25K4tKe021413
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 15:04:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLZ1-0005ZI-J1
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 15:04:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26723
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 15:04:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLYw-0002bB-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 15:04:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzLY0-0002R9-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 15:03:53 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLXL-0002HK-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 15:03:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLXB-0003gE-WE; Fri, 05 Mar 2004 15:03:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLX8-0003cW-NX
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 15:02:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26578
	for <asrg@ietf.org>; Fri, 5 Mar 2004 15:02:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLX3-0002GT-00
	for asrg@ietf.org; Fri, 05 Mar 2004 15:02:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzLWD-00025r-00
	for asrg@ietf.org; Fri, 05 Mar 2004 15:02:01 -0500
Received: from sokol.elan.net ([216.151.192.200])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLVS-0001vC-00
	for asrg@ietf.org; Fri, 05 Mar 2004 15:01:14 -0500
Received: from sokol.elan.net (localhost.localdomain [127.0.0.1])
	by sokol.elan.net (8.12.5/8.12.5) with ESMTP id i25L5VrC029013
	for <asrg@ietf.org>; Fri, 5 Mar 2004 13:05:31 -0800
Received: from localhost (william@localhost)
	by sokol.elan.net (8.12.5/8.12.5/Submit) with ESMTP id i25L5UBV029009
	for <asrg@ietf.org>; Fri, 5 Mar 2004 13:05:30 -0800
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
From: "william(at)elan.net" <william@elan.net>
To: asrg@ietf.org
Subject: Re: [Asrg] videos of the IETF BoF
In-Reply-To: <x4ishjqoc0.fsf@footbone.midwestcs.com>
Message-ID: <Pine.LNX.4.44.0403051303490.7031-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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/mail-archive/working-groups/asrg/>
Date: Fri, 5 Mar 2004 13:05:30 -0800 (PST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


For windows try the following links (ffdshow is probably what you need):

ffdshow: http://cutka.szm.sk/ffdshow or
 http://sourceforge.net/projects/ffdshow
XviD:    http://www.xvid.org
ffmpeg:  http://ffmpeg.org
mplayer: http://www.mplayerhq.hu

On Fri, 5 Mar 2004, wayne wrote:

> Hi.
> 
> There has been some discussion on the SPF-discuss mailing list about
> the recent BoF on anti-spam systems.  I thought you folks might be
> interested in it also.
> 
> For those that want to see this session, you can download an mpeg from:
> 
> ftp://limestone.uoregon.edu/pub/videolab/video/ietf59/ietf59-ch1-thur-am_040304_0845_5.mpg
> 
> Note that this mpeg is 1.2GB of nice high res pictures of people
> talking in stereo sound at 192kbps.
> 
> I have created a smaller file (over a factor of 6 smaller) that has
> almost the same quality.  The bad news is that this mpeg does not seem
> to run on Windows.  It appears to work fine on Linux and *BSD using
> mplayer and xine, but no one has found any program to display it on
> Windows.  I'm not a video geek and I know just enough about this stuff
> to be dangerous.  :-<
> 
> Sorry Windows people.  If some kind person with a clue would help me
> out, or do the conversion themselves, that would be great.
> 
> The Unix mpeg is available via bittorrent at:
> 
> http://www.midwestcs.com/IETF_videos/ietf_marid.mpg.torrent
> 
> I need bittorrent users to keep their torrents up, I can not provide
> that much bandwidth.  BitTorrent plugins can ben found at: 
> http://bitconjurer.org/BitTorrent/
> 
> There are rumors that this video works under Win2K using the 
> Videolan client.
> 
> http://www.videolan.org/vlc/
> 
> They have a MacOSX port to.
> 
> I also suspect it will work fine under Mac OS X, with the mplayerOSX
> binaries.  See:
> 
> http://mplayerosx.sourceforge.net/
> 
> 
> -wayne
> 
> 
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg


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



From exim@www1.ietf.org  Fri Mar  5 15:32:20 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28524
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 15:32:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLz4-0004Hz-TZ
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 15:31:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i25KVoSo016481
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 15:31:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLz4-0004Hk-O2
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 15:31:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28521
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 15:31:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLz3-0007Xb-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 15:31:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzLyA-0007OL-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 15:30:55 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLxc-0007Es-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 15:30:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLxK-0003vN-Au; Fri, 05 Mar 2004 15:30:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLx6-0003tG-4Y
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 15:29:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28473
	for <asrg@ietf.org>; Fri, 5 Mar 2004 15:29:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLx4-0007Dc-00
	for asrg@ietf.org; Fri, 05 Mar 2004 15:29:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzLw6-00074h-00
	for asrg@ietf.org; Fri, 05 Mar 2004 15:28:46 -0500
Received: from fe01.axelero.hu ([195.228.240.89] helo=damo.axelero.hu)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLvG-0006vp-00
	for asrg@ietf.org; Fri, 05 Mar 2004 15:27:55 -0500
Received: from damo (localhost-02 [127.0.2.1])
	by damo.axelero.hu (8.12.11/8.12.11) with SMTP id i25KRsIF013118
	for <asrg@ietf.org>; Fri, 5 Mar 2004 21:27:54 +0100 (CET)
Received: from fe01.axelero.hu [127.0.2.1] via SMTP gateway
	by damo [195.228.240.89]; id A0333BF172C
	at Fri, 05 Mar 2004 21:27:53 +0100
Received: from axelero.hu (4.164-182-adsl-pool.axelero.hu [81.182.164.4])
	by fe01.axelero.hu (8.12.11/8.12.11) with ESMTP id i25KRnqZ013007
	for <asrg@ietf.org>; Fri, 5 Mar 2004 21:27:52 +0100 (CET)
Message-ID: <4048E2C4.6020607@axelero.hu>
From: "Za'mbori, Zolta'n" <zamboriz@axelero.hu>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: hu, en
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
References: <x4ishjqoc0.fsf@footbone.midwestcs.com>
In-Reply-To: <x4ishjqoc0.fsf@footbone.midwestcs.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: videos of the IETF BoF
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/mail-archive/working-groups/asrg/>
Date: Fri, 05 Mar 2004 21:27:48 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

wayne wrote:
> The Unix mpeg is available via bittorrent at:
> 
> http://www.midwestcs.com/IETF_videos/ietf_marid.mpg.torrent

http://www.midwestcs.com/spf/IETF_videos/ietf_marid.mpg.torrent

z2

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



From exim@www1.ietf.org  Fri Mar  5 15:37:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28664
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 15:37:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzM3z-0005cY-FL
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 15:36:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i25KatsH021600
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 15:36:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzM3z-0005cJ-7K
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 15:36:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28642
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 15:36:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzM3x-0000bC-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 15:36:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzM32-0000Qv-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 15:35:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzM2F-0000Gh-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 15:35:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzM29-0005SB-VX; Fri, 05 Mar 2004 15:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzLzz-0004IV-35
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 15:32:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28552
	for <asrg@ietf.org>; Fri, 5 Mar 2004 15:32:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLzx-0007hr-00
	for asrg@ietf.org; Fri, 05 Mar 2004 15:32:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzLz2-0007XT-00
	for asrg@ietf.org; Fri, 05 Mar 2004 15:31:48 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzLyA-0007OG-00
	for asrg@ietf.org; Fri, 05 Mar 2004 15:30:54 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1AzLy9-0004Bl-00; Fri, 05 Mar 2004 15:30:53 -0500
Received: from [68.244.181.67] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1AzLy8-0002Mu-00; Fri, 05 Mar 2004 15:30:53 -0500
Message-ID: <4048E376.7000101@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their
 Problems (Modified by Anne P. Mitchell, Esq.)
References: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com> <4048D777.4020508@solidmatrix.com> <6D1485F9-6EDE-11D8-B214-000A95AC5778@isipp.com>
In-Reply-To: <6D1485F9-6EDE-11D8-B214-000A95AC5778@isipp.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Fri, 05 Mar 2004 15:30:46 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Anne P. Mitchell, Esq. wrote:
> 
> On Mar 5, 2004, at 11:39 AM, Yakov Shafranovich wrote:
> 
>> I am not saying that they are used specifically by bad guys or people 
>> with bad prior reputation, but the main purpose of accreditation 
>> systems is whitelisting email that might not get through otherwise.
> 
> 
> I'm going to excise this out and answer this specifically, because so 
> much of the rest of your reply is predicated on this premise.
> 

Thank you for the clarifications.

....
> All of these, like a listing in IADB, say "the product bearing this 
> accreditation has been proven to meet a certain set of standards as 
> determined by the accrediting body."
> 
> It's your choice to determine what that means to you;  I know very few 
> people who would accept any of the above, *alone*, as the reason to 
> choose the particular product, or accept the particular email.  There 
> are plenty of schools which are accredited to which I would not send my 
> dog, let alone my child.  Likewise plenty of products bearing the UL 
> label which I would not take if you paid me, let alone spend money on.
> 
> But taken as a datapoint, matched up with other datapoints (in this case 
> sender i.d., lack of presence in a blocklist - whatever criteria *you* 
> choose), it's very useful.
> 
> It is, if you will, reputation once removed.  If you trust Underwriters 
> Lab then you take their seal at face value to mean "this product passes 
> UL's requirements to bear this seal".  If you trust ISIPP, then you take 
> a listing in the IADB at face value to mean "this sender meets the ISIPP 
> criteria".

Thank you very much for the clarifications. In my example, I used a 
letter of reference from a third party as a real world example which 
goes well with the example you are giving here of "reputation once removed".

I guess I would say that my concern is not with the accreditation 
concept itself but rather with how it is used. I agree with you that 
accreditation by itself is not bad if it is used properly, but what 
concerns me is a parallel to blacklists. Many blacklists say that you 
should not use them as the only source of information, but many ISPs 
ignore that and do it anyway. What I am afraid of is the same happening 
with with accreditation.

But I must say that I do not see this problem as significant with as it 
is with blacklists, especially in light of your comment about schools 
above. People will err on the side of caution in the anti-spam world, 
and they will never trust anyone fully for whitelisting, even you (of 
course it depends on how the major ISPs use it - if the big ISPs 
suddenly start using IADB as a single criteria for whitelisting, it 
changes things but that's not your problem). So, the likehood of a 
single whitelist system becoming trusted by a large percentage of the 
Internet is less likely than a blacklist.

Having said that, my original question is more relevant to blacklists 
and statistical systems - with any form of identity and reputation 
system, how can we prevent the same problems that haunt today's blacklists?

Yakov

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



From exim@www1.ietf.org  Fri Mar  5 16:21:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00420
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 16:21:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzMkY-0000aO-HZ
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 16:20:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i25LKsTg002238
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 16:20:54 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzMkV-0000a1-OS
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 16:20:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00370
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 16:20:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzMkU-0000XM-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 16:20:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzMjf-0000MJ-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 16:20:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzMin-0000Ac-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 16:19:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzMii-0000Lq-Fx; Fri, 05 Mar 2004 16:19:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzMhq-0000Jc-H8
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 16:18:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00214
	for <asrg@ietf.org>; Fri, 5 Mar 2004 16:18:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzMho-0007kF-00
	for asrg@ietf.org; Fri, 05 Mar 2004 16:18:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzMgx-0007YL-00
	for asrg@ietf.org; Fri, 05 Mar 2004 16:17:11 -0500
Received: from pop19.ucdavis.edu ([169.237.105.29])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzMft-0007LV-00
	for asrg@ietf.org; Fri, 05 Mar 2004 16:16:05 -0500
Received: from cs.ucdavis.edu (nat6-182.cs.ucdavis.edu [169.237.6.182])
	by pop19.ucdavis.edu (8.12.10/8.12.9/it-std-5.2.0) with ESMTP id i25LG0ox024723;
	Fri, 5 Mar 2004 13:16:01 -0800 (PST)
Message-ID: <4048EE0B.7050800@cs.ucdavis.edu>
From: Greg Wittel <wittel+asrg@cs.ucdavis.edu>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
CC: crosser@rol.ru
Subject: Re: [Asrg] 1c. Analysis of Spam - biological approach
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Fri, 05 Mar 2004 13:15:55 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>> Anyone with a degree in bioscience here?  Or willing to bring in
>> someone knowledgeble?  Any previous works in this area?
> 
> 
> I do not think this view has been taken before with spam (in terms of
> a research paper at least).  Though it's a very interesting idea.

As a small update, I stumbled across two papers (written in 2003) that 
attempt to take a biological approach:
    http://terri.zone12.com/me/publications/
Papers titled:
    Developing an Immunity to Spam
    Increasing the Accuracy of a Spam-Detecting Artificial Immune System

-Greg

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



From exim@www1.ietf.org  Fri Mar  5 20:40:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10596
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 20:40:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzQnT-00007q-7A
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 20:40:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i261eAVS000468
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 20:40:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzQnQ-00007T-QD
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 20:40:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10578
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 20:40:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzQnO-0005Ip-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 20:40:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzQmc-00058k-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 20:39:18 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzQlZ-0004yN-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 20:38:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzQlP-0008IZ-Rx; Fri, 05 Mar 2004 20:38:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzQkb-00081z-1b
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 20:37:13 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10486
	for <asrg@ietf.org>; Fri, 5 Mar 2004 20:37:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzQkY-0004ln-00
	for asrg@ietf.org; Fri, 05 Mar 2004 20:37:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzQjk-0004Zc-00
	for asrg@ietf.org; Fri, 05 Mar 2004 20:36:21 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AzQil-0004NL-00
	for asrg@ietf.org; Fri, 05 Mar 2004 20:35:19 -0500
Received: (qmail 39306 invoked by uid 1013); 6 Mar 2004 01:35:15 -0000
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: Daniel Feenberg <feenberg@nber.org>
Cc: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>,
        "Anne P. Mitchell, Esq." <amitchell@isipp.com>, asrg@ietf.org
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.)
Message-ID: <20040306013515.GC30725@Space.Net>
References: <20040304203054.GF13559@Space.Net> <Pine.GSO.4.10.10403050711570.25828-100000@nber1.nber.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.GSO.4.10.10403050711570.25828-100000@nber1.nber.org>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
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/mail-archive/working-groups/asrg/>
Date: Sat, 6 Mar 2004 02:35:15 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Fri, Mar 05, 2004 at 07:20:59AM -0500, Daniel Feenberg wrote:
> There is a difference between "centralized" and "cooperative". There is
> nothing in the plan that I can see that suggests that they should be the

Where on the web site do you find the word "cooperative"?
All I can detect has the "centralized" direction, like in
    ADDITIONAL REQUIREMENTS FOR LISTING OF ORGANIZATIONS NOT PERSONALLY
    KNOWN TO ISIPP (NON-VOUCHED LISTINGS)

And I surely don't want a service that has worldwide operating ambitions
and that is dependant on US law (I wouldn't like to have one that solely
is dependant on German law, either, no antiamericanism here).

> NSI had their monopoly handed to them by an inattentive government agency.
> These guys will have to earn their market share - a completely different
> matter.

And as soon as you have 4 or 5 of them you'd have to register with all
of them.
Just like with new TLDs which you have to register your trademark with,
if you don't want to loose it (in some countries) or want to risk that
some nerd registers e.g. ibm.biz and puts up a "homepage" with "you all
suck" on it.

In June we had this mega thread about "Mark McCarron" and his "solution
to spam" which was pretty close and a bit more strictly than the ISIPP
Accreditation Database and IIRC not one on this list thought it was a
good idea. Such a database has to be neutral with unemotional terms.

And it has to be free of political influences of one country.
And what will happen, if that country decides that each and everyone from
another country is suddenly untrusted, because the whole other country
is a big danger for the security of the homeland and politically or
through legislation forces the database to remove all the entries
of entities from this specific bad country from their database? Is the
reputation these entities have bought from an organisation like the
ISIPP then suddenly non existant? Do they get their money back? Will the
organisation immediately shut down their service because they (IMHO)
failed? And if not, what is then the worth of such a service?

This is nothing personal against ISIPP, but I think databases like 
IADB are inappropriate and they trick users into a trust situation that
they can't provide.
It's a bit like the "Thawte Secure Site" seal. They encourage https sites
to put it on their pages (and of course make advertising for them).
But the drawback is that people start to think as they see the seal
that the site is a "good" one. So if you are a "bad" one you can add
the seal and people will think they're save.
So basically with the seal Thawte - surely without deliberateness -
tricks the people in a trust feeling they can't control and into
(wrong) trust situations they can't provide.
	
	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"

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



From exim@www1.ietf.org  Fri Mar  5 21:05:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11717
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 21:05:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzRBb-0001sO-47
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 21:05:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i26257Bu007206
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 21:05:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzRBa-0001s9-Vt
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 21:05:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11684
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 21:05:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzRBY-0002EG-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 21:05:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzRAd-00023m-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 21:04:08 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzR9e-0001sv-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 21:03:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzR9Z-0001bI-Kz; Fri, 05 Mar 2004 21:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzR8j-0001Za-Qg
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 21:02:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11556
	for <asrg@ietf.org>; Fri, 5 Mar 2004 21:02:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzR8h-0001i4-00
	for asrg@ietf.org; Fri, 05 Mar 2004 21:02:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzR7o-0001X6-00
	for asrg@ietf.org; Fri, 05 Mar 2004 21:01:12 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzR71-0001L2-00
	for asrg@ietf.org; Fri, 05 Mar 2004 21:00:23 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2620Nfj008352;
        Fri, 5 Mar 2004 18:00:23 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GKD3YD59>; Fri, 5 Mar 2004 18:00:23 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A1952@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Markus Stumpf'" <maex-lists-spam-ietf-asrg@Space.Net>,
        Daniel Feenberg
	 <feenberg@nber.org>
Cc: "Anne P. Mitchell, Esq." <amitchell@isipp.com>, asrg@ietf.org
Subject: RE: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and the
	ir Problems (Modified by Anne P. Mitchell, Esq.)
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Fri, 5 Mar 2004 18:00:22 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

> It's a bit like the "Thawte Secure Site" seal. They encourage 
> https sites
> to put it on their pages (and of course make advertising for them).
> But the drawback is that people start to think as they see the seal
> that the site is a "good" one. So if you are a "bad" one you can add
> the seal and people will think they're save.
> So basically with the seal Thawte - surely without deliberateness -
> tricks the people in a trust feeling they can't control and into
> (wrong) trust situations they can't provide.

The security controls in this case are a set of Web crawlers that
continuously scan the net for violations of the use policy. There
are a couple of other features built in that help detect abuse.

Sure it is a system that is based on enforcement rather than
cryptography. But even so systems of that kind can work. Until
cryptography came along they were all we had.

A transition to a more secure scheme is already under way. If
you look at the more recent SSL roots you will find that they 
use the LogoTypes extension to create a cryptographic binding 
between the certificate and the logo.


		Phill


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



From exim@www1.ietf.org  Fri Mar  5 21:11:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11998
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 21:11:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzRHQ-0002eZ-23
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 21:11:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i262B84p010192
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 21:11:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzRHP-0002eJ-TL
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 21:11:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11962
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 21:11:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzRHN-0003IL-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 21:11:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzRGP-000363-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 21:10:06 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzRFQ-0002tU-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 21:09:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzRFN-0002HY-Pr; Fri, 05 Mar 2004 21:09:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzREX-0002E4-UE
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 21:08:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11821
	for <asrg@ietf.org>; Fri, 5 Mar 2004 21:08:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzREV-0002je-00
	for asrg@ietf.org; Fri, 05 Mar 2004 21:08:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzRDd-0002aE-00
	for asrg@ietf.org; Fri, 05 Mar 2004 21:07:14 -0500
Received: from mail1.panix.com ([166.84.1.72])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzRDG-0002Pe-00
	for asrg@ietf.org; Fri, 05 Mar 2004 21:06:50 -0500
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail1.panix.com (Postfix) with ESMTP id 268B94887A
	for <asrg@ietf.org>; Fri,  5 Mar 2004 21:06:45 -0500 (EST)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i2626ir02302;
	Fri, 5 Mar 2004 21:06:44 -0500 (EST)
Message-Id: <200403060206.i2626ir02302@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <20040305175436.GA21252@Space.Net> (message from Markus Stumpf on
	Fri, 5 Mar 2004 18:54:36 +0100)
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.)
References: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com> <20040304203054.GF13559@Space.Net> <DF237F2C-6E1B-11D8-B214-000A95AC5778@isipp.com> <20040305175436.GA21252@Space.Net>
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/mail-archive/working-groups/asrg/>
Date: Fri, 5 Mar 2004 21:06:44 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net> wrote:
> On Thu, Mar 04, 2004 at 12:38:19PM -0800, Anne P. Mitchell,
> Esq. wrote:

> I am objecting that "FINAL DECISION FOR INCLUSION IN IADB IS AT THE
> DISCRETION OF ISIPP" and not whether it depends on successful passing
> of the criteria.

Who is supposed to determine that "successful passing of the
criteria"?  Do you want whoever that is to be sued by some spammer who
thinks he found a loophole?

> With the above sentence, even if I am the honest man in the whole
> Internet it is up to your good will to be added to the database or
> not.

That's absolutely right.  If mailserver admins don't think they're
doing a good enough job, then mailservers won't be configured to care
about what they say, and they'll be irrelevant.  If mailserver admins
think they (the admins) get benefit by using ISIPP's list, then
they'll use it.

If you think you can provide a better list, go ahead.  Nobody is
claiming to own the concept of a list.

>> The reservation of decision is *terribly* important, so that we don't 
>> get a big fat spammer who techinically can say that they meet the other 
>> requirements, so that therefore we *have* to list them (you wouldn't 
>> want that, would you?)
>
> If you can't find any definitive term to nail him down and separate him
> from the "good guys" than this is a problem with the terms.

If you think you can find the most clever person in the world (so that
nobody else can ever find loopholes in her terms), I wish you luck in
the search.

> I will NEVER trust any system that depends on the good will of some
> people and that backs up goodwill decisions with their terms of
> service.

So don't trust it.  Your toys, your rules.  If your users don't like
the way you run your mailserver, including your decisions about who to
trust, they'll become your ex-users.  I see no problem either way.

> How much time and money per complaint are you willing to spend to
> investigate these cases?

As much as they feel is warranted.  Again, if you think you can do a
better job, go ahead and do it.  If the mailadmins agree that yours is
better, nobody will use theirs.

[another message]

> On Fri, Mar 05, 2004 at 07:20:59AM -0500, Daniel Feenberg wrote:
>> There is a difference between "centralized" and "cooperative". There is
>> nothing in the plan that I can see that suggests that they should be the
>
> Where on the web site do you find the word "cooperative"?
> All I can detect has the "centralized" direction, like in
>    ADDITIONAL REQUIREMENTS FOR LISTING OF ORGANIZATIONS NOT PERSONALLY
>    KNOWN TO ISIPP (NON-VOUCHED LISTINGS)

What makes you think there's anything centralized?  It's _one_
organization.  There should be as many such as people care to create.

> And I surely don't want a service that has worldwide operating
> ambitions and that is dependant on US law (I wouldn't like to have
> one that solely is dependant on German law, either, no
> antiamericanism here).

Any service is dependent on its local law.  If you don't want to use
it, then don't.  Nobody says you have to.

>> NSI had their monopoly handed to them by an inattentive government agency.
>> These guys will have to earn their market share - a completely different
>> matter.
>
> And as soon as you have 4 or 5 of them you'd have to register with all
> of them.

Why?  You're making assumptions about the way mailserver admins will
operate, which are completely unwarranted.  We have no way of knowing
how they'll act.

> Just like with new TLDs which you have to register your trademark
> with, if you don't want to loose it (in some countries) or want to
> risk that some nerd registers e.g. ibm.biz and puts up a "homepage"
> with "you all suck" on it.

I suppose you need to buy accounts with every ISP in the world so you
can have the Markus.Stumpf@<every ISP> just in case somebody else
might get that userid and say silly things from it, too.

> And it has to be free of political influences of one country.

I don't mind if you run yours from Mars.

> And what will happen, if that country decides that each and everyone
> from another country is suddenly untrusted, because the whole other
> country is a big danger for the security of the homeland and
> politically or through legislation forces the database to remove all
> the entries of entities from this specific bad country from their
> database?

Then the services running from that country will lose a lot of
credibility elsewhere in the world, and their competitors in other
countries will gain (relative) credibility.

> Is the reputation these entities have bought from an organisation
> like the ISIPP then suddenly non existant? Do they get their money
> back?

Depends on the contract (as voluntarily agreed to by both sides).

> Will the organisation immediately shut down their service because
> they (IMHO) failed?

I don't see any organization other than your shutting down because in
_your_ opinion they failed.  I have seen organizations
(e.g. anon.penet.fi) shut down because in the opinions of _their
operator_ they failed.

> And if not, what is then the worth of such a service?

That's up to the users.

> This is nothing personal against ISIPP, but I think databases like
> IADB are inappropriate and they trick users into a trust situation
> that they can't provide.

Then don't trust them.

Seth

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



From exim@www1.ietf.org  Fri Mar  5 21:28:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12466
	for <asrg-archive@odin.ietf.org>; Fri, 5 Mar 2004 21:28:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzRXd-0003nD-Cx
	for asrg-archive@odin.ietf.org; Fri, 05 Mar 2004 21:27:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i262RrJA014573
	for asrg-archive@odin.ietf.org; Fri, 5 Mar 2004 21:27:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzRXc-0003my-J4
	for asrg-web-archive@optimus.ietf.org; Fri, 05 Mar 2004 21:27:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12423
	for <asrg-web-archive@ietf.org>; Fri, 5 Mar 2004 21:27:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzRXa-0005vF-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 21:27:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzRWN-0005fT-00
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 21:26:36 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzRVj-0005Ro-02
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 21:25:55 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1AzROD-0008TO-NT
	for asrg-web-archive@ietf.org; Fri, 05 Mar 2004 21:18:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzRO5-0003Ii-Gm; Fri, 05 Mar 2004 21:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AzRN9-0003IG-Od
	for asrg@optimus.ietf.org; Fri, 05 Mar 2004 21:17:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12272
	for <asrg@ietf.org>; Fri, 5 Mar 2004 21:17:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AzRN7-0004JO-00
	for asrg@ietf.org; Fri, 05 Mar 2004 21:17:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AzRMA-0004BH-00
	for asrg@ietf.org; Fri, 05 Mar 2004 21:16:03 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1AzRLs-00042z-00
	for asrg@ietf.org; Fri, 05 Mar 2004 21:15:44 -0500
Received: (qmail 40097 invoked by uid 1013); 6 Mar 2004 02:15:44 -0000
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'Markus Stumpf'" <maex-lists-spam-ietf-asrg@Space.Net>,
        Daniel Feenberg <feenberg@nber.org>,
        "Anne P. Mitchell, Esq." <amitchell@isipp.com>, asrg@ietf.org
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and the ir Problems (Modified by Anne P. Mitchell, Esq.)
Message-ID: <20040306021544.GE30725@Space.Net>
References: <C6DDA43B91BFDA49AA2F1E473732113E0A1952@mou1wnexm05.vcorp.ad.vrsn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A1952@mou1wnexm05.vcorp.ad.vrsn.com>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
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/mail-archive/working-groups/asrg/>
Date: Sat, 6 Mar 2004 03:15:44 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Fri, Mar 05, 2004 at 06:00:22PM -0800, Hallam-Baker, Phillip wrote:
> The security controls in this case are a set of Web crawlers that
> continuously scan the net for violations of the use policy. There
> are a couple of other features built in that help detect abuse.

If I take the "image seal" I steal from the Thawte homepage myself and
put it up on www.eaxmple.com, how will a web crawler detect the abuse?
And even if there is the "accept dialog" people will see the image
and happily believe they are on www.example.com and click the dialog
away as "just another crazy popup I don't know what it means".

> Sure it is a system that is based on enforcement rather than
> cryptography. But even so systems of that kind can work. Until
> cryptography came along they were all we had.

Agreed. But we HAVE cryptography and each Browser has the "security"
button I can click on and see the certificate. IMHO the correct way
would be to have a big "watch out" sign on each https homepage and
encourage the user to check the cert for validity. Instead the user
is discouraged to inspect the "real thing" and encouraged to believe
in an eye catcher as a sign of trust.

Security people always tell us and have the experience that the biggest
issue in security is to have responsible users. But now IMHO the security
industry tries to train the user to believe in a image more than looking
and the cert and this is IMHO highly contradictorily (and wrong).

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"

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



From exim@www1.ietf.org  Mon Mar  8 09:42:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03710
	for <asrg-archive@odin.ietf.org>; Mon, 8 Mar 2004 09:42:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0LxI-0006TG-3f
	for asrg-archive@odin.ietf.org; Mon, 08 Mar 2004 09:42:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i28Eg8Fc024870
	for asrg-archive@odin.ietf.org; Mon, 8 Mar 2004 09:42:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0LxH-0006T3-Tn
	for asrg-web-archive@optimus.ietf.org; Mon, 08 Mar 2004 09:42:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03680
	for <asrg-web-archive@ietf.org>; Mon, 8 Mar 2004 09:42:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0LxG-0003j8-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 09:42:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0LwD-0003S9-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 09:41:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0Luy-0003BC-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 09:39:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0LtK-0005gQ-6R; Mon, 08 Mar 2004 09:38:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0LtA-0005dZ-FR
	for asrg@optimus.ietf.org; Mon, 08 Mar 2004 09:37:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03232
	for <asrg@ietf.org>; Mon, 8 Mar 2004 09:37:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0Lt8-0002iK-00
	for asrg@ietf.org; Mon, 08 Mar 2004 09:37:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0Lrt-0002Jx-00
	for asrg@ietf.org; Mon, 08 Mar 2004 09:36:33 -0500
Received: from grou.ch
	([193.201.200.130] helo=linuxufo.com ident=mail)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0LqV-0001xR-00
	for asrg@ietf.org; Mon, 08 Mar 2004 09:35:08 -0500
Received: from sheriff by linuxufo.com with local (Exim 3.35 #1 (Debian))
	id 1B0LqP-00041e-00
	for <asrg@ietf.org>; Mon, 08 Mar 2004 14:35:01 +0000
From: Peter Sergeant <pete@clueball.com>
To: asrg@ietf.org
Message-ID: <20040308143501.GB14624@linuxufo.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.28i
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Subject: [Asrg] 0. General - Thoughts on testing anti-spam software
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/mail-archive/working-groups/asrg/>
Date: Mon, 8 Mar 2004 14:35:01 +0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-8.0 required=5.0 tests=AWL,HABEAS_SWE autolearn=no 
	version=2.60

[this email rambles a lot. apologies]

This is perhaps a little bit off-topic, so I'm as happy to recieve
replies off-list. This month, the magazine I work for
(http://www.virusbtn.com) is conducting its first test of anti-spam
software. The current plan is to kick off with testing three open-source
lexical analysers - CRM114, DSPAM, and Bogofilter. I've been talking to
some of the big commercial anti-spam people about testing, and how I
plan to test these, and a recurring idea is that while they feel these
solutions will perform exceptionally well for one user, they just don't
scale for multi-user installations...

I've had a think about this. 

The main objection seems to be the fact that you need to maintain
keyword lists for every user. This is seen to be a big problem,
although, looking at my SpamAssassin config directory, my 'keyword
dictionaries' are about 6MB combined. Even with 1,000 users, we're not
talking about a great deal of data retention here... 

Has anyone installed a bayesian/statistical based filtering solution for
a big user-base, and wants to share their experiences of how effective
it's been? How much space it's taking up? I'd be really curious to hear.

We have a number of corpuses we're testing against, put together in
different ways. The review will probably explain each corpus, and what
its strengths and weaknesses are. We're going to be keeping results from
different corpuses different - we won't be testing a product against a
corpus when it's been trained on a different corpus.

Any thoughts, on general anti-spam software testing, or on any points
raised here, welcomed.

Thanks

+Pete

-- 
Do not be too moral. You may cheat yourself out of much life. Aim above
morality. Be not simply good; be good for something.
 -- Henry David Thoreau

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



From exim@www1.ietf.org  Mon Mar  8 11:45:20 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12946
	for <asrg-archive@odin.ietf.org>; Mon, 8 Mar 2004 11:45:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0Ns4-00054G-NX
	for asrg-archive@odin.ietf.org; Mon, 08 Mar 2004 11:44:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i28GiqP9019474
	for asrg-archive@odin.ietf.org; Mon, 8 Mar 2004 11:44:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0Ns4-000541-II
	for asrg-web-archive@optimus.ietf.org; Mon, 08 Mar 2004 11:44:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12913
	for <asrg-web-archive@ietf.org>; Mon, 8 Mar 2004 11:44:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0Ns3-0003vl-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 11:44:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0NqW-0003Us-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 11:43:16 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0Nor-00030M-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 11:41:33 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B0Nor-0003qR-Qo
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 11:41:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0NoM-0004Lj-UL; Mon, 08 Mar 2004 11:41:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0NoI-0004Ki-8U
	for asrg@optimus.ietf.org; Mon, 08 Mar 2004 11:40:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12672
	for <asrg@ietf.org>; Mon, 8 Mar 2004 11:40:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0NoH-0002th-00
	for asrg@ietf.org; Mon, 08 Mar 2004 11:40:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0NnI-0002dw-00
	for asrg@ietf.org; Mon, 08 Mar 2004 11:39:56 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0NmC-0002OA-00
	for asrg@ietf.org; Mon, 08 Mar 2004 11:38:48 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id B18B816FD1
	for <asrg@ietf.org>; Mon,  8 Mar 2004 11:42:09 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.) 
In-Reply-To: Your message of "Fri, 05 Mar 2004 11:50:59 PST."
             <6D1485F9-6EDE-11D8-B214-000A95AC5778@isipp.com> 
Message-Id: <20040308164209.B18B816FD1@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Mon, 08 Mar 2004 11:42:09 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

"Anne P. Mitchell, Esq." <amitchell@isipp.com> wrote:
> That is not what an accreditation system (necessarily) is, and it's not 
> what IADB is.  IADB is very specifically _not_ a whitelist (nor a 
> blocklist) - it is, if you will, a colour-neutral list, whicih provides 
> you with very specific datapoints. 

  From reading your web pages about how it works, I disagree.  You
have a particular agenda, and your "accreditation" system is designed
to enforce that agenda.

  This is not to say the agenda is bad, but it's not neutral.

  If you wanted your list to be neutral, you would also list spammers.
If they claim to send large volumes of spam, and they can be verified
to do so, then they should be listed on a "colour-neutral" list.  You
won't list spammers, so your service isn't neutral.

  The point is not to stop spammers by publishing accreditation
information for non-spammers.  That just won't work.  The point is to
enforce consistency between claims and actions, no matter what those
claims and actions are.  By instead enforcing an agenda, you bias the
service, and make it less useful for everyone.

> The real world example of an accreditation is Underwriters Labs, or the 
> Good Housekeeping Seal of Approval.  Or that certificate in an elevator 
> saying it has been inspected on such-and-such a date.
> Or a school being accredited.

  UL will accredit electronic devices that are useless, so long as
they are safe.  This is the model which has permitted them to be
consistently percieved to be unbiased.  You can by garbage with a UL
seal, and know that it may not do anything, but it won't burn down
your house.

> All of these, like a listing in IADB, say "the product bearing this 
> accreditation has been proven to meet a certain set of standards as 
> determined by the accrediting body."

  Your standards are clear.  You are not publishing accredication, you
are attempting to enforce compliance with your agenda.  That's OK, but
it's not an accreditation service.

  Alan DeKok.

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



From exim@www1.ietf.org  Mon Mar  8 11:53:17 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13555
	for <asrg-archive@odin.ietf.org>; Mon, 8 Mar 2004 11:53:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0Nzm-0005lg-H0
	for asrg-archive@odin.ietf.org; Mon, 08 Mar 2004 11:52:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i28Gqom0022169
	for asrg-archive@odin.ietf.org; Mon, 8 Mar 2004 11:52:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0Nzm-0005lU-Cm
	for asrg-web-archive@optimus.ietf.org; Mon, 08 Mar 2004 11:52:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13552
	for <asrg-web-archive@ietf.org>; Mon, 8 Mar 2004 11:52:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0Nzl-0005se-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 11:52:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0Nyx-0005jd-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 11:52:00 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0NyA-0005Zc-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 11:51:10 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B0NyB-00045z-IO
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 11:51:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0Ny2-0005aL-1a; Mon, 08 Mar 2004 11:51:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0NxH-0005Wc-Eq
	for asrg@optimus.ietf.org; Mon, 08 Mar 2004 11:50:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13403
	for <asrg@ietf.org>; Mon, 8 Mar 2004 11:50:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0NxG-0005NF-00
	for asrg@ietf.org; Mon, 08 Mar 2004 11:50:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0NwP-00058W-00
	for asrg@ietf.org; Mon, 08 Mar 2004 11:49:22 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0NvD-0004pj-00
	for asrg@ietf.org; Mon, 08 Mar 2004 11:48:07 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id 5664E16D00
	for <asrg@ietf.org>; Mon,  8 Mar 2004 11:51:29 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.) 
In-Reply-To: Your message of "Fri, 05 Mar 2004 18:54:36 +0100."
             <20040305175436.GA21252@Space.Net> 
Message-Id: <20040308165129.5664E16D00@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Mon, 08 Mar 2004 11:51:29 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net> wrote:
> Our abuse department receives spam complaints even for double opt-in
> announcement/newsletter mailinglists of our customers for which *I
> guarantee* that the only way to get an address on that list is with
> double opt-in (with crypto support -> ezmlm).

  Exactly.  Even for your own double opt-in customers, a percentage of
your messages are viewed as spam.  This means you are a spammer, at
least so far as they're concerned.  This isn't necessarily a bad
thing, as it shows us what we've been missing in the design of most
anti-spam systems.

  Any anti-spam system that lists you as a spammer because of such
customer reports, and refuses to allow you to participate in it
because of that label, is WRONG.  It's design is wrong, it's
implementation is wrong, and it's intent is wrong.  Such a system
cannot be trusted.  Witness the cross-listing of blacklists, due to
political weener-size arguments.  Those blacklists lost HUGE
credibility when they listed people that most did not view as
spammers.

  If we are to win the war against spam, we must co-opt the spammers.

  To put it another way, if we DON'T include the spammers in a system,
they *you* won't be included, either, because of your customers
issues.  I don't think you would like that.

  Alan DeKok.

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



From exim@www1.ietf.org  Mon Mar  8 13:04:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17320
	for <asrg-archive@odin.ietf.org>; Mon, 8 Mar 2004 13:04:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0P6a-0003KI-7a
	for asrg-archive@odin.ietf.org; Mon, 08 Mar 2004 13:03:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i28I3uH4012780
	for asrg-archive@odin.ietf.org; Mon, 8 Mar 2004 13:03:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0P6a-0003K3-1A
	for asrg-web-archive@optimus.ietf.org; Mon, 08 Mar 2004 13:03:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17281
	for <asrg-web-archive@ietf.org>; Mon, 8 Mar 2004 13:03:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0P6Y-0003OU-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 13:03:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0P5X-0003F9-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 13:02:52 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0P4v-00035n-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 13:02:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0P4j-00035r-0p; Mon, 08 Mar 2004 13:02:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0P4T-00035B-GW
	for asrg@optimus.ietf.org; Mon, 08 Mar 2004 13:01:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17123
	for <asrg@ietf.org>; Mon, 8 Mar 2004 13:01:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0P4R-00033s-00
	for asrg@ietf.org; Mon, 08 Mar 2004 13:01:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0P3X-0002ub-00
	for asrg@ietf.org; Mon, 08 Mar 2004 13:00:48 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1B0P2e-0002kd-00
	for asrg@ietf.org; Mon, 08 Mar 2004 12:59:52 -0500
Received: (qmail 87898 invoked by uid 1013); 8 Mar 2004 17:59:50 -0000
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: Seth Breidbart <sethb@panix.com>
Cc: asrg@ietf.org
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.)
Message-ID: <20040308175950.GB26695@Space.Net>
References: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com> <20040304203054.GF13559@Space.Net> <DF237F2C-6E1B-11D8-B214-000A95AC5778@isipp.com> <20040305175436.GA21252@Space.Net> <200403060206.i2626ir02302@panix5.panix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200403060206.i2626ir02302@panix5.panix.com>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
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/mail-archive/working-groups/asrg/>
Date: Mon, 8 Mar 2004 18:59:50 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Fri, Mar 05, 2004 at 09:06:44PM -0500, Seth Breidbart wrote:
> Who is supposed to determine that "successful passing of the
> criteria"?

The process of being added to the list is indepedent of successfully
passing the terms listed.
It is "if we don't like your face we might not add you".

> If you think you can provide a better list, go ahead.  Nobody is
> claiming to own the concept of a list.

I didn't say it is a bad list.
I said such kind of lists are a bad thing in general. So why do you
think I'd be interested in operating "a better one"?

> If you think you can find the most clever person in the world (so that
> nobody else can ever find loopholes in her terms), I wish you luck in
> the search.

Isn't that a funny thing?
They're going to give reputation for something they can't define? 
Isn't it like "company XYZ is one of the good guys, whatever they might
be doing".

> > How much time and money per complaint are you willing to spend to
> > investigate these cases?
> 
> As much as they feel is warranted.

No, they claim giving reputation. So if they want someone to believe them
they have to post rules they'll abide to. Just like VeriSign, Thawte,
Geotrust and all the other are giving some kind of reputation: they have
checked a list of facts and they certify that these facts are correct
according to their revision.
At the moment the IADB warrants nothing.

> Again, if you think you can do a
> better job, go ahead and do it.  If the mailadmins agree that yours is
> better, nobody will use theirs.

Look, I feel like in a sandbox.
If I say something critical I get from you "nae nae nae ... do it better".
But there is nothing to be done better, because, as I said, IMHO such
kind of lists are an error in general. And I am writing this to share my
opinions with other people and to make them think about it.
So I am not interested in your "nae nae nae ... do it better" whatever.

> Any service is dependent on its local law.

No it is not.

> If you don't want to use
> it, then don't.  Nobody says you have to.

If you want to use it do it, where is your problem? But tell us why you
want to use it?

> Why?  You're making assumptions about the way mailserver admins will
> operate, which are completely unwarranted.  We have no way of knowing
> how they'll act.

Don't say "we" if you mean "I". The experience of block lists gave
enough examples, so for /me/ I am knowing enough. And I know enough
so called "mailserver admins" to know how they operate.

> I suppose you need to buy accounts with every ISP in the world so you
> can have the Markus.Stumpf@<every ISP> just in case somebody else
> might get that userid and say silly things from it, too.

No, because Markus.Stumpf@<any ISP> does not have the same legal implications
trademarks (and not using them) have. And Joe Luser will not
try to reach me just by typing "Markus.Stumpf@<any ISP>" as an email
address, but zillions of clueless journalists have told the Joe Lusers
out there for nearly ten years now that the DNS is a search engine and
Joe Luser is naive enough to think that using  porsche.biz  (or
porsche.ctld) will really get him where he thinks.

> Then the services running from that country will lose a lot of
> credibility elsewhere in the world, and their competitors in other
> countries will gain (relative) credibility.

Most Joe Luser Mailadmins will not even notice. I see the DNS queries
of a lot of mailservers run by customers. Monkeys.com DNSBLs are out of
order for some months now, but queries for them continue and that is
really an easy thing to recognize that they don't work any more.
Changes in the operation of a reputation database are hard to recognize
without tracking the terms of service all the time.
Oh and you really think they'll run around and tell everyone what some
secret service guys told them they have to do?

> I don't see any organization other than your shutting down because in
> _your_ opinion they failed.  I have seen organizations
> (e.g. anon.penet.fi) shut down because in the opinions of _their
> operator_ they failed.

So what? I am asking what their opinions would be in such a case and
whether they'll think they have failed.

> Then don't trust them.

I don't. So what's your problem?
I am simply listing pitfalls that arise from trusting in those kind of
lists.

With all that contra arguments of yours where is your argument "pro"
such a list? That's what I am missing all the way through your email.

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"

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



From exim@www1.ietf.org  Mon Mar  8 13:22:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19018
	for <asrg-archive@odin.ietf.org>; Mon, 8 Mar 2004 13:22:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0PO9-0005LL-RF
	for asrg-archive@odin.ietf.org; Mon, 08 Mar 2004 13:22:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i28IM5lH020533
	for asrg-archive@odin.ietf.org; Mon, 8 Mar 2004 13:22:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0PO9-0005L6-M7
	for asrg-web-archive@optimus.ietf.org; Mon, 08 Mar 2004 13:22:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18972
	for <asrg-web-archive@ietf.org>; Mon, 8 Mar 2004 13:22:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0PO7-0007OX-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 13:22:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0PMn-00074m-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 13:20:42 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0PLU-0006hK-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 13:19:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0PLC-0004hn-35; Mon, 08 Mar 2004 13:19:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0PKG-0004eF-F1
	for asrg@optimus.ietf.org; Mon, 08 Mar 2004 13:18:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18481
	for <asrg@ietf.org>; Mon, 8 Mar 2004 13:17:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0PKE-0006OG-00
	for asrg@ietf.org; Mon, 08 Mar 2004 13:18:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0PJ1-00060D-00
	for asrg@ietf.org; Mon, 08 Mar 2004 13:16:47 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0PH7-0005Qz-00
	for asrg@ietf.org; Mon, 08 Mar 2004 13:14:49 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id 10C6816D00
	for <asrg@ietf.org>; Mon,  8 Mar 2004 13:18:07 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation Systems and their Problems 
In-Reply-To: Your message of "Wed, 03 Mar 2004 14:37:23 EST."
             <404633F3.2010503@solidmatrix.com> 
Message-Id: <20040308181807.10C6816D00@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Mon, 08 Mar 2004 13:18:07 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Yakov Shafranovich <research@solidmatrix.com> wrote:
> In the current world the closest approximation we have to reputation 
> systems that are planned with LMAP are blacklists and Senderbase. Given 
> that current blacklists have numerous problems, why would any proposed 
> reputation or accrediation systems of the future be any different?

  If you base the accreditiation system on something other than
personal prejudices (which is what most content filters and blacklists
end up being), then the accreditation becomes a little more useful.

> How are we planning on avoiding the same problems we have today in
> the future, if we want to deploy such systems?

  Keep the accreditation focused on simple data which can be trivially
verified in the network.  The only reason to have a centralized
accrediation service is to simplify record keeping.  e.g. You *could*
find web pages by rooting around the net yourself, but it's a lot
easier just to use a search engine.

  The #1 accreditation that I see is something to solve the MTA/MUA
imbalance.  STMP should be an MTA to MTA protocol.  SUBMIT has been
around for years now.  People should use it.  The lack of deployment
indicates that the IETF standards process has created a protocol for
which there's no demand.

  Simply dropping the number of SMTP originators by 3 orders of
magnitude would make the spam problem hugely easier to deal with.

  Alan DeKok.

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



From exim@www1.ietf.org  Mon Mar  8 13:22:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19035
	for <asrg-archive@odin.ietf.org>; Mon, 8 Mar 2004 13:22:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0POA-0005Ld-L0
	for asrg-archive@odin.ietf.org; Mon, 08 Mar 2004 13:22:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i28IM6Sl020551
	for asrg-archive@odin.ietf.org; Mon, 8 Mar 2004 13:22:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0POA-0005LO-Gb
	for asrg-web-archive@optimus.ietf.org; Mon, 08 Mar 2004 13:22:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18976
	for <asrg-web-archive@ietf.org>; Mon, 8 Mar 2004 13:22:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0PO8-0007Oc-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 13:22:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0PMo-00074y-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 13:20:43 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0PLW-0006hO-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 13:19:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0PLE-0004jD-Ns; Mon, 08 Mar 2004 13:19:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0PL8-0004hI-Hp
	for asrg@optimus.ietf.org; Mon, 08 Mar 2004 13:18:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18567
	for <asrg@ietf.org>; Mon, 8 Mar 2004 13:18:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0PL6-0006b1-00
	for asrg@ietf.org; Mon, 08 Mar 2004 13:18:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0PJh-0006BX-00
	for asrg@ietf.org; Mon, 08 Mar 2004 13:17:30 -0500
Received: from mail1.panix.com ([166.84.1.72])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0PIE-0005iI-00
	for asrg@ietf.org; Mon, 08 Mar 2004 13:15:58 -0500
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail1.panix.com (Postfix) with ESMTP
	id E8A0948714; Mon,  8 Mar 2004 13:15:56 -0500 (EST)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i28IFuR11083;
	Mon, 8 Mar 2004 13:15:56 -0500 (EST)
Message-Id: <200403081815.i28IFuR11083@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: maex-lists-spam-ietf-asrg@Space.Net
Cc: asrg@ietf.org
In-reply-to: <20040308175950.GB26695@Space.Net> (message from Markus Stumpf on
	Mon, 8 Mar 2004 18:59:50 +0100)
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.)
References: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com> <20040304203054.GF13559@Space.Net> <DF237F2C-6E1B-11D8-B214-000A95AC5778@isipp.com> <20040305175436.GA21252@Space.Net> <200403060206.i2626ir02302@panix5.panix.com> <20040308175950.GB26695@Space.Net>
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/mail-archive/working-groups/asrg/>
Date: Mon, 8 Mar 2004 13:15:56 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net> wrote:
> On Fri, Mar 05, 2004 at 09:06:44PM -0500, Seth Breidbart wrote:
>> Who is supposed to determine that "successful passing of the
>> criteria"?
>
> The process of being added to the list is indepedent of successfully
> passing the terms listed.

So what is the list supposed to list?  Everybody who asks?  What use
would that be?

Or would it have a notation as to whether or not the list entry
actually passed the criteria?  If so, how would that differ from not
even listing those who didn't (other than it being less likely to be
sued for not mentioning X than for saying "X didn't pass the
criteria")?

>> If you think you can provide a better list, go ahead.  Nobody is
>> claiming to own the concept of a list.
>
> I didn't say it is a bad list.
> I said such kind of lists are a bad thing in general. So why do you
> think I'd be interested in operating "a better one"?

Why do you think such lists are bad?  Many people find them useful.

>> If you think you can find the most clever person in the world (so that
>> nobody else can ever find loopholes in her terms), I wish you luck in
>> the search.
>
> Isn't that a funny thing?
> They're going to give reputation for something they can't define? 
> Isn't it like "company XYZ is one of the good guys, whatever they might
> be doing".

Isn't that exactly how reputation works in the real world?

When X tells me "Y has characteristic A" I filter that through (my
belief in) X's credibility, X's ability to judge characteristic A, and
other knowledge or beliefs I have about Y.

>> > How much time and money per complaint are you willing to spend to
>> > investigate these cases?
>> As much as they feel is warranted.
>
> No, they claim giving reputation. So if they want someone to believe them
> they have to post rules they'll abide to.

They did.  You're objecting to their rules because you don't feel
they're explicit enough.

> Just like VeriSign, Thawte, Geotrust and all the other are giving
> some kind of reputation: they have checked a list of facts and they
> certify that these facts are correct according to their revision.

Given that several of those are _known_ to lie, of what value is their
certification?

> At the moment the IADB warrants nothing.

If you don't find their list _useful to you_ then don't use it.

If you want the ability to sue them should they be wrong about a
listing, too bad.

> But there is nothing to be done better, because, as I said, IMHO
> such kind of lists are an error in general.

What makes them "an error in general"?  Once again, to some people,
they're _useful_.

>> Any service is dependent on its local law.
> No it is not.

Really?  There's some service in some location that can ignore its
local law?  Can you give some examples?

>> If you don't want to use
>> it, then don't.  Nobody says you have to.
>
> If you want to use it do it, where is your problem? But tell us why you
> want to use it?

I might find that there is a correlation (probably negative) between
their listings and spammers.

>> Why?  You're making assumptions about the way mailserver admins will
>> operate, which are completely unwarranted.  We have no way of knowing
>> how they'll act.
>
> Don't say "we" if you mean "I". The experience of block lists gave
> enough examples, so for /me/ I am knowing enough. And I know enough
> so called "mailserver admins" to know how they operate.

If they all act the same way you clearly don't know very many of them.

>> I suppose you need to buy accounts with every ISP in the world so you
>> can have the Markus.Stumpf@<every ISP> just in case somebody else
>> might get that userid and say silly things from it, too.
>
> No, because Markus.Stumpf@<any ISP> does not have the same legal implications
> trademarks (and not using them) have. And Joe Luser will not
> try to reach me just by typing "Markus.Stumpf@<any ISP>" as an email
> address, but zillions of clueless journalists have told the Joe Lusers
> out there for nearly ten years now that the DNS is a search engine and
> Joe Luser is naive enough to think that using  porsche.biz  (or
> porsche.ctld) will really get him where he thinks.

Zillions of clueless journalists and other idiots who believe them do
not make for intelligent policies.

>> Then the services running from that country will lose a lot of
>> credibility elsewhere in the world, and their competitors in other
>> countries will gain (relative) credibility.
>
> Most Joe Luser Mailadmins will not even notice.

Then their customers lose out.  Not my problem.

> With all that contra arguments of yours where is your argument "pro"
> such a list?

It might be useful.  I don't know yet; it isn't fully operating, and
I'm not using it.

Seth

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



From exim@www1.ietf.org  Mon Mar  8 14:46:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23658
	for <asrg-archive@odin.ietf.org>; Mon, 8 Mar 2004 14:46:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0QhX-0003oa-Pp
	for asrg-archive@odin.ietf.org; Mon, 08 Mar 2004 14:46:11 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i28JkBK1014658
	for asrg-archive@odin.ietf.org; Mon, 8 Mar 2004 14:46:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0QhX-0003oL-LJ
	for asrg-web-archive@optimus.ietf.org; Mon, 08 Mar 2004 14:46:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23614
	for <asrg-web-archive@ietf.org>; Mon, 8 Mar 2004 14:46:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0QhU-0007Fx-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 14:46:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0QgZ-000744-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 14:45:12 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0Qfg-0006rY-00
	for asrg-web-archive@ietf.org; Mon, 08 Mar 2004 14:44:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0QfR-0003Vk-Od; Mon, 08 Mar 2004 14:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B0Qeb-0003Pn-IE
	for asrg@optimus.ietf.org; Mon, 08 Mar 2004 14:43:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23409
	for <asrg@ietf.org>; Mon, 8 Mar 2004 14:43:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B0QeY-0006by-00
	for asrg@ietf.org; Mon, 08 Mar 2004 14:43:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B0Qdc-0006Ps-00
	for asrg@ietf.org; Mon, 08 Mar 2004 14:42:09 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1B0Qcs-0006FB-00
	for asrg@ietf.org; Mon, 08 Mar 2004 14:41:22 -0500
Received: (qmail 96572 invoked by uid 1013); 8 Mar 2004 19:41:20 -0000
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: Seth Breidbart <sethb@panix.com>
Cc: maex-lists-spam-ietf-asrg@Space.Net, asrg@ietf.org
Subject: Re: [Asrg] Re: 3b. SMTP Verification - Reputation Systems and their Problems (Modified by Anne P. Mitchell, Esq.)
Message-ID: <20040308194120.GA92695@Space.Net>
References: <854ED2A8-6E0E-11D8-B214-000A95AC5778@isipp.com> <20040304203054.GF13559@Space.Net> <DF237F2C-6E1B-11D8-B214-000A95AC5778@isipp.com> <20040305175436.GA21252@Space.Net> <200403060206.i2626ir02302@panix5.panix.com> <20040308175950.GB26695@Space.Net> <200403081815.i28IFuR11083@panix5.panix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200403081815.i28IFuR11083@panix5.panix.com>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
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/mail-archive/working-groups/asrg/>
Date: Mon, 8 Mar 2004 20:41:20 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60

On Mon, Mar 08, 2004 at 01:15:56PM -0500, Seth Breidbart wrote:
> So what is the list supposed to list?  Everybody who asks?  What use
> would that be?

Everybody who asks and conforms to the terms. Yeah I know this terms
are the problems, because "I don't like your face" should not be one
of the terms. The terms should be clear and the decisions should be
possible for everyone to reproduce.

E.g. DNSBLs that have examples of relayed emails are more trustworthy
(at first glance) than those who don't. I am fully aware that these
can be faked, but the records make it reproducible and if I cannot
reproduce the behaviour either the problem is fixed or they might
be telling lies. DNS /blacklists/ also give reputation, even if it is
negative.

> Or would it have a notation as to whether or not the list entry
> actually passed the criteria?  If so, how would that differ from not
> even listing those who didn't (other than it being less likely to be
> sued for not mentioning X than for saying "X didn't pass the
> criteria")?

The problem is that if someone is not listed, they either
a) did not try
b) failed the listed terms
c) had an ugly face
and my problems are that c) is a possibility at all.

> Why do you think such lists are bad?  Many people find them useful.

Because they are not neutral, they have stale entries and the terms
are unclear.
There are days were I receive from mail.<bigisp>.com as much (an more)
spam mails as I receive from mail.<some spammer>.com.
I have never seen mail.<bigisp>.com listed in any spam block lists. Why?
I have never gotten an answer to spam complaints and I don't notice
something is changing.
They are not listed probably because that would cause a lot of
"innocent" users to be punished by false positives. But where is the
difference to mail.<small isp>.com that gets added to the list, just
because one customer had a hacked proxy?

> Isn't that exactly how reputation works in the real world?
> 
> When X tells me "Y has characteristic A" I filter that through (my
> belief in) X's credibility, X's ability to judge characteristic A, and
> other knowledge or beliefs I have about Y.

No, not in my experience. I don't believe in "wildcard credibility".
If someone brings a letter as reputation for a job as a programmer and
that letter says "I know he can look at monitors as he worked in a TV
shop and he has a nice face" all I can do is laugh about that but I'll
surely not take that into account for the decision to give him that job.

> They did.  You're objecting to their rules because you don't feel
> they're explicit enough.

Agreed ;-)

> Given that several of those are _known_ to lie, of what value is their
> certification?

It's a matter of trust. But if I really want to I can check it myself.

> If you want the ability to sue them should they be wrong about a
> listing, too bad.

I think it is ridiculous to sue someone because of expressing their
opinion if it is based on facts (like with most RBLs, that's why records
are important).
However if someone expresses their opinion as a public service (and IIRC
is the intent of IADB) then their process of decision should be
reproducible.

> What makes them "an error in general"?  Once again, to some people,
> they're _useful_.

To some people it is useful to drink a whole bottle of Vodka in a few
gulps. To some people it is useful to smoke crack.

> >> Any service is dependent on its local law.
> > No it is not.
> 
> Really?  There's some service in some location that can ignore its
> local law?  Can you give some examples?

Sure, services run by the UNO. /If/ there needs to be such a list
it should not depend on the law and influence of one country. We've
seen what happend/happens with IANA and especially ICANN.
There have to be terms of service and as e.g. ICANN is operating for
all countries connected to the Internet and it is ridiculous that
ICANN is subject to the laws of one country pr even state, just because
of the fact that the headquarter is there.

> I might find that there is a correlation (probably negative) between
> their listings and spammers.

Ok. And I think they are tricking people into thinking that and that
their terms would also allow a spammer to be added if they like to.
    FINAL DECISION FOR INCLUSION IN IADB IS AT THE DISCRETION OF ISIPP.
without any limitation.

> If they all act the same way you clearly don't know very many of them.

I didn't say I know all ... I said I know enough of them and I didn't
say they all operate the same way.

> Zillions of clueless journalists and other idiots who believe them do
> not make for intelligent policies.

Right. But they show how easy it is to trick people.

    "All over the place, from the popular culture to the propaganda
     system, there is constant pressure to make people feel that they
     are helpless, that the only role they can have is to ratify decisions
     and to consume."     -- Noam Chomsky

> Then their customers lose out.  Not my problem.

Sure. That's a valid point.
But wasn't our goal to design a system that works for all? Not only
for the 1% (is it that much) of clueful admins who know what they are doing?
It's easy to have (nearly) zero spam: don't accept email from MTAs whose
admins you don't know personally and whom you do not trust to correctly
operate a mailserver. The problem is that as an ISP you will /very/
quickly loose all your customers.

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"

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



From exim@www1.ietf.org  Wed Mar 10 08:00:07 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06624
	for <asrg-archive@odin.ietf.org>; Wed, 10 Mar 2004 08:00:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B13JB-0008Ec-Te
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 07:59:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2ACxbdo031654
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 07:59:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B13JB-0008ES-2Q
	for asrg-web-archive@optimus.ietf.org; Wed, 10 Mar 2004 07:59:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06592
	for <asrg-web-archive@ietf.org>; Wed, 10 Mar 2004 07:59:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B13JA-0007nP-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 07:59:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B13IG-0007e7-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 07:58:41 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B13HT-0007UP-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 07:57:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B13Ge-0007nt-WC; Wed, 10 Mar 2004 07:57:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B13DM-0007db-RP
	for asrg@optimus.ietf.org; Wed, 10 Mar 2004 07:53:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06523
	for <asrg@ietf.org>; Wed, 10 Mar 2004 07:53:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B13DM-0006t7-00
	for asrg@ietf.org; Wed, 10 Mar 2004 07:53:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B13CT-0006kR-00
	for asrg@ietf.org; Wed, 10 Mar 2004 07:52:41 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B13CD-0006bH-00
	for asrg@ietf.org; Wed, 10 Mar 2004 07:52:25 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B13CC-0006lV-00; Wed, 10 Mar 2004 07:52:24 -0500
Received: from [68.244.223.82] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B13CB-0000rF-00; Wed, 10 Mar 2004 07:52:24 -0500
Message-ID: <404F0F7D.40002@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Alan DeKok <aland@ox.org>
CC: ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation Systems and their Problems
References: <20040308181807.10C6816D00@mail.nitros9.org>
In-Reply-To: <20040308181807.10C6816D00@mail.nitros9.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Wed, 10 Mar 2004 07:52:13 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Alan DeKok wrote:

> Yakov Shafranovich <research@solidmatrix.com> wrote:
> 
>>In the current world the closest approximation we have to reputation 
>>systems that are planned with LMAP are blacklists and Senderbase. Given 
>>that current blacklists have numerous problems, why would any proposed 
>>reputation or accrediation systems of the future be any different?
> 
> 
>   If you base the accreditiation system on something other than
> personal prejudices (which is what most content filters and blacklists
> end up being), then the accreditation becomes a little more useful.
> 
> 
>>How are we planning on avoiding the same problems we have today in
>>the future, if we want to deploy such systems?
> 
> 
>   Keep the accreditation focused on simple data which can be trivially
> verified in the network.  The only reason to have a centralized
> accrediation service is to simplify record keeping.  e.g. You *could*
> find web pages by rooting around the net yourself, but it's a lot
> easier just to use a search engine.
> 

What about the draft that was suggested in the following message:

https://www1.ietf.org/mail-archive/working-groups/asrg/current/msg09253.html

Yakov

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



From exim@www1.ietf.org  Wed Mar 10 08:00:13 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06642
	for <asrg-archive@odin.ietf.org>; Wed, 10 Mar 2004 08:00:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B13JH-0008FN-QQ
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 07:59:43 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2ACxhDW031695
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 07:59:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B13JH-0008F8-Lr
	for asrg-web-archive@optimus.ietf.org; Wed, 10 Mar 2004 07:59:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06602
	for <asrg-web-archive@ietf.org>; Wed, 10 Mar 2004 07:59:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B13JG-0007nq-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 07:59:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B13IJ-0007eW-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 07:58:44 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B13Hc-0007UY-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 07:58:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B13Hc-0007ry-L8; Wed, 10 Mar 2004 07:58:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B13FL-0007ib-1s
	for asrg@optimus.ietf.org; Wed, 10 Mar 2004 07:55:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA06535
	for <asrg@ietf.org>; Wed, 10 Mar 2004 07:55:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B13FK-0007BA-00
	for asrg@ietf.org; Wed, 10 Mar 2004 07:55:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B13EL-00072T-00
	for asrg@ietf.org; Wed, 10 Mar 2004 07:54:38 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B13E4-0006te-00
	for asrg@ietf.org; Wed, 10 Mar 2004 07:54:20 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B13E4-0007HJ-00
	for asrg@ietf.org; Wed, 10 Mar 2004 07:54:20 -0500
Received: from [68.244.223.82] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B13E3-0000uP-00
	for asrg@ietf.org; Wed, 10 Mar 2004 07:54:20 -0500
Message-ID: <404F0FF1.2000800@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 3b. SMTP Verification - Reputation/Accreditation Services - Problem
 Statement
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/mail-archive/working-groups/asrg/>
Date: Wed, 10 Mar 2004 07:54:09 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

After the much heated discussion on the topic, I want to back track and 
ask all of you a simple question:

What aspects of the spam problem do these services 
(reputation/accreditation) propose to solve? What types of spam messages 
specifically do they address?

Yakov

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



From exim@www1.ietf.org  Wed Mar 10 10:50:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16763
	for <asrg-archive@odin.ietf.org>; Wed, 10 Mar 2004 10:50:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B15xj-0008AD-D5
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 10:49:39 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2AFndZ2031380
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 10:49:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B15xj-0008A3-5a
	for asrg-web-archive@optimus.ietf.org; Wed, 10 Mar 2004 10:49:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16724
	for <asrg-web-archive@ietf.org>; Wed, 10 Mar 2004 10:49:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B15xg-0000d5-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 10:49:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B15wi-0000Rr-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 10:48:37 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B15vo-0000GG-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 10:47:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B15vC-0007me-2I; Wed, 10 Mar 2004 10:47:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B15uF-0007Uj-0q
	for asrg@optimus.ietf.org; Wed, 10 Mar 2004 10:46:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16480
	for <asrg@ietf.org>; Wed, 10 Mar 2004 10:45:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B15uC-0007jE-00
	for asrg@ietf.org; Wed, 10 Mar 2004 10:46:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B15tH-0007Y9-00
	for asrg@ietf.org; Wed, 10 Mar 2004 10:45:03 -0500
Received: from host217-35-105-169.in-addr.btopenworld.com ([217.35.105.169] helo=mail.neosinteractive.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B15sg-0007Mk-00
	for asrg@ietf.org; Wed, 10 Mar 2004 10:44:27 -0500
Received: from tthomson ([217.35.105.173] unverified) by mail.neosinteractive.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 10 Mar 2004 14:49:34 +0000
From: "Tom Thomson" <tthomson@neosinteractive.com>
To: "Yakov Shafranovich" <research@solidmatrix.com>, "ASRG" <asrg@ietf.org>
Subject: RE: [Asrg] 3b. SMTP Verification - Reputation/Accreditation Services - Problem Statement
Message-ID: <IOEPKAPPDKHPENCKFNNGIEDCDCAA.tthomson@neosinteractive.com>
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 IMO, Build 9.0.6604 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
In-Reply-To: <404F0FF1.2000800@solidmatrix.com>
X-OriginalArrivalTime: 10 Mar 2004 14:49:34.0406 (UTC) FILETIME=[E712C660:01C406AE]
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/mail-archive/working-groups/asrg/>
Date: Wed, 10 Mar 2004 15:44:26 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I think they are attempting to address the problem of recognizing non-spam
as non-spam.  They don't address any particular sort of spam, they merely
tell us that certain people are accredited as non-spammers according to yhe
service managers definition of non-spammer..

Given that mailboxes that have been used for mailing lists (like ASRG) which
expose addresses in their archives and/or for posting to newsgroups tend for
a long time will tend to receive more spam than non-spam, anthing that helps
make the distinction is potentially useful.

We are going to have to put up with vast quantities of spam for the
forseeable future, especially since US Federal legislation has provided the
spammers with the right to send as much spam as they like provided they
conform to some fairly trivial rules, and also prevented the ordinary
victims of spam from suing spammers who don't follow even those rules, so
accreditation services may be useful.  On the other hand, they may be about
as useful some of the RBLs we currently suffer from (ie no use at all).

It's a pity the US legislature has again, as it so often does, chosen a
model that supports the providers of campaign funds instead of a model that
protects the ordinary Joe. Maybe we can get can-spam canned and siome
sensible legislation in its place (adopting the EU directive might be a good
start) but I doubt it - the "legitimate" advertisers have an axe to grind
and provide too many pennies to the election candidates to be ignored.

Tom.

-----Original Message-----
From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org]On Behalf Of Yakov
Shafranovich
Sent: 10 March 2004 12:54
To: ASRG
Subject: [Asrg] 3b. SMTP Verification - Reputation/Accreditation
Services - Problem Statement


After the much heated discussion on the topic, I want to back track and
ask all of you a simple question:

What aspects of the spam problem do these services
(reputation/accreditation) propose to solve? What types of spam messages
specifically do they address?

Yakov

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


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



From exim@www1.ietf.org  Wed Mar 10 12:49:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23002
	for <asrg-archive@odin.ietf.org>; Wed, 10 Mar 2004 12:49:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B17p5-0004CD-KZ
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 12:48:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2AHmpGt016120
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 12:48:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B17p5-0004Bq-C2
	for asrg-web-archive@optimus.ietf.org; Wed, 10 Mar 2004 12:48:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22975
	for <asrg-web-archive@ietf.org>; Wed, 10 Mar 2004 12:48:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B17p3-0006Tr-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 12:48:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B17o9-0006Kb-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 12:47:54 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B17ni-0006BS-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 12:47:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B17nK-00040Y-7M; Wed, 10 Mar 2004 12:47:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B17lE-0003pm-40
	for asrg@optimus.ietf.org; Wed, 10 Mar 2004 12:44:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22787
	for <asrg@ietf.org>; Wed, 10 Mar 2004 12:44:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B17lC-0005rE-00
	for asrg@ietf.org; Wed, 10 Mar 2004 12:44:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B17kL-0005hv-00
	for asrg@ietf.org; Wed, 10 Mar 2004 12:43:58 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B17jl-0005YL-00
	for asrg@ietf.org; Wed, 10 Mar 2004 12:43:22 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B17jl-0004kU-00
	for asrg@ietf.org; Wed, 10 Mar 2004 12:43:21 -0500
Received: from [68.244.245.11] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B17jk-0000cK-00
	for asrg@ietf.org; Wed, 10 Mar 2004 12:43:21 -0500
Message-ID: <404F53AC.8090008@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 0. General - List Policy - No E-postage or C/R
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/mail-archive/working-groups/asrg/>
Date: Wed, 10 Mar 2004 12:43:08 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HOT_NASTY autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The bounce message below arrived to day in my mailbox. As a reminder to 
everyone, if you use C/R systems or any kind of e-postage systems, 
PLEASE WHITELIST mailing lists. Otherwise, we'll be forced to take you 
off the list since we simply do not have enough time to reply to C/R 
challenges and obtain trial postage stamps.

Sincerely,
Yakov Shafranovich
Co-Chair, ASRG

P.S. and whoever this "dps" user is, please contact me off-list from a 
non-epostage account so I can renable your subscription.

-------- Original Message --------
Subject: Unstamped mail
Date: 10 Mar 2004 15:40:58 -0000
From: dps@xxxxxxx
To: xxxxxx@ietf.org

Hi,

You forgot to put a stamp on your email.

Sorry to bounce your email to dps@xxxxxxxxxxx. As an anti-spam measure, 
this user now asks you to add an email stamp when you send them email.

You mail was returned with the following status: 991 Postage required. 
Please add a stamp.

If you want your message delivered or more information please visit: 
http://www.pennymail.com/bounce.jsp?user=dps@xxxxxxxxxx

Thank you.

Here is the full list of recipients that did not receive your message:
     dps@xxxxxxxxx

Here is a copy of the first 200 characters of the original message:


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



From exim@www1.ietf.org  Wed Mar 10 14:38:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28848
	for <asrg-archive@odin.ietf.org>; Wed, 10 Mar 2004 14:38:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B19Wj-0006Kj-Bi
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 14:38:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2AJc1Hn024322
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 14:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B19Wi-0006KD-N7
	for asrg-web-archive@optimus.ietf.org; Wed, 10 Mar 2004 14:38:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28838
	for <asrg-web-archive@ietf.org>; Wed, 10 Mar 2004 14:37:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B19Wg-0002R5-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 14:37:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B19Vj-0002Hb-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 14:36:59 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B19VD-00028P-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 14:36:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B19Uo-0005vw-6N; Wed, 10 Mar 2004 14:36:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B19Ui-0005vG-Dy
	for asrg@optimus.ietf.org; Wed, 10 Mar 2004 14:35:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28741
	for <asrg@ietf.org>; Wed, 10 Mar 2004 14:35:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B19Uf-00026N-00
	for asrg@ietf.org; Wed, 10 Mar 2004 14:35:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B19TY-0001w1-00
	for asrg@ietf.org; Wed, 10 Mar 2004 14:34:45 -0500
Received: from plounts.uits.indiana.edu ([129.79.1.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B19Sg-0001lV-00
	for asrg@ietf.org; Wed, 10 Mar 2004 14:33:50 -0500
Received: from fontz.uits.indiana.edu (fontz.uits.indiana.edu [129.79.1.76])
	by plounts.uits.indiana.edu (8.12.10/8.12.10/IUPO) with ESMTP id i2AJXlxI029485
	for <asrg@ietf.org>; Wed, 10 Mar 2004 14:33:48 -0500 (EST)
Received: from [156.56.79.87] ([156.56.79.87])
	(authenticated bits=0)
	by fontz.uits.indiana.edu (8.12.10/8.12.10/IUPO) with ESMTP id i2AJXlCg005618
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <asrg@ietf.org>; Wed, 10 Mar 2004 14:33:48 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v609)
In-Reply-To: <20040310170011.25768.104.Mailman@www1.ietf.org>
References: <20040310170011.25768.104.Mailman@www1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <D4C8DE52-72C9-11D8-BEC2-000393DC31DA@bloomington.in.us>
Content-Transfer-Encoding: 7bit
From: Jim Witte <jswitte@bloomington.in.us>
To: asrg@ietf.org
X-Mailer: Apple Mail (2.609)
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: Spam laws
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/mail-archive/working-groups/asrg/>
Date: Wed, 10 Mar 2004 14:33:39 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> It's a pity the US legislature has again, as it so often does, chosen a
> model that supports the providers of campaign funds instead of a model 
> that
> protects the ordinary Joe. Maybe we can get can-spam canned and siome
> sensible legislation in its place (adopting the EU directive might be 
> a good

   Getting probably off-topic into the "politics of spam" - what about 
all the porm spam out there?

   That should certainly fall under almost any indecency standard I can 
imagine - and it shouldn't be too hard to write some indecency law that 
would trap them, never even get *near* the "artistic soft-porn" side of 
things..  And probably get around first-ammendment problems too (what 
exactly is the Free Speech value of showing explicitly naked breasts, 
clitorii (Latin plural correct?) and  penises, in various 
configurations, pray tell me?)  An in the EU, one might not have the 
save "high bar" of protection as the First Ammendment in the US - I 
don't know how much EU laws on speech protect.

Jim Witte
jswitte@bloomington.in.us
Indiana University CS


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



From exim@www1.ietf.org  Wed Mar 10 15:11:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00796
	for <asrg-archive@odin.ietf.org>; Wed, 10 Mar 2004 15:11:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1A2U-0007uB-Vz
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 15:10:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2AKAowZ030381
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 15:10:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1A2U-0007tw-QD
	for asrg-web-archive@optimus.ietf.org; Wed, 10 Mar 2004 15:10:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00720
	for <asrg-web-archive@ietf.org>; Wed, 10 Mar 2004 15:10:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1A2R-0007hE-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 15:10:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1A1Y-0007Z3-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 15:09:53 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1A0t-0007Q0-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 15:09:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1A0i-0007Df-Mh; Wed, 10 Mar 2004 15:09:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B19xm-0005NA-7g
	for asrg@optimus.ietf.org; Wed, 10 Mar 2004 15:05:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00286
	for <asrg@ietf.org>; Wed, 10 Mar 2004 15:05:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B19xj-0006wZ-00
	for asrg@ietf.org; Wed, 10 Mar 2004 15:05:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B19wn-0006og-00
	for asrg@ietf.org; Wed, 10 Mar 2004 15:04:58 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B19wT-0006g4-00
	for asrg@ietf.org; Wed, 10 Mar 2004 15:04:37 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B19wQ-0004co-00; Wed, 10 Mar 2004 15:04:34 -0500
Received: from [68.244.245.11] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B19wP-0003a9-00; Wed, 10 Mar 2004 15:04:34 -0500
Message-ID: <404F74C6.4000409@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Tom Thomson <tthomson@neosinteractive.com>
CC: ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation/Accreditation Services
 - Problem Statement
References: <IOEPKAPPDKHPENCKFNNGIEDCDCAA.tthomson@neosinteractive.com>
In-Reply-To: <IOEPKAPPDKHPENCKFNNGIEDCDCAA.tthomson@neosinteractive.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Wed, 10 Mar 2004 15:04:22 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The problem is that these definitions vary as we have seen with
blacklists, and if we go that way, we'll end up with the same problems.
That's what worries me in particular regarding reputation systems and 
blacklists. In regards to whitelists and accreditation, what worries me 
is how they are used.

Yakov

Tom Thomson wrote:
> I think they are attempting to address the problem of recognizing non-spam
> as non-spam.  They don't address any particular sort of spam, they merely
> tell us that certain people are accredited as non-spammers according to yhe
> service managers definition of non-spammer..
> 
> 
> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org]On Behalf Of Yakov
> Shafranovich
> Sent: 10 March 2004 12:54
> To: ASRG
> Subject: [Asrg] 3b. SMTP Verification - Reputation/Accreditation
> Services - Problem Statement
> 
> 
> After the much heated discussion on the topic, I want to back track and
> ask all of you a simple question:
> 
> What aspects of the spam problem do these services
> (reputation/accreditation) propose to solve? What types of spam messages
> specifically do they address?
> 
> 



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



From exim@www1.ietf.org  Wed Mar 10 17:37:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10740
	for <asrg-archive@odin.ietf.org>; Wed, 10 Mar 2004 17:37:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1CJw-0006Ep-VP
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 17:37:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2AMb0di023969
	for asrg-archive@odin.ietf.org; Wed, 10 Mar 2004 17:37:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1CJw-0006EW-Mp
	for asrg-web-archive@optimus.ietf.org; Wed, 10 Mar 2004 17:37:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10737
	for <asrg-web-archive@ietf.org>; Wed, 10 Mar 2004 17:36:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1CJu-0001tA-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 17:36:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1CJ1-0001lB-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 17:36:04 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1CIJ-0001cU-00
	for asrg-web-archive@ietf.org; Wed, 10 Mar 2004 17:35:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1CI3-00063B-DK; Wed, 10 Mar 2004 17:35:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1CH3-0005vg-RF
	for asrg@optimus.ietf.org; Wed, 10 Mar 2004 17:34:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10659
	for <asrg@ietf.org>; Wed, 10 Mar 2004 17:33:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1CH1-0001Sx-00
	for asrg@ietf.org; Wed, 10 Mar 2004 17:33:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1CGA-0001Kc-00
	for asrg@ietf.org; Wed, 10 Mar 2004 17:33:06 -0500
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1CFl-0001BN-00
	for asrg@ietf.org; Wed, 10 Mar 2004 17:32:41 -0500
Received: from fda.zemos.net ([68.38.12.170])
          by comcast.net (rwcrmhc11) with ESMTP
          id <20040310223015013002um1ae>; Wed, 10 Mar 2004 22:30:15 +0000
Received: from zemos.net (phil [10.0.0.2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by fda.zemos.net (Postfix) with ESMTP
	id 549AC18680; Wed, 10 Mar 2004 17:30:12 -0500 (EST)
Message-ID: <404F96F3.2070608@zemos.net>
From: Philip Miller <millenix@zemos.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Tom Thomson <tthomson@neosinteractive.com>
Cc: ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation/Accreditation Services
 - Problem Statement
References: <IOEPKAPPDKHPENCKFNNGIEDCDCAA.tthomson@neosinteractive.com>
In-Reply-To: <IOEPKAPPDKHPENCKFNNGIEDCDCAA.tthomson@neosinteractive.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Wed, 10 Mar 2004 17:30:11 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Tom Thomson wrote:
> I think they are attempting to address the problem of recognizing non-spam
> as non-spam.  They don't address any particular sort of spam, they merely
> tell us that certain people are accredited as non-spammers according to the
> service managers' definition of non-spammer.

That would be a broken reputation system. Any honest reputation system 
should have hard, definite rules for inclusion, with no element of 
subjectivity. This will quite intentionally include 'legitimate' spammers, 
who can then be filtered by a blacklist that references some well-known 
accreditation system. Any spammer who registers his mail immediately becomes 
identifiable and filterable. Any spammer (or non-compliant regular sender) 
who doesn't register gets filtered out because they have no reputation on 
record anywhere.

> Given that mailboxes that have been used for mailing lists (like ASRG) which
> expose addresses in their archives and/or for posting to newsgroups tend for
> a long time will tend to receive more spam than non-spam, anthing that helps
> make the distinction is potentially useful.

It's too bad groups like this don't exclusively use newsgroups instead of 
email. Unfortunately, although it sounded like a great idea when it was 
discussed here, it never really jelled.

> We are going to have to put up with vast quantities of spam for the
> forseeable future, especially since US Federal legislation has provided the
> spammers with the right to send as much spam as they like provided they
> conform to some fairly trivial rules, and also prevented the ordinary
> victims of spam from suing spammers who don't follow even those rules, so
> accreditation services may be useful.  On the other hand, they may be about
> as useful some of the RBLs we currently suffer from (ie no use at all).

Although I don't like the law either, that doesn't sound like a fair 
characterization of CAN-SPAM. I don't recall it specifically denying any 
private right of action, although it did preempt some state laws that 
provided for that right.

> It's a pity the US legislature has again, as it so often does, chosen a
> model that supports the providers of campaign funds instead of a model that
> protects the ordinary Joe. Maybe we can get can-spam canned and some
> sensible legislation in its place (adopting the EU directive might be a good
> start) but I doubt it - the "legitimate" advertisers have an axe to grind
> and provide too many pennies to the election candidates to be ignored.

Legislation is not within the scope of this group, and with good reason: the 
Internet is international, and so must be any _technical_ solution to the 
spam problem. There is no possibility of an international convention 
defining and outlawing spam any time soon.

> Tom.

Philip Miller

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



From exim@www1.ietf.org  Thu Mar 11 11:39:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10210
	for <asrg-archive@odin.ietf.org>; Thu, 11 Mar 2004 11:39:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1TCr-0000Nf-73
	for asrg-archive@odin.ietf.org; Thu, 11 Mar 2004 11:38:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2BGcncZ001444
	for asrg-archive@odin.ietf.org; Thu, 11 Mar 2004 11:38:49 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1TCq-0000N7-79
	for asrg-web-archive@optimus.ietf.org; Thu, 11 Mar 2004 11:38:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10190
	for <asrg-web-archive@ietf.org>; Thu, 11 Mar 2004 11:38:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1TCp-0003Kn-00
	for asrg-web-archive@ietf.org; Thu, 11 Mar 2004 11:38:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1TBw-0003Cn-00
	for asrg-web-archive@ietf.org; Thu, 11 Mar 2004 11:37:52 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1TBF-00034Z-00
	for asrg-web-archive@ietf.org; Thu, 11 Mar 2004 11:37:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1TAA-0008Jl-8h; Thu, 11 Mar 2004 11:36:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1T9s-0008It-Iz
	for asrg@optimus.ietf.org; Thu, 11 Mar 2004 11:35:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA10089
	for <asrg@ietf.org>; Thu, 11 Mar 2004 11:35:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1T9r-0002uM-00
	for asrg@ietf.org; Thu, 11 Mar 2004 11:35:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1T8x-0002mZ-00
	for asrg@ietf.org; Thu, 11 Mar 2004 11:34:47 -0500
Received: from amber.ccs.neu.edu ([129.10.116.51])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1T81-0002du-00
	for asrg@ietf.org; Thu, 11 Mar 2004 11:33:49 -0500
Received: from jmarshall.ccs.neu.edu ([129.10.115.140] helo=RASPUTIN.ccs.neu.edu)
	by amber.ccs.neu.edu with esmtp (Exim 4.30)
	id 1B1T80-0005ey-TQ; Thu, 11 Mar 2004 11:33:48 -0500
To: Jim Witte <jswitte@bloomington.in.us>
Cc: asrg@ietf.org
From: Joe Marshall <jrm@ccs.neu.edu>
In-Reply-To: <D4C8DE52-72C9-11D8-BEC2-000393DC31DA@bloomington.in.us> (Jim
 Witte's message of "Wed, 10 Mar 2004 14:33:39 -0500")
References: <20040310170011.25768.104.Mailman@www1.ietf.org>
	<D4C8DE52-72C9-11D8-BEC2-000393DC31DA@bloomington.in.us>
Message-ID: <ptbj8hsi.fsf_-_@ccs.neu.edu>
User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN,
 windows-nt)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Asrg] [OT] plurals
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/mail-archive/working-groups/asrg/>
Date: Thu, 11 Mar 2004 11:33:49 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Jim Witte <jswitte@bloomington.in.us> writes:

> clitorii (Latin plural correct?) 

These are fun to be pedantic about.

penis -> penes
clitoris -> clitorides


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



From exim@www1.ietf.org  Thu Mar 11 12:49:14 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13327
	for <asrg-archive@odin.ietf.org>; Thu, 11 Mar 2004 12:49:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1UIY-0007FC-Ok
	for asrg-archive@odin.ietf.org; Thu, 11 Mar 2004 12:48:47 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2BHmkdj027840
	for asrg-archive@odin.ietf.org; Thu, 11 Mar 2004 12:48:46 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1UIY-0007Ex-JS
	for asrg-web-archive@optimus.ietf.org; Thu, 11 Mar 2004 12:48:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13298
	for <asrg-web-archive@ietf.org>; Thu, 11 Mar 2004 12:48:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1UIW-0005Qp-00
	for asrg-web-archive@ietf.org; Thu, 11 Mar 2004 12:48:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1UHa-0005HY-00
	for asrg-web-archive@ietf.org; Thu, 11 Mar 2004 12:47:47 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1UGh-00057y-00
	for asrg-web-archive@ietf.org; Thu, 11 Mar 2004 12:46:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1UFu-0006mQ-0q; Thu, 11 Mar 2004 12:46:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1UEy-0006iM-9v
	for asrg@optimus.ietf.org; Thu, 11 Mar 2004 12:45:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12933
	for <asrg@ietf.org>; Thu, 11 Mar 2004 12:45:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1UEw-0004pC-00
	for asrg@ietf.org; Thu, 11 Mar 2004 12:45:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1UDz-0004fZ-00
	for asrg@ietf.org; Thu, 11 Mar 2004 12:44:03 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1B1UD4-0004Va-00
	for asrg@ietf.org; Thu, 11 Mar 2004 12:43:06 -0500
Received: (qmail 59594 invoked by uid 1013); 11 Mar 2004 17:43:04 -0000
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: Yakov Shafranovich <research@solidmatrix.com>
Cc: ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation/Accreditation Services - Problem Statement
Message-ID: <20040311174304.GA56829@Space.Net>
References: <404F0FF1.2000800@solidmatrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <404F0FF1.2000800@solidmatrix.com>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
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/mail-archive/working-groups/asrg/>
Date: Thu, 11 Mar 2004 18:43:04 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Wed, Mar 10, 2004 at 07:54:09AM -0500, Yakov Shafranovich wrote:
> What aspects of the spam problem do these services 
> (reputation/accreditation) propose to solve? What types of spam messages 
> specifically do they address?

IMHO the idea behind a reputation/accreditation works like that:
w1) gain a good reputation for the system by getting some people
   with a good reputation to work for or give their name for it.
w2) depending on the type of reputation system (whitelist
   / blacklist / neutral list) they try to use this information and
   e.g. in case of whitelists try to hand down their reputation.
   It works like a web of trust: I trust the system so I trust
   their statements.
w3) the problem arising is the quality of the system and the time and
   effort they put on the validation process and keeping the information
   uptodate.
   There are also external influences like legislation and political
   pressure.

The problem these kind of systems try to solve are IMHO
1) authentication
   with the worth of their own reputation they try to build a trust
   situation for the sender by providing some kind of certificate
   like "this sender is really the sender he pretends to be".
   This could also be done with TLS/CERTs but would require such
   a cert for each and every mailserver (like we now have it with
   most HTTPS server that want to offer authentication).
   They kinda run a central authentication service instead of a
   decentralized one and solve the problem for the admins to have their
   MTAs talk TLS which is not widely deployed currently.
2) policy
   while the authentication information per se is neutral with regards
   to good or bad, white or black it is important for some receivers
   to get a clue about policies the sender adopts to.
   There have been proposals to allow the sender to communicate his
   policies, however I don't know of any sending MTA communicating
   policies. (Some receiving MTAs express policies in the initial
   greeting like "220 mail.example.com no spam/UCE allowed").
   There is something (roughly) similiar for HTTP that are called P3P
   and PICS (Platform for Internet Content Selection)
       http://www.w3.org/P3P/
       http://www.w3.org/PICS/
   The problem that still exists, even with publishing policies, is again
   trust. Receivers wish to know whether they can trust the policies
   published by the sender or if the sender simply is a liar.
   This is the second area reputation/accreditation try to help with,
   they publish policies that senders promised to stick to and they
   certify that the sender is not a liar.

But with w3) above there are problems with the correctness of this
information.

IMHO the problems these systems try to solve is not only spam but mainly
provide values for a rating system (like spamassassin uses) to reduce the
number of false positives by allowing to apply rather high scores and
thus work like white/blacklists.

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"

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



From exim@www1.ietf.org  Thu Mar 11 14:33:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17920
	for <asrg-archive@odin.ietf.org>; Thu, 11 Mar 2004 14:33:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1VvG-0001A0-EK
	for asrg-archive@odin.ietf.org; Thu, 11 Mar 2004 14:32:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2BJWoHP004454
	for asrg-archive@odin.ietf.org; Thu, 11 Mar 2004 14:32:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1VvG-00019l-8V
	for asrg-web-archive@optimus.ietf.org; Thu, 11 Mar 2004 14:32:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17872
	for <asrg-web-archive@ietf.org>; Thu, 11 Mar 2004 14:32:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1VvD-0004hu-00
	for asrg-web-archive@ietf.org; Thu, 11 Mar 2004 14:32:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1VuI-0004YP-00
	for asrg-web-archive@ietf.org; Thu, 11 Mar 2004 14:31:50 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1VtQ-0004R6-00
	for asrg-web-archive@ietf.org; Thu, 11 Mar 2004 14:30:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1VsZ-0000g8-4U; Thu, 11 Mar 2004 14:30:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1VsJ-0000fO-OY
	for asrg@optimus.ietf.org; Thu, 11 Mar 2004 14:29:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17755
	for <asrg@ietf.org>; Thu, 11 Mar 2004 14:29:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1VsH-0004Hw-00
	for asrg@ietf.org; Thu, 11 Mar 2004 14:29:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1VrK-00049a-00
	for asrg@ietf.org; Thu, 11 Mar 2004 14:28:47 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1VqT-0003zU-00
	for asrg@ietf.org; Thu, 11 Mar 2004 14:27:53 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id 4EA0916FD1
	for <asrg@ietf.org>; Thu, 11 Mar 2004 14:31:16 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation Systems and their Problems 
In-Reply-To: Your message of "Wed, 10 Mar 2004 07:52:13 EST."
             <404F0F7D.40002@solidmatrix.com> 
Message-Id: <20040311193117.4EA0916FD1@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Thu, 11 Mar 2004 14:31:16 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Yakov Shafranovich <research@solidmatrix.com> WROTE:
> >   Keep the accreditation focused on simple data which can be trivially
> > verified in the network.
...
> 
> What about the draft that was suggested in the following message:
> 
> https://www1.ietf.org/mail-archive/working-groups/asrg/current/msg09253.html

  It's a good start.  Now if only I had the time to follow up.

  Alan DeKok.

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



From exim@www1.ietf.org  Fri Mar 12 01:03:48 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20293
	for <asrg-archive@odin.ietf.org>; Fri, 12 Mar 2004 01:03:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1flP-0003Vj-CB
	for asrg-archive@odin.ietf.org; Fri, 12 Mar 2004 01:03:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2C63JH7013489
	for asrg-archive@odin.ietf.org; Fri, 12 Mar 2004 01:03:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1flP-0003VU-7i
	for asrg-web-archive@optimus.ietf.org; Fri, 12 Mar 2004 01:03:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA20286
	for <asrg-web-archive@ietf.org>; Fri, 12 Mar 2004 01:03:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1flM-0007eJ-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 01:03:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1fkP-0007Wt-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 01:02:18 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1fk7-0007PF-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 01:01:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1fjC-0003KM-Gp; Fri, 12 Mar 2004 01:01:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1fhS-0003GZ-AA
	for asrg@optimus.ietf.org; Fri, 12 Mar 2004 00:59:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA20171
	for <asrg@ietf.org>; Fri, 12 Mar 2004 00:59:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1fhP-00078H-00
	for asrg@ietf.org; Fri, 12 Mar 2004 00:59:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1fgT-00070J-00
	for asrg@ietf.org; Fri, 12 Mar 2004 00:58:13 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1ffm-0006tF-00
	for asrg@ietf.org; Fri, 12 Mar 2004 00:57:30 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B1ffm-00074Q-00
	for asrg@ietf.org; Fri, 12 Mar 2004 00:57:30 -0500
Received: from [68.244.211.82] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B1ffl-0005qY-00
	for asrg@ietf.org; Fri, 12 Mar 2004 00:57:30 -0500
Message-ID: <40515134.8070306@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id AAA20172
Subject: [Asrg] 0. General - FCC soliciting comments on mobile spam rules
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/mail-archive/working-groups/asrg/>
Date: Fri, 12 Mar 2004 00:57:08 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

 From (http://hraunfoss.fcc.gov/edocs_public/attachmatch/DOC-244843A1.pdf=
):

-------------------------------------------------------------------------=
-----
Specifically, the Commission asked for comments on, among other things:

o The ability of senders to determine whether a message is a mobile
commercial electronic mail message and methods to enable the sender to
make this determination; for instance, whether there should be a list=20
of, or standard naming convention for domain names, or an individual=20
registry of e-mail addresses. Another area for comment is that of=20
automatic challenge-response mechanisms that alert senders they are=20
sending their message to such a subscriber.

o How to provide subscribers with the ability to avoid receiving mobile
service commercial messages sent without the subscribers=92 prior consent=
,
and how to indicate electronically a desire not to receive future mobile
service commercial messages from specific senders.

o Whether commercial cellular providers should be exempted from having=20
to obtain express prior authorization before sending a commercial=20
message to their customers.

o How senders can comply with the Act in general, given the unique
technical limitations, particularly message length limitations and the
information required to be included in messages by the Act.
-------------------------------------------------------------------------=
-----

Yakov

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



From exim@www1.ietf.org  Fri Mar 12 10:04:08 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25575
	for <asrg-archive@odin.ietf.org>; Fri, 12 Mar 2004 10:04:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1oCL-0006Sf-8R
	for asrg-archive@odin.ietf.org; Fri, 12 Mar 2004 10:03:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2CF3ftq024837
	for asrg-archive@odin.ietf.org; Fri, 12 Mar 2004 10:03:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1oCL-0006SV-1q
	for asrg-web-archive@optimus.ietf.org; Fri, 12 Mar 2004 10:03:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA25539
	for <asrg-web-archive@ietf.org>; Fri, 12 Mar 2004 10:03:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1oCI-0001Vv-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 10:03:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1oBP-0001M4-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 10:02:44 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1oAj-0001Ax-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 10:02:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1o9l-00053o-5Y; Fri, 12 Mar 2004 10:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1o8m-0004g9-PC
	for asrg@optimus.ietf.org; Fri, 12 Mar 2004 10:00:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA24889
	for <asrg@ietf.org>; Fri, 12 Mar 2004 09:59:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1o8k-0000n6-00
	for asrg@ietf.org; Fri, 12 Mar 2004 09:59:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1o7T-0000bO-00
	for asrg@ietf.org; Fri, 12 Mar 2004 09:58:40 -0500
Received: from pengo.systems.pipex.net ([62.241.160.193])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1o74-0000Sn-00
	for asrg@ietf.org; Fri, 12 Mar 2004 09:58:14 -0500
Received: from tom3 (1Cust237.tnt13.lnd4.gbr.da.uu.net [62.188.142.237])
	by pengo.systems.pipex.net (Postfix) with SMTP id B2A384C0039B
	for <asrg@ietf.org>; Fri, 12 Mar 2004 14:57:40 +0000 (GMT)
Message-ID: <000a01c40842$25597560$0301a8c0@tom3>
Reply-To: "Tom Petch" <nwnetworks@dial.pipex.com>
From: "Tom Petch" <nwnetworks@dial.pipex.com>
To: "'ASRG'" <asrg@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.2106.4
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4
Content-Transfer-Encoding: 7bit
Subject: [Asrg] trojans in the IETF ?
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/mail-archive/working-groups/asrg/>
Date: Fri, 12 Mar 2004 14:54:42 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

I just got an unwanted e-mail offering an improvement in performance
directed to several IETF lists namely
gsmp@ietf.org, hubmib-admin@ietf.org, hubmib@ietf.org,  iab@ietf.org,
idr-admin@ietf.org, idr@ietf.org, ieprep-admin@ietf.org

Three things puzzle me. I am subscribed to more than one of these lists but
only received the mail on idr - why the inconsistency?

Second, the e-mail contains a check saying hits 8.4 required 5 so  why did
it get sent it at all?

And, I extracted enough of the header to identify the mail and sent it off
to idr-admin to get back a message saying blocked by s p a m control; err
yes, the IETF can send it to me but I cannot tell the IETF what they are
doing.

Explanations, especially conspiracy theories, appreciated.

Tom Petch




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



From exim@www1.ietf.org  Fri Mar 12 10:52:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29133
	for <asrg-archive@odin.ietf.org>; Fri, 12 Mar 2004 10:52:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1owh-0006XG-Mq
	for asrg-archive@odin.ietf.org; Fri, 12 Mar 2004 10:51:36 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2CFpZBS025116
	for asrg-archive@odin.ietf.org; Fri, 12 Mar 2004 10:51:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1owh-0006X1-Ed
	for asrg-web-archive@optimus.ietf.org; Fri, 12 Mar 2004 10:51:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29112
	for <asrg-web-archive@ietf.org>; Fri, 12 Mar 2004 10:51:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1owf-00002a-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 10:51:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1ovm-0007jL-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 10:50:39 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1ouw-0007co-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 10:49:46 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1ouD-0006Lg-58; Fri, 12 Mar 2004 10:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1otu-0006ID-O5
	for asrg@optimus.ietf.org; Fri, 12 Mar 2004 10:48:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29010
	for <asrg@ietf.org>; Fri, 12 Mar 2004 10:48:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1ots-0007Tp-00
	for asrg@ietf.org; Fri, 12 Mar 2004 10:48:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1osw-0007M4-00
	for asrg@ietf.org; Fri, 12 Mar 2004 10:47:42 -0500
Received: from host217-35-105-169.in-addr.btopenworld.com ([217.35.105.169] helo=mail.neosinteractive.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1osE-0007EZ-00
	for asrg@ietf.org; Fri, 12 Mar 2004 10:46:59 -0500
Received: from tthomson ([217.35.105.173] unverified) by mail.neosinteractive.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Fri, 12 Mar 2004 14:52:04 +0000
From: "Tom Thomson" <tthomson@neosinteractive.com>
To: "Philip Miller" <millenix@zemos.net>
Cc: "ASRG" <asrg@ietf.org>
Subject: RE: [Asrg] 3b. SMTP Verification - Reputation/Accreditation Services - Problem Statement
Message-ID: <IOEPKAPPDKHPENCKFNNGMEEBDCAA.tthomson@neosinteractive.com>
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 IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <404F96F3.2070608@zemos.net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-OriginalArrivalTime: 12 Mar 2004 14:52:04.0421 (UTC) FILETIME=[9550BF50:01C40841]
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/mail-archive/working-groups/asrg/>
Date: Fri, 12 Mar 2004 15:46:53 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Philip Miller [mailto:millenix@zemos.net] wrote:
>
> Tom Thomson wrote:
> > I think they are attempting to address the problem of recognizing
non-spam
> > as non-spam.  They don't address any particular sort of spam, they
merely
> > tell us that certain people are accredited as non-spammers according to
the
> > service managers' definition of non-spammer.
>
> That would be a broken reputation system. Any honest reputation system
> should have hard, definite rules for inclusion, with no element of
> subjectivity. This will quite intentionally include 'legitimate' spammers,
> who can then be filtered by a blacklist that references some well-known
> accreditation system. Any spammer who registers his mail immediately
becomes
> identifiable and filterable. Any spammer (or non-compliant regular sender)
> who doesn't register gets filtered out because they have no reputation on
> record anywhere.

What do you mean by "subjectivity"?  Are you are saying that there are
greater elements of subjectivity if the service manager publishes a
definition than if he fails to do so?  I can't see what else what you wrote
can mean, but I also can't actually believe you really meant that.

Why is the system broken if the person running it publishes definitions?
Surely it would be more broken if there were no definitions provided?

Why does an accreditation service have to include all emailers?  If I have
have hard rules for inclusion, surely those hard rules can exclude people?
If they can't, the "hard rules"  you say the system must have are actually
impotent and there's no point in having them.

[snip]
> Legislation is not within the scope of this group, and with good reason:
the
> Internet is international, and so must be any _technical_ solution to the
> spam problem. There is no possibility of an international convention
> defining and outlawing spam any time soon.

depends what you mean by "international".  There have been attempts to get
US/EU agreement on the topic, but they have failed because the US side
doesn't want to do anything that might actually stop the spammers from
spamming.  The EU seems to be quite successful in promoting bilateral
agreements on this topic with countries other than the US.  Agreements
withing the EU and bilateral agreements between the EU and other parties are
"international" by most definitions of the term.

Tom




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



From exim@www1.ietf.org  Fri Mar 12 14:37:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13521
	for <asrg-archive@odin.ietf.org>; Fri, 12 Mar 2004 14:37:35 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1sSx-0002T4-GL
	for asrg-archive@odin.ietf.org; Fri, 12 Mar 2004 14:37:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2CJb7iu009477
	for asrg-archive@odin.ietf.org; Fri, 12 Mar 2004 14:37:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1sSx-0002Sh-2q
	for asrg-web-archive@optimus.ietf.org; Fri, 12 Mar 2004 14:37:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13407
	for <asrg-web-archive@ietf.org>; Fri, 12 Mar 2004 14:37:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1sSu-0001mn-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 14:37:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1sR7-0001K5-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 14:35:14 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1sQO-00018X-05
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 14:34:28 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B1sJh-0006Kv-Bh
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 14:27:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1sJB-0001or-Ka; Fri, 12 Mar 2004 14:27:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1sIv-0001km-DB
	for asrg@optimus.ietf.org; Fri, 12 Mar 2004 14:26:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12861
	for <asrg@ietf.org>; Fri, 12 Mar 2004 14:26:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1sIs-0000Gs-00
	for asrg@ietf.org; Fri, 12 Mar 2004 14:26:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1sHz-0000AO-00
	for asrg@ietf.org; Fri, 12 Mar 2004 14:25:47 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1B1sHg-00003M-00
	for asrg@ietf.org; Fri, 12 Mar 2004 14:25:28 -0500
Received: (qmail 28643 invoked by uid 1013); 12 Mar 2004 19:25:25 -0000
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: Tom Thomson <tthomson@neosinteractive.com>
Cc: Philip Miller <millenix@zemos.net>, ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation/Accreditation Services - Problem Statement
Message-ID: <20040312192525.GA27254@Space.Net>
References: <404F96F3.2070608@zemos.net> <IOEPKAPPDKHPENCKFNNGMEEBDCAA.tthomson@neosinteractive.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <IOEPKAPPDKHPENCKFNNGMEEBDCAA.tthomson@neosinteractive.com>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
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/mail-archive/working-groups/asrg/>
Date: Fri, 12 Mar 2004 20:25:25 +0100
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Fri, Mar 12, 2004 at 03:46:53PM -0000, Tom Thomson wrote:
> What do you mean by "subjectivity"?  Are you are saying that there are
> greater elements of subjectivity if the service manager publishes a
> definition than if he fails to do so?  I can't see what else what you wrote
> can mean, but I also can't actually believe you really meant that.

I don't know if it is what Philip meant, but I understood it that way that
such a system has to have hard rules and only these rules decide about
inclusion or not. Addons like "but we may not include you if we don't like
the name of your company, even if all the other rules are fulfilled" in
inacceptable.

> Why does an accreditation service have to include all emailers?  If I have
> have hard rules for inclusion, surely those hard rules can exclude people?
> If they can't, the "hard rules"  you say the system must have are actually
> impotent and there's no point in having them.

The rules should not separate spammers from non-spammers per inclusion
but allow inclusion of all and thus provide authentication. You then can
have blacklist based on the authenticated data.

Think SSL/TLS: Everyone can buy a certificate signed by a CA as long
as the domain/server he wants to buy it for is theirs and they can
authenticate themselves via official documents like a company register
or something like that. This authenticates the host, but it does not
rate him good or bad.
However it is easier and safer for e.g. the receiver to build a blacklist
based on this authenticated data.
So the reputation/accreditation system should be open to everyone.

> depends what you mean by "international".  There have been attempts to get
> US/EU agreement on the topic, but they have failed because the US side
> doesn't want to do anything that might actually stop the spammers from
> spamming.  The EU seems to be quite successful in promoting bilateral
> agreements on this topic with countries other than the US.  Agreements
> withing the EU and bilateral agreements between the EU and other parties are
> "international" by most definitions of the term.

*lol*
The EU doesn't even manage to get the agreement ratified by all it's
member countries. Sad to say that but even my government hasn't ratified
the EU directive whose deadline has been sometime last year.
I haven't yet seen any agreements of the EU with other non-EU countries
regarding spam.
And sorry, providing a link for opt-out is not a solution to spam.
And IANAL but IMHO the demand for providing a opt-out possibility does
not include that a spammer must honor the request.

What the governments try is to kid all joe users because the pressure
from the indutry and their clueless marketing departments is so strong
that they will never decide something that will cause them disprofit.
And some companies that cry out loud and complain about spam are
spammers themselves.

So it is better not to trust on political help to solve the problem.

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"

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



From exim@www1.ietf.org  Fri Mar 12 22:41:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10147
	for <asrg-archive@odin.ietf.org>; Fri, 12 Mar 2004 22:41:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B201C-0007bE-DY
	for asrg-archive@odin.ietf.org; Fri, 12 Mar 2004 22:40:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2D3ewpR029206
	for asrg-archive@odin.ietf.org; Fri, 12 Mar 2004 22:40:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B201C-0007az-6G
	for asrg-web-archive@optimus.ietf.org; Fri, 12 Mar 2004 22:40:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10134
	for <asrg-web-archive@ietf.org>; Fri, 12 Mar 2004 22:40:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2018-0000Sq-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 22:40:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B200D-0000R4-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 22:39:58 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1zzW-0000PK-00
	for asrg-web-archive@ietf.org; Fri, 12 Mar 2004 22:39:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1zzJ-0007Rx-6G; Fri, 12 Mar 2004 22:39:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B1zzE-0007Rb-UY
	for asrg@optimus.ietf.org; Fri, 12 Mar 2004 22:38:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA10109
	for <asrg@ietf.org>; Fri, 12 Mar 2004 22:38:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1zzB-0000Ob-00
	for asrg@ietf.org; Fri, 12 Mar 2004 22:38:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B1zyH-0000Mq-00
	for asrg@ietf.org; Fri, 12 Mar 2004 22:37:58 -0500
Received: from sccrmhc12.comcast.net ([204.127.202.56])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B1zxc-0000I9-00
	for asrg@ietf.org; Fri, 12 Mar 2004 22:37:16 -0500
Received: from fda.zemos.net ([68.38.12.170])
          by comcast.net (sccrmhc12) with ESMTP
          id <20040313033641012006delee>; Sat, 13 Mar 2004 03:36:41 +0000
Received: from zemos.net (phil [10.0.0.2])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by fda.zemos.net (Postfix) with ESMTP
	id DA0CE1867F; Fri, 12 Mar 2004 22:36:40 -0500 (EST)
Message-ID: <405281C8.80007@zemos.net>
From: Philip Miller <millenix@zemos.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1
X-Accept-Language: en, en-us
MIME-Version: 1.0
To: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
Cc: Tom Thomson <tthomson@neosinteractive.com>, ASRG <asrg@ietf.org>
Subject: Re: [Asrg] 3b. SMTP Verification - Reputation/Accreditation Services
 - Problem Statement
References: <404F96F3.2070608@zemos.net> <IOEPKAPPDKHPENCKFNNGMEEBDCAA.tthomson@neosinteractive.com> <20040312192525.GA27254@Space.Net>
In-Reply-To: <20040312192525.GA27254@Space.Net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Fri, 12 Mar 2004 22:36:40 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Markus Stumpf wrote:
> On Fri, Mar 12, 2004 at 03:46:53PM -0000, Tom Thomson wrote:
>>What do you mean by "subjectivity"?  Are you are saying that there are
>>greater elements of subjectivity if the service manager publishes a
>>definition than if he fails to do so?  I can't see what else what you wrote
>>can mean, but I also can't actually believe you really meant that.
> 
> I don't know if it is what Philip meant, but I understood it that way that
> such a system has to have hard rules and only these rules decide about
> inclusion or not. Addons like "but we may not include you if we don't like
> the name of your company, even if all the other rules are fulfilled" in
> inacceptable.

That's exactly what I meant. It was an echo of sentiments expressed by 
others here.

>>Why does an accreditation service have to include all emailers?  If I have
>>have hard rules for inclusion, surely those hard rules can exclude people?
>>If they can't, the "hard rules"  you say the system must have are actually
>>impotent and there's no point in having them.
> 
> The rules should not separate spammers from non-spammers per inclusion
> but allow inclusion of all and thus provide authentication. You then can
> have blacklist based on the authenticated data.

Exactly my point. I didn't say a list has to include all email users, but 
all those in compliance with the rules for inclusion, spammer or not.

> Think SSL/TLS: Everyone can buy a certificate signed by a CA as long
> as the domain/server he wants to buy it for is theirs and they can
> authenticate themselves via official documents like a company register
> or something like that. This authenticates the host, but it does not
> rate him good or bad.
> However it is easier and safer for e.g. the receiver to build a blacklist
> based on this authenticated data.
> So the reputation/accreditation system should be open to everyone.

My personal opinion is that there are much lighter-weight ways to do 
authentication for this purpose, but I figure that if people are going to 
make these lists, then they should be on sound technical footing, and hard 
rules are one facets of that.

>>depends what you mean by "international".  There have been attempts to get
>>US/EU agreement on the topic, but they have failed because the US side
>>doesn't want to do anything that might actually stop the spammers from
>>spamming.  The EU seems to be quite successful in promoting bilateral
>>agreements on this topic with countries other than the US.  Agreements
>>withing the EU and bilateral agreements between the EU and other parties are
>>"international" by most definitions of the term.
> 
> *lol*
> The EU doesn't even manage to get the agreement ratified by all it's
> member countries. Sad to say that but even my government hasn't ratified
> the EU directive whose deadline has been sometime last year.
> I haven't yet seen any agreements of the EU with other non-EU countries
> regarding spam.
> And sorry, providing a link for opt-out is not a solution to spam.
> And IANAL but IMHO the demand for providing a opt-out possibility does
> not include that a spammer must honor the request.
> 
> What the governments try is to kid all joe users because the pressure
> from the indutry and their clueless marketing departments is so strong
> that they will never decide something that will cause them disprofit.
> And some companies that cry out loud and complain about spam are
> spammers themselves.
> 
> So it is better not to trust on political help to solve the problem.

Thank you Markus, you made that point much more effectively than I could.

Philip Miller

> 
> 	\Maex
> 


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



From exim@www1.ietf.org  Sun Mar 14 17:31:58 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11288
	for <asrg-archive@odin.ietf.org>; Sun, 14 Mar 2004 17:31:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2e8o-00062A-PV
	for asrg-archive@odin.ietf.org; Sun, 14 Mar 2004 17:31:30 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2EMVUUX023188
	for asrg-archive@odin.ietf.org; Sun, 14 Mar 2004 17:31:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2e8o-00061v-JJ
	for asrg-web-archive@optimus.ietf.org; Sun, 14 Mar 2004 17:31:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11284
	for <asrg-web-archive@ietf.org>; Sun, 14 Mar 2004 17:31:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2e8m-0007lt-00
	for asrg-web-archive@ietf.org; Sun, 14 Mar 2004 17:31:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B2e7k-0007f6-00
	for asrg-web-archive@ietf.org; Sun, 14 Mar 2004 17:30:24 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2e7Y-0007Yn-00
	for asrg-web-archive@ietf.org; Sun, 14 Mar 2004 17:30:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2e7P-0005qh-SF; Sun, 14 Mar 2004 17:30:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2e6i-0005og-2d
	for asrg@optimus.ietf.org; Sun, 14 Mar 2004 17:29:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11253
	for <asrg@ietf.org>; Sun, 14 Mar 2004 17:29:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2e6f-0007Xc-00
	for asrg@ietf.org; Sun, 14 Mar 2004 17:29:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B2e5g-0007Qm-00
	for asrg@ietf.org; Sun, 14 Mar 2004 17:28:16 -0500
Received: from www.somewhere.com ([66.92.72.194] helo=somewhere.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2e4j-0007JX-00
	for Asrg@ietf.org; Sun, 14 Mar 2004 17:27:17 -0500
Received: from [66.92.72.194] (account nazgul HELO [192.168.1.104])
  by somewhere.com (CommuniGate Pro SMTP 4.1.5)
  with ESMTP-TLS id 3807792; Sun, 14 Mar 2004 17:27:18 -0500
Mime-Version: 1.0
X-Sender: nazgul@somewhere.com@pop.messagefire.com
Message-Id: <p06100f38bc7a8c7eadb7@[192.168.1.104]>
In-Reply-To: 
 <8DB501AB5DDFD7119E1B00508B318AAC011AC19A@csmail2.coolsavings.com>
References: 
 <8DB501AB5DDFD7119E1B00508B318AAC011AC19A@csmail2.coolsavings.com>
To: "GroupShield for Exchange (CSMAIL2)" <postmaster@coolsavings.com>
From: Kee Hinckley <nazgul@somewhere.com>
Cc: "'Asrg@ietf.org'" <Asrg@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Subject: [Asrg] Re: ALERT -  GroupShield ticket number OB3_1079298010_CSMAIL2_1
 was g 	enerated
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/mail-archive/working-groups/asrg/>
Date: Sun, 14 Mar 2004 17:27:02 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,SUBJ_HAS_SPACES 
	autolearn=no version=2.60

At 3:00 PM -0600 3/14/04, GroupShield for Exchange (CSMAIL2) wrote:
>Action Taken:
>The message was quarantined and replaced with a text informing the recipient
>of the action taken.

I've complained to coolsavings.com several times in the past year 
about the fact that their servers perform the brilliant action of 
responding to viruses who are known forgers.  They literally have 
sent hundreds of these pieces of garbage to somewhere.com.  They've 
ignored my complaints.
-- 
Kee Hinckley
http://www.messagefire.com/         Next Generation Spam Defense
http://commons.somewhere.com/buzz/  Writings on Technology and Society

I'm not sure which upsets me more: that people are so unwilling to accept
responsibility for their own actions, or that they are so eager to regulate
everyone else's.

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



From exim@www1.ietf.org  Sun Mar 14 17:38:55 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11433
	for <asrg-archive@odin.ietf.org>; Sun, 14 Mar 2004 17:38:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2eFY-0006dP-Fs
	for asrg-archive@odin.ietf.org; Sun, 14 Mar 2004 17:38:28 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2EMcSHp025497
	for asrg-archive@odin.ietf.org; Sun, 14 Mar 2004 17:38:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2eFY-0006dA-B6
	for asrg-web-archive@optimus.ietf.org; Sun, 14 Mar 2004 17:38:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11424
	for <asrg-web-archive@ietf.org>; Sun, 14 Mar 2004 17:38:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2eFV-0000py-00
	for asrg-web-archive@ietf.org; Sun, 14 Mar 2004 17:38:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B2eEg-0000is-00
	for asrg-web-archive@ietf.org; Sun, 14 Mar 2004 17:37:34 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2eEC-0000bP-00
	for asrg-web-archive@ietf.org; Sun, 14 Mar 2004 17:37:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2eE9-0006Ah-38; Sun, 14 Mar 2004 17:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2eDV-00069e-TV
	for asrg@optimus.ietf.org; Sun, 14 Mar 2004 17:36:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11395
	for <asrg@ietf.org>; Sun, 14 Mar 2004 17:36:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2eDT-0000Yi-00
	for asrg@ietf.org; Sun, 14 Mar 2004 17:36:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B2eCX-0000RX-00
	for asrg@ietf.org; Sun, 14 Mar 2004 17:35:21 -0500
Received: from z.spamhaus.org ([67.89.105.244])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2eBb-0000DC-00
	for Asrg@ietf.org; Sun, 14 Mar 2004 17:34:23 -0500
X-Sender: matt@y.spamhaus.org (Unverified)
To: "'Asrg@ietf.org'" <Asrg@ietf.org>
From: Matt Schneider <matt@spamhaus.org>
Subject: Re: [Asrg] Re: ALERT -  GroupShield ticket number
  OB3_1079298010_CSMAIL2_1 was g 	enerated
In-Reply-To: <p06100f38bc7a8c7eadb7@[192.168.1.104]>
References: < <8DB501AB5DDFD7119E1B00508B318AAC011AC19A@csmail2.coolsavings.com>
 <8DB501AB5DDFD7119E1B00508B318AAC011AC19A@csmail2.coolsavings.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Message-Id: <20040314223353.5DE644269@z.spamhaus.org>
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/mail-archive/working-groups/asrg/>
Date: Sun, 14 Mar 2004 22:33:53 +0000 (GMT)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,SUBJ_HAS_SPACES 
	autolearn=no version=2.60

At 05:27 PM 3/14/2004 -0500, Kee Hinckley wrote:
>At 3:00 PM -0600 3/14/04, GroupShield for Exchange (CSMAIL2) wrote:
>>Action Taken:
>>The message was quarantined and replaced with a text informing the recipient
>>of the action taken.
>
>I've complained to coolsavings.com several times in the past year about 
>the fact that their servers perform the brilliant action of responding to 
>viruses who are known forgers.  They literally have sent hundreds of these 
>pieces of garbage to somewhere.com.  They've ignored my complaints.

And this is different than anyone else running GroupShield how?

I'd rather complain to them about them being spammers, instead of just 
running a broken mailserver.

- Matt


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



From exim@www1.ietf.org  Tue Mar 16 09:31:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02717
	for <asrg-archive@odin.ietf.org>; Tue, 16 Mar 2004 09:31:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3Fay-0005AM-Ks
	for asrg-archive@odin.ietf.org; Tue, 16 Mar 2004 09:31:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2GEV4NL019857
	for asrg-archive@odin.ietf.org; Tue, 16 Mar 2004 09:31:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3Fay-0005AC-De
	for asrg-web-archive@optimus.ietf.org; Tue, 16 Mar 2004 09:31:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02685
	for <asrg-web-archive@ietf.org>; Tue, 16 Mar 2004 09:31:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Faw-0000Qk-00
	for asrg-web-archive@ietf.org; Tue, 16 Mar 2004 09:31:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3FaP-0000Jb-00
	for asrg-web-archive@ietf.org; Tue, 16 Mar 2004 09:30:30 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3FZR-00008d-00
	for asrg-web-archive@ietf.org; Tue, 16 Mar 2004 09:29:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3FYz-0004oW-4K; Tue, 16 Mar 2004 09:29:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3FYk-0004mx-LE
	for asrg@optimus.ietf.org; Tue, 16 Mar 2004 09:28:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02422
	for <asrg@ietf.org>; Tue, 16 Mar 2004 09:28:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3FYj-0007np-00
	for asrg@ietf.org; Tue, 16 Mar 2004 09:28:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3FXm-0007ji-00
	for asrg@ietf.org; Tue, 16 Mar 2004 09:27:47 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3FX9-0007fg-00
	for asrg@ietf.org; Tue, 16 Mar 2004 09:27:07 -0500
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (mailer3.verisign.com [65.205.251.55])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2GER5fc013054;
        Tue, 16 Mar 2004 06:27:05 -0800 (PST)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GWHGT48W>; Tue, 16 Mar 2004 06:27:05 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A19CF@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Philip Miller'" <millenix@zemos.net>,
        Markus Stumpf
	 <maex-lists-spam-ietf-asrg@Space.Net>
Cc: Tom Thomson <tthomson@neosinteractive.com>, ASRG <asrg@ietf.org>
Subject: RE: [Asrg] 3b. SMTP Verification - Reputation/Accreditation Servi
	ces - Problem Statement
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Tue, 16 Mar 2004 06:27:00 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

> > I don't know if it is what Philip meant, but I understood 
> it that way that
> > such a system has to have hard rules and only these rules 
> decide about
> > inclusion or not. Addons like "but we may not include you 
> if we don't like
> > the name of your company, even if all the other rules are 
> fulfilled" in
> > inacceptable.
> 
> That's exactly what I meant. It was an echo of sentiments 
> expressed by others here.

This is my main complaint against some of the folk who appear
to be looking to enter this market. They seem to think that
they can run an accreditation service as if it was a blacklist.

If you allow room for discretion you are going to find that
you are forced to use it in favor of the vast majority of your
customers. Relying parties won't be able to quantify the level
of trust you are providing. The results are very bad.


> Exactly my point. I didn't say a list has to include all 
> email users, but 
> all those in compliance with the rules for inclusion, spammer or not.

There could be empirical rules for determining who is a spammer.
Sending quantities of email to honeypots would be an example.

That is an empirical rule.


> > Think SSL/TLS: Everyone can buy a certificate signed by a CA as long
> > as the domain/server he wants to buy it for is theirs and they can
> > authenticate themselves via official documents like a 
> company register
> > or something like that. This authenticates the host, but it does not
> > rate him good or bad.
> > However it is easier and safer for e.g. the receiver to 
> build a blacklist
> > based on this authenticated data.
> > So the reputation/accreditation system should be open to everyone.
> 
> My personal opinion is that there are much lighter-weight ways to do 
> authentication for this purpose, 

You don't need to have digital signatures for this purpose. You merely
need to make the cost of breaking the auth scheme higher than the benefit.

If we take the highest value spam - phishing, the payoff for a successful
message is about $2, being the black market price for a hijacked credit
card. The conversion rate for this spam is pretty high, call it 1%. That
gives a value of 2 cents/message.


Breaking a 512 bit digital signature would cost in the tens or hundreds
of thousands of dollars. It is clearly secure. But breaking the DNS
authentication mechanisms such as SPF would cost a significant amount,
I have not seen bulk cracking of DNS machines, unlike end user machines
they do not usually run other code, you can't really download a virus.

If the machine has to be bespoke hacked we are talking about a $50 hack
minimum, so you have to send 2,500 spams from that domain to recoup the 
cost. 

But if you send out a large volume of spam you will start to hit spam 
pots and the hijacked domain name's reputation will be killed.


OK the IP based authentication does not put the most technically 
sophisticated spammer with criminal connections out of business, but
it does put most of the field out of business. 2 cents is much more
than the cost of clickthroughs.

> >>depends what you mean by "international".  There have been 
> attempts to get
> >>US/EU agreement on the topic, but they have failed because 
> the US side
> >>doesn't want to do anything that might actually stop the 
> spammers from
> >>spamming.  

Thats not really the case. The EU had existing privacy legislation
for dealling with junk mail. This was extended to cover spam.

The US did not have junk mail legislation, it acted against spam
alone. As a result the can-spam act was narrowly drawn to attack
only the worst of the worst spammers.

Sure the US has to do more here, it has to write legislation to
deal with what is now the secondary problem of merely irresponsible
emailing rather than bulk sending of forged mail. But I would not
want those rules written at this time.

		Phill 

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



From exim@www1.ietf.org  Tue Mar 16 11:26:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09171
	for <asrg-archive@odin.ietf.org>; Tue, 16 Mar 2004 11:26:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3HO2-0005WN-IZ
	for asrg-archive@odin.ietf.org; Tue, 16 Mar 2004 11:25:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2GGPojR021219
	for asrg-archive@odin.ietf.org; Tue, 16 Mar 2004 11:25:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3HO1-0005WA-C8
	for asrg-web-archive@optimus.ietf.org; Tue, 16 Mar 2004 11:25:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09150
	for <asrg-web-archive@ietf.org>; Tue, 16 Mar 2004 11:25:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3HO0-0002qX-00
	for asrg-web-archive@ietf.org; Tue, 16 Mar 2004 11:25:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3HNE-0002kQ-00
	for asrg-web-archive@ietf.org; Tue, 16 Mar 2004 11:25:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3HMT-0002cX-00
	for asrg-web-archive@ietf.org; Tue, 16 Mar 2004 11:24:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3HMG-0005Ll-U6; Tue, 16 Mar 2004 11:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3HM7-0005LX-Vz
	for asrg@optimus.ietf.org; Tue, 16 Mar 2004 11:23:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08946
	for <asrg@ietf.org>; Tue, 16 Mar 2004 11:23:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3HM7-0002ZJ-00
	for asrg@ietf.org; Tue, 16 Mar 2004 11:23:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3HL8-0002S8-00
	for asrg@ietf.org; Tue, 16 Mar 2004 11:22:51 -0500
Received: from host217-35-105-169.in-addr.btopenworld.com ([217.35.105.169] helo=mail.neosinteractive.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3HKJ-0002Mi-00
	for asrg@ietf.org; Tue, 16 Mar 2004 11:21:59 -0500
Received: from tthomson ([217.35.105.173] unverified) by mail.neosinteractive.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Tue, 16 Mar 2004 15:27:09 +0000
From: "Tom Thomson" <tthomson@neosinteractive.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>,
        "'Philip Miller'" <millenix@zemos.net>,
        "Markus Stumpf" <maex-lists-spam-ietf-asrg@Space.Net>
Cc: "ASRG" <asrg@ietf.org>
Subject: RE: [Asrg] 3b. SMTP Verification - Reputation/Accreditation Services - Problem Statement
Message-ID: <IOEPKAPPDKHPENCKFNNGMEEMDCAA.tthomson@neosinteractive.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A19CF@mou1wnexm05.vcorp.ad.vrsn.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-OriginalArrivalTime: 16 Mar 2004 15:27:09.0500 (UTC) FILETIME=[25B14FC0:01C40B6B]
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/mail-archive/working-groups/asrg/>
Date: Tue, 16 Mar 2004 16:21:54 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Hallam-Baker, Phillip [mailto:pbaker@verisign.com] wrote:
> >>depends what you mean by "international".  There have been
> attempts to get
> >>US/EU agreement on the topic, but they have failed because
> the US side
> >>doesn't want to do anything that might actually stop the
> spammers from
> >>spamming.

> Thats not really the case. The EU had existing privacy legislation
> for dealling with junk mail. This was extended to cover spam.
>
> The US did not have junk mail legislation, it acted against spam
> alone. As a result the can-spam act was narrowly drawn to attack
> only the worst of the worst spammers.

Not quite right.  The junk mail stuff is about opt-out, but the anti-spam
stuff requires opt-in - so it isn't s a simple extension of the junk mail
stuff.



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



From exim@www1.ietf.org  Tue Mar 16 21:52:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14541
	for <asrg-archive@odin.ietf.org>; Tue, 16 Mar 2004 21:52:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3R9e-0007PJ-U2
	for asrg-archive@odin.ietf.org; Tue, 16 Mar 2004 21:51:39 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2H2pZGY028462
	for asrg-archive@odin.ietf.org; Tue, 16 Mar 2004 21:51:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3R9Y-0007Ov-Qj
	for asrg-web-archive@optimus.ietf.org; Tue, 16 Mar 2004 21:51:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14484
	for <asrg-web-archive@ietf.org>; Tue, 16 Mar 2004 21:51:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3R9R-00029W-00
	for asrg-web-archive@ietf.org; Tue, 16 Mar 2004 21:51:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3R8h-00021j-00
	for asrg-web-archive@ietf.org; Tue, 16 Mar 2004 21:50:40 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3R7h-0001uE-00
	for asrg-web-archive@ietf.org; Tue, 16 Mar 2004 21:49:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3R77-000798-Dw; Tue, 16 Mar 2004 21:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3R6Y-000770-80
	for asrg@optimus.ietf.org; Tue, 16 Mar 2004 21:48:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA14334
	for <asrg@ietf.org>; Tue, 16 Mar 2004 21:48:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3R6V-0001nQ-00
	for asrg@ietf.org; Tue, 16 Mar 2004 21:48:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3R5z-0001gy-00
	for asrg@ietf.org; Tue, 16 Mar 2004 21:47:51 -0500
Received: from bsdsgr04.sagres.com.br ([200.140.134.134])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3R4Y-0001V4-00
	for asrg@ietf.org; Tue, 16 Mar 2004 21:46:23 -0500
Received: from ntsgr07.sagres.com.br (NTsgr07.sagres.com.br [10.0.17.7])
	by BSDsgr04.sagres.com.br (8.12.10/8.12.10) with ESMTP id i2H2jtGq031382
	for <asrg@ietf.org>; Wed, 17 Mar 2004 02:45:56 GMT
	(envelope-from saurwein@uniwares.com)
Received: from leonone.uniwares.com ([200.101.110.127])
          by ntsgr07.sagres.com.br (Lotus Domino Release 5.0.12)
          with ESMTP id 2004031623543098:8201 ;
          Tue, 16 Mar 2004 23:54:30 -0300 
Message-Id: <6.0.3.0.0.20040316233552.01cd7740@mail.uniwares.com>
X-Sender: saurwein.uniwares@mail.uniwares.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
To: asrg@ietf.org
From: Andreas Saurwein <saurwein@uniwares.com>
Mime-Version: 1.0
X-MIMETrack: Itemize by SMTP Server on ntsgr07/SAGRES(Release 5.0.12  |February 13, 2003) at
 03/16/2004 11:54:32 PM,
	Serialize by Router on ntsgr07/SAGRES(Release 5.0.12  |February 13, 2003) at
 03/16/2004 11:54:33 PM,
	Serialize complete at 03/16/2004 11:54:33 PM
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Asrg] 1a. Inventory of Problems - new spam channels
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/mail-archive/working-groups/asrg/>
Date: Tue, 16 Mar 2004 23:45:29 -0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL autolearn=no version=2.60

Recent discussion about the ability of modern games, raised the question 
about using online game networks for spamming.
Current game technology allows for tight integration of voice chat, text 
chat, server redirections, web links and more. They allow for full 
scripting, mod creation, custom content, etc.
I believe it is only a matter of a few month until we see serious spam in 
online games. Most games have, as far as I can see, no protection against 
this type of misuse.
Games like the Unreal series on the PC, Mac and Linux, allow for cheap 
server creation - even without the need to own the game (as if this would 
be a problem) - and hosting of custom content.
Given the number of people playing games online, this might in a year or 
two reach critical saturation.
It is probably time to start building up guidelines and BCPs for game 
developers too.

Andreas


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



From exim@www1.ietf.org  Wed Mar 17 04:53:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28169
	for <asrg-archive@odin.ietf.org>; Wed, 17 Mar 2004 04:53:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3Xjp-00050c-Ub
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 04:53:26 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2H9rPE9019250
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 04:53:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3Xjn-00050P-8J
	for asrg-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 04:53:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28154
	for <asrg-web-archive@ietf.org>; Wed, 17 Mar 2004 04:53:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Xjj-0002kx-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 04:53:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3Xin-0002eq-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 04:52:22 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Xhr-0002Z1-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 04:51:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3XhZ-0004oG-Jg; Wed, 17 Mar 2004 04:51:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3Xgz-0004mV-Ay
	for asrg@optimus.ietf.org; Wed, 17 Mar 2004 04:50:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA28090
	for <asrg@ietf.org>; Wed, 17 Mar 2004 04:50:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Xgm-0002Rl-00
	for asrg@ietf.org; Wed, 17 Mar 2004 04:50:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3Xfq-0002Lg-00
	for asrg@ietf.org; Wed, 17 Mar 2004 04:49:19 -0500
Received: from adsl-64-165-36-235.dsl.snfc21.pacbell.net ([64.165.36.235] helo=shedevil.annepmitchell.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3Xf1-0002GO-00
	for asrg@ietf.org; Wed, 17 Mar 2004 04:48:27 -0500
Received: from [192.168.0.247] ([192.168.0.247])
	by shedevil.annepmitchell.com (8.11.6/8.11.4) with ESMTP id i2H9mSX24994
	for <asrg@ietf.org>; Wed, 17 Mar 2004 01:48:28 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Transfer-Encoding: 7bit
Message-Id: <3DC625B6-77F8-11D8-AD47-000A95AC5778@isipp.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: asrg@ietf.org
From: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
X-Mailer: Apple Mail (2.612)
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Update on Querying IADB
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 01:48:27 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

For those interested in seeing how this has evolved, and what exactly 
this particular accreditation database provides, our query pages have 
been expanded, and include a link to the full suggested DNSL data 
response codes.

The codes we use at present include:

127.0.0.1 		 Listed in IADB
127.0.1.255 		 Vouched listing
127.2.255.1 		 Publishes SPF record
127.2.255.2 		 Publishes Microsoft "Caller I.D. for Email" record
127.2.255.101	 Participates in Habeas program
127.2.255.102	 Participates in Ironport's Bonded Sender program
127.3.100.0		 Has absolutely no mailing controls in place
127.3.100.1		 Scrapes addresses, pure opt-out only
127.3.100.2		 Accepts unverified sign-ups such as through web page
127.3.100.3		 Accepts unverified sign-ups, gives chance to opt out
127.3.100.4		 Reserved
127.3.100.5		 Has opt-in confirmation mechanism
127.3.100.6		 Has and uses opt-in confirmation mechanism
127.3.100.7		 Reserved
127.3.100.8		 Reserved
127.3.100.9		 Reserved
127.3.100.10		 All mailing list mail is confirmed opt-in

The general information is at http://www.isipp.com/iadb.php
Query information specifically is at http://www.isipp.com/iadbquery.php

It is, of course, free to query IADB, as well as to be listed as an 
individual.

Anne


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



From exim@www1.ietf.org  Wed Mar 17 10:29:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11884
	for <asrg-archive@odin.ietf.org>; Wed, 17 Mar 2004 10:29:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3cyD-0006pM-Ok
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 10:28:37 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HFSbpQ026241
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 10:28:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3cyC-0006p9-EU
	for asrg-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 10:28:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11834
	for <asrg-web-archive@ietf.org>; Wed, 17 Mar 2004 10:28:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3cyA-0003HI-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 10:28:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3cxJ-0003AV-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 10:27:43 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3cwO-00033K-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 10:26:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3cvj-0006cK-BG; Wed, 17 Mar 2004 10:26:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3cvE-0006ag-88
	for asrg@optimus.ietf.org; Wed, 17 Mar 2004 10:25:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11686
	for <asrg@ietf.org>; Wed, 17 Mar 2004 10:25:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3cvB-0002uY-00
	for asrg@ietf.org; Wed, 17 Mar 2004 10:25:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3cuG-0002oQ-00
	for asrg@ietf.org; Wed, 17 Mar 2004 10:24:35 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3ctO-0002if-00
	for asrg@ietf.org; Wed, 17 Mar 2004 10:23:38 -0500
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (mailer3.verisign.com [65.205.251.55])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2HFNbCs023432
        for <asrg@ietf.org>; Wed, 17 Mar 2004 07:23:37 -0800 (PST)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <HCHA0HQK>; Wed, 17 Mar 2004 07:23:37 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A19E4@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: asrg@ietf.org
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C40C33.CE6B24FC"
Subject: [Asrg] Accreditation Mechanism Proposal
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 07:23:32 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C40C33.CE6B24FC
Content-Type: text/plain;
	charset="iso-8859-1"

All,

	A proposal for an accreditation mechanism is attached. This proposal
is based on the earlier RBL scheme proposed by Vixie, and designed to be
compatible with CallerID. I will submit as an ID later on today.

	Basically the scheme returns an A record in response to a lookup. So
in order for example.com to announce that it is accredited by the class3
service of verisign the SPF or CallerID record would contain the tripple:

	"accreditation" "class3.verisign.com""DNS-A"

	I.e. this is an accreditation property, the accreditor service is at
class3.verisign.com, the protocol is a DNS A record lookup.

	We can conflate the "accreditation" and "DNS-A" components, but that
is a bad idea, the A record convention is pretty limiting, there are only 24
bits worth of data that can be returned. It would be useful to be able to
extend to use of other protocol records such as NAPTR and SRV.

	Some folk inside VeriSign suggested that we use the convention that
an unlisted domain just returns domain does not exist. 


	I believe that we should have some facility here for a description
of the accreditation service. This is because the receiver has to arrive at
an evaluation of the accreditation service before the information can
converge. The ability to use learning systems is very attractive here.
Telling the learning system basic information about the format of the data
is pretty useful, what is the basis that the info was collected on, is the
data bit field formatted or in some other form?

	I provide the start of a description language here but on second
thoughts the best approach here would be to write the data structure in XML,
stick it up on a web site and put the URL in the DNS. The format is not a
big priority for me at the moment since it only really affects the
accreditation services and the filter writers. I don't think that either
community will be particularly large (10 to 20 at most). It is not something
we need to make a priority when we are using our limited standards track
bandwidth.

	
			Phill


------_=_NextPart_000_01C40C33.CE6B24FC
Content-Type: text/plain;
	name="accreditation.txt"
Content-Disposition: attachment;
	filename="accreditation.txt"
Content-Transfer-Encoding: quoted-printable


          ASRG Working Group                                            =
      =20
          Internet Draft                                       P. =
Hallam-Baker=20
          Document: draft-spf-accreditation-00.txt               =
VeriSign Inc.=20
          Expires: September 2004                                   =
March 2004=20
          =20
          =20
                          DNS Publication Accreditation Data=20
          =20
          =20
       Status of this Memo=20
          =20
          This document is an Internet-Draft and is NOT offered in =
accordance=20
          with Section 10 of RFC2026, and the author does not provide =
the=20
          IETF with any rights other than to publish as an =
Internet-Draft =20
       =20
          Internet-Drafts are working documents of the Internet =
Engineering=20
          Task Force (IETF), its areas, and its working groups.  Note =
that     =20
          other groups may also distribute working documents as =
Internet-
          Drafts.=20
          =20
          Internet-Drafts are draft documents valid for a maximum of =
six=20
          months and may be updated, replaced, or obsoleted by other=20
          documents at any time.  It is inappropriate to use =
Internet-Drafts=20
          as reference material or to cite them other than as "work in=20
          progress."=20
          =20
          The list of current Internet-Drafts can be accessed at=20
               http://www.ietf.org/ietf/1id-abstracts.txt=20
          The list of Internet-Draft Shadow Directories can be accessed =
at=20
               http://www.ietf.org/shadow.html.=20
          =20
       Abstract=20
          =20
          This document describes a mechanism that may be used to =
publish=20
          accreditation data associated with email senders =
authenticated by=20
          means of SPF or CallerID.=20
          =20
          An accreditation is a description by a third party that =
describes=20
          an email sender in some way that helps the recipient estimate =
the=20
          likelihood that a message authenticated as being originated =
by the=20
          sender is spam. =20
       =20
       Conventions used in this document=20
          =20
          The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL =
NOT",=20
          "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" =
in=20
          this document are to be interpreted as described in RFC-2119 =
[1].=20
          =20

       =20
       =20
       Hallam-Baker           Expires - September 2004               =
[Page 1]=20
       =20
=0C                       DNS Publication of Accreditation Data      =
March 2004=20
       =20
       =20
       Table of Contents=20
          =20
          1. =
Introduction...................................................2=20
             1.1 Accreditation =
Authorities..................................2=20
             1.2 Accreditation =
Statements...................................4=20
             1.3 Publication of Accreditation =
Statements....................4=20
             1.4 Interpretation of Accreditation =
Statements.................5=20
          2. DNS Publication of Accreditation =
Statements....................5=20
             2.1 Accreditation Authority Description TXT =
Record.............7=20
             2.2 Sender Recipient A =
Record..................................8=20
             2.3 Sender Recipient TXT =
Record................................8=20
          3. Filter Interpretation =
Guidelines...............................8=20
             3.1 Establishing Provider =
Reputation...........................9=20
             3.2 Combining =
Accreditations...................................9=20
          4. Security =
Considerations........................................9=20
             4.1 Unauthenticated or Wrongly Authenticated =
Sender............9=20
             4.2 Untrustworthy Accreditation =
Provider......................10=20
             4.3 DNS Security =
Issues.......................................10=20
          =
References.......................................................10=20
          =
Acknowledgments..................................................11=20
          Author's =
Addresses...............................................11=20
          =20
       1. Introduction=20
       =20
          This specification describes a mechanism that may be used to=20
          publish accreditation data associated with email senders=20
          authenticated by means of SPF [2] or CallerID [3].=20
          =20
          An accreditation is a statement by a third party that the =
recipient=20
          of an email may use to estimate the probability that the =
sender is=20
          a spammer.=20
          =20
          The architecture of this proposal generalizes existing =
industry=20
          practice with respect to publication of DNS blacklists =
according to=20
          the method proposed by Vixie [4]. =20
          =20
          Unlike the earlier proposal the mechanism described in this=20
          document MAY be used by accreditation agencies that only =
report=20
          accreditation data for some email senders without unnecessary =

          queries for parties that are not covered. It is thus better =
suited=20
          to applications where the accreditation authority is =
reporting=20
          positive accreditation data concerning a small group of =
trusted=20
          senders.=20
       =20
       1.1 Accreditation Authorities=20
          =20


       =20
       =20
       Hallam-Baker           Expires - September 2004               =
[Page 2]=20
       =20
=0C                       DNS Publication of Accreditation Data      =
March 2004=20
       =20
       =20
          An Accreditation Authority is a third party that is =
responsible for=20
          making statements that describe email senders. =20
          =20
          Accreditation Authorities MAY be restricted or unrestricted. =
A=20
          restricted accreditation authority only publishes statements =
that=20
          relate to a restricted number of email senders. An =
unrestricted=20
          accreditation authority publishes statements for all email =
senders.=20
          =20
          An accreditation authority may take additional measures to =
improve=20
          the value of their accreditation, for example bringing civil =
suits=20
          against parties that breach the undertakings given.=20
       =20
       1.2 Accountability of Accreditation Authorities=20
       =20
          Experience of anti-spam blacklists has shown that those who =
attempt=20
          to provide accountability must in turn be accountable.=20
          =20
          There is no difficulty in ensuring that accreditation =
providers are=20
          accountable to email recipients. An accreditation authority =
that=20
          provides incorrect accreditation will soon be ignored. The =
value of=20
          an accreditation may be measured empirically by measuring the =

          proportion of the message sent bearing a particular =
accreditation=20
          that are determined to be spam (e.g. through user reports).=20
          =20
          If the ability to measure the value of an accreditation =
agency is=20
          to be of use to the recipient it must be possible for new=20
          accreditation providers to offer their services without =
artificial=20
          barriers to entry such as magic lists of =91approved=92 =
providers.=20
          =20
          One way to avoid this problem is to allow email senders to =
specify=20
          the accreditation providers they favor. Although it is =
unlikely=20
          that any individual would specify an accreditation provider =
that=20
          gave them a bad rating, an accreditation service that had=20
          established a sufficiently high reputation on the basis of =
its=20
          positive accreditations could offer to supply negative =
ratings.=20
          =20
          This mechanism offers substantial advantages over the current =

          situation in which maintainers of anti-spam blacklists are=20
          effectively unaccountable to any party. Accreditation =
services are=20
          held accountable to both senders and receivers.  =20
          =20
       1.3 Practices Considerations=20
           
          As a trusted third party the actions of an Accreditation =
Authority=20
          are raise numerous legal issues. These issues are outside the =
scope=20
          of this document. =20
          =20

       =20
       =20
       Hallam-Baker           Expires - September 2004               =
[Page 3]=20
       =20
=0C                       DNS Publication of Accreditation Data      =
March 2004=20
       =20
       =20
       1.4 Accreditation Statements=20
          =20
          At present a large number of different parties act as =
Accreditation=20
          Authorities with respect to sending of email. Blacklists =
attempt to=20
          identify bad faith actors while whitelists look to identify =
good=20
          faith actors. Whitelist accreditations may involve a simple =
promise=20
          not to spam or a promise that is backed up by some form of =
penalty=20
          such as the forfeiture of a bond or the publication of =
negative=20
          reputation data.=20
          =20
          Despite the wide variety in the types of data Accreditation=20
          Authorities provide the inferences that anti-spam filtering=20
          techniques attempt to draw are the same, is a particular item =
of=20
          email likely or unlikely to be spam. For this reason we leave =
the=20
          details of the accreditation mechanism to the Accreditation=20
          Authority.=20
          =20
          An accreditation authority MAY publish any form of =
accreditation=20
          statement they choose. The following types of statement are =
likely=20
          to be of greatest utility.=20
       =20
       Identity Accreditation=20
       =20
          The email sender has provided a real world identity and a =
physical=20
          address at which legal process can be served and this =
information=20
          has been authenticated by means of some trustworthy process.=20
       =20
       Undertaking Accreditation=20
       =20
          In addition to meeting the identity accreditation =
requirements, the=20
          email sender has undertaken to comply with a specified email=20
          sending policy.=20
       =20
       Performance Accreditation=20
       =20
          The email sender has been determined to have met the =
requirements=20
          of an email sending policy. If the email sender has =
previously=20
          undertaken to comply with the email sending policy in =
question the=20
          accreditation is a Compliance Accreditation.=20
       =20
       1.5 Notification of Accreditation Existence=20
          =20
          A sender MAY notify recipients of the existence of an =
accreditation=20
          statement by means of a policy notification mechanism such as =

          CallerID or SPF.=20
          =20
          The use of the policy notification mechanism allows senders =
to=20
          bring the existence of a new accreditation mechanism to the=20
       =20
       =20
       Hallam-Baker           Expires - September 2004               =
[Page 4]=20
       =20
=0C                       DNS Publication of Accreditation Data      =
March 2004=20
       =20
       =20
          attention of an adaptive filtering mechanism. Such a filter =
would=20
          determine the reputation of an accreditation agency =
empirically by=20
          measuring the accuracy with which the agency categorizes =
senders.=20
          =20
          Senders are unlikely to advertise the existence of =
unfavorable=20
          accreditation statements unless they believe that there is a =
high=20
          probability that the recipient will not verify the statement. =

          =20
          Accreditation authorities that publish unfavorable data =
concerning=20
          a subject need to inform recipients that the accreditation =
service=20
          is 'open' and MAY be consulted to obtain information even if =
the=20
          sender does not list the service as an accreditor. This =
information=20
          SHOULD be provided by means of an Accreditation Authority=20
          Description record.=20
          =20
       1.6 Publication of Accreditation Statements=20
          =20
          Accreditation statements are published by means of an =
extension of=20
          the existing mechanism used for publication of anti-spam =
blacklists=20
          via DNS.=20
          =20
          An accreditation statement is published by means of the DNS A =

          record. To avoid collisions with other uses of the DNS =
addresses in=20
          the 127.x.x.x loopback address range are used.=20
       =20
       1.7 Accreditation Authority Description Data=20
          =20
          The domain prefix specified for an accreditation service MAY=20
          contain a record that describes the use of the particular=20
          accreditation service with the key _accredit.=20
          =20
       1.8 Interpretation of Accreditation Statements=20
          =20
          Email recipients MAY interpret Accreditation Statements in =
any=20
          fashion they choose, including regarding an Accreditation =
Statement=20
          as a negative indicator.=20
          =20
          The reputation of the Accreditation Authority MUST be =
considered=20
          suspect until proven reliable.=20
       =20
       2. Policy Notification Bindings=20
          =20
          Policy notification bindings are specified for SPF and =
CallerID.=20
          Other notification bindings MAY be specified in the =
specification=20
          document describing the policy notification mechanism where =
they=20
          are to be used.=20


       =20
       =20
       Hallam-Baker           Expires - September 2004               =
[Page 5]=20
       =20
=0C                       DNS Publication of Accreditation Data      =
March 2004=20
       =20
       =20
          Note that the policy bindings are not exclusive. A sender MAY =
use=20
          both the SPF and CallerID methods of specifying the email =
policy.=20
          =20
       2.1 SPF=20
          =20
          A sender MAY use the SPF modifier 'accredit' to notify =
recipients=20
          of the existence of an accreditation record concerning the =
sender=20
          domain.=20
          =20
             accredit =3D <domain>=20
          =20
          The value <domain> specifies the location of the =
accreditation=20
          service. =20
          =20
          If the value of <domain> is 'accredit.test' and the sender =
domain=20
          is 'example.com':=20
          =20
             The accreditation authority description record for the =
domain=20
             will be the TXT record associated with the DNS label=20
             accredit.test.=20
             =20
             The sender recipient record for the domain 'example.com' =
will be=20
             associated with the DNS label=20
             example.com._accredit.accredit.test.=20
          =20
          A sender MAY specify multiple accreditation records. =20
          =20
       2.2 CallerID=20
          =20
          A sender MAY use the =91Per domain indication of email =
transmission=20
          policy=92 specified in the CSRI architecture [5]. The =
accreditation=20
          domain is specified by means of the <cdr> element as =
specified in=20
          that document. The equivalent code for the SPF example above =
would=20
          be:=20
          =20
       <ep xmlns=3D'http://ms.net/1'>=20
          <out>=20
             <cdl>accredit.test</cdl>=20
          </out>=20
       </ep>=20
       =20
       3. DNS Publication of Accreditation Statements=20
       =20
       The DNS is used to publish two types of accreditation =
information:=20
       =20
            1. Information that describes how accreditation records MAY =
be=20
               interpreted.=20
       =20
       =20
       Hallam-Baker           Expires - September 2004               =
[Page 6]=20
       =20
=0C                       DNS Publication of Accreditation Data      =
March 2004=20
       =20
       =20
            2. Accreditation records that describe the accreditation =
status=20
               of specific domains.=20
       =20
       The accreditation statements will in most cases be interpreted =
by an=20
       email filtering system that estimates the likelihood that the =
email=20
       message is wanted by combining information from a large number =
of=20
       sources.=20
       =20
       3.1 Accreditation Authority Description TXT Record=20
          =20
       The accreditation authority description record provides such a =
filter=20
       with hints that help an email filtering system interpret the=20
       accreditation information. Such a filter can never be required =
to=20
       interpret any piece of data in a particular fashion since the =
data may=20
       be provided by an untrustworthy or even a malicious source.=20
       =20
       Knowing the type of information that an accreditation record =
expresses=20
       is useful when attempting to compare the information provided by =
one=20
       accreditation source with information from other sources.=20
       Accreditation sources that claim to provide the same type of=20
       information should show a high degree of correlation in the=20
       information they provide.=20
       =20
             type:{ identity | undertaking | performance }=20
                 The type of accreditation provided as described in the =

                 introduction.=20
             =20
             open:<boolean>=20
                 If true the accreditation service is open and MAY be=20
                 consulted to obtain information even if the sender =
does not=20
                 list the service as an accreditor.=20
             =20
             protocol: {dns-a | dns-txt | other }=20
                 The protocol by which the accreditation may be =
retrieved.=20
                 The keyword dns-a specifies that the accreditation =
record is=20
                 encoded as a DNS A record. The keyword dns-txt =
specifies=20
                 that the accreditation record is encoded as a DNS TXT=20
                 record.=20
             =20
             length:<integer>=20
                 The number of bits in the record value that have=20
                 significance. =20
             =20


       =20
       =20
       Hallam-Baker           Expires - September 2004               =
[Page 7]=20
       =20
=0C                       DNS Publication of Accreditation Data      =
March 2004=20
       =20
       =20
             scale: {log2 | log10 | linear | none}=20
                 The scale to be applied when comparing the =
corresponding=20
                 record values.=20
       =20
       3.2 Sender Recipient A Record=20
          =20
          The data in the A record is interpreted using direction =
provided by=20
          the accreditation authority description TXT record. =20
          =20
          The A record data field consists of four bytes. The existing=20
          convention established by real-time DNS blacklist schemes =
requires=20
          that the most significant byte of the address be 127 to =
indicate=20
          the host loop-back address and that the least significant bit =
of=20
          the address indicate the presence or absence of a party from =
a=20
          blacklist.=20
          =20
            Bits 24-31=20
              Authority SHOULD set these bits to the value 127. Relying =

              parties MUST ignore.=20
            =20
            Bits 8-23=20
              These bits are used to encode the scale value=20
            =20
            Bits 4-7=20
              These bits are reserved. Relying parties MUST ignore=20
            =20
            Bits 0-3=20
              If the subject is accredited these bits are set to the =
value=20
              10. If the subject is not accredited these bits are set =
to the=20
              value 15.=20
       =20
       This convention is broadly compatible with existing conventions, =

       including those specified in the CSRI and SPF specifications.=20
          =20
       3.3 Other Sender Recipient Records=20
          =20
          Additional information MAY be provided by means of other DNS=20
          records, for example TXT or NAPTR records. A Certificate =
Authority=20
          that has issued digital certificate(s) corresponding to an=20
          accreditation MAY publish links to the certificate in the=20
          accreditation record.=20
          =20
       4. Filter Interpretation Guidelines=20
          =20
          An email filter MAY make any use it chooses of information=20
          provided. Accreditation information may come from an =
untrustworthy=20
          or even outright malicious source. The fact that an email =
sender is=20
       =20
       =20
       Hallam-Baker           Expires - September 2004               =
[Page 8]=20
       =20
=0C                       DNS Publication of Accreditation Data      =
March 2004=20
       =20
       =20
          accredited by such a source MAY be considered a negative =
judgment=20
          on the reputation of the source.=20
       =20
       4.1 Establishing Provider Reputation=20
          =20
          It is suggested that email filters SHOULD determine =
weightings to=20
          assign to accreditation notices from particular Accreditation =

          Authorities by means of empirical measurement of their=20
          effectiveness rather than fixed a-priori values. If fixed=20
          weightings are assigned it SHOULD be possible to override =
these=20
          values.=20
          =20
          For example an email recipient receiving a large quantity of =
email=20
          might perform an analysis of the accuracy of various =
Accreditation=20
          Authorities on a statistically significant sample of that =
email.=20
          =20
          Recipients of smaller quantities of email might rely on third =
party=20
          assessments of the accuracy of Accreditation Authorities or =
on=20
          feedback from end-users identifying messages that have been =
wrongly=20
          categorized.=20
       =20
       4.2 Combining Accreditations=20
          =20
          When combining Accreditations from different Accreditation=20
          Providers filters MAY use the information provided in the=20
          Accreditation Authority Description record to determine =
whether the=20
          information provided is likely to have dependencies or not.=20
          =20
          For example an email sender that is accredited by two =
different=20
          Accreditation Authorities that verify identity information is =
not=20
          likely to be significantly less likely to be a spammer than =
an=20
          email sender that is only accredited by one Accreditation=20
          Authority. But an Email sender that is accredited by one=20
          Accreditation Authority that verifies identity information =
and=20
          another that monitors complaints from end users is less =
likely to=20
          be a spammer than a sender with only one of the =
accreditations.=20
       =20
       5. Security Considerations=20
       =20
       5.1 Unauthenticated or Wrongly Authenticated Sender=20
          =20
          A positive accreditation has no value if someone other than =
the=20
          accreditation subject can make use of it. It is therefore =
essential=20
          for the sender of an email to be accredited before a positive =

          weight is given to an accreditation value.=20
       =20


       =20
       =20
       Hallam-Baker           Expires - September 2004               =
[Page 9]=20
       =20
=0C                       DNS Publication of Accreditation Data      =
March 2004=20
       =20
       =20
       5.2 Untrustworthy Accreditation Provider=20
          =20
          An Accreditation Authority may be untrustworthy for many =
reasons,=20
          they may perform their activities in a negligent fashion or =
with=20
          actual malice.=20
          =20
          For example a spammer might run an unrestricted accreditation =

          service that accurately listed all his rivals as spammers but =
did=20
          not list the spammer who operated the service. Alternatively =
an=20
          Accreditation service may maliciously publish a negative =
reputation=20
          about a subject.=20
          =20
          For this reason email filters MUST evaluate the reputation of =
the=20
          Accreditation Authority as well as the data provided by that=20
          authority. =20
          =20
          The number of email senders that reference accreditation =
records=20
          published by an Accreditation Authority MAY provide an =
indication=20
          of the relative trustworthiness of that provider.=20
       =20
       5.3 DNS Security Issues=20
          =20
          The DNS protocol does not provide cryptographic assurance of =
the=20
          integrity of the information published and is vulnerable to =
Denial=20
          of Service attacks.=20
          =20
          These weaknesses do not seriously affect the security of the=20
          accreditation mechanism when used for the purpose of spam =
reduction=20
          but may affect the security of the mechanism if it is applied =
to=20
          other purposes.=20
       =20
       References=20
       =20
                           =20
          1     Bradner, S., "Key words for use in RFCs to Indicate=20
             Requirement Levels", BCP 14, RFC 2119, March 1997=20
          =20
          2  Meng Weng Wong, et. al., "Sender Policy Framework (SPF)",=20
             Internet draft, February 2004, http://spf.pobox.com/draft-
             mengwong-spf-00.txt =20
          =20
          3  Microsoft Corp., "Caller ID for E-Mail Technical =
Specification",=20
             =
http://www.microsoft.com/mscorp/twc/privacy/spam_callerid.mspx =20
          =20
          4  Paul Vixie, Proposal to IETF ASRG working group.=20
             http://www1.ietf.org/mail-archive/working-
             groups/asrg/current/msg04508.html =20

       =20
       =20
       Hallam-Baker           Expires - September 2004              =
[Page 10]=20
       =20
=0C                       DNS Publication of Accreditation Data      =
March 2004=20
       =20
       =20
                                                                        =
     =20
          =20
          5 Microsoft Corp. "Coordinated Spam Reduction Initiative", =
February=20
             2004, =
http://download.microsoft.com/download/7/6/b/76b1a9e6-
             e240-4678-bcc7-fa2d4c1142ea/csri.pdf =20
       =20
       Acknowledgments=20
       =20
       The author acknowledges the contributions made to this proposal =
by=20
       Jeff Burstein and Nico Popp of VeriSign, Meng Weng Wong of =
PoBox.com=20
       and Bob Atkinson of Microsoft.=20
       =20
       Author's Addresses=20
       =20
       Phillip Hallam-Baker=20
       VeriSign Inc.=20
       Email: pbaker@verisign.com=20
              =20





























       =20
       =20
       Hallam-Baker           Expires - September 2004              =
[Page 11]=20
       =20
=0C
------_=_NextPart_000_01C40C33.CE6B24FC--

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



From exim@www1.ietf.org  Wed Mar 17 12:17:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22929
	for <asrg-archive@odin.ietf.org>; Wed, 17 Mar 2004 12:17:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3eek-0007r3-Du
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 12:16:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HHGcoo030190
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 12:16:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3eej-0007qZ-EB
	for asrg-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 12:16:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22902
	for <asrg-web-archive@ietf.org>; Wed, 17 Mar 2004 12:16:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3eeh-0007F9-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 12:16:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3ed1-00072K-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 12:14:52 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3ecZ-0006uF-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 12:14:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3ecD-0007kM-7F; Wed, 17 Mar 2004 12:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3ec7-0007k2-LS
	for asrg@optimus.ietf.org; Wed, 17 Mar 2004 12:13:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22784
	for <asrg@ietf.org>; Wed, 17 Mar 2004 12:13:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3ec6-0006tl-00
	for asrg@ietf.org; Wed, 17 Mar 2004 12:13:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3ebC-0006l7-00
	for asrg@ietf.org; Wed, 17 Mar 2004 12:12:59 -0500
Received: from ns2.ohmi.org ([216.187.106.200] helo=ohmi.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3eag-0006aM-00
	for asrg@ietf.org; Wed, 17 Mar 2004 12:12:26 -0500
Received: from smart (smart.ohmi.org [192.168.1.151])
	by ohmi.org (8.11.6/8.11.6) with ESMTP id i2HHBtb02033
	for <asrg@ietf.org>; Wed, 17 Mar 2004 12:11:55 -0500
From: "Radu Hociung" <radu.asrg@ohmi.org>
To: <asrg@ietf.org>
Message-ID: <002801c40c42$f27b2cb0$9701a8c0@smart>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Content-Transfer-Encoding: quoted-printable
Subject: [Asrg] asrg-cri - spam to mailing lists ?
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 12:11:54 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hello all,

I've been following the group for a while, and I can't find the answer =
I'm
looking for:

1. About the challenge-response draft document: Are your intentions to =
make
it into an RFC? Is it a possibilty that it can/will become a mainstream
standard?

2. About the contents: If a spammer would add headers to his message to
make it look like a mailing list, this message would then not be subject =
to
the other provisions of the draft? Is there a separate draft/RFC to deal
with the mailing list/CR combination, or do you intend to address this =
in
some way?

Thank you in advance.
Radu.
--
Radu Hociung                                                 =
radu@ohmi.org
=20



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



From exim@www1.ietf.org  Wed Mar 17 12:31:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24196
	for <asrg-archive@odin.ietf.org>; Wed, 17 Mar 2004 12:31:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3esI-0001Wd-MK
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 12:30:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HHUcLn005857
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 12:30:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3esI-0001WO-Gl
	for asrg-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 12:30:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24137
	for <asrg-web-archive@ietf.org>; Wed, 17 Mar 2004 12:30:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3esH-0001pJ-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 12:30:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3erH-0001bc-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 12:29:36 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3epy-0001IS-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 12:28:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3epm-000134-8C; Wed, 17 Mar 2004 12:28:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3emT-0000X1-CT
	for asrg@optimus.ietf.org; Wed, 17 Mar 2004 12:24:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23423
	for <asrg@ietf.org>; Wed, 17 Mar 2004 12:24:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3emR-0000bQ-00
	for asrg@ietf.org; Wed, 17 Mar 2004 12:24:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3elY-0000TD-00
	for asrg@ietf.org; Wed, 17 Mar 2004 12:23:41 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3ekd-0000Lp-00
	for asrg@ietf.org; Wed, 17 Mar 2004 12:22:43 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B3ekc-0000l8-00; Wed, 17 Mar 2004 12:22:42 -0500
Received: from [68.244.169.73] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B3ekb-00056w-00; Wed, 17 Mar 2004 12:22:42 -0500
Message-ID: <40588953.6070503@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Radu Hociung <radu.asrg@ohmi.org>
CC: asrg@ietf.org
Subject: Re: [Asrg] asrg-cri - spam to mailing lists ?
References: <002801c40c42$f27b2cb0$9701a8c0@smart>
In-Reply-To: <002801c40c42$f27b2cb0$9701a8c0@smart>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 12:22:27 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Radu Hociung wrote:
> Hello all,
> 
> I've been following the group for a while, and I can't find the answer I'm
> looking for:
> 
> 1. About the challenge-response draft document: Are your intentions to make
> it into an RFC? Is it a possibilty that it can/will become a mainstream
> standard?
> 

I am assuming you are refering to the following:

http://www.ietf.org/internet-drafts/draft-irtf-asrg-cri-00.txt

There has been very little feedback at all on this document, so it looks 
to me that there is very little interest in this kind of stuff. 
Something only has a chance of becoming a standard if people are willing 
to support it and so far no one has been.

> 2. About the contents: If a spammer would add headers to his message to
> make it look like a mailing list, this message would then not be subject to
> the other provisions of the draft? Is there a separate draft/RFC to deal
> with the mailing list/CR combination, or do you intend to address this in
> some way?
> 

As the draft is written now in section 4.2 lists can be exempt, but we 
were planning on dealing with this in the future, IF sufficient interest 
would be shown in the idea. So far no interest was shown and as a matter 
of fact, the document is about to expire.

Yakov


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



From exim@www1.ietf.org  Wed Mar 17 13:52:07 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28953
	for <asrg-archive@odin.ietf.org>; Wed, 17 Mar 2004 13:52:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3g8D-0007lb-BD
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 13:51:29 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HIoxDj029811
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 13:50:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3g82-0007kG-Si
	for asrg-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 13:50:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28848
	for <asrg-web-archive@ietf.org>; Wed, 17 Mar 2004 13:50:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3g7l-0005qD-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 13:50:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3g6p-0005ge-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 13:49:44 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3g5q-0005XT-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 13:48:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3g4T-0007Wc-PC; Wed, 17 Mar 2004 13:47:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3g3w-0007Va-M9
	for asrg@optimus.ietf.org; Wed, 17 Mar 2004 13:46:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28667
	for <asrg@ietf.org>; Wed, 17 Mar 2004 13:46:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3g3u-0005Io-00
	for asrg@ietf.org; Wed, 17 Mar 2004 13:46:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3g31-0005Ca-00
	for asrg@ietf.org; Wed, 17 Mar 2004 13:45:47 -0500
Received: from bay2-dav63.bay2.hotmail.com ([65.54.246.198] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3g2R-00054C-00
	for asrg@ietf.org; Wed, 17 Mar 2004 13:45:11 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 17 Mar 2004 10:44:36 -0800
Received: from 67.21.231.79 by bay2-dav63.bay2.hotmail.com with DAV;
	Wed, 17 Mar 2004 18:44:36 +0000
X-Originating-IP: [67.21.231.79]
X-Originating-Email: [joe_kern_1001@hotmail.com]
X-Sender: joe_kern_1001@hotmail.com
From: "joe" <joe_kern_1001@hotmail.com>
To: <asrg@ietf.org>
Message-ID: <017801c40c4f$e53d3540$0b00000a@teledeal>
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
Importance: Normal
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A19E4@mou1wnexm05.vcorp.ad.vrsn.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 17 Mar 2004 18:44:36.0689 (UTC) FILETIME=[E594A410:01C40C4F]
Content-Transfer-Encoding: 7bit
Subject: [Asrg] CallerID and disposable addresses
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 13:44:36 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=3.0 required=5.0 tests=AWL,FROM_ENDS_IN_NUMS,
	FROM_HAS_ULINE_NUMS autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

All,

While CallerID sounds like a simple solution, it may in fact cripple
popular anti-spam measures such as third party disposable email address
provider.
A sender will not be able to use a disposable email address as his or
her sender's address if the domain of the disposable forwarding server
is different from the SMTP server used for sending out the mail.

No wander, larger ISP support such a draft which cripples competition.

Joe Kern




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



From exim@www1.ietf.org  Wed Mar 17 14:56:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02425
	for <asrg-archive@odin.ietf.org>; Wed, 17 Mar 2004 14:56:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3h92-0003wU-Sf
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 14:56:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HJtw22015131
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 14:55:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3h8u-0003vc-Vw
	for asrg-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 14:55:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02400
	for <asrg-web-archive@ietf.org>; Wed, 17 Mar 2004 14:55:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3h8d-0007Do-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 14:55:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3h7d-00076o-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 14:54:38 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3h6d-0006vu-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 14:53:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3h65-0003kJ-5U; Wed, 17 Mar 2004 14:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3h5n-0003iI-Ul
	for asrg@optimus.ietf.org; Wed, 17 Mar 2004 14:52:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02383
	for <asrg@ietf.org>; Wed, 17 Mar 2004 14:52:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3h5l-0006sv-00
	for asrg@ietf.org; Wed, 17 Mar 2004 14:52:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3h4y-0006my-00
	for asrg@ietf.org; Wed, 17 Mar 2004 14:51:52 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3h4X-0006fx-00
	for asrg@ietf.org; Wed, 17 Mar 2004 14:51:25 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id 587BB170C4
	for <asrg@ietf.org>; Wed, 17 Mar 2004 14:54:59 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] 1a. Inventory of Problems - new spam channels 
In-Reply-To: Your message of "Tue, 16 Mar 2004 23:45:29 -0300."
             <6.0.3.0.0.20040316233552.01cd7740@mail.uniwares.com> 
Message-Id: <20040317195459.587BB170C4@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 14:54:59 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Andreas Saurwein <saurwein@uniwares.com> wrote:
> I believe it is only a matter of a few month until we see serious spam in 
> online games. Most games have, as far as I can see, no protection against 
> this type of misuse.

  As a larger question, is the IETF designing protocols for the
Internet, or for IP networks?

  Online games may be viewed as private networks layered on top of the
Internet.  So are we interested in solving their spam problems, or
are they out of scope:

  Alan DeKok.

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



From exim@www1.ietf.org  Wed Mar 17 15:53:01 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06719
	for <asrg-archive@odin.ietf.org>; Wed, 17 Mar 2004 15:53:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3i0x-0001ji-LZ
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 15:52:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HKpbU6006666
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 15:51:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3i0m-0001jK-V9
	for asrg-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 15:51:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06649
	for <asrg-web-archive@ietf.org>; Wed, 17 Mar 2004 15:51:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3i0V-0007Eh-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 15:51:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3hzP-00073L-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 15:50:12 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3hyp-0006sI-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 15:49:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3hwy-0001OW-R8; Wed, 17 Mar 2004 15:47:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3hu6-0001GB-00
	for asrg@optimus.ietf.org; Wed, 17 Mar 2004 15:44:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06244
	for <asrg@ietf.org>; Wed, 17 Mar 2004 15:44:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3hu4-0006CL-00
	for asrg@ietf.org; Wed, 17 Mar 2004 15:44:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3ht9-00063j-00
	for asrg@ietf.org; Wed, 17 Mar 2004 15:43:43 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3hsE-0005wB-00
	for asrg@ietf.org; Wed, 17 Mar 2004 15:42:46 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B3hsD-0004Tl-00; Wed, 17 Mar 2004 15:42:45 -0500
Received: from [68.244.233.132] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B3hsB-0005VA-00; Wed, 17 Mar 2004 15:42:44 -0500
Message-ID: <4058B839.3060002@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Alan DeKok <aland@ox.org>
CC: asrg@ietf.org
Subject: Re: [Asrg] 1a. Inventory of Problems - new spam channels
References: <20040317195459.587BB170C4@mail.nitros9.org>
In-Reply-To: <20040317195459.587BB170C4@mail.nitros9.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 15:42:33 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Alan DeKok wrote:
> Andreas Saurwein <saurwein@uniwares.com> wrote:
> 
>>I believe it is only a matter of a few month until we see serious spam in 
>>online games. Most games have, as far as I can see, no protection against 
>>this type of misuse.
> 
> 
>   As a larger question, is the IETF designing protocols for the
> Internet, or for IP networks?
> 

 From a draft IETF mission statement 
(http://www.ietf.org/u/ietfchair/ietf-mission.html):

"The purpose of the IETF is to create high quality, relevant, and timely 
standards for the Internet."

and

"It is important that this is "For the Internet," and does not include 
everything that happens to use IP. IP is being used in a myriad of 
real-world applications, such as controlling street lights, but the IETF 
does not standardize those applications."

>   Online games may be viewed as private networks layered on top of the
> Internet.  So are we interested in solving their spam problems, or
> are they out of scope:
> 

Now if game sites were using a standard protocol to talk to each other, 
or between players AND that protocol would be standardized on the 
Internet level and not proprietary to each company; then it would be in 
scope.

Yakov

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



From exim@www1.ietf.org  Wed Mar 17 16:33:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09069
	for <asrg-archive@odin.ietf.org>; Wed, 17 Mar 2004 16:33:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3iel-000650-OD
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 16:32:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HLWt0F023371
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 16:32:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3iel-00064j-Bx
	for asrg-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 16:32:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09054
	for <asrg-web-archive@ietf.org>; Wed, 17 Mar 2004 16:32:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3iej-0005kb-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 16:32:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3idn-0005ca-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 16:31:56 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3id5-0005Us-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 16:31:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3icw-0005u1-EZ; Wed, 17 Mar 2004 16:31:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3ice-0005tO-HS
	for asrg@optimus.ietf.org; Wed, 17 Mar 2004 16:30:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08940
	for <asrg@ietf.org>; Wed, 17 Mar 2004 16:30:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3icc-0005S2-00
	for asrg@ietf.org; Wed, 17 Mar 2004 16:30:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3ibh-0005Ja-00
	for asrg@ietf.org; Wed, 17 Mar 2004 16:29:45 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3ial-00059C-00
	for asrg@ietf.org; Wed, 17 Mar 2004 16:28:47 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2HLSknt016906;
        Wed, 17 Mar 2004 13:28:46 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GYBNPB52>; Wed, 17 Mar 2004 13:28:46 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A19FB@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Yakov Shafranovich'" <research@solidmatrix.com>,
        Alan DeKok
	 <aland@ox.org>
Cc: asrg@ietf.org
Subject: RE: [Asrg] 1a. Inventory of Problems - new spam channels
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 13:28:40 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

The spam problem is the result of a lack of accountability.

That lack of accountability tends to be the result of being part of an
Internet rather than a private network. 

So while Yakov makes a valid point these non email spam problems are
relevant because they occur because the protocol is used over a network of
networks rather than just a network.


Regardless of what happens in MARID people will take the same principles and
apply them. You can even recycle the same syntax and even the same RRs the
same way MX was generalized first to SRV and then to NAPTR.

Try to give the following a reasonable meaning that is not the one that is
intended.

_http._spf.example.com "TLS=always "
		"CA=SHA1:742C3192E607E424EB4549542BE1BBC53E6174E2=="

If the scheme is unambiguous enough to eliminate ambiguity we have a
solution. Let the market decide whether or not it wants to use it.

		Phill

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



From exim@www1.ietf.org  Wed Mar 17 17:08:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11354
	for <asrg-archive@odin.ietf.org>; Wed, 17 Mar 2004 17:08:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3jCh-0000mH-AY
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 17:07:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HM7xFi002983
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 17:07:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3jCg-0000ly-S5
	for asrg-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 17:07:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11268
	for <asrg-web-archive@ietf.org>; Wed, 17 Mar 2004 17:07:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3jCe-0003P7-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 17:07:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3jAi-0002qA-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 17:05:57 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3j80-0002MN-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 17:03:08 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B3j0s-00051z-6v
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 16:55:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3j0J-00080j-Or; Wed, 17 Mar 2004 16:55:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3izx-000809-6x
	for asrg@optimus.ietf.org; Wed, 17 Mar 2004 16:54:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10598
	for <asrg@ietf.org>; Wed, 17 Mar 2004 16:54:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3izv-0001NO-00
	for asrg@ietf.org; Wed, 17 Mar 2004 16:54:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3iz5-0001Gf-00
	for asrg@ietf.org; Wed, 17 Mar 2004 16:53:56 -0500
Received: from adsl-64-165-36-235.dsl.snfc21.pacbell.net ([64.165.36.235] helo=shedevil.annepmitchell.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3iyn-00019Q-00
	for asrg@ietf.org; Wed, 17 Mar 2004 16:53:37 -0500
Received: from [192.168.0.247] ([192.168.0.247])
	by shedevil.annepmitchell.com (8.11.6/8.11.4) with ESMTP id i2HLraX36354
	for <asrg@ietf.org>; Wed, 17 Mar 2004 13:53:36 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <20040317170011.22524.86258.Mailman@www1.ietf.org>
References: <20040317170011.22524.86258.Mailman@www1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <8AC79F3A-785D-11D8-9507-000A95AC5778@isipp.com>
Content-Transfer-Encoding: 7bit
From: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
To: asrg@ietf.org
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: Asrg digest, Vol 1 #563 - 3 msgs
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 13:53:36 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


Ken?

> 	A proposal for an accreditation mechanism is attached. This proposal
> is based on the earlier RBL scheme proposed by Vixie, and designed to 
> be
> compatible with CallerID. I will submit as an ID later on today.
>
> 	Basically the scheme returns an A record in response to a lookup. So
> in order for example.com to announce that it is accredited by the 
> class3
> service of verisign the SPF or CallerID record would contain the 
> tripple:
>
> 	"accreditation" "class3.verisign.com""DNS-A"
>

How does this differ from IADB?  It sounds identical, although I'm sure 
that it must not be.

http://www.isipp.com/iadb.php
http://www.isipp.com/iadbquery.php

See also:

http://www.isipp.com/codelist.php

Anne



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



From exim@www1.ietf.org  Thu Mar 18 03:02:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25814
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 03:02:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sU1-0000Mt-2h
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 03:02:29 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2I82SFM001409
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 03:02:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sU0-0000Me-LV
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 03:02:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25787
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 03:02:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sTw-00023k-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 03:02:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3sSx-0001uQ-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 03:01:24 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sS4-0001lX-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 03:00:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sRh-0008WN-JX; Thu, 18 Mar 2004 03:00:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sQs-0008In-Ki
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 02:59:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25620
	for <asrg@ietf.org>; Thu, 18 Mar 2004 02:59:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sQo-0001aS-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:59:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3sPm-0001Ri-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:58:06 -0500
Received: from adsl-64-165-36-235.dsl.snfc21.pacbell.net ([64.165.36.235] helo=shedevil.annepmitchell.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sOq-0001Jf-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:57:09 -0500
Received: from [192.168.0.247] ([192.168.0.247])
	by shedevil.annepmitchell.com (8.11.6/8.11.4) with ESMTP id i2I7v7X44911;
	Wed, 17 Mar 2004 23:57:07 -0800 (PST)
In-Reply-To: <405954A5.1010007@solidmatrix.com>
References: <3DC625B6-77F8-11D8-AD47-000A95AC5778@isipp.com> <405954A5.1010007@solidmatrix.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <DA07C4E0-78B1-11D8-9C3A-000A95AC5778@isipp.com>
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
From: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
Subject: Re: [Asrg] Update on Querying IADB
To: Yakov Shafranovich <research@solidmatrix.com>
X-Mailer: Apple Mail (2.613)
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 23:57:06 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>
Yakov,

> All of these codes bring to mind an interesting question. The current 
> systems of this kind, both blacklist and whitelist, do not have a 
> standard set of codes outside the 127.0.0.1 - present. Wouldn't a 
> standard set help? Or perhaps a whole new trust protocol for 
> negotiating trust among two entities and quering third parties?

>
Actually the codes we use are a subset of the proposed standardized 
codeset we developed with Craig Hughes (SpamAssassin) (Craig actually 
did the initial development, with after-input from us, and tweaking a 
bit for the needs of ISPs, from whom we also had input).  We worked 
very closely with Craig as well as the ISP community because we wanted 
to be sure to provide a product which was completely useful, 
functional, and practical for both spam filters and ISPs (which is also 
why we offer it in two flavors - one with each individual data response 
returned per query, and one with an aggregate score, the latter being 
requested by some of the ISPs).

The current codeset can be seen at http://www.isipp.com/codelist.php

Anne


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



From exim@www1.ietf.org  Thu Mar 18 03:18:01 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26392
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 03:18:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sia-0001Wu-Bk
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 03:17:32 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2I8HWKQ005874
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 03:17:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3siZ-0001Wf-CL
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 03:17:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26379
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 03:17:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3siX-0003wF-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 03:17:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3shk-0003nH-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 03:16:41 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sgl-0003di-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 03:15:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sgC-0001KP-Lu; Thu, 18 Mar 2004 03:15:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sba-00015D-Vf
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 03:10:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26052
	for <asrg@ietf.org>; Thu, 18 Mar 2004 03:10:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sbX-0002yP-00
	for asrg@ietf.org; Thu, 18 Mar 2004 03:10:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3saY-0002qa-00
	for asrg@ietf.org; Thu, 18 Mar 2004 03:09:15 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3saB-0002jl-00
	for asrg@ietf.org; Thu, 18 Mar 2004 03:08:51 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B3sa9-0004zM-00; Thu, 18 Mar 2004 03:08:49 -0500
Received: from [68.244.163.173] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B3sa8-0005LD-00; Thu, 18 Mar 2004 03:08:49 -0500
Message-ID: <40595903.4090502@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] Update on Querying IADB
References: <3DC625B6-77F8-11D8-AD47-000A95AC5778@isipp.com> <405954A5.1010007@solidmatrix.com> <DA07C4E0-78B1-11D8-9C3A-000A95AC5778@isipp.com>
In-Reply-To: <DA07C4E0-78B1-11D8-9C3A-000A95AC5778@isipp.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 03:08:35 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Anne P. Mitchell, Esq. wrote:
>>
> Yakov,
> 
>> All of these codes bring to mind an interesting question. The current 
>> systems of this kind, both blacklist and whitelist, do not have a 
>> standard set of codes outside the 127.0.0.1 - present. Wouldn't a 
>> standard set help? Or perhaps a whole new trust protocol for 
>> negotiating trust among two entities and quering third parties?
> 
> 
>>
> Actually the codes we use are a subset of the proposed standardized 
> codeset we developed with Craig Hughes (SpamAssassin) (Craig actually 
> did the initial development, with after-input from us, and tweaking a 
> bit for the needs of ISPs, from whom we also had input).  We worked very 
> closely with Craig as well as the ISP community because we wanted to be 
> sure to provide a product which was completely useful, functional, and 
> practical for both spam filters and ISPs (which is also why we offer it 
> in two flavors - one with each individual data response returned per 
> query, and one with an aggregate score, the latter being requested by 
> some of the ISPs).
> 
> The current codeset can be seen at http://www.isipp.com/codelist.php
> 

What concerns me about this is that you are overloading an existing 
protocol (DNSBLs) of an existing protocol (DNS A records) to do this. My 
original question is really focused on whether we should consider a 
protocol and format for exchanging information about senders that would 
be more extensive that what is currently found.

For example, the SMTP VERIFY subgroup is discussing among other things, 
standardizing Senderbase-like counters via SNMP.

Yakov

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



From exim@www1.ietf.org  Thu Mar 18 08:40:49 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10053
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 08:40:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3xky-00062p-Hx
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 08:40:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IDeKvj023231
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 08:40:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3xkx-00062c-UJ
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 08:40:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10019
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 08:40:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3xkw-00067c-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 08:40:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3xjy-0005zD-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 08:39:18 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3xj0-0005qj-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 08:38:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3xik-0005gZ-TW; Thu, 18 Mar 2004 08:38:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3xiE-0005YF-90
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 08:37:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09921
	for <asrg@ietf.org>; Thu, 18 Mar 2004 08:37:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3xiC-0005kw-00
	for asrg@ietf.org; Thu, 18 Mar 2004 08:37:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3xhJ-0005e6-00
	for asrg@ietf.org; Thu, 18 Mar 2004 08:36:34 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3xgz-0005Wa-00
	for asrg@ietf.org; Thu, 18 Mar 2004 08:36:13 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2IDaCqQ001295;
        Thu, 18 Mar 2004 05:36:12 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GYBNS3A4>; Thu, 18 Mar 2004 05:36:12 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E5DBA55@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Yakov Shafranovich'" <research@solidmatrix.com>,
        "Anne P. Mitchell, Esq." <amitchell@isipp.com>
Cc: asrg@ietf.org
Subject: RE: [Asrg] Update on Querying IADB
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 05:36:11 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

I agree with Yakov here, the A record convention is widely used it has
become a defacto extension to the specs. But the data being exchanged is
essentially binary in nature.

Anne's proposal strikes me as trying to use the A record to do far too much.
Once you start to try to move that amount of data it would be better to move
to using the TXT record or get a whole new RR defined. As long as the
overall record is shorter than 512 bytes there is no impact on performance.

This has another concrete benefit, the need for ad-hoc extensions of the
code set as new accrediting agencies appear goes away. 


The big difference between Anne's approach and mine is that I am proposing
that the accreditation data be separated into two parts, the accreditations
themselves and a single master record that describes the accreditation
service.

This ties in with what I think would be the data structures that filters
would build up. Each accreditation service being tracked would be
represented by some sort of master record that described the current
evaluation of the service. The description provided by the service would
provide part of that record, measurements of the performance of the service
would then be added in.

		Phil

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



From exim@www1.ietf.org  Thu Mar 18 09:32:17 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13451
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 09:32:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3yYo-0002Rj-Le
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 09:31:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IEVoIr009397
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 09:31:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3yYo-0002RU-Fy
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 09:31:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13446
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 09:31:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3yYm-0005jF-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 09:31:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3yXt-0005Zk-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 09:30:54 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3yXD-0005Q4-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 09:30:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3yX4-0001w6-BQ; Thu, 18 Mar 2004 09:30:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3yWl-0001ti-1v
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 09:29:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13150
	for <asrg@ietf.org>; Thu, 18 Mar 2004 09:29:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3yWj-0005LZ-00
	for asrg@ietf.org; Thu, 18 Mar 2004 09:29:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3yVX-00055k-00
	for asrg@ietf.org; Thu, 18 Mar 2004 09:28:27 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3yUV-0004rN-00
	for asrg@ietf.org; Thu, 18 Mar 2004 09:27:23 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2IERN4H005424;
        Thu, 18 Mar 2004 06:27:23 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GYBNSVKV>; Thu, 18 Mar 2004 06:27:22 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E5DBA58@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Yakov Shafranovich'" <research@solidmatrix.com>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: asrg@ietf.org
Subject: RE: [Asrg] Accreditation Mechanism Proposal
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 06:27:22 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60


> Hallam-Baker, Phillip wrote:
> > 	A proposal for an accreditation mechanism is attached. 
> This proposal
> > is based on the earlier RBL scheme proposed by Vixie, and 
> designed to be
> > compatible with CallerID. I will submit as an ID later on today.
> > 
> 
> Is the other consent proposal being submitted as well?

yes, I am just getting the PDf versions done. I have worked out 
how to get word to edit in plaintext format and a readable format
at the same time.


> There has been talk in at least four forums (ASRG, 
> SMTP-VERIFY, MXCOMP 
> and main IETF list) about trust, establishing trust between 
> two parties 
> and quering third party providers of information. The SMTP-VERIFY 
> subgroup is also talking about exchanging information on 
> neutral metrics like MTA volume via some protocol.

I will check the SMTP-VERIFY archives.

I think that the scope of trust exchange in this particular domain
needs to be limited, there are trillions of emails sent each week, 
there is no way that every one can be backed by an essay the 
length of war and peace describing the trustworthiness.

On the other hand we do want more than binary data, there has to 
be a gradation here. In practice I suspect we do not need a huge
number of levels at this point in time.


I think it is also useful to see a description of the domain. An
ISP or university cannot be held to the same standard as a lawyers
office. The lawyer should have very tight control over their 
employees. If there are persistent spam runs then there is a real
problem that is not really explainable. An ISP on the other hand cannot
be expected to stop all spam outright, not without controlling their
customers in an unacceptable way.


	Phill

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



From exim@www1.ietf.org  Thu Mar 18 11:45:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24180
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 11:45:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B40dr-0003Ox-Le
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 11:45:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IGjBdO013069
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 11:45:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B40dr-0003Oi-GT
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 11:45:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24050
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 11:45:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B40dq-0002hm-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 11:45:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B40ct-0002a5-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 11:44:12 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B40c1-0002SN-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 11:43:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B40bm-0002uz-ON; Thu, 18 Mar 2004 11:43:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B40Yo-0002Ox-64
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 11:39:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23613
	for <asrg@ietf.org>; Thu, 18 Mar 2004 11:39:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B40Yl-0002Br-00
	for asrg@ietf.org; Thu, 18 Mar 2004 11:39:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B40Xs-00024F-00
	for asrg@ietf.org; Thu, 18 Mar 2004 11:39:01 -0500
Received: from mercury.mv.net ([199.125.85.40])
	by ietf-mx with smtp (Exim 4.12)
	id 1B40Wl-0001xX-00
	for asrg@ietf.org; Thu, 18 Mar 2004 11:37:51 -0500
Received: (qmail 4921 invoked from network); 18 Mar 2004 11:37:51 -0500
Received: from iridium.mv.net (HELO mv.mv.com) (199.125.85.17)
  by mercury.mv.net with SMTP; 18 Mar 2004 11:37:51 -0500
X-Peer-Info: remote-ip 199.125.85.17 local-ip 199.125.85.40
  local-name mercury.mv.net
Received: (qmail 20545 invoked by uid 101); 18 Mar 2004 11:37:51 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: asrg@ietf.org
Subject: Re: [Asrg] Accreditation Mechanism Proposal
Message-ID: <20040318163751.GB12873@iridium.mv.net>
References: <C6DDA43B91BFDA49AA2F1E473732113E0A19E4@mou1wnexm05.vcorp.ad.vrsn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A19E4@mou1wnexm05.vcorp.ad.vrsn.com>
User-Agent: Mutt/1.4.2.1i
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 11:37:51 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

On Wed, Mar 17, 2004 at 07:23:32AM -0800, Hallam-Baker, Phillip wrote:
> 
> 	Basically the scheme returns an A record in response to a lookup. So
> in order for example.com to announce that it is accredited by the class3
> service of verisign the SPF or CallerID record would contain the tripple:
> 
> 	"accreditation" "class3.verisign.com""DNS-A"
> 
> 	I.e. this is an accreditation property, the accreditor service is at
> class3.verisign.com, the protocol is a DNS A record lookup.
> 
> 	Some folk inside VeriSign suggested that we use the convention that
> an unlisted domain just returns domain does not exist. 

You mean when querying the accreditation service?
How would this interact with Verisign's publishing of wildcard
records (e.g. if the accreditation service goes out of business and
its domain name is revoked)? 

This goal of indirect identification of accreditation services seems
like a positive thing.  Has there been any attempt to analyze the
additional overhead?

Also, as with SPF et al there is the question of feedback from the
recipient: e.g. one might want to have the ability for the recipient
to publish information about what that recipient requires of a
sender.  Some unified scheme might be useful, like:

    ( Sender domain must publish SPF OR DMP
    AND Sender must be accredited by any two of {abc, def, ghi, xyz}
    AND Sender IP must publish MTAMark)
    OR  ( Sender must accept address verification probe )

but that's probably a whole nother effort.
    

A couple of random remarks from a very cursory reading:

>           There is no difficulty in ensuring that accreditation providers are 
>           accountable to email recipients. An accreditation authority that 
>           provides incorrect accreditation will soon be ignored.

Pretty bold assertion :-)
It hasn't held true with some DNSBL services.  Among other reasons is
the wide variety of definitions of "incorrect," as well as extremely
polar opinions about listing criteria, remedies, responsibility, et al.



>        1.3 Practices Considerations 
> 
>           As a trusted third party the actions of an Accreditation Authority 
>           are raise numerous legal issues.

syntax problem there.


>        3.2 Sender Recipient A Record 
  ...
>              
>             Bits 4-7 
>               These bits are reserved. Relying parties MUST ignore 

Red flag:  better would be "these bits are reserved and must be set
to zero."  If you don't guarantee they are zero from the outset,
it's hard to make sure you can use them in the future.


>        3.3 Other Sender Recipient Records 
>            
>           Additional information MAY be provided by means of other DNS 
>           records, for example TXT or NAPTR records.

Do you really anticipate using NAPTR?

mm

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



From exim@www1.ietf.org  Thu Mar 18 12:50:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26958
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 12:50:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41f1-0001e8-16
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 12:50:28 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IHoQPm006322
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 12:50:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41f0-0001dp-S1
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 12:50:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26887
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 12:50:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41ez-0006m3-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:50:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41e1-0006gp-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:49:26 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41d5-0006bg-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:48:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41cf-0001AM-Lf; Thu, 18 Mar 2004 12:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41cJ-00016a-4l
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 12:47:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26748
	for <asrg@ietf.org>; Thu, 18 Mar 2004 12:47:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41cH-0006Xu-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:47:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41bN-0006UM-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:46:42 -0500
Received: from adsl-64-165-36-235.dsl.snfc21.pacbell.net ([64.165.36.235] helo=shedevil.annepmitchell.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41aI-0006QL-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:45:34 -0500
Received: from [192.168.0.247] ([192.168.0.247])
	by shedevil.annepmitchell.com (8.11.6/8.11.4) with ESMTP id i2IHjVX52984;
	Thu, 18 Mar 2004 09:45:31 -0800 (PST)
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E5DBA55@mou1wnexm05.vcorp.ad.vrsn.com>
References: <C6DDA43B91BFDA49AA2F1E473732113E5DBA55@mou1wnexm05.vcorp.ad.vrsn.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0CAB1654-7904-11D8-9C3A-000A95AC5778@isipp.com>
Content-Transfer-Encoding: 7bit
Cc: "'Yakov Shafranovich'" <research@solidmatrix.com>, asrg@ietf.org
From: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
Subject: Re: [Asrg] Update on Querying IADB
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
X-Mailer: Apple Mail (2.613)
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 09:45:30 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



> Anne's proposal strikes me as trying to use the A record to do far too 
> much.
> Once you start to try to move that amount of data it would be better 
> to move
> to using the TXT record or get a whole new RR defined. As long as the
> overall record is shorter than 512 bytes there is no impact on 
> performance.
>

I'm not here to debate merits (and certainly not to argue :-) );  I do 
just want to point out that first, the codes that IADB uses are not a 
'proposal' - this is an active,  live accreditation database, presently 
online, and being used to help ISPs and spam filters make email 
acceptance, delivery, and processing decisions for more than 30million 
email boxes, and the number is growing every day.

Second, the proposal which *is* on the table is not ISIPP's, and 
certainly not mine. :-)  It is Craig Hughes'.

Anne


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



From exim@www1.ietf.org  Thu Mar 18 12:57:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27576
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 12:57:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41l5-0002Q4-4e
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 12:56:43 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IHuhiD009294
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 12:56:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41l4-0002Pp-VM
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 12:56:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27562
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 12:56:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41l2-0007Fo-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:56:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41kE-0007CN-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:55:50 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41jb-00078T-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:55:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41jR-0002D7-8Q; Thu, 18 Mar 2004 12:55:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41j0-0002Bf-3v
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 12:54:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27266
	for <asrg@ietf.org>; Thu, 18 Mar 2004 12:54:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41iy-00075i-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:54:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41i0-00072F-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:53:32 -0500
Received: from adsl-64-165-36-235.dsl.snfc21.pacbell.net ([64.165.36.235] helo=shedevil.annepmitchell.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41h7-0006ye-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:52:38 -0500
Received: from [192.168.0.247] ([192.168.0.247])
	by shedevil.annepmitchell.com (8.11.6/8.11.4) with ESMTP id i2IHqbX53162;
	Thu, 18 Mar 2004 09:52:37 -0800 (PST)
In-Reply-To: <4059E12C.9010704@solidmatrix.com>
References: <C6DDA43B91BFDA49AA2F1E473732113E5DBA55@mou1wnexm05.vcorp.ad.vrsn.com> <0CAB1654-7904-11D8-9C3A-000A95AC5778@isipp.com> <4059E12C.9010704@solidmatrix.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <0AA38EEF-7905-11D8-9C3A-000A95AC5778@isipp.com>
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
From: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
Subject: Re: [Asrg] Update on Querying IADB
To: Yakov Shafranovich <research@solidmatrix.com>
X-Mailer: Apple Mail (2.613)
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 09:52:36 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit




> We are not attacking your proposal per se,

Yakov, I know you aren't, and I wasn't feeling attacked, but *thank 
you* for saying that!

> rather we are discussing the need for possibly making a single 
> Internet standard for this type of stuff with your system and SORBS's 
> codes as an example.
>
>

That's precisely what Craig's proposal is.  You can read that at:

http://www.rungie.com/wiki/VouchListSpec

Anne


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



From exim@www1.ietf.org  Thu Mar 18 13:34:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29432
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 13:34:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42Ld-0000XO-2A
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 13:34:29 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IIYTN7002062
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 13:34:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42Lc-0000XB-Sx
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 13:34:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29364
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 13:34:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B42La-0001h4-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 13:34:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B42Kf-0001b1-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 13:33:29 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B42Jl-0001Wt-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 13:32:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42JF-0008DS-6O; Thu, 18 Mar 2004 13:32:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42Il-00089S-8e
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 13:31:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29210
	for <asrg@ietf.org>; Thu, 18 Mar 2004 13:31:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B42Ij-0001SF-00
	for asrg@ietf.org; Thu, 18 Mar 2004 13:31:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B42Hn-0001PZ-00
	for asrg@ietf.org; Thu, 18 Mar 2004 13:30:32 -0500
Received: from mercury.mv.net ([199.125.85.40])
	by ietf-mx with smtp (Exim 4.12)
	id 1B42H5-0001Mg-00
	for asrg@ietf.org; Thu, 18 Mar 2004 13:29:47 -0500
Received: (qmail 6277 invoked from network); 18 Mar 2004 13:29:30 -0500
Received: from iridium.mv.net (HELO mv.mv.com) (199.125.85.17)
  by mercury.mv.net with SMTP; 18 Mar 2004 13:29:34 -0500
X-Peer-Info: remote-ip 199.125.85.17 local-ip 199.125.85.40
  local-name mercury.mv.net
Received: (qmail 21613 invoked by uid 101); 18 Mar 2004 13:29:29 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
To: Yakov Shafranovich <research@solidmatrix.com>
Cc: "Mark E. Mallett" <mem@mv.mv.com>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>, asrg@ietf.org
Subject: Re: [Asrg] Accreditation Mechanism Proposal
Message-ID: <20040318182928.GA12118@iridium.mv.net>
References: <C6DDA43B91BFDA49AA2F1E473732113E0A19E4@mou1wnexm05.vcorp.ad.vrsn.com> <20040318163751.GB12873@iridium.mv.net> <4059E282.3030704@solidmatrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4059E282.3030704@solidmatrix.com>
User-Agent: Mutt/1.4.2.1i
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 13:29:28 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

On Thu, Mar 18, 2004 at 12:55:14PM -0500, Yakov Shafranovich wrote:
> Mark E. Mallett wrote:
> >On Wed, Mar 17, 2004 at 07:23:32AM -0800, Hallam-Baker, Phillip wrote:
> >
> >A couple of random remarks from a very cursory reading:
> >
> >
> >>         There is no difficulty in ensuring that accreditation providers 
> >>         are accountable to email recipients. An accreditation authority 
> >>         that provides incorrect accreditation will soon be ignored.
> >
> >Pretty bold assertion :-)
> >It hasn't held true with some DNSBL services.  Among other reasons is
> >the wide variety of definitions of "incorrect," as well as extremely
> >polar opinions about listing criteria, remedies, responsibility, et al.
> 
> The key difference from blacklists is that blacklists do not ask ISPs 
> whether they want to be listed. Here, the sender actively goes to a 
> provider and signs up, and then indicates his accredidation in some 
> protocol.

I don't think that's really a difference, at least not in all cases.
There will be "market forces" in play where (assuming the accreditation
system works) once enough recipients use a paricular set of
accreditors, there will be pressure for senders to be listed in at
least one of them.

Besides, the statement was about the services being accountable to the
recipients, not to the senders.  That's quite analogous to DNSBLs
being accountable to their users.  That isn't a truism, at least not
in my opinion.  "Ethical consumerism" isn't likely to be present in
consumers of DNSBLs any more than it is in people looking for any
other goods and services (like choosing an ISP), not to mention that
the "ethics" involved (aka correctness) are widely disputed.  There
are tons of people using DNSBLs without any clue about how correct
those services are.  I'm not trying to make any deep statement here
though, just a comment on the prediction.

mm

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



From exim@www1.ietf.org  Thu Mar 18 13:37:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29526
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 13:37:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42Mo-0000bC-NK
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 13:36:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IIZW5r002185
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 13:35:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42Lp-0000Xy-AW
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 13:34:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29387
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 13:34:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B42Li-0001i2-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 13:34:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B42Kw-0001dI-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 13:33:46 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B42KB-0001ZY-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 13:32:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42KC-00008W-Bu; Thu, 18 Mar 2004 13:33:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41g8-0001uB-S2
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 12:51:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27005
	for <asrg@ietf.org>; Thu, 18 Mar 2004 12:51:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41g7-0006t6-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:51:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41fC-0006o9-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:50:38 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41eN-0006kM-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:49:47 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B41eH-0001Qm-00; Thu, 18 Mar 2004 12:49:41 -0500
Received: from [68.244.172.97] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B41eG-0001oD-00; Thu, 18 Mar 2004 12:49:41 -0500
Message-ID: <4059E12C.9010704@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
CC: "Hallam-Baker, Phillip" <pbaker@verisign.com>, asrg@ietf.org
Subject: Re: [Asrg] Update on Querying IADB
References: <C6DDA43B91BFDA49AA2F1E473732113E5DBA55@mou1wnexm05.vcorp.ad.vrsn.com> <0CAB1654-7904-11D8-9C3A-000A95AC5778@isipp.com>
In-Reply-To: <0CAB1654-7904-11D8-9C3A-000A95AC5778@isipp.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 12:49:32 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Anne P. Mitchell, Esq. wrote:
>> Anne's proposal strikes me as trying to use the A record to do far too 
>> much.
>> Once you start to try to move that amount of data it would be better 
>> to move
>> to using the TXT record or get a whole new RR defined. As long as the
>> overall record is shorter than 512 bytes there is no impact on 
>> performance.
>>
> 
> I'm not here to debate merits (and certainly not to argue :-) );  I do 
> just want to point out that first, the codes that IADB uses are not a 
> 'proposal' - this is an active,  live accreditation database, presently 
> online, and being used to help ISPs and spam filters make email 
> acceptance, delivery, and processing decisions for more than 30million 
> email boxes, and the number is growing every day.
> 
> Second, the proposal which *is* on the table is not ISIPP's, and 
> certainly not mine. :-)  It is Craig Hughes'.
> 

Anne,

We are not attacking your proposal per se, rather we are discussing the 
need for possibly making a single Internet standard for this type of 
stuff with your system and SORBS's codes as an example.

As for Craig, I'll drop him a line.

Yakov

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



From exim@www1.ietf.org  Thu Mar 18 13:37:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29543
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 13:37:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42Mo-0000bB-Lv
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 13:36:33 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IIZWaK002184
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 13:35:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42Lp-0000Xz-Vs
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 13:34:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29390
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 13:34:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B42Li-0001i7-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 13:34:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B42Kw-0001dR-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 13:33:47 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B42KC-0001Za-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 13:33:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42KD-00009J-1f; Thu, 18 Mar 2004 13:33:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41lv-0002rH-H6
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 12:57:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27608
	for <asrg@ietf.org>; Thu, 18 Mar 2004 12:57:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41ls-0007J0-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:57:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41l3-0007G1-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:56:42 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41kF-0007Ca-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:55:51 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B41kC-0008FU-00; Thu, 18 Mar 2004 12:55:48 -0500
Received: from [68.244.172.97] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B41kB-0008FL-00; Thu, 18 Mar 2004 12:55:48 -0500
Message-ID: <4059E282.3030704@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Mark E. Mallett" <mem@mv.mv.com>
CC: "Hallam-Baker, Phillip" <pbaker@verisign.com>, asrg@ietf.org
Subject: Re: [Asrg] Accreditation Mechanism Proposal
References: <C6DDA43B91BFDA49AA2F1E473732113E0A19E4@mou1wnexm05.vcorp.ad.vrsn.com> <20040318163751.GB12873@iridium.mv.net>
In-Reply-To: <20040318163751.GB12873@iridium.mv.net>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 12:55:14 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mark E. Mallett wrote:
> On Wed, Mar 17, 2004 at 07:23:32AM -0800, Hallam-Baker, Phillip wrote:
> 
> A couple of random remarks from a very cursory reading:
> 
> 
>>          There is no difficulty in ensuring that accreditation providers are 
>>          accountable to email recipients. An accreditation authority that 
>>          provides incorrect accreditation will soon be ignored.
> 
> Pretty bold assertion :-)
> It hasn't held true with some DNSBL services.  Among other reasons is
> the wide variety of definitions of "incorrect," as well as extremely
> polar opinions about listing criteria, remedies, responsibility, et al.

The key difference from blacklists is that blacklists do not ask ISPs 
whether they want to be listed. Here, the sender actively goes to a 
provider and signs up, and then indicates his accredidation in some 
protocol.

My issue with this is something else - if all of this becomes prevalent 
enough, aren't we essentially raising a barrier of entry for new domains 
on the Internet? Doesn't such accredidation service essentially become a 
gatekeeper for the Internet?

Yes, I read Microsoft's proposals about different types of tricks for 
different domains, for example hash cash-type puzzles for smaller 
domains in lieu of accreditation. I am still not convinced that a given 
ISP will bother with supporting both accreditation and hash cash, they 
just might take the easy way out and only support accreditation services.

Yakov

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



From exim@www1.ietf.org  Thu Mar 18 14:19:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01625
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 14:19:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B432J-0003fu-Cv
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 14:18:35 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IJIZUa014124
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 14:18:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B432J-0003fj-16
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 14:18:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01533
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 14:18:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B432G-0004IJ-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 14:18:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B431L-0004Db-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 14:17:35 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B430i-0004Be-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 14:16:56 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B430P-0003Uu-GM; Thu, 18 Mar 2004 14:16:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B42zO-0003TT-Rf
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 14:15:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01435
	for <asrg@ietf.org>; Thu, 18 Mar 2004 14:15:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B42zM-000484-00
	for asrg@ietf.org; Thu, 18 Mar 2004 14:15:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B42yT-00046Q-00
	for asrg@ietf.org; Thu, 18 Mar 2004 14:14:38 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B42yC-00044M-00
	for asrg@ietf.org; Thu, 18 Mar 2004 14:14:21 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2IJEJf7028257;
        Thu, 18 Mar 2004 11:14:19 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GYBNT0D6>; Thu, 18 Mar 2004 11:14:28 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E5DBA60@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Mark E. Mallett'" <mem@mv.mv.com>,
        "Hallam-Baker, Phillip"
	 <pbaker@verisign.com>
Cc: asrg@ietf.org
Subject: RE: [Asrg] Accreditation Mechanism Proposal
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 11:14:26 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

> You mean when querying the accreditation service?
> How would this interact with Verisign's publishing of wildcard
> records (e.g. if the accreditation service goes out of business and
> its domain name is revoked)? 

Given that 20 odd TLDs publish wildcard records today this looks
like a problem regardless of what might happen in any given domain.

This is what happens when you have what the DNS folks call a DNS
hack.


> This goal of indirect identification of accreditation services seems
> like a positive thing.  Has there been any attempt to analyze the
> additional overhead?

I don't think it is large. You simply keep a log of the citations
of unknown accreditation services. You feed it back in every now
and again and look to see if you should track them.


> Also, as with SPF et al there is the question of feedback from the
> recipient: e.g. one might want to have the ability for the recipient
> to publish information about what that recipient requires of a
> sender.  Some unified scheme might be useful, like:
> 
>     ( Sender domain must publish SPF OR DMP
>     AND Sender must be accredited by any two of {abc, def, ghi, xyz}
>     AND Sender IP must publish MTAMark)
>     OR  ( Sender must accept address verification probe )
> 
> but that's probably a whole nother effort.

I think that is essentially mirroring the WS-Policy work in
web services land.


> Pretty bold assertion :-)
> It hasn't held true with some DNSBL services.  Among other reasons is
> the wide variety of definitions of "incorrect," as well as extremely
> polar opinions about listing criteria, remedies, 
> responsibility, et al.

That why I want to avoid static listing. The accreditation services
must be accountable.


> Red flag:  better would be "these bits are reserved and must be set
> to zero."  If you don't guarantee they are zero from the outset,
> it's hard to make sure you can use them in the future.

I don't want acceptors to assume that they will be zero. I want 
them to be ignored.


> Do you really anticipate using NAPTR?

Hey look who is the co-chair of the MARID-WG...

		Phill

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



From exim@www1.ietf.org  Thu Mar 18 15:06:04 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04698
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 15:06:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B43lp-0002sa-F4
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 15:05:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IK5bwn011061
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 15:05:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B43lp-0002sF-7S
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 15:05:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04635
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 15:05:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B43lm-0007j3-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 15:05:34 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B43kv-0007fV-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 15:04:41 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B43k8-0007cj-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 15:03:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B43jJ-0001Br-Mu; Thu, 18 Mar 2004 15:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B43ir-0000io-70
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 15:02:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04221
	for <asrg@ietf.org>; Thu, 18 Mar 2004 15:02:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B43io-0007WB-00
	for asrg@ietf.org; Thu, 18 Mar 2004 15:02:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B43hq-0007Rw-00
	for asrg@ietf.org; Thu, 18 Mar 2004 15:01:31 -0500
Received: from mail3.panix.com ([166.84.1.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B43gu-0007Nf-00
	for asrg@ietf.org; Thu, 18 Mar 2004 15:00:32 -0500
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail3.panix.com (Postfix) with ESMTP id 105699876E
	for <asrg@ietf.org>; Thu, 18 Mar 2004 15:00:18 -0500 (EST)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i2IK0Ic23679;
	Thu, 18 Mar 2004 15:00:18 -0500 (EST)
Message-Id: <200403182000.i2IK0Ic23679@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <4059E282.3030704@solidmatrix.com> (message from Yakov
	Shafranovich on Thu, 18 Mar 2004 12:55:14 -0500)
Subject: Re: [Asrg] Accreditation Mechanism Proposal
References: <C6DDA43B91BFDA49AA2F1E473732113E0A19E4@mou1wnexm05.vcorp.ad.vrsn.com> <20040318163751.GB12873@iridium.mv.net> <4059E282.3030704@solidmatrix.com>
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 15:00:18 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Yakov Shafranovich <research@solidmatrix.com> wrote:

> Yes, I read Microsoft's proposals about different types of tricks
> for different domains, for example hash cash-type puzzles for
> smaller domains in lieu of accreditation. I am still not convinced
> that a given ISP will bother with supporting both accreditation and
> hash cash, they just might take the easy way out and only support
> accreditation services.

So somebody will run an "accreditation" service that says "they
answered a hash-cash request for your message".  Yes, this requires
passing the Message-ID around to prevent a DoS attack, and probably
some other tricks; but there's nothing preventing it from happening.

Seth

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



From exim@www1.ietf.org  Thu Mar 18 18:23:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16279
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 18:23:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B46qb-0004t2-9S
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 18:22:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2INMjiL018780
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 18:22:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B46qb-0004sZ-0j
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 18:22:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16269
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 18:22:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B46qY-0006Wn-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 18:22:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B46pf-0006Uf-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 18:21:47 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B46p5-0006Rr-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 18:21:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B46ny-0004fe-Lu; Thu, 18 Mar 2004 18:20:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B46a6-0007vM-PC
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 18:05:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14698
	for <asrg@ietf.org>; Thu, 18 Mar 2004 18:05:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B46a3-0005Ur-00
	for asrg@ietf.org; Thu, 18 Mar 2004 18:05:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B46Z9-0005Rz-00
	for asrg@ietf.org; Thu, 18 Mar 2004 18:04:44 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B46YM-0005PZ-00
	for asrg@ietf.org; Thu, 18 Mar 2004 18:03:54 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B46YK-0005W6-00; Thu, 18 Mar 2004 18:03:52 -0500
Received: from [68.244.172.97] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B46YJ-00065U-00; Thu, 18 Mar 2004 18:03:52 -0500
Message-ID: <405A2ABA.3070006@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] 3 Proof of consent spec
References: <C6DDA43B91BFDA49AA2F1E473732113E0A19FC@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A19FC@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 18:03:22 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hallam-Baker, Phillip wrote:
>             3.1 Initialization 
>              
>             The incoming mail server establishes a shared secret k. In 
>             the case that there are multiple incoming servers the 
>             shared secret may be established manually or by means of 
>             some form of key agreement protocol using public key based 
>             credentials. 
>              

This shared secret - who is established with?

Yakov

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



From exim@www1.ietf.org  Thu Mar 18 19:13:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18748
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 19:13:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B47cz-0000QY-B9
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 19:12:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2J0CjUN001636
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 19:12:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B47cz-0000QJ-4z
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 19:12:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18695
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 19:12:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B47cx-0002CW-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 19:12:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B47bx-00025Q-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 19:11:41 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B47b1-00020W-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 19:10:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B47aN-0008Qr-Cc; Thu, 18 Mar 2004 19:10:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B47a2-0008JL-5j
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 19:09:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18481
	for <asrg@ietf.org>; Thu, 18 Mar 2004 19:09:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B47Zy-0001vo-00
	for asrg@ietf.org; Thu, 18 Mar 2004 19:09:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B47Z0-0001sZ-00
	for asrg@ietf.org; Thu, 18 Mar 2004 19:08:38 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B47Y8-0001oT-00
	for asrg@ietf.org; Thu, 18 Mar 2004 19:07:45 -0500
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (mailer3.verisign.com [65.205.251.55])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2J07hDD010391;
        Thu, 18 Mar 2004 16:07:43 -0800 (PST)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <HCHBGLD2>; Thu, 18 Mar 2004 16:07:52 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E5DBA65@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Yakov Shafranovich'" <research@solidmatrix.com>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: asrg@ietf.org
Subject: RE: [Asrg] 3 Proof of consent spec
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 16:07:42 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

> Hallam-Baker, Phillip wrote:
> >             3.1 Initialization 
> >              
> >             The incoming mail server establishes a shared 
> secret k. In 
> >             the case that there are multiple incoming servers the 
> >             shared secret may be established manually or by 
> means of 
> >             some form of key agreement protocol using 
> public key based 
> >             credentials. 
> >              
> 
> This shared secret - who is established with?

Any other incomming mail server. I guess it could be reworded.


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



From exim@www1.ietf.org  Thu Mar 18 23:55:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00265
	for <asrg-archive@odin.ietf.org>; Thu, 18 Mar 2004 23:55:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4C2F-0000D5-WD
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 23:55:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2J4t7Xv000803
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 23:55:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4C2F-0000Cs-Gu
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 23:55:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00241
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 23:55:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4C2D-0006mb-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 23:55:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4C1C-0006gr-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 23:54:03 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4C0S-0006cT-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 23:53:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4C0D-0008P4-2A; Thu, 18 Mar 2004 23:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4BzK-0008OA-3h
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 23:52:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA00026
	for <asrg@ietf.org>; Thu, 18 Mar 2004 23:52:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4BzH-0006Tb-00
	for asrg@ietf.org; Thu, 18 Mar 2004 23:52:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4ByJ-0006Ow-00
	for asrg@ietf.org; Thu, 18 Mar 2004 23:51:04 -0500
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4BxM-0006FY-00
	for asrg@ietf.org; Thu, 18 Mar 2004 23:50:04 -0500
Received: from [192.168.0.7] (h00095b86f221.ne.client2.attbi.com[24.61.46.50])
          by comcast.net (rwcrmhc12) with SMTP
          id <2004031904493401400esi3je>; Fri, 19 Mar 2004 04:49:34 +0000
Message-Id: <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com>
X-Habeas-Swe-6: email in exchange for a license for this Habeas
X-Habeas-Swe-3: like Habeas SWE (tm)
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
X-Habeas-Swe-8: Message (HCM) and not spam. Please report use of this
From: mathew <meta@pobox.com>
X-Habeas-Swe-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-Swe-2: brightly anticipated
In-Reply-To: <401850EC.3080803@solidmatrix.com>
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com>
To: asrg@ietf.org
X-Habeas-Swe-7: warrant mark warrants that this is a Habeas Compliant
Mime-Version: 1.0 (Apple Message framework v613)
X-Habeas-Swe-4: Copyright 2002 Habeas (tm) 
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-2-432838717; protocol="application/pkcs7-signature"
X-Habeas-Swe-1: winter into spring
X-Habeas-Swe-9: mark in spam to <http://www.habeas.com/report/>.
X-Mailer: Apple Mail (2.613)
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 23:49:29 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--Apple-Mail-2-432838717
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

On Jan 28, 2004, at 19:16, Yakov Shafranovich wrote:
> Any ideas on what is the percentage of users that do not have S/MIME? 
> If MSFT, Mozilla, etc. and the other MUAs cover a virtual majority of 
> the market, and would cover a majority of users affected by the 
> phishing attacks, why aren't the banks deploying it?

Speaking as someone who's actually gone to the trouble of getting 
S/MIME set up... I can think of at least two reasons:

1. It's a pain in the ass to set up. You need to go through an 
unpleasant
    bureaucratic procedure to get your certificate, and there are 
apparently
    half a dozen different file formats and obscure tools needed to 
convert
    between them.

2. It doesn't work. Just because client A and client B both claim to 
support
    S/MIME, doesn't appear to mean that client A and client B can 
exchange
    messages.

In particular, if I sent myself an S/MIME message from work using Lotus 
Notes, Apple Mail can't read it. However, mail from Apple Mail to Lotus 
Notes verifies OK. I'm trying to interest our QA department in further 
investigation... Point is, it's still a rather flaky technology.


mathew
-- 
<URL:http://www.pobox.com/~meta/>
--Apple-Mail-2-432838717
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGEDCCAskw
ggIyoAMCAQICAwtCvTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDMxMjAzMTUwOTU3WhcNMDQxMjAyMTUwOTU3WjBAMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMR0wGwYJKoZIhvcNAQkBFg5tZXRhQHBvYm94LmNvbTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANA40G+RMi0LMG++Lz6J4LpIaXkydRxJoLjz
9EPfZGLn6dPBumvzLVWDaQrOshYuyViOW+oPk62xz6HBnarbOX3VoiFVyGCjqkZz+TToHDDlya/z
D8l/WF92nvsEPFPKE6Fw/Lg13/g9zzBlxrjwW98bL6dI1tKvdokMH91++35sC0Yu5oZjuBF4ydUA
1n7pX2KgEDhRRP5b/RhQPrdpbZhO5fwzthiD0VlCG9zkloNJ8GOFxMFd2lpVpV1ISySCHYwEtA1n
zxR7Kq4oRaMvAodHj8NHRPDjE+vyALzi0mCZ+JlQAyKr+Li5YvKZNRobyYBQGLLOyt31ZAj9vfSS
g2cCAwEAAaMrMCkwGQYDVR0RBBIwEIEObWV0YUBwb2JveC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQQFAAOBgQCVJDuVViVm9t4++qdMFmiF4yfAowCy3/bauIAcxAJXvd21LnorWF+49YJk
jBZO74MDPrsYb5M9ybKMy04vxNuXXHM9TVLUWJjz5PUCcaNIj9DqGIW9eAPWj/Pvn6j5qSP8OcoK
mwwrKcurmSi+sJqajLjET0wzsuvgRFNE4pkOyDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEF
BQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg
VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24g
U2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAw
MDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3Vs
dGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWlu
ZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me
7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r
1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCB
kTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3Rl
LmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAg
pB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPq
Cy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUa
C4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx
0x1G/11fZU8xggLnMIIC4wIBATBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u
c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz
dWluZyBDQQIDC0K9MAkGBSsOAwIaBQCgggFTMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJ
KoZIhvcNAQkFMQ8XDTA0MDMxOTA0NDkzMFowIwYJKoZIhvcNAQkEMRYEFGqGUerHtrCHHC6xvdcV
bVNZqfAdMHgGCSsGAQQBgjcQBDFrMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBD
b25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAgMLQr0wegYLKoZIhvcNAQkQAgsxa6BpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK
ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQQIDC0K9MA0GCSqGSIb3DQEBAQUABIIBALoN2zHjtQovduHcFfSY
cpVYzmtlJnLC4TZp9Cz6AcRWa+9m0Dq8P83ABVY3oiwPCJkXcNggYylxyeQwisjmCv0fRq+7/29z
DbQBa++4DMzfr1M4loYtGeU9Oo8wCQaLbgnH59NjtX9Ivu73taDcR64eT04r8JxJvcAy9XKMAS45
GOZRplsAelIgNgMMLUnVsjgPE0Pi1E4gUP57jBxdm6hSuLBemL1uMM+xZbPZzCNK+axBW7itNY8T
cYOECCAzejrgsWyJTNeSgmNBXqDK6zFyOJZbMwJWP7B9vatL+gsIoN+WN8HFinBHus2igKFzbMez
b5sXN9AQCcgSzm9f45YAAAAAAAA=

--Apple-Mail-2-432838717--


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



From exim@www1.ietf.org  Fri Mar 19 08:16:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02008
	for <asrg-archive@odin.ietf.org>; Fri, 19 Mar 2004 08:16:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4JrG-0008QY-6y
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 08:16:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JDGIY3032390
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 08:16:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4JrG-0008QL-1z
	for asrg-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 08:16:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02002
	for <asrg-web-archive@ietf.org>; Fri, 19 Mar 2004 08:16:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4JrF-0006gp-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 08:16:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4JqG-0006cy-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 08:15:19 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4Jpg-0006YK-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 08:14:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Jp3-0008Dk-DA; Fri, 19 Mar 2004 08:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4JoV-0008CD-3C
	for asrg@optimus.ietf.org; Fri, 19 Mar 2004 08:13:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA01820
	for <asrg@ietf.org>; Fri, 19 Mar 2004 08:13:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4JoU-0006SO-00
	for asrg@ietf.org; Fri, 19 Mar 2004 08:13:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4JnU-0006NI-00
	for asrg@ietf.org; Fri, 19 Mar 2004 08:12:27 -0500
Received: from svrmail.roving.com ([208.198.98.29])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4Jma-0006Dy-00
	for asrg@ietf.org; Fri, 19 Mar 2004 08:11:28 -0500
Received: by mail.constantcontact.com with Internet Mail Service (5.5.2653.19)
	id <GV5XYFHA>; Fri, 19 Mar 2004 08:11:58 -0500
Message-ID: <E48D24225D499E44BE0256A68B615E62093915@mail.constantcontact.com>
From: "Olson, Margaret" <molson@roving.com>
To: "'Yakov Shafranovich'" <research@solidmatrix.com>
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>, asrg@ietf.org
Subject: RE: [Asrg] Accreditation Mechanism Proposal
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C40DB3.BE1830E0"
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/mail-archive/working-groups/asrg/>
Date: Fri, 19 Mar 2004 08:11:51 -0500

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C40DB3.BE1830E0
Content-Type: text/plain


>My issue with this is something else - if all of this becomes prevalent 
>enough, aren't we essentially raising a barrier of entry for new domains 
>on the Internet? Doesn't such accredidation service essentially become a 
>gatekeeper for the Internet?

My belief - which makes some assumptions about how accreditation is
implemented - is that the barrier to running your own mail server will go
up, but not necessarily having your own domain. Many people today have a
domain and outsource all aspects of running it to some other organization
(or organizations). By aggregating small domains an outsource provider
should be able to keep the prices close to what they are today. 

One thing that I noticed that has not been widely addresses in accreditation
discussions, and which I think should be addressed, is controlling the
reward side of the spam equation. If you can accredit the mail servers and
the sending domains separately, then a receiving system can reasonably know
that mail originating from clients of example.com from the set of servers at
"small.example.com" are limited to some number of messages per day. 

If you can control the reward side of the equation, then sending domains
using outsourced providers don't need much in the way of an accreditation -
they just need to state "we use small.example.com", which for a small sender
tells the receiver something really useful. You can also envision something
along these lines without actually outsourcing - an ISP that is accredited
to limit SMTP traffic coming out of their network on a per client basis.

This does presume that there is a specific accreditation for mail service
providers of all kinds. There are other types of organizations that could
also benefit from industry specific accreditations as well - financial
organizations and political/free speech organizations spring to mind
immediately.

Just to be clear, I am not assuming that the accrediting agency attempt to
guess volume when accrediting and monitoring organizations that run mail
servers. I'm assuming they have a contract that permits them to walk in to
the network center and investigate when ever they want, and some sort of
audit process.

What I have outlined here primarily addresses the needs small commercial
domains that are already outsourcing their mail services for a variety of
technical and business reasons. It does not address the small mail or list
server run by a knowledgeable individual. Do the puzzle type solutions cover
this case? 

Margaret. 

------_=_NextPart_001_01C40DB3.BE1830E0
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [Asrg] Accreditation Mechanism Proposal</TITLE>
</HEAD>
<BODY>
<BR>

<P><FONT SIZE=3D2>&gt;My issue with this is something else - if all of =
this becomes prevalent </FONT>
<BR><FONT SIZE=3D2>&gt;enough, aren't we essentially raising a barrier =
of entry for new domains </FONT>
<BR><FONT SIZE=3D2>&gt;on the Internet? Doesn't such accredidation =
service essentially become a </FONT>
<BR><FONT SIZE=3D2>&gt;gatekeeper for the Internet?</FONT>
</P>

<P><FONT SIZE=3D2>My belief - which makes some assumptions about how =
accreditation is implemented - is that the barrier to running your own =
mail server will go up, but not necessarily having your own domain. =
Many people today have a domain and outsource all aspects of running it =
to some other organization (or organizations). By aggregating small =
domains an outsource provider should be able to keep the prices close =
to what they are today. </FONT></P>

<P><FONT SIZE=3D2>One thing that I noticed that has not been widely =
addresses in accreditation discussions, and which I think should be =
addressed, is controlling the reward side of the spam equation. If you =
can accredit the mail servers and the sending domains separately, then =
a receiving system can reasonably know that mail originating from =
clients of example.com from the set of servers at =
&quot;small.example.com&quot; are limited to some number of messages =
per day. </FONT></P>

<P><FONT SIZE=3D2>If you can control the reward side of the equation, =
then sending domains using outsourced providers don't need much in the =
way of an accreditation - they just need to state &quot;we use =
small.example.com&quot;, which for a small sender tells the receiver =
something really useful. You can also envision something along these =
lines without actually outsourcing - an ISP that is accredited to limit =
SMTP traffic coming out of their network on a per client =
basis.</FONT></P>

<P><FONT SIZE=3D2>This does presume that there is a specific =
accreditation for mail service providers of all kinds. There are other =
types of organizations that could also benefit from industry specific =
accreditations as well - financial organizations and political/free =
speech organizations spring to mind immediately.</FONT></P>

<P><FONT SIZE=3D2>Just to be clear, I am not assuming that the =
accrediting agency attempt to guess volume when accrediting and =
monitoring organizations that run mail servers. I'm assuming they have =
a contract that permits them to walk in to the network center and =
investigate when ever they want, and some sort of audit =
process.</FONT></P>

<P><FONT SIZE=3D2>What I have outlined here primarily addresses the =
needs small commercial domains that are already outsourcing their mail =
services for a variety of technical and business reasons. It does not =
address the small mail or list server run by a knowledgeable =
individual. Do the puzzle type solutions cover this case? </FONT></P>

<P><FONT SIZE=3D2>Margaret. </FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C40DB3.BE1830E0--

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



From exim@www1.ietf.org  Fri Mar 19 08:22:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02233
	for <asrg-archive@odin.ietf.org>; Fri, 19 Mar 2004 08:22:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Jwa-0000IB-Fa
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 08:21:49 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JDLmte001117
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 08:21:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Jwa-0000Hw-AX
	for asrg-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 08:21:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02205
	for <asrg-web-archive@ietf.org>; Fri, 19 Mar 2004 08:21:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4JwZ-0007DI-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 08:21:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4JvP-000752-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 08:20:38 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4Jtu-0006uo-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 08:19:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Jtt-00005E-4t; Fri, 19 Mar 2004 08:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4JtD-0008Ul-Ik
	for asrg@optimus.ietf.org; Fri, 19 Mar 2004 08:18:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02081
	for <asrg@ietf.org>; Fri, 19 Mar 2004 08:18:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4JtC-0006sb-00
	for asrg@ietf.org; Fri, 19 Mar 2004 08:18:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4JsJ-0006mZ-00
	for asrg@ietf.org; Fri, 19 Mar 2004 08:17:26 -0500
Received: from argon.connectinternetsolutions.com ([193.110.243.33] helo=argon.connect.org.uk)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4Jr8-0006gA-00
	for asrg@ietf.org; Fri, 19 Mar 2004 08:16:10 -0500
Received: from mmail by argon.connect.org.uk with local (connectmail/exim)
	id 1B4Jr1-0005qw-9p; Fri, 19 Mar 2004 13:16:03 +0000
Subject: Re: [Asrg] CallerID and disposable addresses
To: "joe"  <joe_kern_1001@hotmail.com>
From: "Jon Kyme" <jrk@merseymail.com>
Cc: "ASRG" <asrg@ietf.org>
X-Mailer: [ConnectMail 3.13.0]
X-connectmail-Originating-IP: 172.25.243.3
Message-Id: <E1B4Jr1-0005qw-9p@argon.connect.org.uk>
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/mail-archive/working-groups/asrg/>
Date: Fri, 19 Mar 2004 13:16:03 +0000

Joe>
> While CallerID sounds like a simple solution, it may in fact cripple
> popular anti-spam measures such as third party disposable email address
> provider.
> A sender will not be able to use a disposable email address as his or
> her sender's address if the domain of the disposable forwarding server
> is different from the SMTP server used for sending out the mail.
> 

Is the controller of the forwarder domain able to publish 0/0 for <out/> or
some other wildcard sort of thing?





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



From exim@www1.ietf.org  Fri Mar 19 12:48:49 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12493
	for <asrg-archive@odin.ietf.org>; Fri, 19 Mar 2004 12:48:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4O6Y-0001gf-8R
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 12:48:22 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JHmMLA006479
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 12:48:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4O6Y-0001gQ-0B
	for asrg-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 12:48:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12465
	for <asrg-web-archive@ietf.org>; Fri, 19 Mar 2004 12:48:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4O6W-0006DA-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 12:48:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4O5X-00068X-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 12:47:20 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4O4u-00063d-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 12:46:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4O4H-0001Pg-TL; Fri, 19 Mar 2004 12:46:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4O3a-0001Oa-QR
	for asrg@optimus.ietf.org; Fri, 19 Mar 2004 12:45:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12392
	for <asrg@ietf.org>; Fri, 19 Mar 2004 12:45:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4O3Z-0005yX-00
	for asrg@ietf.org; Fri, 19 Mar 2004 12:45:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4O2c-0005uO-00
	for asrg@ietf.org; Fri, 19 Mar 2004 12:44:19 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4O1k-0005qI-00
	for asrg@ietf.org; Fri, 19 Mar 2004 12:43:24 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2JHhNEu015636;
        Fri, 19 Mar 2004 09:43:24 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GYBNXTRJ>; Fri, 19 Mar 2004 09:43:23 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E5DBA6E@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Olson, Margaret'" <molson@roving.com>,
        "'Yakov Shafranovich'"
	 <research@solidmatrix.com>
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>, asrg@ietf.org
Subject: RE: [Asrg] Accreditation Mechanism Proposal
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C40DD9.ABDECE35"
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/mail-archive/working-groups/asrg/>
Date: Fri, 19 Mar 2004 09:43:22 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,HTML_20_30,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C40DD9.ABDECE35
Content-Type: text/plain;
	charset="iso-8859-1"

 

 


>My issue with this is something else - if all of this becomes prevalent 
>enough, aren't we essentially raising a barrier of entry for new domains 
>on the Internet? Doesn't such accredidation service essentially become a 
>gatekeeper for the Internet? 

My belief - which makes some assumptions about how accreditation is
implemented - is that the barrier to running your own mail server will go
up, but not necessarily having your own domain. Many people today have a
domain and outsource all aspects of running it to some other organization
(or organizations). By aggregating small domains an outsource provider
should be able to keep the prices close to what they are today. 

I can assure folk I am not in the business of raising the barrier to people
having their own domain names. The number of domain name owners running
their own mail servers is vanishingly small.

Actually I think Margaret is wrong here. With accreditation the barrier to
running your own mail server goes down dramatically, thats the whole idea.
At the moment the biggest cost you have in running your mail service is
getting your name onto whitelists after some totally unaccountable blacklist
listed you because somebody did not happen to like your ISP.

I don't think that very many people are going to need the expensive high end
accreditation services that people like Margaret are using. If you are not a
bulk email sender the cost of accreditation should not be an issue. Sure it
will cost a lot to police the bulk senders, but not the people who don't do
anything that looks spammy.

        Phill


------_=_NextPart_001_01C40DD9.ABDECE35
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Asrg] Accreditation Mechanism Proposal</TITLE>

<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT face=Arial color=#0000ff size=2></FONT>&nbsp;</DIV>
<BLOCKQUOTE dir=ltr 
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
  <DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma 
  size=2></FONT>&nbsp;</DIV><BR>
  <P><FONT size=2>&gt;My issue with this is something else - if all of this 
  becomes prevalent </FONT><BR><FONT size=2>&gt;enough, aren't we essentially 
  raising a barrier of entry for new domains </FONT><BR><FONT size=2>&gt;on the 
  Internet? Doesn't such accredidation service essentially become a 
  </FONT><BR><FONT size=2>&gt;gatekeeper for the Internet?</FONT> </P>
  <P><FONT size=2>My belief - which makes some assumptions about how 
  accreditation is implemented - is that the barrier to running your own mail 
  server will go up, but not necessarily having your own domain. Many people 
  today have a domain and outsource all aspects of running it to some other 
  organization (or organizations). By aggregating small domains an outsource 
  provider should be able to keep the prices close to what they are today.<SPAN 
  class=711183317-19032004><FONT face=Arial 
  color=#0000ff>&nbsp;</FONT></SPAN></FONT></P></BLOCKQUOTE>
<P dir=ltr><FONT size=2><SPAN class=711183317-19032004><FONT face=Arial 
color=#0000ff>I can assure folk I am not in the business of raising the barrier 
to people having their own domain names. The number of domain name owners 
running their own mail servers is vanishingly small.</FONT></SPAN></FONT></P>
<P dir=ltr><FONT size=2><SPAN class=711183317-19032004><FONT face=Arial 
color=#0000ff>Actually I think Margaret is wrong here. With accreditation the 
barrier to running your own mail server goes down dramatically, thats the whole 
idea. </FONT>&nbsp;<FONT face=Arial color=#0000ff>At the moment the biggest cost 
you have in running your mail service is getting your name onto whitelists after 
some totally unaccountable blacklist listed you because somebody did not happen 
to like your ISP.</FONT></SPAN></FONT></P>
<P dir=ltr><FONT face=Arial color=#0000ff size=2><SPAN 
class=711183317-19032004>I don't think that very many people are going to need 
the expensive high end accreditation services that people like Margaret are 
using. If you are not a bulk email sender the cost of accreditation should not 
be an issue. Sure it will cost a lot to police the bulk senders, but not the 
people who don't do anything that looks spammy.</SPAN></FONT></P>
<P dir=ltr><FONT face=Arial color=#0000ff size=2><SPAN 
class=711183317-19032004>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Phill</SPAN></FONT></P></BODY></HTML>

------_=_NextPart_001_01C40DD9.ABDECE35--

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



From exim@www1.ietf.org  Fri Mar 19 14:15:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16501
	for <asrg-archive@odin.ietf.org>; Fri, 19 Mar 2004 14:15:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4PSn-0007KE-2l
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 14:15:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JJFPRZ028159
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 14:15:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4PSm-0007K6-Ql
	for asrg-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 14:15:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16482
	for <asrg-web-archive@ietf.org>; Fri, 19 Mar 2004 14:15:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4PSk-0006e6-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 14:15:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4PRw-0006Yv-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 14:14:33 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4PR9-0006TD-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 14:13:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4PQS-00075A-S4; Fri, 19 Mar 2004 14:13:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4PPt-00073F-JX
	for asrg@optimus.ietf.org; Fri, 19 Mar 2004 14:12:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16377
	for <asrg@ietf.org>; Fri, 19 Mar 2004 14:12:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4PPr-0006Le-00
	for asrg@ietf.org; Fri, 19 Mar 2004 14:12:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4PP1-0006GL-00
	for asrg@ietf.org; Fri, 19 Mar 2004 14:11:31 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4POU-0006AJ-00
	for asrg@ietf.org; Fri, 19 Mar 2004 14:10:58 -0500
Received: from Royer.com (69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2JJAEev031653
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Fri, 19 Mar 2004 11:10:16 -0800
Message-ID: <405B4591.4080808@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com> <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com>
In-Reply-To: <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms080200080104000100040301"
X-Royer.com-MailScanner-Information: Please contact SiteAdmin@Royer.com for more information
X-Royer.com-MailScanner: Found to be clean
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/mail-archive/working-groups/asrg/>
Date: Fri, 19 Mar 2004 12:10:09 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms080200080104000100040301
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



mathew wrote:

> On Jan 28, 2004, at 19:16, Yakov Shafranovich wrote:
>
>> Any ideas on what is the percentage of users that do not have S/MIME? 
>> If MSFT, Mozilla, etc. and the other MUAs cover a virtual majority of 
>> the market, and would cover a majority of users affected by the 
>> phishing attacks, why aren't the banks deploying it?
>
>
> Speaking as someone who's actually gone to the trouble of getting 
> S/MIME set up... I can think of at least two reasons:
>
> 1. It's a pain in the ass to set up. You need to go through an unpleasant
>    bureaucratic procedure to get your certificate, and there are 
> apparently
>    half a dozen different file formats and obscure tools needed to 
> convert
>    between them. 

Bad documentation from your vendors have nothing to do with S/MIME.

>
> 2. It doesn't work. Just because client A and client B both claim to 
> support
>    S/MIME, doesn't appear to mean that client A and client B can exchange
>    messages. 

A popular vendor broke their implementation of S/MIME, that was fixed years
ago and a simple upgrade will fix that.

No matter what solutions are chosen  to combat spam, the vendor will have
to implement it correctly or things will not work.

S/MIME is not broken, the vendors may have broken implementations.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms080200080104000100040301
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzE5MTkxMDA5WjAjBgkqhkiG9w0BCQQxFgQUOrTXiYlmGvxiELiKJlmT
73AhJFQwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAlqqmuhcCj/n2EcX4GhDoi8FK0qaAr7bY7a0xL6w3wGjRqZZ/RJi2QVP7BI0lo6Sk
c5CEqhjbh2ThlZcOW1dmaKDs2vIiVENjfvO4wYxldJxvRs4kj+pAh7D/GjtmnvPpRXjmpd6n
3CFHNxwk3yWOo7QNCUY7U8LJMzFbuyhIDIjQuzm9Cty3EqKcepga6Sztduu1Yd1qYyaq0uJC
1matzv3Lvc0yM7b8brT0crs6v6e4XY+67LrPsG6EdJQJM7+MaZjvzlE2kvJFQsv+I7wYg7u2
tRNYGHHdtjlPsXe/ZvcsYGWqvOEyoZ0f+6uOoS19sa/rlB5i76n4fxqd87MYkAAAAAAAAA==
--------------ms080200080104000100040301--


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



From exim@www1.ietf.org  Fri Mar 19 16:06:52 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22642
	for <asrg-archive@odin.ietf.org>; Fri, 19 Mar 2004 16:06:52 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4RCB-0007XT-VH
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 16:06:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JL6N8j028979
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 16:06:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4RCB-0007XK-OK
	for asrg-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 16:06:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22542
	for <asrg-web-archive@ietf.org>; Fri, 19 Mar 2004 16:06:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4RCA-0001aq-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 16:06:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4RBI-0001W0-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 16:05:28 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4RAK-0001R8-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 16:04:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4R9u-0007GA-G6; Fri, 19 Mar 2004 16:04:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4R9G-0007FQ-EB
	for asrg@optimus.ietf.org; Fri, 19 Mar 2004 16:03:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22339
	for <asrg@ietf.org>; Fri, 19 Mar 2004 16:03:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4R9E-0001LZ-00
	for asrg@ietf.org; Fri, 19 Mar 2004 16:03:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4R8L-0001Hq-00
	for asrg@ietf.org; Fri, 19 Mar 2004 16:02:26 -0500
Received: from mail.dysanalytics.com ([68.162.202.226] helo=galileo.dysanalytics.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1B4R7Z-000180-00
	for asrg@ietf.org; Fri, 19 Mar 2004 16:01:37 -0500
Received: from galileo.dysanalytics.com ([192.168.100.3])
 by galileo.dysanalytics.com (SAVSMTP 3.1.1.32) with SMTP id M2004031916005027997
 for <asrg@ietf.org>; Fri, 19 Mar 2004 16:00:50 -0500
From: Dave Durfee <ddurfee@dysanalytics.com>
To: asrg@ietf.org
Message-ID: <OFA74513B2.543587D2-ON85256E5C.007363F2-85256E5C.007363F2@DYSAnalytics.com>
X-MIMETrack: Serialize by Router on Mail/DYS Analytics/US(Release 6.5|September 26, 2003) at
 03/19/2004 04:00:50 PM
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Subject: [Asrg] Dave Durfee is out of the office.
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/mail-archive/working-groups/asrg/>
Date: Fri, 19 Mar 2004 16:00:22 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60





I will be out of the office starting  03/18/2004 and will not return until
03/26/2004.

I will respond to your message when I return.


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



From exim@www1.ietf.org  Fri Mar 19 16:54:59 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26670
	for <asrg-archive@odin.ietf.org>; Fri, 19 Mar 2004 16:54:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Rwl-0003n9-Pv
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 16:54:32 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JLsVsd014571
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 16:54:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Rwl-0003mw-Lf
	for asrg-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 16:54:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26663
	for <asrg-web-archive@ietf.org>; Fri, 19 Mar 2004 16:54:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4Rwj-0007c3-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 16:54:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4Rvn-0007XB-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 16:53:31 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4RvS-0007SE-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 16:53:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4RvJ-0003aU-Br; Fri, 19 Mar 2004 16:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Ruf-0003Ty-Cl
	for asrg@optimus.ietf.org; Fri, 19 Mar 2004 16:52:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26535
	for <asrg@ietf.org>; Fri, 19 Mar 2004 16:52:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4Rud-0007PF-00
	for asrg@ietf.org; Fri, 19 Mar 2004 16:52:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4Rte-0007Hq-00
	for asrg@ietf.org; Fri, 19 Mar 2004 16:51:19 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4Rsf-00077g-00
	for asrg@ietf.org; Fri, 19 Mar 2004 16:50:17 -0500
Received: from mbaugher-w2k07.cisco.com (sjc-vpn1-882.cisco.com [10.21.99.114])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i2JLnh8Q008189;
	Fri, 19 Mar 2004 13:49:44 -0800 (PST)
Message-Id: <6.0.0.22.2.20040319134808.04490900@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
From: Mark Baugher <mbaugher@cisco.com>
Subject: RE: [Asrg] 3 Proof of consent spec
Cc: asrg@ietf.org
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E5DBA65@mou1wnexm05.vcorp.a
 d.vrsn.com>
References: <C6DDA43B91BFDA49AA2F1E473732113E5DBA65@mou1wnexm05.vcorp.ad.vrsn.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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/mail-archive/working-groups/asrg/>
Date: Fri, 19 Mar 2004 13:49:42 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

At 04:07 PM 3/18/2004, Hallam-Baker, Phillip wrote:
> > Hallam-Baker, Phillip wrote:
> > >             3.1 Initialization
> > >
> > >             The incoming mail server establishes a shared
> > secret k. In
> > >             the case that there are multiple incoming servers the
> > >             shared secret may be established manually or by
> > means of
> > >             some form of key agreement protocol using
> > public key based
> > >             credentials.

I know of only one IETF key agreement protocol that establishes a shared 
key among n>1 parties and that is GDOI.  I don't think this is what you 
have in mind, though.

Mark

> > >
> >
> > This shared secret - who is established with?
>
>Any other incomming mail server. I guess it could be reworded.
>
>
>_______________________________________________
>Asrg mailing list
>Asrg@ietf.org
>https://www1.ietf.org/mailman/listinfo/asrg



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



From exim@www1.ietf.org  Fri Mar 19 17:18:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27652
	for <asrg-archive@odin.ietf.org>; Fri, 19 Mar 2004 17:18:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4SJt-0005Ka-T9
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 17:18:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JMIPF7020486
	for asrg-archive@odin.ietf.org; Fri, 19 Mar 2004 17:18:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4SJt-0005KL-N4
	for asrg-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 17:18:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27607
	for <asrg-web-archive@ietf.org>; Fri, 19 Mar 2004 17:18:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4SJr-0002JY-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 17:18:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4SIu-00026r-00
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 17:17:25 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4SHd-0001tW-01
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 17:16:05 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B4S2O-00009d-HN
	for asrg-web-archive@ietf.org; Fri, 19 Mar 2004 17:00:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4S28-000432-JT; Fri, 19 Mar 2004 17:00:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4S1X-00041X-PW
	for asrg@optimus.ietf.org; Fri, 19 Mar 2004 16:59:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26853
	for <asrg@ietf.org>; Fri, 19 Mar 2004 16:59:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4S1V-0000Ir-00
	for asrg@ietf.org; Fri, 19 Mar 2004 16:59:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4S0a-0000Dm-00
	for asrg@ietf.org; Fri, 19 Mar 2004 16:58:28 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4Rzg-00007H-00
	for asrg@ietf.org; Fri, 19 Mar 2004 16:57:32 -0500
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (mailer3.verisign.com [65.205.251.55])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2JLvR75024724;
        Fri, 19 Mar 2004 13:57:27 -0800 (PST)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <HCHBJTHY>; Fri, 19 Mar 2004 13:57:27 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E5DBA79@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Mark Baugher'" <mbaugher@cisco.com>,
        "Hallam-Baker, Phillip"
	 <pbaker@verisign.com>
Cc: asrg@ietf.org
Subject: RE: [Asrg] 3 Proof of consent spec
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Fri, 19 Mar 2004 13:57:26 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

> I know of only one IETF key agreement protocol that 
> establishes a shared 
> key among n>1 parties and that is GDOI.  I don't think this 
> is what you 
> have in mind, though.

This is out of scope of what is required to achieve interop.

	Phill


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



From exim@www1.ietf.org  Sat Mar 20 00:09:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12731
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 00:09:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4YjD-0007Xm-91
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 00:08:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2K58xYh028997
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 00:08:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4YjC-0007Xc-IJ
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 00:08:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12723
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 00:08:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4YjA-000268-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 00:08:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4YiR-0001yl-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 00:08:12 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4YhW-0001or-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 00:07:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Ygb-0006sZ-BT; Sat, 20 Mar 2004 00:06:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4YgE-0006mo-8K
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 00:05:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA12479
	for <asrg@ietf.org>; Sat, 20 Mar 2004 00:05:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4YgB-0001YP-00
	for asrg@ietf.org; Sat, 20 Mar 2004 00:05:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4Yez-0001Ep-00
	for asrg@ietf.org; Sat, 20 Mar 2004 00:04:38 -0500
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4Ycq-0000k3-00
	for asrg@ietf.org; Sat, 20 Mar 2004 00:02:24 -0500
Received: from [192.168.0.7] (h00095b86f221.ne.client2.attbi.com[24.61.46.50])
          by comcast.net (sccrmhc13) with SMTP
          id <2004032005015501600s73p7e>; Sat, 20 Mar 2004 05:01:55 +0000
Message-Id: <B3545D83-7A2B-11D8-B58D-000393CAA6AA@pobox.com>
X-Habeas-Swe-6: email in exchange for a license for this Habeas
X-Habeas-Swe-3: like Habeas SWE (tm)
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
X-Habeas-Swe-8: Message (HCM) and not spam. Please report use of this
From: mathew <meta@pobox.com>
X-Habeas-Swe-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-Swe-2: brightly anticipated
In-Reply-To: <405B4591.4080808@Royer.com>
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com> <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com> <405B4591.4080808@Royer.com>
To: asrg@ietf.org
X-Habeas-Swe-7: warrant mark warrants that this is a Habeas Compliant
Mime-Version: 1.0 (Apple Message framework v613)
X-Habeas-Swe-4: Copyright 2002 Habeas (tm) 
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-2-519980417; protocol="application/pkcs7-signature"
X-Habeas-Swe-1: winter into spring
X-Habeas-Swe-9: mark in spam to <http://www.habeas.com/report/>.
X-Mailer: Apple Mail (2.613)
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/mail-archive/working-groups/asrg/>
Date: Sat, 20 Mar 2004 00:01:51 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--Apple-Mail-2-519980417
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

On Mar 19, 2004, at 14:10, Doug Royer wrote:
> A popular vendor broke their implementation of S/MIME, that was fixed 
> years
> ago and a simple upgrade will fix that.

Well, your message signature doesn't seem valid to my mail program.

> S/MIME is not broken, the vendors may have broken implementations.

Yeah, and SMTP isn't broken, the servers just have broken 
configurations.


mathew
--Apple-Mail-2-519980417
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGEDCCAskw
ggIyoAMCAQICAwtCvTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDMxMjAzMTUwOTU3WhcNMDQxMjAyMTUwOTU3WjBAMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMR0wGwYJKoZIhvcNAQkBFg5tZXRhQHBvYm94LmNvbTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANA40G+RMi0LMG++Lz6J4LpIaXkydRxJoLjz
9EPfZGLn6dPBumvzLVWDaQrOshYuyViOW+oPk62xz6HBnarbOX3VoiFVyGCjqkZz+TToHDDlya/z
D8l/WF92nvsEPFPKE6Fw/Lg13/g9zzBlxrjwW98bL6dI1tKvdokMH91++35sC0Yu5oZjuBF4ydUA
1n7pX2KgEDhRRP5b/RhQPrdpbZhO5fwzthiD0VlCG9zkloNJ8GOFxMFd2lpVpV1ISySCHYwEtA1n
zxR7Kq4oRaMvAodHj8NHRPDjE+vyALzi0mCZ+JlQAyKr+Li5YvKZNRobyYBQGLLOyt31ZAj9vfSS
g2cCAwEAAaMrMCkwGQYDVR0RBBIwEIEObWV0YUBwb2JveC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQQFAAOBgQCVJDuVViVm9t4++qdMFmiF4yfAowCy3/bauIAcxAJXvd21LnorWF+49YJk
jBZO74MDPrsYb5M9ybKMy04vxNuXXHM9TVLUWJjz5PUCcaNIj9DqGIW9eAPWj/Pvn6j5qSP8OcoK
mwwrKcurmSi+sJqajLjET0wzsuvgRFNE4pkOyDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEF
BQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg
VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24g
U2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAw
MDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3Vs
dGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWlu
ZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me
7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r
1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCB
kTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3Rl
LmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAg
pB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPq
Cy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUa
C4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx
0x1G/11fZU8xggLnMIIC4wIBATBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u
c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz
dWluZyBDQQIDC0K9MAkGBSsOAwIaBQCgggFTMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJ
KoZIhvcNAQkFMQ8XDTA0MDMyMDA1MDE1MlowIwYJKoZIhvcNAQkEMRYEFLjnQEUFSZfIW+uQNeSr
q7NmiWa4MHgGCSsGAQQBgjcQBDFrMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBD
b25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAgMLQr0wegYLKoZIhvcNAQkQAgsxa6BpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK
ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQQIDC0K9MA0GCSqGSIb3DQEBAQUABIIBAH6RfEib+wo5eDPc3ja0
0q9nSXeDQ95dQ25If0IKrCjAlob+9eQrss5wv0DWcCcDbIm/2JqB4U7WZuOQKPQoY3aiq6EkQnTL
9lP+uX/Tckhfmw/bgWwMYPTG/BnIikDtdy5IDMfHNtkveLQUwEPZb8PdAl2SeH/eqX84yYxILYRs
BmE1d4n5blBg8atrp/rb44wYuwXGdNW7EZMvmtmOcCauac6qFm2o2m6V0RXLoA3HkeGvLA4tuFuZ
+vgZ01iVQUyaWxzKUxuIvDyHg8ZWWEZ3JNp+v39UAh+5j+ou9TcjhZz8B9qtv352kjybVDvpLRLf
U6J7DSABbuI9PELoup0AAAAAAAA=

--Apple-Mail-2-519980417--


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



From exim@www1.ietf.org  Sat Mar 20 09:55:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11965
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 09:55:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4hsJ-00048z-GC
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 09:54:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2KEsxnb015926
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 09:54:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4hsJ-00048n-3v
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 09:54:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11943
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 09:54:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4hsH-0007bc-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 09:54:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4hrJ-0007Vd-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 09:53:58 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4hqh-0007QE-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 09:53:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4hqP-0003ss-F0; Sat, 20 Mar 2004 09:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4hpR-0003qk-Ts
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 09:52:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11908
	for <asrg@ietf.org>; Sat, 20 Mar 2004 09:51:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4hpQ-0007Jh-00
	for asrg@ietf.org; Sat, 20 Mar 2004 09:52:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4hoR-0007EB-00
	for asrg@ietf.org; Sat, 20 Mar 2004 09:51:00 -0500
Received: from [216.200.145.36] (helo=omta08.mta.everyone.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4ho4-00078R-00
	for asrg@ietf.org; Sat, 20 Mar 2004 09:50:36 -0500
Received: from rmta05.mta.everyone.net (webmail.netscape [216.200.145.19])
	by omta08.mta.everyone.net (Postfix) with ESMTP
	id C83363FF6C; Sat, 20 Mar 2004 06:50:35 -0800 (PST)
Received: from sohonotebook (ip68-100-37-118.dc.dc.cox.net [68.100.37.118])
	by rmta05.mta.everyone.net (Postfix) with ESMTP
	id CB80063177; Sat, 20 Mar 2004 06:50:34 -0800 (PST)
From: "Eric Dean" <eric@purespeed.com>
To: "'Radu Hociung'" <radu.asrg@ohmi.org>, <asrg@ietf.org>
Subject: RE: [Asrg] asrg-cri - spam to mailing lists ?
Message-ID: <00f001c40e8a$b71c7df0$6701a8c0@sohonotebook>
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: <002801c40c42$f27b2cb0$9701a8c0@smart>
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/mail-archive/working-groups/asrg/>
Date: Sat, 20 Mar 2004 09:50:40 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


If a spammer included exempt headers then the process would not be
automated and the message would be subject to manual deletion.  The
intent is that valid email would automatically be delivered and anything
else would do something else.

 
> 2. About the contents: If a spammer would add headers to his 
> message to make it look like a mailing list, this message 
> would then not be subject to the other provisions of the 
> draft? Is there a separate draft/RFC to deal with the mailing 
> list/CR combination, or do you intend to address this in some way?


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



From exim@www1.ietf.org  Sat Mar 20 12:52:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17595
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 12:52:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4kdd-0004bA-Co
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 12:52:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2KHq1Wo017670
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 12:52:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4kdd-0004av-6G
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 12:52:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17585
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 12:51:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4kdb-0002sj-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 12:51:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4kcf-0002nH-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 12:51:02 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4kc9-0002i4-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 12:50:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4kbj-0004C4-LP; Sat, 20 Mar 2004 12:50:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4kam-00049b-O6
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 12:49:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17524
	for <asrg@ietf.org>; Sat, 20 Mar 2004 12:49:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4kal-0002c5-00
	for asrg@ietf.org; Sat, 20 Mar 2004 12:49:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4kZp-0002Wo-00
	for asrg@ietf.org; Sat, 20 Mar 2004 12:48:06 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4kZE-0002R8-00
	for asrg@ietf.org; Sat, 20 Mar 2004 12:47:28 -0500
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (mailer3.verisign.com [65.205.251.55])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2KHlSjP013252
        for <asrg@ietf.org>; Sat, 20 Mar 2004 09:47:28 -0800 (PST)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <HCHBMTD5>; Sat, 20 Mar 2004 09:47:28 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E5DBA7F@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: asrg@ietf.org
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Asrg] 0 General - Fake HIV Letters in mail
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/mail-archive/working-groups/asrg/>
Date: Sat, 20 Mar 2004 09:47:27 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

http://www.nytimes.com/2004/03/20/nyregion/20letters.html

The email variants cannot be far off.

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



From exim@www1.ietf.org  Sat Mar 20 15:16:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23327
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 15:16:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4mtA-0005az-9H
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 15:16:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2KKGC8F021503
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 15:16:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4mtA-0005ak-1d
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 15:16:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23171
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 15:16:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4mt8-0003KI-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 15:16:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4msA-000390-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 15:15:10 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4mrH-00032l-03
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 15:14:15 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B4mnE-0001BQ-56
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 15:10:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4mnC-0003lk-U9; Sat, 20 Mar 2004 15:10:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4mmJ-0003Wi-DT
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 15:09:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22517
	for <asrg@ietf.org>; Sat, 20 Mar 2004 15:09:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4mmG-0002Zu-00
	for asrg@ietf.org; Sat, 20 Mar 2004 15:09:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4mlI-0002Td-00
	for asrg@ietf.org; Sat, 20 Mar 2004 15:08:04 -0500
Received: from plounts.uits.indiana.edu ([129.79.1.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4mkM-0002NA-00
	for asrg@ietf.org; Sat, 20 Mar 2004 15:07:06 -0500
Received: from fontz.uits.indiana.edu (fontz.uits.indiana.edu [129.79.1.76])
	by plounts.uits.indiana.edu (8.12.10/8.12.10/IUPO) with ESMTP id i2KK73xI015207
	for <asrg@ietf.org>; Sat, 20 Mar 2004 15:07:03 -0500 (EST)
Received: from [10.0.2.2] (dial-64-151-129-254.bton.kiva.net [64.151.129.254])
	(authenticated bits=0)
	by fontz.uits.indiana.edu (8.12.10/8.12.10/IUPO) with ESMTP id i2KK6O4w028052
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <asrg@ietf.org>; Sat, 20 Mar 2004 15:07:00 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v612)
In-Reply-To: <20040320170007.4242.54343.Mailman@www1.ietf.org>
References: <20040320170007.4242.54343.Mailman@www1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <0F877F04-7AAA-11D8-91B6-000393DC31DA@bloomington.in.us>
Content-Transfer-Encoding: 7bit
From: Jim Witte <jswitte@bloomington.in.us>
To: asrg@ietf.org
X-Mailer: Apple Mail (2.612)
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: And filtering SMIME Sigs from digets..
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/mail-archive/working-groups/asrg/>
Date: Sat, 20 Mar 2004 15:06:23 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,UPPERCASE_25_50 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> Content-Type: application/x-pkcs7-signature; name="smime.p7s"
> Content-Disposition: attachment; filename="smime.p7s"
> Content-Description: S/MIME Cryptographic Signature
> Content-Transfer-Encoding: base64
>
> MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDC 
> C
> A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1U 
> E

   To add to my last email about the possibility of filtering HTML from  
digests, I could add SMIME attachements...

Jim Witte
jswitte@bloomington.in.us
Indiana University CS


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



From exim@www1.ietf.org  Sat Mar 20 15:16:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23348
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 15:16:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4mtD-0005bq-GH
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 15:16:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2KKGFAt021553
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 15:16:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4mtD-0005bY-CY
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 15:16:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23190
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 15:16:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4mtC-0003Km-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 15:16:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4msE-00039m-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 15:15:15 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4mrI-00032l-03
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 15:14:16 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B4mjP-0000eQ-9K
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 15:06:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4mjK-0001ck-1t; Sat, 20 Mar 2004 15:06:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4miP-00012u-8J
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 15:05:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22135
	for <asrg@ietf.org>; Sat, 20 Mar 2004 15:05:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4miM-0002C0-00
	for asrg@ietf.org; Sat, 20 Mar 2004 15:05:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4mhR-000272-00
	for asrg@ietf.org; Sat, 20 Mar 2004 15:04:06 -0500
Received: from rockridge.uits.indiana.edu ([129.79.1.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4mgX-00021m-00
	for asrg@ietf.org; Sat, 20 Mar 2004 15:03:09 -0500
Received: from logchain.uits.indiana.edu (logchain.uits.indiana.edu [129.79.1.77])
	by rockridge.uits.indiana.edu (8.12.10/8.12.10/IUPO) with ESMTP id i2KK37bV016099
	for <asrg@ietf.org>; Sat, 20 Mar 2004 15:03:08 -0500 (EST)
Received: from [10.0.2.2] (dial-64-151-129-254.bton.kiva.net [64.151.129.254])
	(authenticated bits=0)
	by logchain.uits.indiana.edu (8.12.10/8.12.10/IUPO) with ESMTP id i2KK337c013530
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <asrg@ietf.org>; Sat, 20 Mar 2004 15:03:06 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v612)
In-Reply-To: <20040320170007.4242.54343.Mailman@www1.ietf.org>
References: <20040320170007.4242.54343.Mailman@www1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <9861A5E8-7AA9-11D8-91B6-000393DC31DA@bloomington.in.us>
Content-Transfer-Encoding: 7bit
From: Jim Witte <jswitte@bloomington.in.us>
To: asrg@ietf.org
X-Mailer: Apple Mail (2.612)
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: HTML in mail sent to list
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/mail-archive/working-groups/asrg/>
Date: Sat, 20 Mar 2004 15:03:03 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> I don't think that very many people are going to need the expensive 
> high end
> accreditation services that people like Margaret are using. If you are 
> not a
> bulk email sender the cost of accreditation should not be an issue. 
> Sure it
> will cost a lot to police the bulk senders, but not the people who 
> don't do
> anything that looks spammy.
>
>         Phill
>
>
> ------_=_NextPart_001_01C40DD9.ABDECE35
> Content-Type: text/html;
> 	charset="iso-8859-1"
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <snip>

   Can the maillist software running this list filter out HTML content 
from digests?  Considering that there seems no spec for making 
'concatenating' multipart-email messages, which I assume is how the 
digests are made (all the messages are just concatenated together, so 
MIME boundaries for individual messages no longer make sense.)

Jim Witte
jswitte@bloomington.in.us
Indiana University CS


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



From exim@www1.ietf.org  Sat Mar 20 15:17:00 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23402
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 15:17:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4mtT-0005gT-Ib
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 15:16:31 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2KKGV2f021843
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 15:16:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4mtT-0005gE-DI
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 15:16:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23255
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 15:16:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4mtS-0003Ma-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 15:16:30 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4msT-0003CS-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 15:15:30 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4mrM-00032l-03
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 15:14:20 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B4mcp-0000Cv-2v
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 14:59:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4mcZ-0003mF-4c; Sat, 20 Mar 2004 14:59:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4lYk-00085Q-UV
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 13:51:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19369
	for <asrg@ietf.org>; Sat, 20 Mar 2004 13:51:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4lYi-0001gS-00
	for asrg@ietf.org; Sat, 20 Mar 2004 13:51:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4lXm-0001bW-00
	for asrg@ietf.org; Sat, 20 Mar 2004 13:50:03 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4lX6-0001RF-00
	for asrg@ietf.org; Sat, 20 Mar 2004 13:49:20 -0500
Received: from Royer.com (69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2KImgFp017213
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Sat, 20 Mar 2004 10:48:44 -0800
Message-ID: <405C9208.4050506@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com> <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com> <405B4591.4080808@Royer.com> <B3545D83-7A2B-11D8-B58D-000393CAA6AA@pobox.com>
In-Reply-To: <B3545D83-7A2B-11D8-B58D-000393CAA6AA@pobox.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090001050103010408000402"
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/mail-archive/working-groups/asrg/>
Date: Sat, 20 Mar 2004 11:48:40 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms090001050103010408000402
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



mathew wrote:

> On Mar 19, 2004, at 14:10, Doug Royer wrote:
>
>> A popular vendor broke their implementation of S/MIME, that was fixed 
>> years
>> ago and a simple upgrade will fix that.
>
>
> Well, your message signature doesn't seem valid to my mail program. 

Again, your vendor being busted  does not mean that S/MIME is busted.
It means you need to contact your vendor and get them to fix their product.

Do you really mean to imply that if your vendor of choice does not get it
right that the protocol is busted?

>> S/MIME is not broken, the vendors may have broken implementations.
>
>
> Yeah, and SMTP isn't broken, the servers just have broken configurations. 

Some might be busted, others implemented SMTP correctly.
It sill is not relevant to whether SMTP or S/MIME is busted.


-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms090001050103010408000402
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIwMTg0ODQwWjAjBgkqhkiG9w0BCQQxFgQU/5lK8azbha0oGKXX0Hov
ar1Tp/cwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAkGROm9U431UqT2pIOI7uLI8fDtu6W8rzvX0+0GtqeVB4odcccJPvQ1jVHtDQ8MSb
6fLD8eHSrcYxfncXLbPngwbdHTcTi/3V5GsoB93E3VX68NFMLyzVSFMgfYjpd7NzqDrkIO/R
KRyv0eONTNZg+1TLP11D265bxPqqheQMgG4ejoHmZf9wuk+cL2ES4ls1Ll0So1qh4HZurL2A
qc547buo45Rt/oX0Q7h6Qd72l7jdexSGPnr2ntl4qBVZ2E4Li5OlzHTO9fgZtQWR9X+WG15T
mgoQIVvfff0hPYtp/4eDPkj2+y4eVsHTBOVeDgPmmvzIoUasu6YUq50TQc/6KgAAAAAAAA==
--------------ms090001050103010408000402--


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



From exim@www1.ietf.org  Sat Mar 20 16:31:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25316
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 16:31:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4o3h-0002PF-LE
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 16:31:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2KLV991009243
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 16:31:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4o3h-0002P0-F2
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 16:31:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25282
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 16:31:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4o3f-0003CB-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 16:31:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4o2f-00035w-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 16:30:06 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4o1n-00030a-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 16:29:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4o1e-00025n-Ib; Sat, 20 Mar 2004 16:29:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4o13-000255-AV
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 16:28:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25208
	for <asrg@ietf.org>; Sat, 20 Mar 2004 16:28:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4o11-0002vG-00
	for asrg@ietf.org; Sat, 20 Mar 2004 16:28:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4o08-0002oM-00
	for asrg@ietf.org; Sat, 20 Mar 2004 16:27:28 -0500
Received: from sparkle.rodents.montreal.qc.ca ([216.46.5.7] ident=X2LHgaOXRKyTXlwagmVQtxViPQPkUXYq4xd5pTJE32X)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4nzM-0002fh-00
	for asrg@ietf.org; Sat, 20 Mar 2004 16:26:40 -0500
Received: (from mouse@localhost)
	by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id QAA16806;
	Sat, 20 Mar 2004 16:26:39 -0500 (EST)
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Message-Id: <200403202126.QAA16806@Sparkle.Rodents.Montreal.QC.CA>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
To: asrg@ietf.org
Subject: Re: [Asrg] 0 General - Fake HIV Letters in mail
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E5DBA7F@mou1wnexm05.vcorp.ad.vrsn.com>
References: <C6DDA43B91BFDA49AA2F1E473732113E5DBA7F@mou1wnexm05.vcorp.ad.vrsn.com>
Content-Transfer-Encoding: 8bit
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/mail-archive/working-groups/asrg/>
Date: Sat, 20 Mar 2004 16:19:24 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> http://www.nytimes.com/2004/03/20/nyregion/20letters.html

Registration required.  Anyone have a pointer a place the story can be
found that doesn't, or a summary of the story, or some such?

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

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



From exim@www1.ietf.org  Sat Mar 20 18:16:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00047
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 18:16:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4phP-00065Y-6g
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 18:16:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2KNGFo7023398
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 18:16:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4phO-00065J-TB
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 18:16:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29982
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 18:16:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4phM-0006j5-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 18:16:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4pgP-0006cK-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 18:15:13 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4pfT-0006VL-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 18:14:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4pfF-0005PV-HA; Sat, 20 Mar 2004 18:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4pee-0005G9-2v
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 18:13:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29714
	for <asrg@ietf.org>; Sat, 20 Mar 2004 18:13:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4pea-0006Oc-00
	for asrg@ietf.org; Sat, 20 Mar 2004 18:13:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4pdf-0006HX-00
	for asrg@ietf.org; Sat, 20 Mar 2004 18:12:23 -0500
Received: from xuxa.iecc.com ([208.31.42.42])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4pct-00069u-00
	for asrg@ietf.org; Sat, 20 Mar 2004 18:11:35 -0500
Received: (qmail 27677 invoked by uid 100); 20 Mar 2004 23:11:35 -0000
Message-ID: <20040320231135.27676.qmail@xuxa.iecc.com>
From: John Levine <asrg@johnlevine.com>
To: asrg@ietf.org
Subject: Re: [Asrg] Re: HTML in mail sent to list
In-Reply-To: <9861A5E8-7AA9-11D8-91B6-000393DC31DA@bloomington.in.us>
Organization: I.E.C.C., Trumansburg NY USA
Cc: jswitte@bloomington.in.us
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/mail-archive/working-groups/asrg/>
Date: 20 Mar 2004 23:11:35 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

>   Can the maillist software running this list filter out HTML content 
>from digests?  Considering that there seems no spec for making 
>'concatenating' multipart-email messages, which I assume is how the 
>digests are made (all the messages are just concatenated together, so 
>MIME boundaries for individual messages no longer make sense.)

Actually, there's a perfectly good MIME type for mail digests.
Majordomo2, which I use to host all the subgroup lists, can make MIME
digests, but Mailman, which is what the main ASRG list at the IETF
uses, doesn't seem to be able to do that.

I'm not a big fan of HTML mail, but indigestibility is not one of its
flaws.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
http://www.taugh.com

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



From exim@www1.ietf.org  Sat Mar 20 20:12:55 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03441
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 20:12:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4rVq-0007eC-Fj
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 20:12:26 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2L1CQ54029390
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 20:12:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4rVq-0007dx-AR
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 20:12:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA03434
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 20:12:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4rVo-0003F7-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 20:12:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4rUk-00036T-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 20:11:18 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4rTn-00030c-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 20:10:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4rTX-0007Ri-A1; Sat, 20 Mar 2004 20:10:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4pbY-0004Tf-J2
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 18:10:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29369
	for <asrg@ietf.org>; Sat, 20 Mar 2004 18:10:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4pbV-000628-00
	for asrg@ietf.org; Sat, 20 Mar 2004 18:10:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4paY-0005wR-00
	for asrg@ietf.org; Sat, 20 Mar 2004 18:09:10 -0500
Received: from pcls3.std.com ([192.74.137.143] helo=TheWorld.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4pZZ-0005qG-00
	for asrg@ietf.org; Sat, 20 Mar 2004 18:08:09 -0500
Received: from world.std.com (root@world-e.std.com [69.38.147.5])
	by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id i2KN897A015912;
	Sat, 20 Mar 2004 18:08:09 -0500
Received: (from bzs@localhost)
	by world.std.com (8.9.3/8.9.3) id SAA12983;
	Sat, 20 Mar 2004 18:08:08 -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: <16476.52952.644839.293761@world.std.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: asrg@ietf.org
Subject: Re: [Asrg] 0 General - Fake HIV Letters in mail
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E5DBA7F@mou1wnexm05.vcorp.ad.vrsn.com>
References: <C6DDA43B91BFDA49AA2F1E473732113E5DBA7F@mou1wnexm05.vcorp.ad.vrsn.com>
X-Mailer: VM 7.07 under Emacs 21.2.2
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/mail-archive/working-groups/asrg/>
Date: Sat, 20 Mar 2004 18:08:08 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On March 20, 2004 at 09:47 pbaker@verisign.com (Hallam-Baker, Phillip) wrote:
 > http://www.nytimes.com/2004/03/20/nyregion/20letters.html
 > 
 > The email variants cannot be far off.

Yes, and perhaps I'm jumping the gun here, but isn't the real msg that
after 200+ years in operation the USPS hasn't really been able to do
anything about this sort of thing other than via mail fraud laws or
similar? And warning people to be suspicious as this article does.

I guess my real bone is that there's been a growing conflation, to my
thinking, of authentication vs UBE. Fraudulent messages needn't be
bulk, and not even particularly unsolicited, and unsolicited bulk
email needn't be fraudulent.

I think we can do something about UBE, but before trying to do
something about authentication one might seriously ponder why the USPS
(and no doubt non-US) haven't tackled this in general except by
offering special, higher-cost authenticating services.

I think the answer is in that last phrase: authentication costs.

This is why I'm rather dim on the whole SPF/RMX/CallerID effort, I
think you're better off just coming up with a higher-cost
authenticated messaging using something like SSL and certificates or
PGP or whatever for those who want it (and we all might want it at
some times, just like certified or registered mail) and just let
everyone know that if it isn't via an authenticating source then,
well, it's no more trustable than any random letter you get in your
postal mailbox (Congratulations, You have just won one of the
following four prizes!)

-- 
        -Barry Shein

Software Tool & Die    | bzs@TheWorld.com           | http://www.TheWorld.com
Purveyors to the Trade | Voice: 617-739-0202        | Login: 617-739-WRLD
The World              | Public Access Internet     | Since 1989     *oo*

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



From exim@www1.ietf.org  Sat Mar 20 20:40:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05065
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 20:40:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4rwp-0001NJ-8P
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 20:40:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2L1eJjR005282
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 20:40:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4rwo-0001N7-W8
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 20:40:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05062
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 20:40:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4rwm-0007Ce-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 20:40:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4rvq-00077Q-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 20:39:19 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4rvh-000728-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 20:39:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4rva-0001D8-1w; Sat, 20 Mar 2004 20:39:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4rut-0001CQ-FN
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 20:38:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05021
	for <asrg@ietf.org>; Sat, 20 Mar 2004 20:38:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4rur-00071B-00
	for asrg@ietf.org; Sat, 20 Mar 2004 20:38:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4rtw-0006vk-00
	for asrg@ietf.org; Sat, 20 Mar 2004 20:37:20 -0500
Received: from xuxa.iecc.com ([208.31.42.42])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4rtN-0006pY-00
	for asrg@ietf.org; Sat, 20 Mar 2004 20:36:45 -0500
Received: (qmail 7884 invoked by uid 100); 21 Mar 2004 01:36:40 -0000
Message-ID: <20040321013640.7883.qmail@xuxa.iecc.com>
From: John Levine <asrg@johnlevine.com>
To: asrg@ietf.org
Subject: Re: [Asrg] 0 General - Forgery isn't just UBE
In-Reply-To: <16476.52952.644839.293761@world.std.com>
Organization: I.E.C.C., Trumansburg NY USA
Cc: bzs@world.std.com
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/mail-archive/working-groups/asrg/>
Date: 21 Mar 2004 01:36:40 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

>I guess my real bone is that there's been a growing conflation, to my
>thinking, of authentication vs UBE. Fraudulent messages needn't be
>bulk, and not even particularly unsolicited, and unsolicited bulk
>email needn't be fraudulent.

All quite true.  I went to a meeting a month ago of the Anti-phishing
Working Group which despite its funky name consists of big banks, big
ISPs, and big law enforcement with a smattering of software vendors
and a few tourists like me.  Phishing is as bad a problem as spam, but
it's less well known because the primary targets are large
organizations that tend not to talk about it other than to each other.
They're now seeing upwards of 12 distinct attacks per day with the
most common targets being eBay, Citibank, and Paypal.

Some phishing is done by broadcast spam, but a lot is carefully
targeted, e.g., at foreign holders of US bank accounts who often fall
for the verify your account scam.  Losses are large.  At the meeting a
guy from the Department of Justice talked about cases with six and
occasionally seven figure losses, and people going to jail for many
years.

Phishing entirely depends on authentication failure.  A web site,
e-mail, or other message looks like it's from a large familiar
organization, but it's not.  At the moment, there's little they can do
to prevent it.  SSL is no help since any crook with $50 can get a 100%
genuine SSL certificate that works in all of the browsers and mail
programs people use, that proudly certifies that a web page or e-mail
is truly from CITIBANK-ACCOUNTS.COM which, of course, is not Citibank.

I suggested that since the banking industry is heavily regulated and
in the US there's no question who's a bank and who isn't, they need a
distinctive signer who only signs for banks with a trademark that
could be advertised for brand awareness.  ("It's not from your bank
unless it has a Golden Dollar Sign in the corner.")  A guy from the
FDIC said they've been thinking about it.

This could help the phishing problem, at least the part of it that's
against banks, but I don't see any extension to dealing with spam.
It's pretty clear that pure authentication agents don't work, because
the costs and benefits don't work.  Most people aren't willing to pay
$5000 for a signer to send someone out to do a background check and a
personal visit, nor are they even willing to go to PGP signing fests,
but without some sort of real world check, it's just pushing paper
around.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
http://www.taugh.com


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



From exim@www1.ietf.org  Sat Mar 20 22:03:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08218
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 22:03:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4tEn-00069D-7H
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 22:02:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2L32vp3023625
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 22:02:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4tEn-00068y-1S
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 22:02:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08173
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 22:02:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4tEk-0001gd-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 22:02:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4tDp-0001Sy-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 22:01:58 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4tCU-0001C2-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 22:00:35 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B4tCV-0006Pc-GT
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 22:00:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4tCE-0005lc-UA; Sat, 20 Mar 2004 22:00:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4tA9-0005N2-9g
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 21:58:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA07594
	for <asrg@ietf.org>; Sat, 20 Mar 2004 21:58:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4tA6-0000Xp-00
	for asrg@ietf.org; Sat, 20 Mar 2004 21:58:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4t89-00006N-00
	for asrg@ietf.org; Sat, 20 Mar 2004 21:56:06 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4t6r-0007fI-00
	for asrg@ietf.org; Sat, 20 Mar 2004 21:54:45 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B4t6s-0004KU-00
	for asrg@ietf.org; Sat, 20 Mar 2004 21:54:46 -0500
Received: from [68.244.224.26] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B4t6q-0002K4-00
	for asrg@ietf.org; Sat, 20 Mar 2004 21:54:45 -0500
Message-ID: <405D03BB.9010407@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 2. Documentating the DNS protocol used by blacklists
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/mail-archive/working-groups/asrg/>
Date: Sat, 20 Mar 2004 21:53:47 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

To my knowledge there has not been any RFC or internet draft published 
that documents the protocol used by DNS blacklists. Would someone be 
willing to volunteer some time to write up a draft?

Yakov

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



From exim@www1.ietf.org  Sat Mar 20 22:45:58 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09561
	for <asrg-archive@odin.ietf.org>; Sat, 20 Mar 2004 22:45:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4ttz-00018d-F1
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 22:45:31 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2L3jVeu004371
	for asrg-archive@odin.ietf.org; Sat, 20 Mar 2004 22:45:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4ttz-00018Q-92
	for asrg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 22:45:31 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09551
	for <asrg-web-archive@ietf.org>; Sat, 20 Mar 2004 22:45:27 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4ttv-0006yE-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 22:45:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4tsw-0006se-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 22:44:27 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4tsj-0006n3-00
	for asrg-web-archive@ietf.org; Sat, 20 Mar 2004 22:44:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4tsX-0000yr-4s; Sat, 20 Mar 2004 22:44:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4ts2-0000rb-W4
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 22:43:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09520
	for <asrg@ietf.org>; Sat, 20 Mar 2004 22:43:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4trz-0006mG-00
	for asrg@ietf.org; Sat, 20 Mar 2004 22:43:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4tqz-0006ge-00
	for asrg@ietf.org; Sat, 20 Mar 2004 22:42:25 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4tqZ-0006ae-00
	for asrg@ietf.org; Sat, 20 Mar 2004 22:41:59 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id 6CFA816FDF
	for <asrg@ietf.org>; Sat, 20 Mar 2004 22:45:45 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] 0 General - Fake HIV Letters in mail 
In-Reply-To: Your message of "Sat, 20 Mar 2004 18:08:08 EST."
             <16476.52952.644839.293761@world.std.com> 
Message-Id: <20040321034545.6CFA816FDF@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Sat, 20 Mar 2004 22:45:45 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Barry Shein <bzs@world.std.com> wrote:
> This is why I'm rather dim on the whole SPF/RMX/CallerID effort, I
> think you're better off just coming up with a higher-cost
> authenticated messaging using something like SSL and certificates or
> PGP

  To authenticate what, exactly?

  Part of the problem is the lack of a naming scheme for domains.  I
don't know if a company is at "example.com", or "example-company.com",
or "example-this-is-cool.com".  The inability of the end user to trust
a name has a direct correlation to the spammers ability to abuse that
name.

  DNS names are structured, but for marketing/political reasons,
everybody wants a "dot com" name.  So even Canadian businesses aren't
using "example.ca", they're using "example-canada.com", or
"example-ca.com".  That kind of nonsense is causing them problems, but
we're the ones asked to fix the problem.

  So why not enforce structured names?  It's technically feasible, and
is a start towards authenticating *something*.

> ... and just let everyone know that if it isn't via an authenticating
> source then, well, it's no more trustable than any random letter you
> get in your postal mailbox (Congratulations, You have just won one
> of the following four prizes!)

  That requires well-known sources.  If I get a letter from my bank, I
have many ways of telling that the letter is authentic.  If I get an
email from them, I have many fewer ways.

  Signing messages is a start.  But what identity is trusted?
example.com, example.ca, or example-canada.com?  Without a trusted
naming scheme, cryptographic signatures not much more than a way to
burn CPU cycles.

  Alan DeKok.

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



From exim@www1.ietf.org  Sun Mar 21 00:42:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13414
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 00:42:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4viu-00017k-5h
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 00:42:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2L5gCe3004316
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 00:42:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4viu-00017X-1o
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 00:42:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA13322
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 00:42:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4vir-0004JR-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 00:42:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4vhr-000471-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 00:41:08 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4vge-0003tJ-06
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 00:39:53 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B4vRb-0007Si-Q0
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 00:24:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4vRJ-0006m5-GK; Sun, 21 Mar 2004 00:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4uMp-0002FX-3R
	for asrg@optimus.ietf.org; Sat, 20 Mar 2004 23:15:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA10220
	for <asrg@ietf.org>; Sat, 20 Mar 2004 23:15:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4uMn-0002Ga-00
	for asrg@ietf.org; Sat, 20 Mar 2004 23:15:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4uLp-0002AP-00
	for asrg@ietf.org; Sat, 20 Mar 2004 23:14:18 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4uKq-0001we-00
	for asrg@ietf.org; Sat, 20 Mar 2004 23:13:17 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2L4CcFp022585
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Sat, 20 Mar 2004 20:12:39 -0800
Message-ID: <405D1635.8010609@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] 0 General - Fake HIV Letters in mail
References: <20040321034545.6CFA816FDF@mail.nitros9.org>
In-Reply-To: <20040321034545.6CFA816FDF@mail.nitros9.org>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070402070301070606040305"
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/mail-archive/working-groups/asrg/>
Date: Sat, 20 Mar 2004 21:12:37 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms070402070301070606040305
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



Alan DeKok wrote:

>
>  That requires well-known sources.  If I get a letter from my bank, I
>have many ways of telling that the letter is authentic.  If I get an
>email from them, I have many fewer ways.
>
>  Signing messages is a start.  But what identity is trusted?
>example.com, example.ca, or example-canada.com?  Without a trusted
>naming scheme, cryptographic signatures not much more than a way to
>burn CPU cycles.
>
>  Alan DeKok.
>  
>
S/MIME  forces the 'From' address to match the signature.
It makes no other claim. It has nothing to do with your location
or the originating domain. In fact I can send email from several domains,
each using my cert that says I am 'doug@royer.com'. It makes no difference
which domain I send it from, it only means I have the private
key to that public signature and it matches the 'From' line. The
signature only means - yes the signature matches the From line.

If the cert has not been revoked (by checking), then you know that
the person that used the cert had permission to use that 'From' address.

*IF* you trust the CA in the signature, then you trust that it came from
a valid user of that email address and was not forged.

That alone would stop 1,000's of forged email spams I get every week
to the domains I administer.

*IF* you do trust the CA and it is spam - you could add that public
cert to your blacklist, publish that as a spam cert. And you can 
*automaticly*
find the authority for that domain in the signature and complain.

*IF* you do NOT trust the CA - your where your at now. I for one have
a handful of CA's that I trust.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms070402070301070606040305
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIxMDQxMjM3WjAjBgkqhkiG9w0BCQQxFgQU3z1TWLWeDtwl4X30jWmP
94GQ8ikwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAq2b9+/SyIv2ocfajaGBw6FbjjsKxAk/0H1LO5+IJ1doWLBM8f9kkmWGL3r681yUL
aSrQKKl656y92bQmHdicDTNuSmOYb3iG3w8nQx1gzxhnnRPfMRnYasB8Y33WxzBLpZ6yC0Xj
D1FwO+HaLXI/pLLxgbD8/B/m7goEsMshT02i8moNYWIZlf65op8OeN3h3dLq4Qe5NiTROdq9
HTD6EUegx/+P033BWUy1ZJ9XH5cEr/UIWszzJ3cdeCDoW0zjQhPujM7qeEnnBI/wxkZ50vJ3
RKEh2YbgYHwX99zznHao5AFXhRCDWCpdb7xLwSZf5HKMGEJOnec4gStPMCRaeAAAAAAAAA==
--------------ms070402070301070606040305--


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



From exim@www1.ietf.org  Sun Mar 21 10:01:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13700
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 10:01:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B54RR-00086k-Aa
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 10:00:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LF0jka031163
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 10:00:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B54RR-00086W-6Z
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 10:00:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13695
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 10:00:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B54RP-00003A-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 10:00:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B54QT-0007m0-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 09:59:45 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B54QC-0007h7-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 09:59:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B54Pl-0007ZN-6N; Sun, 21 Mar 2004 09:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B54PV-0007Yu-Rc
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 09:58:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13623
	for <asrg@ietf.org>; Sun, 21 Mar 2004 09:58:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B54PT-0007gM-00
	for asrg@ietf.org; Sun, 21 Mar 2004 09:58:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B54Oa-0007Zi-00
	for asrg@ietf.org; Sun, 21 Mar 2004 09:57:48 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B54Nm-0007RG-00
	for asrg@ietf.org; Sun, 21 Mar 2004 09:56:58 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id BD4DD170BB
	for <asrg@ietf.org>; Sun, 21 Mar 2004 10:00:43 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] 0 General - Fake HIV Letters in mail 
In-Reply-To: Your message of "Sat, 20 Mar 2004 21:12:37 MST."
             <405D1635.8010609@Royer.com> 
Message-Id: <20040321150043.BD4DD170BB@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 10:00:43 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Doug Royer <Doug@Royer.com> wrote:
> S/MIME  forces the 'From' address to match the signature.
> It makes no other claim. It has nothing to do with your location
> or the originating domain.

  Which means that you still have no idea if the the address in the
"From" line is truthful.  Please go back and read the rest of my comments.

  If you want to spoof example.com, which has a Canadian branch
office, as an individual, you can register "example-canada.com", and
send S/MIME signed messages from it.  The recipients have no way of
knowing such messages are fraudulent.

  Sure, the signature means it's easier to verify that it was *you*
who committed the fraud, but how does that help the recipients, who've
lost money?  How does that help law enforcement, when you've used that
money to flee the country?

  Validating identities means nothing if the identities being
validated are fraudulent.

> If the cert has not been revoked (by checking), then you know that
> the person that used the cert had permission to use that 'From' address.

  From who?  The signing authority, who sells signed certs for $40?

> *IF* you do trust the CA and it is spam - you could add that public
> cert to your blacklist, publish that as a spam cert. And you can 
> *automaticly* find the authority for that domain in the signature
> and complain.

  Again, if that information is valid.  If not, you're stuck.

  It's easy to get a domain and/or certificate with fraudulent identities.

> *IF* you do NOT trust the CA - your where your at now. I for one have
> a handful of CA's that I trust.

  That's nice for you.  How does that scale to everyone else?

  Alan DeKok.

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



From exim@www1.ietf.org  Sun Mar 21 11:59:17 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20145
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 11:59:17 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B56Hi-0004Ux-5h
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 11:58:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LGwoKY017290
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 11:58:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B56Hh-0004Un-VA
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 11:58:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20137
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 11:58:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B56Hg-0006Is-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 11:58:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B56Gq-0006DI-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 11:57:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B56G7-00067O-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 11:57:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B56Fx-0004BP-EO; Sun, 21 Mar 2004 11:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B56F4-0004AA-AR
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 11:56:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20095
	for <asrg@ietf.org>; Sun, 21 Mar 2004 11:56:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B56F3-0005ze-00
	for asrg@ietf.org; Sun, 21 Mar 2004 11:56:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B56EF-0005sG-00
	for asrg@ietf.org; Sun, 21 Mar 2004 11:55:16 -0500
Received: from xuxa.iecc.com ([208.31.42.42])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B56DZ-0005jF-00
	for asrg@ietf.org; Sun, 21 Mar 2004 11:54:33 -0500
Received: (qmail 9898 invoked by uid 100); 21 Mar 2004 16:54:33 -0000
Message-ID: <20040321165433.9897.qmail@xuxa.iecc.com>
From: John Levine <asrg@johnlevine.com>
To: asrg@ietf.org
Subject: Re: [Asrg] 0 General - Fake HIV Letters in mail
In-Reply-To: <405D1635.8010609@Royer.com>
Organization: I.E.C.C., Trumansburg NY USA
Cc: asrg@ietf.org
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/mail-archive/working-groups/asrg/>
Date: 21 Mar 2004 16:54:33 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

>If the cert has not been revoked (by checking), then you know that
>the person that used the cert had permission to use that 'From' address.

Well, not quite, you know that the CA that signed the cert thought
that the sender had permission to use that address.

>*IF* you trust the CA in the signature, then you trust that it came from
>a valid user of that email address and was not forged.

We're back to the key management problem.  I don't see how a public
signer that signed enough keys to be useful as a whitelist wouldn't
also let enough bad guys sneak through that you'd want to use it as
a blacklist.

For small and reasonably well defined communities, a company signing
its employees certs, or various geekly groups who know each other,
sigs can work, but I've never been able to see a plausible way to
scale up to the whole world of e-mail.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
http://www.taugh.com


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



From exim@www1.ietf.org  Sun Mar 21 11:59:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20162
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 11:59:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B56Hj-0004VK-Mx
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 11:58:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LGwpGC017308
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 11:58:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B56Hj-0004V5-I6
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 11:58:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20141
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 11:58:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B56Hi-0006J5-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 11:58:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B56Gr-0006DQ-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 11:57:58 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B56G7-00067P-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 11:57:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B56Fx-0004BX-TS; Sun, 21 Mar 2004 11:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B56F4-0004AF-Uw
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 11:56:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20098
	for <asrg@ietf.org>; Sun, 21 Mar 2004 11:56:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B56F3-0005zj-00
	for asrg@ietf.org; Sun, 21 Mar 2004 11:56:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B56EG-0005sO-00
	for asrg@ietf.org; Sun, 21 Mar 2004 11:55:17 -0500
Received: from xuxa.iecc.com ([208.31.42.42])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B56Db-0005jI-00
	for asrg@ietf.org; Sun, 21 Mar 2004 11:54:35 -0500
Received: (qmail 9898 invoked by uid 100); 21 Mar 2004 16:54:33 -0000
Message-ID: <20040321165433.9897.qmail@xuxa.iecc.com>
From: John Levine <asrg@johnlevine.com>
To: asrg@ietf.org
Subject: Re: [Asrg] 0 General - Fake HIV Letters in mail
In-Reply-To: <405D1635.8010609@Royer.com>
Organization: I.E.C.C., Trumansburg NY USA
Cc: asrg@ietf.org
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/mail-archive/working-groups/asrg/>
Date: 21 Mar 2004 16:54:33 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

>If the cert has not been revoked (by checking), then you know that
>the person that used the cert had permission to use that 'From' address.

Well, not quite, you know that the CA that signed the cert thought
that the sender had permission to use that address.

>*IF* you trust the CA in the signature, then you trust that it came from
>a valid user of that email address and was not forged.

We're back to the key management problem.  I don't see how a public
signer that signed enough keys to be useful as a whitelist wouldn't
also let enough bad guys sneak through that you'd want to use it as
a blacklist.

For small and reasonably well defined communities, a company signing
its employees certs, or various geekly groups who know each other,
sigs can work, but I've never been able to see a plausible way to
scale up to the whole world of e-mail.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
http://www.taugh.com


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



From exim@www1.ietf.org  Sun Mar 21 14:35:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25842
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 14:35:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58iy-0007Ym-Mu
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 14:35:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LJZ8Cc029054
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 14:35:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58iy-0007YV-HC
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 14:35:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25818
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 14:35:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58iv-00002p-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:35:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B58i2-0007k3-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:34:10 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58hS-0007ca-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:33:34 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58gu-0007KK-Su; Sun, 21 Mar 2004 14:33:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58g4-0007GY-DH
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 14:32:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25609
	for <asrg@ietf.org>; Sun, 21 Mar 2004 14:32:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58g1-0007RH-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:32:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B58f4-0007J3-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:31:06 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58eG-00072x-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:30:16 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2LJTYFp020722
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Sun, 21 Mar 2004 11:29:36 -0800
Message-ID: <405DED1E.6010102@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME
References: <20040321150043.BD4DD170BB@mail.nitros9.org>
In-Reply-To: <20040321150043.BD4DD170BB@mail.nitros9.org>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070301030406080905080202"
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 12:29:34 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms070301030406080905080202
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



Alan DeKok wrote:

>Doug Royer <Doug@Royer.com> wrote:
>  
>
>>S/MIME  forces the 'From' address to match the signature.
>>It makes no other claim. It has nothing to do with your location
>>or the originating domain.
>>    
>>
>
>  Which means that you still have no idea if the the address in the
>"From" line is truthful.  Please go back and read the rest of my comments.
>
Now that I have -  so what?

>  If you want to spoof example.com, which has a Canadian branch
>office, as an individual, you can register "example-canada.com", and
>send S/MIME signed messages from it.  The recipients have no way of
>knowing such messages are fraudulent.
>
And which trusted CA are you talking about would issue a user@example.com
address to a example-canada.com email address? None that I know of, so
they could send email as user@example-canada.com - which would not
be forged - so what?

>  Sure, the signature means it's easier to verify that it was *you*
>who committed the fraud, but how does that help the recipients, who've
>lost money?  How does that help law enforcement, when you've used that
>money to flee the country?
>
You have failed to make your point. The only thing you have shown so far
is that user@example-canada.com sent you email.

I own royer.com, it does not mean that I own all businesses named 'royer'.
So again so what?

>  Validating identities means nothing if the identities being
>validated are fraudulent.
>
You have not made the case that user@example-canada.com is invalid.
You just have declared that it is not user@example.com and we agree.

>>If the cert has not been revoked (by checking), then you know that
>>the person that used the cert had permission to use that 'From' address.
>>    
>>
>
>  From who?  The signing authority, who sells signed certs for $40?
>
Read up on certs to find the answer. If you pre declare that your
will not trust any CA anyway - what's your point?

>>*IF* you do trust the CA and it is spam - you could add that public
>>cert to your blacklist, publish that as a spam cert. And you can 
>>*automaticly* find the authority for that domain in the signature
>>and complain.
>>    
>>
>
>  Again, if that information is valid.  If not, you're stuck.
>  
>
Stuck with what? You now know that user@example-canada.com is a cert
to ignore or blacklist. Why is that a bad thing?

>  It's easy to get a domain and/or certificate with fraudulent identities.
>
I'll reimburse you if you can get a fraudulent cert for 'royer.com' from 
a CA that I trust.
Willing to try? In fact I'll pay you twice their fee. Else please stop 
this noise.

>>*IF* you do NOT trust the CA - your where your at now. I for one have
>>a handful of CA's that I trust.
>>    
>>
>
>  That's nice for you.  How does that scale to everyone else?
>
Scale has nothing to do with it - nothing changes.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms070301030406080905080202
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIxMTkyOTM0WjAjBgkqhkiG9w0BCQQxFgQUtCrAILR7vgjluIWfEknh
xLEvwu8wUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAR47C2p1AOBfzjUipATR0i80wG7aM/UKptlCS8PIzK6wAvOW/EEe3zaPd3onyjiVz
day4bIcRL4A3897kPYqSYuRP4tjx2vndRb1WTqwY28fRBJj6qj3a0GPEift7mckx66h91APD
j3aSgf1aw1Vt9TDz1MwTJ8i+0M+E2cRWs662cDC6tc1EC06ry73tZHjQgWEiVtg49hpz9Wk2
3IOzK56cNkPTYSGgeECAXwnnHU/I7NRvJnS7GTjp2a/7TXCOE3P0WbB7mZuM40VmPhyIqI7d
njQ2YpN1DMocUoK4sAv61ArA5vMkebiAR1HCVUlAItA/ByN0BrKLF+VFHa6G6gAAAAAAAA==
--------------ms070301030406080905080202--


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



From exim@www1.ietf.org  Sun Mar 21 14:43:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26203
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 14:43:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58qj-0000t6-C1
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 14:43:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LJh9MY003406
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 14:43:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58qj-0000sr-6P
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 14:43:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26188
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 14:43:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58qg-0000zt-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:43:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B58pn-0000rz-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:42:12 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58on-0000il-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:41:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58of-0000Ov-PD; Sun, 21 Mar 2004 14:41:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58nn-0000A4-DW
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 14:40:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26042
	for <asrg@ietf.org>; Sun, 21 Mar 2004 14:40:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58nk-0000a8-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:40:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B58md-0000Qo-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:38:56 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58lt-0000G1-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:38:09 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2LJbaFp020784
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Sun, 21 Mar 2004 11:37:38 -0800
Message-ID: <405DEF00.6030306@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
References: <20040321165433.9897.qmail@xuxa.iecc.com>
In-Reply-To: <20040321165433.9897.qmail@xuxa.iecc.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070706030407020702050606"
Subject: [Asrg] Re: S/MIME
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 12:37:36 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms070706030407020702050606
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



John Levine wrote:

>>If the cert has not been revoked (by checking), then you know that
>>the person that used the cert had permission to use that 'From' address.
>>    
>>
>
>Well, not quite, you know that the CA that signed the cert thought
>that the sender had permission to use that address.
>
Which is why I said:

    "The  signature only means - yes the signature matches the From line. "

and

  "*IF* you trust the CA in the signature, then you trust that it came from
    a valid user of that email address and was not forged. "

>>*IF* you trust the CA in the signature, then you trust that it came from
>>a valid user of that email address and was not forged.
>>    
>>
>
>We're back to the key management problem.  I don't see how a public
>signer that signed enough keys to be useful as a whitelist wouldn't
>also let enough bad guys sneak through that you'd want to use it as
>a blacklist.
>
I do not know of anyone selling keys for a white or black list. I do 
know of a few
CAs that sell certs that match the domains they check them against. The CA
sell certs that match the 'From' line, they do not declare the email 
address pure.

>
>For small and reasonably well defined communities, a company signing
>its employees certs, or various geekly groups who know each other,
>sigs can work, but I've never been able to see a plausible way to
>scale up to the whole world of e-mail.
>  
>
This is mixing subjects. Being able to validate that the 'From' line is 
not forged
has nothing to do with black or white lists.  You can black or white list
based on email address as well as certs - no change to scaleability.

If over time I learn that 'spam-certs-ca' sells certs for any domain name
I can blacklist any cert signed by them. MUCH more scalable that
trying to guess the thousands 'From' address that may be sending spam.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms070706030407020702050606
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIxMTkzNzM2WjAjBgkqhkiG9w0BCQQxFgQUKCHe7rp09OvuONXlOXOH
lxNhbT0wUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAx5HA3L3fJPymq3/5mozhKVoWZuabwwsP+W0OhiXkPBmVVu8fW5ywxoHa3lK1wl4d
KBoxxdBFwqLG7K9AGwJtNvlpwutgDqZudHDqFPTtDnpbI4r90QTLzQmBGpWuZupaI/sOQVQi
WkcaTuYvskXHznvGZeQfqk8ZosXQLuP+NPQbpeZR9Nvnnf3lK56CIs22wB34+04UfVwUxinl
lIkHVS7J/HBsHMHO7CaZaMok63qoFK+8IuL5q5mcWsrWO+w1THh+0nUzc1wBZ0uby4aUYRLC
GbGEZ2nF/2RebA126Vy11UO/QIszSUnsAtwNwOITwREi8EM3WjbWJeO3E/Mk8wAAAAAAAA==
--------------ms070706030407020702050606--


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



From exim@www1.ietf.org  Sun Mar 21 14:52:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26547
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 14:52:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58zH-0001PT-Um
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 14:52:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LJpxJU005413
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 14:51:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58zH-0001PE-Pk
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 14:51:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26532
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 14:51:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58zF-0001y9-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:51:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B58yO-0001rZ-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:51:05 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58xU-0001lp-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:50:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58xO-00016Y-JX; Sun, 21 Mar 2004 14:50:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58sP-0000vi-6O
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 14:44:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26271
	for <asrg@ietf.org>; Sun, 21 Mar 2004 14:44:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58sM-0001CR-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:44:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B58rQ-00015o-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:43:53 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58qP-0000xj-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:42:49 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B58qP-0004lx-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:42:49 -0500
Received: from [68.244.134.132] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B58qO-00014r-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:42:49 -0500
Message-ID: <405DF02E.6050905@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME
References: <20040321150043.BD4DD170BB@mail.nitros9.org> <405DED1E.6010102@Royer.com>
In-Reply-To: <405DED1E.6010102@Royer.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 14:42:38 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Doug Royer wrote:
> Alan DeKok wrote:
> 
>> Doug Royer <Doug@Royer.com> wrote:
>>  

>>  Validating identities means nothing if the identities being
>> validated are fraudulent.
>>
> You have not made the case that user@example-canada.com is invalid.
> You just have declared that it is not user@example.com and we agree.
> 

You know that a given email address or domain is valid, and matches the 
S/MIME certificate. Now what? It still does not prove to you that 
someone is not a spammer.

Yakov

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



From exim@www1.ietf.org  Sun Mar 21 14:53:20 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26598
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 14:53:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5909-0001X0-6i
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 14:52:53 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LJqrOe005880
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 14:52:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5909-0001Wl-1w
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 14:52:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26569
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 14:52:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5906-00025I-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:52:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B58zA-0001xY-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:51:53 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58yK-0001qu-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:51:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58yL-0001GF-RD; Sun, 21 Mar 2004 14:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B58xL-00016A-Ew
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 14:49:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26518
	for <asrg@ietf.org>; Sun, 21 Mar 2004 14:49:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58xI-0001lI-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:49:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B58wM-0001gV-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:48:59 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B58vz-0001av-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:48:35 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B58vz-0006Dz-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:48:35 -0500
Received: from [68.244.134.132] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B58vx-0001My-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:48:35 -0500
Message-ID: <405DF189.1020708@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] Re: S/MIME
References: <20040321165433.9897.qmail@xuxa.iecc.com> <405DEF00.6030306@Royer.com>
In-Reply-To: <405DEF00.6030306@Royer.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 14:48:25 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Doug Royer wrote:
>>
>> For small and reasonably well defined communities, a company signing
>> its employees certs, or various geekly groups who know each other,
>> sigs can work, but I've never been able to see a plausible way to
>> scale up to the whole world of e-mail.
>>  
>>
> This is mixing subjects. Being able to validate that the 'From' line is 
> not forged
> has nothing to do with black or white lists.  You can black or white list
> based on email address as well as certs - no change to scaleability.
> 

While S/MIME certificates may prove to you that a given email address or 
domain is valid, the question is what do we do with that information? 
The end goal here is to reduce spam - the question is how would the use 
of S/MIME help with that?

This is the same problem that we face with LMAP/MARID proposals like SPF 
- once you have established identity, what do you do with that identity? 
Same for IP addresses of MTAs.

> If over time I learn that 'spam-certs-ca' sells certs for any domain name
> I can blacklist any cert signed by them. MUCH more scalable that
> trying to guess the thousands 'From' address that may be sending spam.
> 

Just like we cannot blacklist domain registrars, we will not be able to 
do the same for CAs. All that the CA is providing is assurance that a 
given email address or domain matches the information in the 
certificate. They do not try to tell us whether a given person is a 
spammer. Same for domain registrars.

Yakov

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



From exim@www1.ietf.org  Sun Mar 21 15:01:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26884
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 15:01:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B597y-0003mi-S0
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 15:00:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LK0wiD014539
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 15:00:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B597y-0003mM-Lp
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 15:00:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26879
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 15:00:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B597v-0002v3-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 15:00:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B596v-0002qa-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:59:54 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B596A-0002m7-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 14:59:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5965-0001lQ-Fz; Sun, 21 Mar 2004 14:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B595y-0001lF-S7
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 14:58:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26821
	for <asrg@ietf.org>; Sun, 21 Mar 2004 14:58:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B595w-0002lR-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:58:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5954-0002gj-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:57:59 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B594U-0002Z4-00
	for asrg@ietf.org; Sun, 21 Mar 2004 14:57:22 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2LJuoFp020955
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Sun, 21 Mar 2004 11:56:51 -0800
Message-ID: <405DF381.6020006@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME
References: <20040321150043.BD4DD170BB@mail.nitros9.org> <405DED1E.6010102@Royer.com> <405DF02E.6050905@solidmatrix.com>
In-Reply-To: <405DF02E.6050905@solidmatrix.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms050501090201000901050107"
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 12:56:49 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms050501090201000901050107
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



Yakov Shafranovich wrote:

>
>>>  Validating identities means nothing if the identities being
>>> validated are fraudulent.
>>>
>> You have not made the case that user@example-canada.com is invalid.
>> You just have declared that it is not user@example.com and we agree.
>>
>
> You know that a given email address or domain is valid, and matches 
> the S/MIME certificate. Now what? It still does not prove to you that 
> someone is not a spammer.

Now go back and read my email and point out where I said that S/MIME
emails are guaranteed free from spam? I said it would stop forged email.
I made no other claim. I also said that would stop the 1,000's of forged 
emails I get
every week on the systems I administer.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms050501090201000901050107
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIxMTk1NjQ5WjAjBgkqhkiG9w0BCQQxFgQUKARydOcD4xcuemk5clSJ
gx/fU4AwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEApTE1UptVKQ229mthTiNzxxewxQKpgzKcIDVpXcD30kxYEiPRBEc+ZVQRAzhNkaRI
C3TJ9OhFoLecwqjZNA+lSVmiKu+l5PZprzxde1mxGaMAC0/XkdrsFAbxj7YquxUVh8on4FD1
VjzEv/mN+nNqfwMEdljGidfEaNXaWKxZcD1HLnGwM0bQawBg5/2TrqJKs48k+hBlHxSGCz8O
tLfiwswNqtxZJbO5uSc54I1MvF6UEpCuFj6tqujRrFTGVzXMhYynEn99NXjbcWHzyc9Az1Tu
8XzkhT9UVHS/1tm93bEDQgslvu/adM6ErCV9JRM6TtMM7O6O/7Cc8z9Hn8D7HQAAAAAAAA==
--------------ms050501090201000901050107--


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



From exim@www1.ietf.org  Sun Mar 21 15:21:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28567
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 15:21:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B59RI-0005Za-Q5
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 15:20:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LKKutR021416
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 15:20:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B59RI-0005ZL-JV
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 15:20:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28560
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 15:20:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B59RH-0004k6-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 15:20:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B59QO-0004es-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 15:20:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B59Pd-0004ZT-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 15:19:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B59PR-0005He-5C; Sun, 21 Mar 2004 15:19:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B59LR-0003mw-78
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 15:14:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28080
	for <asrg@ietf.org>; Sun, 21 Mar 2004 15:14:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B59LQ-00049Q-00
	for asrg@ietf.org; Sun, 21 Mar 2004 15:14:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B59KS-00044l-00
	for asrg@ietf.org; Sun, 21 Mar 2004 15:13:53 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B59Js-00040L-00
	for asrg@ietf.org; Sun, 21 Mar 2004 15:13:16 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B59Jt-0007X0-00
	for asrg@ietf.org; Sun, 21 Mar 2004 15:13:17 -0500
Received: from [68.244.134.132] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B59Jr-0002TV-00
	for asrg@ietf.org; Sun, 21 Mar 2004 15:13:17 -0500
Message-ID: <405DF753.3020404@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME
References: <20040321150043.BD4DD170BB@mail.nitros9.org> <405DED1E.6010102@Royer.com> <405DF02E.6050905@solidmatrix.com> <405DF381.6020006@Royer.com>
In-Reply-To: <405DF381.6020006@Royer.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 15:13:07 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Doug Royer wrote:
> Yakov Shafranovich wrote:
>>
>>>>  Validating identities means nothing if the identities being
>>>> validated are fraudulent.
>>>>
>>> You have not made the case that user@example-canada.com is invalid.
>>> You just have declared that it is not user@example.com and we agree.
>>
>> You know that a given email address or domain is valid, and matches 
>> the S/MIME certificate. Now what? It still does not prove to you that 
>> someone is not a spammer.
> 
> Now go back and read my email and point out where I said that S/MIME
> emails are guaranteed free from spam? I said it would stop forged email.
> I made no other claim. I also said that would stop the 1,000's of forged 
> emails I get
> every week on the systems I administer.
> 

Mea culpa - you only addressed the forgery issue. There are still some 
interoperability issues with S/MIME but that's probably something that 
will be solved sooner or later.

However, this is an anti-spam group and within the context of fighting 
spam, how will this help? The problem that I have is that there are 
several identity schemes here and none of them address the point of what 
do you do, once the identity is established. There is IP identity, 
domain/IP identity (LMAP/MARID), more heavier cryptographic identities, 
etc. All of these lead into the same point - once the identity has been 
established, what happens then?

This is a question to the entire group, not you directly.

Yakov

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



From exim@www1.ietf.org  Sun Mar 21 15:37:03 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29309
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 15:37:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B59gR-00078x-9r
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 15:36:35 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LKaZwo027456
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 15:36:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B59gR-00078j-4X
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 15:36:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29280
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 15:36:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B59gP-0006xi-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 15:36:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B59fB-0006ma-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 15:35:18 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B59eZ-0006eE-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 15:34:39 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B59eZ-0006vs-DH
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 15:34:39 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B59dx-0006sy-3W; Sun, 21 Mar 2004 15:34:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B59dq-0006s1-Hv
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 15:33:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29178
	for <asrg@ietf.org>; Sun, 21 Mar 2004 15:33:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B59dp-0006Yv-00
	for asrg@ietf.org; Sun, 21 Mar 2004 15:33:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B59cr-0006Tx-00
	for asrg@ietf.org; Sun, 21 Mar 2004 15:32:54 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B59cg-0006Oy-00
	for asrg@ietf.org; Sun, 21 Mar 2004 15:32:42 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2LKW9Fp021583
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Sun, 21 Mar 2004 12:32:10 -0800
Message-ID: <405DFBC8.9060400@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] Re: S/MIME
References: <20040321165433.9897.qmail@xuxa.iecc.com> <405DEF00.6030306@Royer.com> <405DF189.1020708@solidmatrix.com>
In-Reply-To: <405DF189.1020708@solidmatrix.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020205080907050303020901"
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 13:32:08 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms020205080907050303020901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



Yakov Shafranovich wrote:

> Doug Royer wrote:
>
>>>
>>> For small and reasonably well defined communities, a company signing
>>> its employees certs, or various geekly groups who know each other,
>>> sigs can work, but I've never been able to see a plausible way to
>>> scale up to the whole world of e-mail.
>>>  
>>>
>> This is mixing subjects. Being able to validate that the 'From' line 
>> is not forged
>> has nothing to do with black or white lists.  You can black or white 
>> list
>> based on email address as well as certs - no change to scaleability.
>>
>
> While S/MIME certificates may prove to you that a given email address 
> or domain is valid, the question is what do we do with that 
> information? The end goal here is to reduce spam - the question is how 
> would the use of S/MIME help with that? 

Computer automated traceability when you trust the CA.

Computer automated cert blacklist creation on spam detection.

Currently it takes manual labor to track spam. Some things can be 
automated, others
take manual time to verify or decipher the true source of the spam. With 
certs from
trusted CAs you can automatically process the cert  back to the cert domain
and complain, blacklist or whatever.

Now you know who is responsible for the domain that used that 'From' 
line.  I can automate
the rejection of that cert. And over time I may elect to stop trusting 
and toss all email
signed by that CA if it turns out they sell a cert to anyone for any domain.

If all email was required to be signed. A spammer could buy a cert from 
a trusted
CA. It would take seconds to minutes for that  cert to be blacklisted 
once they started
sending spam. They would get one shot per cert and that cert would then 
be useless
in a very short amount of time. They would hit very view systems that used a
shared cert blacklist. It would not matter if each copy of the spam was 
unique
or not. A VERY expensive way to send spam.

>
> This is the same problem that we face with LMAP/MARID proposals like 
> SPF - once you have established identity, what do you do with that 
> identity? Same for IP addresses of MTAs. 

Not sure why you think that SPF establishes identity. It only says that 
domain X is
valid for sending with the  address for the listed domain.

Virtual hosting makes blacklisting the IP address a hostile act to the 
innocent
domains on the same shared virtual hosts. Not the same issue.

>> If over time I learn that 'spam-certs-ca' sells certs for any domain 
>> name
>> I can blacklist any cert signed by them. MUCH more scalable that
>> trying to guess the thousands 'From' address that may be sending spam.
>>
>
> Just like we cannot blacklist domain registrars, we will not be able 
> to do the same for CAs. All that the CA is providing is assurance that 
> a given email address or domain matches the information in the 
> certificate. They do not try to tell us whether a given person is a 
> spammer. Same for domain registrars. 

I agree and I never claimed it would stop spam. I claimed it would stop 
forged email.
And I claim that it would allow for much faster an accurate spam blacklists.

Anyone can blacklist a non-trusted CA.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms020205080907050303020901
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIxMjAzMjA4WjAjBgkqhkiG9w0BCQQxFgQUwNrl4q8jiNoquCEFv2iT
DZmtx60wUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAifeKMeH4Apq7PTaz4MTB0LYuJCsQkR7a2S2wLnAvKKRyZp9qsQ+bguXXGH46fTLT
sb1htl2DLzocD5PBImE9PbAhWXGerWgHp2IFO5N7rL8LftZ7/42MiX58HwfwU/myjoakEsly
caBUNOdKvpjIqqel9HUZtD2+VGhy/pNtF1bEC69jvg9S1OOTIieaZAjCEC+mkgoSkvfg798S
eJ2BCNX4OIOLqJm3iS8DMXMBNoLJ1dIZeCW6deHYZDR/3Eq/CY0gw3BJqe7AkTjnlc70Yp6R
hLbs3jkMxhyMvYo5qnhW+DEh40fB7/xTA9cIo3l9PEBqp7efhzCCC47YXFyYIgAAAAAAAA==
--------------ms020205080907050303020901--


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



From exim@www1.ietf.org  Sun Mar 21 16:08:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00551
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 16:08:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AAy-0001Eq-5i
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 16:08:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LL887V004745
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 16:08:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AAx-0001EA-KM
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 16:08:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00355
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 16:08:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5AAw-0003RL-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:08:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5A7K-0002ca-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:04:22 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5A5t-0002OU-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:02:53 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B59wm-0007dY-Be
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 15:53:28 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B59wL-0008WS-2r; Sun, 21 Mar 2004 15:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B59wD-0008Vh-JO
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 15:52:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29980
	for <asrg@ietf.org>; Sun, 21 Mar 2004 15:52:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B59wC-0001ee-00
	for asrg@ietf.org; Sun, 21 Mar 2004 15:52:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B59vH-0001Ye-00
	for asrg@ietf.org; Sun, 21 Mar 2004 15:51:56 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B59ui-0001Sv-00
	for asrg@ietf.org; Sun, 21 Mar 2004 15:51:20 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2LKomFp021730
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Sun, 21 Mar 2004 12:50:49 -0800
Message-ID: <405E0027.9090404@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME
References: <20040321150043.BD4DD170BB@mail.nitros9.org> <405DED1E.6010102@Royer.com> <405DF02E.6050905@solidmatrix.com> <405DF381.6020006@Royer.com> <405DF753.3020404@solidmatrix.com>
In-Reply-To: <405DF753.3020404@solidmatrix.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms090100030200020407030307"
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 13:50:47 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL,OPT_OUT_CAPS autolearn=no 
	version=2.60

This is a cryptographically signed message in MIME format.

--------------ms090100030200020407030307
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit


>
> However, this is an anti-spam group and within the context of fighting 
> spam, how will this help? The problem that I have is that there are 
> several identity schemes here and none of them address the point of 
> what do you do, once the identity is established. There is IP 
> identity, domain/IP identity (LMAP/MARID), more heavier cryptographic 
> identities, etc. All of these lead into the same point - once the 
> identity has been established, what happens then?
>
> This is a question to the entire group, not you directly. 


(1) Sign email so that you have a handle for the sender.

(2) Create a standard header that provides information for an 'opt-out'. And
      can be used automatically by a computer. That data needs to also 
include the RCPT value
      that was used as the target. Legal spammers and mailing lists 
would use this.

     Now you can get off of lists by clicking an OPT-OUT button on a 
future MUAs
     that says 'take this RCPT TO' value and remove it from your lists'.

(3) Create a protocol for for black lists much like the IM complain buttons.
      It does not matter why thousands of people 'complain' about the 
email (or IM)
      If thousands of people complain, add the cert to the black list.

     Have the protocol track if the user says 'spam', 'offensive', or 
whatever.
     Allow the black list subscribers to select they do not care about 
offensive
     complaints and only want a mostly spam free inbox. We have PG-13
     PG-17 and it got this rating for 'adult content' or whatever. No 
censoring
     of the address, just a meta tag. One, two, or a few may get mis 
tagged a few times.
     But thousands of people says 'offensive' would be a good hint to 
others.

     Who would hold this data? The same people that make money selling
     the much less accurate black lists now. If you do not like them, do 
not subscribe.

(4) Some kind of SPF record is needed. If someone steals my S/MIME cert
       and the matching password. They COULD send spam as me. But with
       some kind of SPF record, they would have to do that from my domain.

       Now I can retake control of my cert (a) cancel it (b) blacklist my
       own cert as 'stolen' (c) call my admin and say that 'someone' 
from 'our'
       domain has stolen my cert and password and is sending email as me.
       MUCH more controllable and trackable.

(5) If some kind of virus figures out how to use my cert / password.
       Same solution as (4).

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms090100030200020407030307
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIxMjA1MDQ3WjAjBgkqhkiG9w0BCQQxFgQUKDA+ppfvlFPXFX4tVgBj
5aDpCfgwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAFVOPNaY40ZwpQwrB0fnnd4WHegoKCqEvMhFIaKUvSd95BDDpcI/tPLLcja5edcT4
WdOROsBRZaRiKAG+kPb1VrxODGhXzduqJZB/BLeeaPSf47b3K0XLThhvmftpV33SwWZi3rwm
exnvKP/exG529d4Xb8EiNoCxPEeX0U2bh1GWbFsBV4QynL7QB0DiJXAi6j2WSO59EX1NISiS
r+Io7l4YYXRj01X05RWcP+wim6Cuo8ypAfxN/HNqgo8FTlluliC2RISj2NFaG7hVH9NTb7pH
J4XEIp60sPxMXSzXWNUf6ifMNj8LJ9F/HBsVOEQwzWnKfJbBYeCyNJfZX2v1pAAAAAAAAA==
--------------ms090100030200020407030307--


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



From exim@www1.ietf.org  Sun Mar 21 16:24:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01475
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 16:24:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AQP-0002r8-2e
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 16:24:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LLO59f010972
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 16:24:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AQO-0002qt-Sb
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 16:24:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01452
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 16:24:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5AQN-0005My-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:24:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5APP-0005Gh-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:23:03 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5AOd-0005Af-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:22:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AOO-0002QY-Ao; Sun, 21 Mar 2004 16:22:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AON-0002QN-7h
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 16:21:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01390
	for <asrg@ietf.org>; Sun, 21 Mar 2004 16:21:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5AOL-00059h-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:21:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5ANM-00054f-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:20:57 -0500
Received: from xuxa.iecc.com ([208.31.42.42])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5AMr-0004zm-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:20:25 -0500
Received: (qmail 25122 invoked by uid 100); 21 Mar 2004 21:20:24 -0000
Message-ID: <20040321212024.25121.qmail@xuxa.iecc.com>
From: John Levine <asrg@johnlevine.com>
To: asrg@ietf.org
Subject: Re: [Asrg] Re: S/MIME
In-Reply-To: <405DFBC8.9060400@Royer.com>
Organization: I.E.C.C., Trumansburg NY USA
Cc: asrg@ietf.org
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/mail-archive/working-groups/asrg/>
Date: 21 Mar 2004 21:20:24 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

>Computer automated cert blacklist creation on spam detection.

Oh, goody, anyone who dislikes me can send in a few denouncements and
get me added to blacklists.  You're making one of the classic FUSSP
errors, to assume that bad guys (not all of whom are spammers) will
play by the rules.

AOL has a system fairly similar to what you're proposing built around
their spam button.  Since their mail system is closed, they know the
IP from which each message was sent, and they carefully track the
complaint rates of each sending IP.  Moreover, if you send them your
IP range and contact address, their scomp subsystem will send you back
the mail that people complain about.  I can report that 100% of the
mail that scomp sends me is either mail from confirmed opt-in lists or
direct responses to mail that the AOL member sent.  None of it is spam
by any definition other than "mail I don't want".  If you're going to
blacklist on complaints, the false positive level will be ferocious.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
http://www.taugh.com


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



From exim@www1.ietf.org  Sun Mar 21 16:25:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01512
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 16:25:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5ARE-0002sL-9O
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 16:24:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LLOuaY011047
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 16:24:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5ARE-0002s6-4w
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 16:24:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01501
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 16:24:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5ARC-0005Sa-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:24:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5AQJ-0005MW-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:23:59 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5APM-0005G7-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:23:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5APM-0002hO-W4; Sun, 21 Mar 2004 16:23:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AOO-0002Qc-Ke
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 16:22:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01395
	for <asrg@ietf.org>; Sun, 21 Mar 2004 16:21:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5AOM-00059s-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:21:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5ANO-00054v-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:20:58 -0500
Received: from xuxa.iecc.com ([208.31.42.42])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5AMu-0004zp-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:20:28 -0500
Received: (qmail 25122 invoked by uid 100); 21 Mar 2004 21:20:24 -0000
Message-ID: <20040321212024.25121.qmail@xuxa.iecc.com>
From: John Levine <asrg@johnlevine.com>
To: asrg@ietf.org
Subject: Re: [Asrg] Re: S/MIME
In-Reply-To: <405DFBC8.9060400@Royer.com>
Organization: I.E.C.C., Trumansburg NY USA
Cc: asrg@ietf.org
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/mail-archive/working-groups/asrg/>
Date: 21 Mar 2004 21:20:24 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

>Computer automated cert blacklist creation on spam detection.

Oh, goody, anyone who dislikes me can send in a few denouncements and
get me added to blacklists.  You're making one of the classic FUSSP
errors, to assume that bad guys (not all of whom are spammers) will
play by the rules.

AOL has a system fairly similar to what you're proposing built around
their spam button.  Since their mail system is closed, they know the
IP from which each message was sent, and they carefully track the
complaint rates of each sending IP.  Moreover, if you send them your
IP range and contact address, their scomp subsystem will send you back
the mail that people complain about.  I can report that 100% of the
mail that scomp sends me is either mail from confirmed opt-in lists or
direct responses to mail that the AOL member sent.  None of it is spam
by any definition other than "mail I don't want".  If you're going to
blacklist on complaints, the false positive level will be ferocious.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
http://www.taugh.com


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



From exim@www1.ietf.org  Sun Mar 21 16:31:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01736
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 16:31:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AX7-00038H-Td
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 16:31:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LLV15J012035
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 16:31:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AX7-00037s-OP
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 16:31:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01722
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 16:30:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5AX5-00062D-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:31:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5AW8-0005wI-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:30:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5AVE-0005qh-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:29:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AVB-0002wY-FJ; Sun, 21 Mar 2004 16:29:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AVA-0002wL-GW
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 16:29:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01631
	for <asrg@ietf.org>; Sun, 21 Mar 2004 16:28:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5AV8-0005po-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:28:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5AU7-0005kM-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:27:56 -0500
Received: from sparkle.rodents.montreal.qc.ca ([216.46.5.7] ident=J6qoPluSKtrU8IC2rW0Y8H4FMd769bJaQhTQac50PoZ)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5ATY-0005fQ-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:27:20 -0500
Received: (from mouse@localhost)
	by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id QAA10761;
	Sun, 21 Mar 2004 16:27:14 -0500 (EST)
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Message-Id: <200403212127.QAA10761@Sparkle.Rodents.Montreal.QC.CA>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
To: asrg@ietf.org
Subject: Re: [Asrg] Re: S/MIME
In-Reply-To: <405DF189.1020708@solidmatrix.com>
References: <20040321165433.9897.qmail@xuxa.iecc.com> <405DEF00.6030306@Royer.com>
	<405DF189.1020708@solidmatrix.com>
Content-Transfer-Encoding: 8bit
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 16:19:55 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> Just like we cannot blacklist domain registrars,

We can't?  I see no real reason why not.  It would be mildly
complicated by all the different whois output formats, but only mildly.
(More of a problem would be that a few TLDs don't tell you what the
registrar for a domain is in a form that can be matched up with other
TLDs' info, but that merely means you have to maintain separate BLs for
such TLDs.)

You do write that

> [CAs] do not try to tell us whether a given person is a spammer.
> Same for domain registrars.

Legitmate CAs, and legitimate registrars, perhaps.  But even among the
legitimate ones, some will be spammer-friendlier than others, and there
will soon be some that are pure spammer fronts - for example, if I
thought it were worth the bother to implement, I would cheerfully
reject anything registered through paycenter.com.cn.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

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



From exim@www1.ietf.org  Sun Mar 21 16:50:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02285
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 16:50:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Api-00045W-Db
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 16:50:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LLoEls015707
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 16:50:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Api-00045G-8I
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 16:50:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02282
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 16:50:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Apg-0000Ct-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:50:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Aoo-00005Q-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:49:19 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Anl-0007lR-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 16:48:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5AnY-0003sD-JH; Sun, 21 Mar 2004 16:48:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Aho-0003iK-PJ
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 16:42:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02096
	for <asrg@ietf.org>; Sun, 21 Mar 2004 16:42:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Ahm-00079j-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:42:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Agr-00074C-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:41:06 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5AgS-0006yB-00
	for asrg@ietf.org; Sun, 21 Mar 2004 16:40:40 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B5Aex-0004Qt-00; Sun, 21 Mar 2004 16:39:07 -0500
Received: from [68.244.134.132] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B5Aew-0005CL-00; Sun, 21 Mar 2004 16:39:07 -0500
Message-ID: <405E0B6C.7080907@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: der Mouse <mouse@Rodents.Montreal.QC.CA>
CC: asrg@ietf.org
Subject: Re: [Asrg] Re: S/MIME
References: <20040321165433.9897.qmail@xuxa.iecc.com> <405DEF00.6030306@Royer.com>	<405DF189.1020708@solidmatrix.com> <200403212127.QAA10761@Sparkle.Rodents.Montreal.QC.CA>
In-Reply-To: <200403212127.QAA10761@Sparkle.Rodents.Montreal.QC.CA>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 16:38:52 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

der Mouse wrote:
>>Just like we cannot blacklist domain registrars,
> 
> 
> We can't?  I see no real reason why not.  It would be mildly
> complicated by all the different whois output formats, but only mildly.
> (More of a problem would be that a few TLDs don't tell you what the
> registrar for a domain is in a form that can be matched up with other
> TLDs' info, but that merely means you have to maintain separate BLs for
> such TLDs.)
> 

Technically it is feasible, practically it might not be as simple.

> You do write that
> 
> 
>>[CAs] do not try to tell us whether a given person is a spammer.
>>Same for domain registrars.
> 
> 
> Legitmate CAs, and legitimate registrars, perhaps.  But even among the
> legitimate ones, some will be spammer-friendlier than others, and there
> will soon be some that are pure spammer fronts - for example, if I
> thought it were worth the bother to implement, I would cheerfully
> reject anything registered through paycenter.com.cn.
> 

How can a registrar be "spam friendly"? They are not required to do any 
checking at all on registrations, so I am not sure how that would be 
defined.

Yakov

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



From exim@www1.ietf.org  Sun Mar 21 17:08:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03017
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 17:08:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5B6w-0005Xi-IV
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 17:08:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LM82JQ021292
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 17:08:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5B6v-0005XD-No
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 17:08:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03001
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 17:07:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5B6t-0002Dg-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 17:07:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5B5s-00026P-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 17:06:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5B55-00021g-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 17:06:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5B4z-000511-KC; Sun, 21 Mar 2004 17:06:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5B42-0004uY-J8
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 17:05:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02938
	for <asrg@ietf.org>; Sun, 21 Mar 2004 17:04:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5B40-0001vR-00
	for asrg@ietf.org; Sun, 21 Mar 2004 17:05:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5B36-0001qY-00
	for asrg@ietf.org; Sun, 21 Mar 2004 17:04:04 -0500
Received: from sparkle.rodents.montreal.qc.ca ([216.46.5.7] ident=EAShZAhh4COJkICzcVzJyQERcXZaaz6kgXdcx7nm5Lw)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5B2q-0001lK-00
	for asrg@ietf.org; Sun, 21 Mar 2004 17:03:48 -0500
Received: (from mouse@localhost)
	by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id RAA11017;
	Sun, 21 Mar 2004 17:03:47 -0500 (EST)
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Message-Id: <200403212203.RAA11017@Sparkle.Rodents.Montreal.QC.CA>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Erik-Conspiracy: There is no Conspiracy - and if there were I wouldn't be part of it anyway.
To: asrg@ietf.org
Subject: Re: [Asrg] Re: S/MIME
In-Reply-To: <405E0B6C.7080907@solidmatrix.com>
References: <20040321165433.9897.qmail@xuxa.iecc.com> <405DEF00.6030306@Royer.com>	<405DF189.1020708@solidmatrix.com> <200403212127.QAA10761@Sparkle.Rodents.Montreal.QC.CA>
	<405E0B6C.7080907@solidmatrix.com>
Content-Transfer-Encoding: 8bit
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 16:55:54 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

> How can a registrar be "spam friendly"?

- The registrar may actually *be* a spammer.  I've seen it said that
   paycenter.com.cn is an example, and what I've found on the subject
   certainly doesn't disagree.

- They may fail to nuke spamemr domains once they are noticed and
   pointed out to them.  (Such failure was recently almost universal.
   This is changing.)

- They may fail to make even rudimentary checks on the information
   provided.  For example, I once saw a spammer domain registered with
   country=US, state=Madrid.  I've seen spammer domains registered to
   postal addresses containing no letter but X, repeated many times
   over.

- They may do pink contracts, or ignore complaints, or any of the
   various other ways that any organization can be spam-friendly.

> They are not required to do any checking at all on registrations, so
> I am not sure how that would be defined.

They are not required to do any checking, no, but they are not
prohibited from, either.  Failing to take reasonable antispam steps
(even if not strictly required to) counts as spam-friendly in most
other contexts (ISPs, webhosters, etc); I don't see why it wouldn't for
domain registrars too.

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B

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



From exim@www1.ietf.org  Sun Mar 21 17:52:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04604
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 17:52:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5BnW-0008Bp-Tw
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 17:52:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LMq2Z6031475
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 17:52:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5BnW-0008Ba-QN
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 17:52:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04596
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 17:51:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5BnU-0007Bq-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 17:52:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Bmk-00075K-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 17:51:14 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Bll-0006vK-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 17:50:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5BlZ-0007k2-Su; Sun, 21 Mar 2004 17:50:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Bkf-0007ig-3j
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 17:49:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA04396
	for <asrg@ietf.org>; Sun, 21 Mar 2004 17:49:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Bkc-0006i7-00
	for asrg@ietf.org; Sun, 21 Mar 2004 17:49:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5BjW-0006SA-00
	for asrg@ietf.org; Sun, 21 Mar 2004 17:47:55 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Bi6-0006DF-00
	for asrg@ietf.org; Sun, 21 Mar 2004 17:46:26 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id EE3CE170BB
	for <asrg@ietf.org>; Sun, 21 Mar 2004 17:50:08 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME 
In-Reply-To: Your message of "Sun, 21 Mar 2004 12:29:34 MST."
             <405DED1E.6010102@Royer.com> 
Message-Id: <20040321225008.EE3CE170BB@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 17:50:08 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Doug Royer <Doug@Royer.com> wrote:
> Now that I have -  so what?

  I was pointing out that you have no way of knowing *which* address
is the "real" one.  The fact that all of them are signed and certified
is irrelevant.  When you get email from "user@example.com", and
"user@example-canada.com", and "user@example.ca", you still don't know
which one is real.  The others could very well be fraudulent.

> And which trusted CA are you talking about would issue a user@example.com
> address to a example-canada.com email address? 

  I've never said that.  Stop trying to misinterpret me.

> I own royer.com, it does not mean that I own all businesses named 'royer'.
> So again so what?

  You're missing my point, that's what.  How does *anyone* associate
the "royer" business they know in meat-space with a "royer" they see
on the net?  Heck, I can register 'the-real-royer.com", steal your
content, get certs signed for it, and announce that "royer.com" is
fraudulent.  How much time and money will you lose?  And you won't be
able to catch me.  The best you can hope for is to convince a
registrar to nuke the name.

> >  It's easy to get a domain and/or certificate with fraudulent identities.
> >
> I'll reimburse you if you can get a fraudulent cert for 'royer.com' from 
> a CA that I trust.

  See, I say "fraudulent identities", and you say "fraudulent cert".
Do you understand that you're not talking about the same thing I'm
talking about?

  Alan DeKok.

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



From exim@www1.ietf.org  Sun Mar 21 18:12:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05965
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 18:12:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5C6q-0006WF-Sd
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 18:12:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LNC0Ma025056
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 18:12:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5C6q-0006W2-JR
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 18:12:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05915
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 18:11:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5C6n-0001Rk-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:11:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5C5t-0001Mh-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:11:02 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5C59-0001HY-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:10:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5C4w-0005lM-VM; Sun, 21 Mar 2004 18:10:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5C43-0005Qo-07
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 18:09:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05607
	for <asrg@ietf.org>; Sun, 21 Mar 2004 18:09:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5C40-00018L-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:09:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5C33-00012h-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:08:06 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5C2Y-0000wJ-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:07:34 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2LN72Fp023159
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Sun, 21 Mar 2004 15:07:04 -0800
Message-ID: <405E2015.4070900@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] Re: S/MIME
References: <20040321212024.25121.qmail@xuxa.iecc.com>
In-Reply-To: <20040321212024.25121.qmail@xuxa.iecc.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030202020107070601090805"
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 16:07:01 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms030202020107070601090805
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



John Levine wrote:

>>Computer automated cert blacklist creation on spam detection.
>>    
>>
>
>Oh, goody, anyone who dislikes me can send in a few denouncements and
>get me added to blacklists.  You're making one of the classic FUSSP
>errors, to assume that bad guys (not all of whom are spammers) will
>play by the rules.
>

Oh goody - you have no constructive comments - guess what?
I can add you to my blacklist anyway.

If you don't like them, don't use them.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms030202020107070601090805
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIxMjMwNzAxWjAjBgkqhkiG9w0BCQQxFgQUrgXq34nL8tVP/8RLCdjS
6K0rmjAwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAopFDzzMqB19SlQvq8w3VcNucJmGynbLjJkOFYCApmUlxpsqMW4opJZkhNuge6bGW
O6hq3o+LV45+M/LFN/KJS+HGPdTaHoDiTwDxSfCYWGivjFjFc2urHwazuPOuXNvAvscsi6a1
uEALbiwZ9EzIAUQQK0ISSDv8J9zsflI9sSpc/fvFraPvYaKRPQtTrQV/30CL0Dntj/0DB6oI
rPoFBhNgFsXHi3csbltn1GIwO5yALN8KYpmTlSOMBoyCiSTGwefwY3kCx4B0mMq/gagvCWf/
HoTmY0PmSMYkE3kqZNU30qP8un5W5BvQJSlLKtD+moThTH5bAU/mLwRQhQGbFgAAAAAAAA==
--------------ms030202020107070601090805--


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



From exim@www1.ietf.org  Sun Mar 21 18:16:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06412
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 18:16:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5CAh-0007mk-Hp
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 18:15:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LNFxDo029914
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 18:15:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5CAh-0007mL-D4
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 18:15:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06335
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 18:15:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5CAe-0001rZ-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:15:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5C9i-0001l7-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:14:58 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5C8m-0001ew-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:14:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5C8m-00079z-TB; Sun, 21 Mar 2004 18:14:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5C7p-0006ud-In
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 18:13:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA06036
	for <asrg@ietf.org>; Sun, 21 Mar 2004 18:12:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5C7m-0001Yn-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:12:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5C6s-0001Sd-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:12:03 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5C61-0001He-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:11:09 -0500
Received: from mbaugher-w2k07.cisco.com (sjc-vpn3-995.cisco.com [10.21.67.227])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i2LNAa8Q016545
	for <asrg@ietf.org>; Sun, 21 Mar 2004 15:10:37 -0800 (PST)
Message-Id: <6.0.0.22.2.20040321150759.03dbbcc8@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
To: asrg@ietf.org
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [Asrg] S/MIME
In-Reply-To: <405DF753.3020404@solidmatrix.com>
References: <20040321150043.BD4DD170BB@mail.nitros9.org>
 <405DED1E.6010102@Royer.com>
 <405DF02E.6050905@solidmatrix.com>
 <405DF381.6020006@Royer.com>
 <405DF753.3020404@solidmatrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 15:10:35 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

At 12:13 PM 3/21/2004, Yakov Shafranovich wrote:
<...>
>Mea culpa - you only addressed the forgery issue. There are still some 
>interoperability issues with S/MIME but that's probably something that 
>will be solved sooner or later.
>
>However, this is an anti-spam group and within the context of fighting 
>spam, how will this help? The problem that I have is that there are 
>several identity schemes here and none of them address the point of what 
>do you do, once the identity is established. There is IP identity, 
>domain/IP identity (LMAP/MARID), more heavier cryptographic identities, 
>etc. All of these lead into the same point - once the identity has been 
>established, what happens then?
>
>This is a question to the entire group, not you directly.

If we get forgery under control, then it is possible to apply reputation, 
accreditation, blacklisting and other techniques to manage spam.  What am I 
missing?

Mark


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



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



From exim@www1.ietf.org  Sun Mar 21 18:39:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07463
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 18:39:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5CWz-0002Oe-RA
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 18:39:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LNd1aV009207
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 18:39:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5CWz-0002ON-BF
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 18:39:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07423
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 18:38:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5CWw-0004SA-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:38:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5CVz-0004Lo-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:38:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5CV9-0004Ez-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:37:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5CV3-0001l3-F2; Sun, 21 Mar 2004 18:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5CUB-0001jN-8c
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 18:36:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07250
	for <asrg@ietf.org>; Sun, 21 Mar 2004 18:36:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5CU8-00047d-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:36:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5CTK-00041o-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:35:15 -0500
Received: from royer.com ([4.23.9.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5CSk-0003qj-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:34:38 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2LNXtFp023384
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Sun, 21 Mar 2004 15:33:57 -0800
Message-ID: <405E2662.4040703@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME
References: <20040321225008.EE3CE170BB@mail.nitros9.org>
In-Reply-To: <20040321225008.EE3CE170BB@mail.nitros9.org>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms000408030702090406020208"
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 16:33:54 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms000408030702090406020208
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



Alan DeKok wrote:

>Doug Royer <Doug@Royer.com> wrote:
>  
>
>>Now that I have -  so what?
>>    
>>
>
>  I was pointing out that you have no way of knowing *which* address
>is the "real" one.  The fact that all of them are signed and certified
>is irrelevant.  When you get email from "user@example.com", and
>"user@example-canada.com", and "user@example.ca", you still don't know
>which one is real.  The others could very well be fraudulent.
>

If you get a signed message where the cert is signed by a trusted CA, then
it is not fraudulent. It is the 'From' address when the signature matches.

Are you claming that you want some way to tell if the content is fraudulent?

>>And which trusted CA are you talking about would issue a user@example.com
>>address to a example-canada.com email address? 
>>    
>>
>
>  I've never said that.  Stop trying to misinterpret me.
>
Then you have failed to make your point as it can't be fraudulent if the
cert is valid from a trusted CA.

>I own royer.com, it does not mean that I own all businesses named 'royer'.
>So again so what?
>  
>
>
>  You're missing my point, that's what.  How does *anyone* associate
>the "royer" business they know in meat-space with a "royer" they see
>on the net?
>
New flash: There are several 'royer.whatever' sites around the world. In 
case this
has confused you  - we are not related in any way with each other. The same
is true of MANY commercial establishments  in your telephone phone book.
Do you think that they are all related if they have similar names?  Did 
you think
that they can not commit fraud just because they are in the phone book
with a similar name to your favorite stores?

Did you think they were? If not - what is your point? If it is that
there is no way to do content fraud detection  then you are right
and it still has nothing to do with S/MIME.

>  Heck, I can register 'the-real-royer.com", steal your
>content, get certs signed for it, and announce that "royer.com" is
>fraudulent.
>
No, you could send email claiming that it was fraudulent.
You could post on your web site claming that it was fraudulent.

My email would still be valid and the cert I used would still
be valid and traceable to royer.com.

The cert used by 'the-real-royer.com' would still be valid
and traceable to 'the-real-royer.com' .

Your talking about SITE  certs - not S/MIME.  Not spam.

Your talking about fraud detection by content  that just happened
to be sent in spam.

>  How much time and money will you lose?  And you won't be
>able to catch me.  The best you can hope for is to convince a
>registrar to nuke the name.
>
Your missing the point. We are NOT talking about  site certs.

Content fraud is for the police when you track them down.

>>> It's easy to get a domain and/or certificate with fraudulent identities.
>>>
>>>      
>>>
>>I'll reimburse you if you can get a fraudulent cert for 'royer.com' from 
>>a CA that I trust.
>>    
>>
>
>  See, I say "fraudulent identities", and you say "fraudulent cert".
>Do you understand that you're not talking about the same thing I'm
>talking about?
>  
>
Do you understand that "fraudulent identities" are extremely difficult if
the there is no "fraudulent cert"? Do you understand that it would require
some kind of mass conspiracy and bribing of a good CA to generate
a "fraudulent cert" that then could be used for "fraudulent identities"?

Or are you talking about fraudulent content detection?

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms000408030702090406020208
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIxMjMzMzU0WjAjBgkqhkiG9w0BCQQxFgQULPS3NCkQmQyFqlACukUI
3bK/CuowUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAPa2BxYPMkKfOPJiQooUcxJ0Lid8UcvfgtECHvcxQyR/wVMRm0GFr8pO4QQwzZrV5
u+iRyz18/af2kdTHCloXdimy0l7IUjgd+F39AHjiKOmIPBy1NndWxPcXmDsDFk4mz/8Q8PQD
gaLqEpU5sP74WoFXFiVwNEk8JC7BqWKvs1B73+XyzSCyiDgeIK1SP+e2REzLrYSNxp7D9/eP
dnh4KWO5Qdxo3qPtX6ceaI2sdqlmKx1efsLVtTVj5XnSyb1wFUzhW/4TLGBbOmduG5RwBUU1
aR3LGirxNGpjcLUuFgxPldEos+dTABQ0/ljkJTPfKJLURk91jLeshYjrsZTV/AAAAAAAAA==
--------------ms000408030702090406020208--


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



From exim@www1.ietf.org  Sun Mar 21 18:43:28 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07609
	for <asrg-archive@odin.ietf.org>; Sun, 21 Mar 2004 18:43:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Cas-0002ue-70
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 18:43:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2LNh2RN011190
	for asrg-archive@odin.ietf.org; Sun, 21 Mar 2004 18:43:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Cas-0002uP-2j
	for asrg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 18:43:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07580
	for <asrg-web-archive@ietf.org>; Sun, 21 Mar 2004 18:42:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Cap-0004sV-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:42:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5CZq-0004kz-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:41:59 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5CYv-0004ec-00
	for asrg-web-archive@ietf.org; Sun, 21 Mar 2004 18:41:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5CYw-0002Tv-1z; Sun, 21 Mar 2004 18:41:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5CVy-0002Eh-BV
	for asrg@optimus.ietf.org; Sun, 21 Mar 2004 18:37:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07368
	for <asrg@ietf.org>; Sun, 21 Mar 2004 18:37:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5CVv-0004L4-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:37:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5CUy-0004Dp-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:36:57 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5CU1-00046Q-00
	for asrg@ietf.org; Sun, 21 Mar 2004 18:35:57 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B5CTz-0005d8-00; Sun, 21 Mar 2004 18:35:55 -0500
Received: from [68.244.134.132] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B5CTx-0008Cr-00; Sun, 21 Mar 2004 18:35:54 -0500
Message-ID: <405E26CB.3040007@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Mark Baugher <mbaugher@cisco.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] S/MIME
References: <20040321150043.BD4DD170BB@mail.nitros9.org> <405DED1E.6010102@Royer.com> <405DF02E.6050905@solidmatrix.com> <405DF381.6020006@Royer.com> <405DF753.3020404@solidmatrix.com> <6.0.0.22.2.20040321150759.03dbbcc8@mira-sjc5-6.cisco.com>
In-Reply-To: <6.0.0.22.2.20040321150759.03dbbcc8@mira-sjc5-6.cisco.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Sun, 21 Mar 2004 18:35:39 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Mark Baugher wrote:
> At 12:13 PM 3/21/2004, Yakov Shafranovich wrote:
> <...>
> 
>> Mea culpa - you only addressed the forgery issue. There are still some 
>> interoperability issues with S/MIME but that's probably something that 
>> will be solved sooner or later.
>>
>> However, this is an anti-spam group and within the context of fighting 
>> spam, how will this help? The problem that I have is that there are 
>> several identity schemes here and none of them address the point of 
>> what do you do, once the identity is established. There is IP 
>> identity, domain/IP identity (LMAP/MARID), more heavier cryptographic 
>> identities, etc. All of these lead into the same point - once the 
>> identity has been established, what happens then?
>>
>> This is a question to the entire group, not you directly.
> 
> 
> If we get forgery under control, then it is possible to apply 
> reputation, accreditation, blacklisting and other techniques to manage 
> spam.  What am I missing?
> 

Yes, you are correct. The trick question is how to apply them.

Yakov

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



From exim@www1.ietf.org  Mon Mar 22 08:00:07 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21424
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 08:00:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5P1m-0004mA-Hc
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 07:59:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MCxckI018354
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 07:59:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5P1m-0004lx-CF
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 07:59:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21406
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 07:59:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5P1l-00057T-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 07:59:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5P0r-00051C-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 07:58:42 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5P0V-0004ur-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 07:58:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5P0D-0004bK-RO; Mon, 22 Mar 2004 07:58:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Ozm-0004ZC-By
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 07:57:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21305
	for <asrg@ietf.org>; Mon, 22 Mar 2004 07:57:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Ozl-0004s8-00
	for asrg@ietf.org; Mon, 22 Mar 2004 07:57:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Oyp-0004jP-00
	for asrg@ietf.org; Mon, 22 Mar 2004 07:56:35 -0500
Received: from host217-35-105-169.in-addr.btopenworld.com ([217.35.105.169] helo=mail.neosinteractive.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Oxs-0004Z3-00
	for asrg@ietf.org; Mon, 22 Mar 2004 07:55:36 -0500
Received: from tthomson ([217.35.105.173] unverified) by mail.neosinteractive.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 22 Mar 2004 12:00:57 +0000
From: "Tom Thomson" <tthomson@neosinteractive.com>
To: <asrg@ietf.org>
Subject: RE: [Asrg] S/MIME
Message-ID: <IOEPKAPPDKHPENCKFNNGGEJODCAA.tthomson@neosinteractive.com>
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 IMO, Build 9.0.6604 (9.0.2911.0)
In-Reply-To: <405DF753.3020404@solidmatrix.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
X-OriginalArrivalTime: 22 Mar 2004 12:00:57.0265 (UTC) FILETIME=[55BE9210:01C41005]
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 12:55:34 -0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Yakov Shafranovich wrote:

> However, this is an anti-spam group and within the context of fighting
> spam, how will this help? The problem that I have is that there are
> several identity schemes here and none of them address the point of what
> do you do, once the identity is established. There is IP identity,
> domain/IP identity (LMAP/MARID), more heavier cryptographic identities,
> etc. All of these lead into the same point - once the identity has been
> established, what happens then?
>
> This is a question to the entire group, not you directly.

It's rather a question of what you do if you can't establisj identity,
surely? Most of the spam I receive has forged From: address (822 header, not
821). If there was an easy way of determinig that an address was forged (a
way which would cater for mailing lists) I would use it and discard all the
mail with forged adresses.  I know this will raise howls of rage from the
undisciplined roamers but I don't care - if they can't be bothered to sort
out their roaming in a disciplined manner (for example From: wherever they
are, with a Reply To: header to identify their base; or secure tunneling to
their base from wherever they are; or use S-Mime; or whatever, depending on
what the authentication method is) then I don't care if I don't see their
mail.  I also know that (unless spammer practises change a lot) such a
mechanism would eliminate most of the spam I receive.

The other useful thing about sender authentication is that it makes law
enforcement easier.  That will help reduce spam too.

Finally, there are plenty of blacklists out there which use email sender
lists (and MS of course provide a nice mechanism for dummies to blacklist
senders in their MUA offererings).  With sender authentication these
blacklists will cease to be a disaster (since they won't contain the forged
addresses).  Maybe they won't be useful, but they will at least be less
harmful than today so the mechanism will reduce the damage done by spam.

To me, that's a good enough reason to want some sort of easy and reliable
sender identification.

Of course it doesn't help with phishing spam, or with anuy sot of spam,
where the sender is using an address he owns - execpt that he might now be a
little easier to trace for law enforcement purposes.

Tom


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



From exim@www1.ietf.org  Mon Mar 22 10:41:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01771
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 10:41:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5RXg-0003G9-BA
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 10:41:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MFeXjU012438
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 10:40:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5RXQ-0003DU-Ew
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 10:40:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01617
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 10:40:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5RXE-0001zB-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 10:40:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5RVh-0001gS-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 10:38:42 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5RTb-00018W-03
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 10:36:31 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B5RCS-0000qw-Im
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 10:18:48 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5RBo-0008PI-3U; Mon, 22 Mar 2004 10:18:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5RBZ-0008FK-11
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 10:17:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29945
	for <asrg@ietf.org>; Mon, 22 Mar 2004 10:17:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5RBW-0006sT-00
	for asrg@ietf.org; Mon, 22 Mar 2004 10:17:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5R9r-0006V9-00
	for asrg@ietf.org; Mon, 22 Mar 2004 10:16:07 -0500
Received: from newgiles.striker.ottawa.on.ca ([205.150.200.131] helo=mail.nitros9.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5R8I-0006E6-00
	for asrg@ietf.org; Mon, 22 Mar 2004 10:14:30 -0500
Received: from newgiles.nitros9.org (localhost [127.0.0.1])
	by mail.nitros9.org (Postfix) with ESMTP id D9C0216FDF
	for <asrg@ietf.org>; Mon, 22 Mar 2004 10:18:14 -0500 (EST)
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME 
In-Reply-To: Your message of "Sun, 21 Mar 2004 16:33:54 MST."
             <405E2662.4040703@Royer.com> 
Message-Id: <20040322151814.D9C0216FDF@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 10:18:14 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Doug Royer <Doug@Royer.com> wrote:
> If you get a signed message where the cert is signed by a trusted CA, then
> it is not fraudulent.

  <sigh>  You are being obtuse.  The cert is valid, the underlying identity the cert is alleging may very well be fraudulent.

> Then you have failed to make your point as it can't be fraudulent if the
> cert is valid from a trusted CA.

  No... you have failed to understand my pouint.  That's different.

> New flash: There are several 'royer.whatever' sites around the
> world. In case this has confused you - we are not related in any way
> with each other. The same is true of MANY commercial establishments
> in your telephone phone book.  Do you think that they are all
> related if they have similar names?  Did you think that they can not
> commit fraud just because they are in the phone book with a similar
> name to your favorite stores?

  It's easier to tell them apart in the physical world.  On-line,
there are fewer clues to tell them apart.

  Are you really that dense?

> Did you think they were? If not - what is your point? If it is that
> there is no way to do content fraud detection  then you are right
> and it still has nothing to do with S/MIME.

  Did I ever say it did?  You're the one getting all hot and bothered
over certificates.  I have no clue why, as my original point had
little to do with certificates.

  So you're either misunderstanding me, or trying to hijack the
conversation.  Either way, you're arguing against a position I've
never taken, so I don't know why I'm wasting my time trying to explain
myself to you.

> Your missing the point. We are NOT talking about  site certs.

  I know what I'm talking about.  I have no clue what you're talking
about, or why you think your conversation has anything to do with the
issues I raised.

  Bye.

  Alan Dekok.

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



From exim@www1.ietf.org  Mon Mar 22 16:04:59 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21465
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 16:04:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Wak-0000MQ-HY
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 16:04:29 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2ML43EM001369
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 16:04:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5WaR-0000LY-Lj
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 16:03:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21288
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 16:03:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5WaI-0003Ra-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 16:03:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5WY2-0002t5-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 16:01:28 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5WVv-0002Ms-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 15:59:15 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B5WVt-0007RD-Iy
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 15:59:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5WUj-0008RV-AE; Mon, 22 Mar 2004 15:58:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5WUd-0008R9-77
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 15:57:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20552
	for <asrg@ietf.org>; Mon, 22 Mar 2004 15:57:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5WUb-000256-00
	for asrg@ietf.org; Mon, 22 Mar 2004 15:57:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5WT6-0001kx-00
	for asrg@ietf.org; Mon, 22 Mar 2004 15:56:20 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5WSJ-0001Xn-00
	for asrg@ietf.org; Mon, 22 Mar 2004 15:55:31 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2MKsqFp004401
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Mon, 22 Mar 2004 12:54:53 -0800
Message-ID: <405F529B.9070202@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME
References: <20040322151814.D9C0216FDF@mail.nitros9.org>
In-Reply-To: <20040322151814.D9C0216FDF@mail.nitros9.org>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070309010304060903050900"
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 13:54:51 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms070309010304060903050900
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Alan DeKok wrote:

>Doug Royer <Doug@Royer.com> wrote:
>  
>
>>If you get a signed message where the cert is signed by a trusted CA, then
>>it is not fraudulent.
>>    
>>
>
>  <sigh>  You are being obtuse.  The cert is valid, the underlying identity the cert is alleging may very well be fraudulent.
>
No the identity matches the cert. Your talking about content fraud not 
identity fraud.
If the cert says its is user-x and the signature is valid then it is not a
fraudulent identity even when the content is a fraudulent.

>  Are you really that dense?
>
Are you always this rude?

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms070309010304060903050900
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIyMjA1NDUxWjAjBgkqhkiG9w0BCQQxFgQUc0ha8mhnSjlySLxJaXKK
luaA6vowUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAwB0133wi68WQcpdsEFMTgFPrqpkccT7IfUKdiFfpHe50j2u9inXwh71L0e3lyqo/
ZfHkryyvG2WB28oLE9YHGviwiotAMcg4pgnZf0xu7gXp5md/UMQ3vYcVfm0J3T9ae9tNL49a
Fqkm65nqKLkTQFz8ma+ojnf9CSeZtOAFlqIUAFv8vV/JBPkYQyqsbx68eJ21rBhhqc9fwoks
kco2AfDhC1jBnpJiAvBmmkd4raXoBk7yGIfzdp5lFkSCxoXgD/eDyxbLSpIc8ORHv0euu44M
pQIsgK5AHBhQ5JLFgKFc/2KJUJ10m3Fs5b4FtMDQ6/A+lX6piHeVawtzH31bCAAAAAAAAA==
--------------ms070309010304060903050900--


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



From exim@www1.ietf.org  Mon Mar 22 17:31:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29548
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 17:31:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5XwX-0008JJ-VJ
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 17:30:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MMUm0s031938
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 17:30:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5XwV-0008J3-PJ
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 17:30:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29543
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 17:30:44 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5XwT-00011V-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:30:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Xvd-0000wR-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:29:54 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Xv3-0000qv-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:29:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Xun-00084R-BW; Mon, 22 Mar 2004 17:29:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5UBL-0001c8-Jg
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 13:29:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10661
	for <asrg@ietf.org>; Mon, 22 Mar 2004 13:29:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5UBJ-0007gL-00
	for asrg@ietf.org; Mon, 22 Mar 2004 13:29:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5UAL-0007YM-00
	for asrg@ietf.org; Mon, 22 Mar 2004 13:28:49 -0500
Received: from pcls1.std.com ([192.74.137.141] helo=TheWorld.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5U9r-0007S1-00
	for asrg@ietf.org; Mon, 22 Mar 2004 13:28:19 -0500
Received: from world.std.com (root@world-e.std.com [69.38.147.5])
	by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id i2MIS8q7013472;
	Mon, 22 Mar 2004 13:28:08 -0500
Received: (from bzs@localhost)
	by world.std.com (8.9.3/8.9.3) id NAA06918;
	Mon, 22 Mar 2004 13:28:08 -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: <16479.12343.923405.180@world.std.com>
To: Mark Baugher <mbaugher@cisco.com>
Cc: asrg@ietf.org
Subject: Re: [Asrg] S/MIME
In-Reply-To: <6.0.0.22.2.20040321150759.03dbbcc8@mira-sjc5-6.cisco.com>
References: <20040321150043.BD4DD170BB@mail.nitros9.org>
	<405DED1E.6010102@Royer.com>
	<405DF02E.6050905@solidmatrix.com>
	<405DF381.6020006@Royer.com>
	<405DF753.3020404@solidmatrix.com>
	<6.0.0.22.2.20040321150759.03dbbcc8@mira-sjc5-6.cisco.com>
X-Mailer: VM 7.07 under Emacs 21.2.2
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 13:28:07 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On March 21, 2004 at 15:10 mbaugher@cisco.com (Mark Baugher) wrote:
 > 
 > If we get forgery under control, then it is possible to apply reputation, 
 > accreditation, blacklisting and other techniques to manage spam.  What am I 
 > missing?

That the USPS (and no doubt others) haven't been able to make much of
a dent in this in 200+ years?

There's a paradox here. Authentication etc costs money, even if just
microcents it adds up in some contexts. People want e-mail to be
essentially free.

I think we can probably find ways to prevent people from bringing fork
lifts into the all you can eat buffet. But fraud and authentication in
general is a huge topic which probably is best solved by someone
figuring out a model for a "charging for authentication business",
akin to registered or certified mail.

Put another way, it's one of those problems that seems to be easy on a
very small scale (exchange PGP keys with your friends), but becomes
very hard as you scale it up, particularly if the first criteria is
that it must not cost anything.

          -b


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



From exim@www1.ietf.org  Mon Mar 22 17:37:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29842
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 17:37:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Y2O-0000Yc-Lk
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 17:36:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MMaqZV002136
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 17:36:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Y2O-0000YN-Hl
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 17:36:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29824
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 17:36:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Y2M-0001hD-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:36:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Y1V-0001b9-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:35:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Y0e-0001Ua-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:35:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Y0b-0000JT-AV; Mon, 22 Mar 2004 17:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Y0I-0000IB-Qx
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 17:34:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29654
	for <asrg@ietf.org>; Mon, 22 Mar 2004 17:34:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Y0G-0001R1-00
	for asrg@ietf.org; Mon, 22 Mar 2004 17:34:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5XzK-0001Jy-00
	for asrg@ietf.org; Mon, 22 Mar 2004 17:33:43 -0500
Received: from [216.226.168.57] (helo=sv-IAS2.fjcs.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5XyS-00018j-00
	for asrg@ietf.org; Mon, 22 Mar 2004 17:32:48 -0500
Received: from goui815 ([172.16.75.250]) by sv-IAS2.fjcs.net with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 22 Mar 2004 14:32:15 -0800
Message-ID: <029101c4105d$870e97e0$fa4b10ac@fpcad.fujitsupc.com>
From: "George Ou" <george_ou@netzero.com>
To: "Ken Hirsch" <kenhirsch@myself.com>, <asrg@ietf.org>
References: <20040322151814.D9C0216FDF@mail.nitros9.org> <405F529B.9070202@Royer.com> <050101c41054$d37abc70$6aae86a2@hirschk1>
Subject: Re: [Asrg] S/MIME
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 22 Mar 2004 22:32:15.0724 (UTC) FILETIME=[8710BAC0:01C4105D]
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 14:32:15 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

1.  This makes a great case for better verification at the time of the
certificate issuance.  Especially for code signing certificates from a major
software company.  Companies should be able to request extremely high
verfication standards for themselves from companies like VeriSign,
especially if you're Microsoft.

2.  This makes a good case for a defacto standard of built in HSMs on all
PCs.  I think the TCG "Trusted Computing Group" is pushing something like
that in their new standard.  Next month, the company I work for will release
our first notebook with a TPM built in.


George

----- Original Message ----- 
From: "Ken Hirsch" <kenhirsch@myself.com>
To: <asrg@ietf.org>
Sent: Monday, March 22, 2004 1:29 PM
Subject: Re: [Asrg] S/MIME


> From: "Doug Royer" <Doug@Royer.com>
> > No the identity matches the cert. Your talking about content fraud not
> > identity fraud.
>
> Consider the following two scenarios.
> 1. A person lies to the CA about their identity, yet the CA issues them a
> certificate.
> E.g. http://www.microsoft.com/technet/security/bulletin/MS01-017.mspx
>
> 2. An email worm installs spyware which steals certificates off of PCs and
> installs keystroke logging software to steal the password.  A spammer uses
the
> thousands of certificates to send email.
>
> If either of these result in somebody sending mail claiming to be
> "Doug@Royer.com", is this identity fraud or content fraud?
>
>
>
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
>


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



From exim@www1.ietf.org  Mon Mar 22 17:39:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29955
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 17:39:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Y4O-00012I-1J
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 17:38:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MMctX2003976
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 17:38:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Y4N-00011s-HC
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 17:38:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29906
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 17:38:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Y4K-0001uV-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:38:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Y3J-0001oM-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:37:50 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Y2Y-0001iM-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:37:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Y2W-0000ZN-QQ; Mon, 22 Mar 2004 17:37:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Y2M-0000Y3-HC
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 17:36:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29812
	for <asrg@ietf.org>; Mon, 22 Mar 2004 17:36:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Y2K-0001gt-00
	for asrg@ietf.org; Mon, 22 Mar 2004 17:36:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Y1O-0001aC-00
	for asrg@ietf.org; Mon, 22 Mar 2004 17:35:51 -0500
Received: from [216.226.168.57] (helo=sv-IAS2.fjcs.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Y0X-0001NC-00
	for asrg@ietf.org; Mon, 22 Mar 2004 17:34:57 -0500
Received: from goui815 ([172.16.75.250]) by sv-IAS2.fjcs.net with Microsoft SMTPSVC(6.0.3790.0);
	 Mon, 22 Mar 2004 14:34:27 -0800
Message-ID: <029b01c4105d$d5b30a20$fa4b10ac@fpcad.fujitsupc.com>
From: "George Ou" <george_ou@netzero.com>
To: "Barry Shein" <bzs@world.std.com>, "Mark Baugher" <mbaugher@cisco.com>
Cc: <asrg@ietf.org>
References: <20040321150043.BD4DD170BB@mail.nitros9.org><405DED1E.6010102@Royer.com><405DF02E.6050905@solidmatrix.com><405DF381.6020006@Royer.com><405DF753.3020404@solidmatrix.com><6.0.0.22.2.20040321150759.03dbbcc8@mira-sjc5-6.cisco.com> <16479.12343.923405.180@world.std.com>
Subject: Re: [Asrg] S/MIME
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
X-OriginalArrivalTime: 22 Mar 2004 22:34:27.0673 (UTC) FILETIME=[D5B68C90:01C4105D]
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 14:34:27 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Isn't that what DNSSEC is suppose to address?  That certainly doesn't have
the scalability problems like PGP.

George

----- Original Message ----- 
From: "Barry Shein" <bzs@world.std.com>
To: "Mark Baugher" <mbaugher@cisco.com>
Cc: <asrg@ietf.org>
Sent: Monday, March 22, 2004 10:28 AM
Subject: Re: [Asrg] S/MIME


>
> On March 21, 2004 at 15:10 mbaugher@cisco.com (Mark Baugher) wrote:
>  >
>  > If we get forgery under control, then it is possible to apply
reputation,
>  > accreditation, blacklisting and other techniques to manage spam.  What
am I
>  > missing?
>
> That the USPS (and no doubt others) haven't been able to make much of
> a dent in this in 200+ years?
>
> There's a paradox here. Authentication etc costs money, even if just
> microcents it adds up in some contexts. People want e-mail to be
> essentially free.
>
> I think we can probably find ways to prevent people from bringing fork
> lifts into the all you can eat buffet. But fraud and authentication in
> general is a huge topic which probably is best solved by someone
> figuring out a model for a "charging for authentication business",
> akin to registered or certified mail.
>
> Put another way, it's one of those problems that seems to be easy on a
> very small scale (exchange PGP keys with your friends), but becomes
> very hard as you scale it up, particularly if the first criteria is
> that it must not cost anything.
>
>           -b
>
>
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
>


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



From exim@www1.ietf.org  Mon Mar 22 17:58:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01013
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 17:58:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5YMb-0003BY-Uy
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 17:57:46 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MMvjXa012238
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 17:57:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5YMb-0003BJ-Pe
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 17:57:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00947
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 17:57:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5YMZ-000422-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:57:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5YLa-0003nc-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:56:42 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5YKK-0003Zz-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:55:25 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B5YKF-0002MO-7e
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 17:55:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5YJx-0002j8-Eq; Mon, 22 Mar 2004 17:55:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5YJp-0002iX-0i
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 17:54:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00668
	for <asrg@ietf.org>; Mon, 22 Mar 2004 17:54:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5YJm-0003Y6-00
	for asrg@ietf.org; Mon, 22 Mar 2004 17:54:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5YIr-0003SI-00
	for asrg@ietf.org; Mon, 22 Mar 2004 17:53:54 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5YIM-0003MR-00
	for asrg@ietf.org; Mon, 22 Mar 2004 17:53:22 -0500
Received: from MOU1WNEXC03.vcorp.ad.vrsn.com (mailer3.verisign.com [65.205.251.55])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2MMrKfA013715;
        Mon, 22 Mar 2004 14:53:20 -0800 (PST)
Received: by mou1wnexc03.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <HCHBVDS0>; Mon, 22 Mar 2004 14:53:20 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E5DBA95@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'George Ou'" <george_ou@netzero.com>, Barry Shein <bzs@world.std.com>,
        Mark Baugher <mbaugher@cisco.com>
Cc: asrg@ietf.org
Subject: RE: [Asrg] S/MIME
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 14:53:19 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60


> Isn't that what DNSSEC is suppose to address?  That certainly 
> doesn't have the scalability problems like PGP.

It does not have a necessary scalability issue, but the spec
was deliberately sabotaged to stop deployment in dotcom and
dotnet.

The number of barriers to deployment of DNSSEC is growing so
long it is just not funny. Even if the technical spec is approved
you still have to persuade the registrars to modify their 
registration process and that is not even considering the 
regulatory angle.

Fortunately it is almost certainly not necessary to have 
DNSSEC for purposes of anti-spam authentication mechanisms.

		Phill



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



From exim@www1.ietf.org  Mon Mar 22 18:16:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02690
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 18:16:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Ye8-0001we-MB
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 18:15:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MNFqc2007475
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 18:15:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Ye8-0001wU-GI
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 18:15:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02604
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 18:15:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Ye5-0005uR-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 18:15:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5YdA-0005oT-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 18:14:52 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Ycc-0005ir-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 18:14:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5YcL-0001HM-Qb; Mon, 22 Mar 2004 18:14:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Yc9-0001Di-MT
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 18:13:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02382
	for <asrg@ietf.org>; Mon, 22 Mar 2004 18:13:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Yc6-0005hQ-00
	for asrg@ietf.org; Mon, 22 Mar 2004 18:13:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5YbC-0005bd-00
	for asrg@ietf.org; Mon, 22 Mar 2004 18:12:50 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5YaM-0005QC-00
	for asrg@ietf.org; Mon, 22 Mar 2004 18:11:58 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2MNBQFp006239
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Mon, 22 Mar 2004 15:11:27 -0800
Message-ID: <405F729D.8000203@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME
References: <20040322151814.D9C0216FDF@mail.nitros9.org> <405F529B.9070202@Royer.com> <050101c41054$d37abc70$6aae86a2@hirschk1>
In-Reply-To: <050101c41054$d37abc70$6aae86a2@hirschk1>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070205090200020004030109"
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 16:11:25 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms070205090200020004030109
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



Ken Hirsch wrote:

>From: "Doug Royer" <Doug@Royer.com>
>  
>
>>No the identity matches the cert. Your talking about content fraud not
>>identity fraud.
>>    
>>
>
>Consider the following two scenarios.
>1. A person lies to the CA about their identity, yet the CA issues them a
>certificate.
>E.g. http://www.microsoft.com/technet/security/bulletin/MS01-017.mspx
>  
>
Yes  - and that CERT was REVOKED before most people knew of the fraud or 
error.
Try to use it and all receiving systems tag it as an invalid revoked 
signature because
the revocation list for that CA lists that serial number as revoked.

Problem solved and that fixed the problem.  So in effect the CERT was 
blacklisted
by all sites even when they do not use blacklists. Because it works to 
use certs.

>2. An email worm installs spyware which steals certificates off of PCs and
>installs keystroke logging software to steal the password.  A spammer uses the
>thousands of certificates to send email.
>  
>
As soon as the blacklist sites detect it as spam, that cert is 
blacklisted. Problem solved no
matter how many variations or password protected zip files it sends, it 
is stopped
once that cert is blacklisted. In many cases within minutes of the start 
of the spamming
when they spam some sites. Because certs work.

Now the owner of that cert can contact their CA and say it was stolen, 
and have
that serial number revoked. Now it is invalid to all sites even to sites 
that do not
use blacklists.

>If either of these result in somebody sending mail claiming to be
>"Doug@Royer.com", is this identity fraud or content fraud?
>  
>
Try to buy an email cert from a CA that I trust for royer.com. Same 
thing I told
the other guy - I'll pay you twice their fee if you can get an email 
cert for a
royer.com email address.

If the content of the email says I am 'Royer Real Estate' (royer.ca) and 
I am
not and I then I sign it doug@royer.com, then it is content fraud and 
not identity
fraud because my identity is 'doug@royer.com' and that is what the valid
signature says.


-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms070205090200020004030109
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIyMjMxMTI1WjAjBgkqhkiG9w0BCQQxFgQU/YPYg9cgMc73J5OmX7ur
aJPidEMwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAbSP3GLxlapyxiQXIYuo1WWwi+ngZXmdjWdWz2bpqd1HhpsEHP+ujXqGMKeryY8+J
mpCrM22Zbmj2/A8FXd+DxwtnkbUrJFL6OHEeogIxocqLoeHVTibU2Kh/BW7Wk8VAMxa4kx/O
ZthesICusaYPe0607y30uF8BMsFvKNFBi6C6c6u6YHYGnlDlSeAAjsub4EjqDt6bu5rhduuL
t73gZBLC5izraKZrWBbcqRTb7Bev0fYyAYug+Zn+xzU3FSB4Bx0JKH4Zm5LuRPCwjroSTPYp
uf0C/Z7EEar6i6MXFGc7YSct6IpR2PUW7a4/DGel0V5uJojZhzsBzx2Stwl5UwAAAAAAAA==
--------------ms070205090200020004030109--


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



From exim@www1.ietf.org  Mon Mar 22 18:41:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04275
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 18:41:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Z2O-0004wH-Ge
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 18:40:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MNeuF1018979
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 18:40:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Z2O-0004w2-C5
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 18:40:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04262
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 18:40:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Z2L-0000rL-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 18:40:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5Z1Y-0000kp-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 18:40:05 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Z0e-0000dg-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 18:39:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Z0X-0004ho-Lk; Mon, 22 Mar 2004 18:39:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5Z0O-0004g2-LH
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 18:38:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04078
	for <asrg@ietf.org>; Mon, 22 Mar 2004 18:38:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Z0L-0000at-00
	for asrg@ietf.org; Mon, 22 Mar 2004 18:38:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5YzO-0000TN-00
	for asrg@ietf.org; Mon, 22 Mar 2004 18:37:50 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Yyh-0000Hn-00
	for asrg@ietf.org; Mon, 22 Mar 2004 18:37:08 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2MNaTFp006462
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Mon, 22 Mar 2004 15:36:32 -0800
Message-ID: <405F787D.2080005@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME
References: <20040321150043.BD4DD170BB@mail.nitros9.org>	<405DED1E.6010102@Royer.com>	<405DF02E.6050905@solidmatrix.com>	<405DF381.6020006@Royer.com>	<405DF753.3020404@solidmatrix.com>	<6.0.0.22.2.20040321150759.03dbbcc8@mira-sjc5-6.cisco.com> <16479.12343.923405.180@world.std.com>
In-Reply-To: <16479.12343.923405.180@world.std.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms050706090302000609090803"
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 16:36:29 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms050706090302000609090803
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit



Barry Shein wrote:

>On March 21, 2004 at 15:10 mbaugher@cisco.com (Mark Baugher) wrote:
> > 
> > If we get forgery under control, then it is possible to apply reputation, 
> > accreditation, blacklisting and other techniques to manage spam.  What am I 
> > missing?
>
>That the USPS (and no doubt others) haven't been able to make much of
> dent in this in 200+ years?
>
I do not think they have that task and as they also do not require that 
the sender sign
the postal mail with a 3rd party verified signature it is not a valid 
comparison.

>There's a paradox here. Authentication etc costs money, even if just
>microcents it adds up in some contexts. People want e-mail to be
>essentially free.
>
An email cert from your ISP could be free or included in your sign up fee.
In fact your ISP could interpose on port 25, check the 'from' values
and sign it for you - for free (for those that use the ISPs email 
addresses) if
the ISP is a CA.

>I think we can probably find ways to prevent people from bringing fork
>lifts into the all you can eat buffet. But fraud and authentication in
>general is a huge topic which probably is best solved by someone
>figuring out a model for a "charging for authentication business",
>akin to registered or certified mail.
>
You can send registered and certified postal mail without showing any ID 
at all. Not
the same model. The recipient of the registered or certified mail has to 
show
identity, not the sender.

If you think that stopping spam will require a fork lift to a buffet, 
then I can
make money selling your competitors digital signatures real cheap :-)

I do not think that it is heavy weight at all. It is implemented by most 
(all?) of
the GUI MUAs that I have seen over the last few years.

>Put another way, it's one of those problems that seems to be easy on a
>very small scale (exchange PGP keys with your friends), but becomes
>very hard as you scale it up, particularly if the first criteria is
>that it must not cost anything.
>
>  
>
Yes - PGP will not work. I am talking S/MIME, it does not have that scaling
problem as the number of CAs is MUCH lower and does not require a 4th
hand he said she said you can trust that person problem.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms050706090302000609090803
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIyMjMzNjI5WjAjBgkqhkiG9w0BCQQxFgQUi6Ij4kDMvhkHLwfRNXCq
7PCT0JAwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEADMy6opftx++bbrJYzjj0ZJTJB5uLbeI+0wW3LnezylWjFcN9uhKaCA/G7S7k65Io
vb9c6zpH63jG09r/VrRafLwmGPk2FNtUgOfNKqSJsPXcH5vWfZCkKtc+VW5dfSuOPAMkth3D
S0RrEI+GgVyjljxUUv2kXry7VW4G8/2zYdXsanlxQaxW/ADxgwrCdBvd7LSM4A3DutXqGydk
W0UTIiGLYmeFoO0uXayAAdbbuegFyNKTY5zk2rVD7wSYV+Ujr8/18SdwRoW5+Du3jGB0XAk4
WZf0FRi/iaZ9iq6uCbHyr9Ir6ZAt0eOn+9wgpZPY+ooFBdaL7Ir9gsGWoAXsfAAAAAAAAA==
--------------ms050706090302000609090803--


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



From exim@www1.ietf.org  Mon Mar 22 19:55:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07428
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 19:55:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5aC8-0001dj-FK
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 19:55:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2N0t4iT006297
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 19:55:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5aC6-0001dE-Ez
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 19:55:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07409
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 19:55:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5aC4-0001pB-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 19:55:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5aB8-0001iF-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 19:54:02 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5aAY-0001bH-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 19:53:26 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5aA9-0001RJ-LC; Mon, 22 Mar 2004 19:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5a9y-0001Qf-DG
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 19:52:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA07220
	for <asrg@ietf.org>; Mon, 22 Mar 2004 19:52:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5a9w-0001Xb-00
	for asrg@ietf.org; Mon, 22 Mar 2004 19:52:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5a92-0001Q8-00
	for asrg@ietf.org; Mon, 22 Mar 2004 19:51:53 -0500
Received: from sccrmhc11.comcast.net ([204.127.202.55])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5a88-0001Dd-00
	for asrg@ietf.org; Mon, 22 Mar 2004 19:50:56 -0500
Received: from [192.168.0.3] (h00095b86f221.ne.client2.attbi.com[24.61.46.50])
          by comcast.net (sccrmhc11) with SMTP
          id <2004032300502601100ilge2e>; Tue, 23 Mar 2004 00:50:26 +0000
Message-Id: <1167864D-7C64-11D8-A507-00039380F1B6@pobox.com>
X-Habeas-Swe-6: email in exchange for a license for this Habeas
X-Habeas-Swe-3: like Habeas SWE (tm)
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
X-Habeas-Swe-8: Message (HCM) and not spam. Please report use of this
From: mathew <meta@pobox.com>
X-Habeas-Swe-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-Swe-2: brightly anticipated
In-Reply-To: <405C9208.4050506@Royer.com>
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com> <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com> <405B4591.4080808@Royer.com> <B3545D83-7A2B-11D8-B58D-000393CAA6AA@pobox.com> <405C9208.4050506@Royer.com>
To: asrg@ietf.org
X-Habeas-Swe-7: warrant mark warrants that this is a Habeas Compliant
Mime-Version: 1.0 (Apple Message framework v612)
X-Habeas-Swe-4: Copyright 2002 Habeas (tm) 
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-2-764092391; protocol="application/pkcs7-signature"
X-Habeas-Swe-1: winter into spring
X-Habeas-Swe-9: mark in spam to <http://www.habeas.com/report/>.
X-Mailer: Apple Mail (2.612)
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 19:50:23 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--Apple-Mail-2-764092391
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

On Mar 20, 2004, at 13:48, Doug Royer wrote:
> mathew wrote:
>> On Mar 19, 2004, at 14:10, Doug Royer wrote:
>>> A popular vendor broke their implementation of S/MIME, that was 
>>> fixed years
>>> ago and a simple upgrade will fix that.
>>
>> Well, your message signature doesn't seem valid to my mail program.
>
> Again, your vendor being busted  does not mean that S/MIME is busted.

No, but it's a good indication that S/MIME isn't ready for prime time 
when the three different S/MIME packages available to me can't talk to 
each other.


mathew
-- 
<URL:http://www.pobox.com/~meta/>
--Apple-Mail-2-764092391
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGEDCCAskw
ggIyoAMCAQICAwtCvTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDMxMjAzMTUwOTU3WhcNMDQxMjAyMTUwOTU3WjBAMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMR0wGwYJKoZIhvcNAQkBFg5tZXRhQHBvYm94LmNvbTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANA40G+RMi0LMG++Lz6J4LpIaXkydRxJoLjz
9EPfZGLn6dPBumvzLVWDaQrOshYuyViOW+oPk62xz6HBnarbOX3VoiFVyGCjqkZz+TToHDDlya/z
D8l/WF92nvsEPFPKE6Fw/Lg13/g9zzBlxrjwW98bL6dI1tKvdokMH91++35sC0Yu5oZjuBF4ydUA
1n7pX2KgEDhRRP5b/RhQPrdpbZhO5fwzthiD0VlCG9zkloNJ8GOFxMFd2lpVpV1ISySCHYwEtA1n
zxR7Kq4oRaMvAodHj8NHRPDjE+vyALzi0mCZ+JlQAyKr+Li5YvKZNRobyYBQGLLOyt31ZAj9vfSS
g2cCAwEAAaMrMCkwGQYDVR0RBBIwEIEObWV0YUBwb2JveC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQQFAAOBgQCVJDuVViVm9t4++qdMFmiF4yfAowCy3/bauIAcxAJXvd21LnorWF+49YJk
jBZO74MDPrsYb5M9ybKMy04vxNuXXHM9TVLUWJjz5PUCcaNIj9DqGIW9eAPWj/Pvn6j5qSP8OcoK
mwwrKcurmSi+sJqajLjET0wzsuvgRFNE4pkOyDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEF
BQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg
VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24g
U2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAw
MDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3Vs
dGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWlu
ZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me
7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r
1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCB
kTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3Rl
LmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAg
pB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPq
Cy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUa
C4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx
0x1G/11fZU8xggLnMIIC4wIBATBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u
c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz
dWluZyBDQQIDC0K9MAkGBSsOAwIaBQCgggFTMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJ
KoZIhvcNAQkFMQ8XDTA0MDMyMzAwNTAyNFowIwYJKoZIhvcNAQkEMRYEFN3I9DrcbfrmFwlS1Ily
ykNbuuHxMHgGCSsGAQQBgjcQBDFrMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBD
b25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAgMLQr0wegYLKoZIhvcNAQkQAgsxa6BpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK
ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQQIDC0K9MA0GCSqGSIb3DQEBAQUABIIBAGVR72gRzpUk9g8J1Qoc
tQkFIVGTht/LCi0h6xAtGkmLzdo/bIe5axzu7muhNQfgzkJ8mFzet5NDoUX4aOB1KXYQCjy2PxK6
0QUS4cQS+rFHmennid0rFEcBftmI+xvkaPmu0tJ7Jw3UPXV0QWGLjNJeh5Bi0EVT8FNd/Kn2Eu41
ndkk4Y13tWES8Fsp43FRnO4eupQkztj6M/ZNsduGbrWIGM7eefTfnP65/tQg2xnnVg6KgKBwXtcl
uRjoEe/PJTtJ15wW4R9diwEDnKqUC9ghib/5HS64sLZoPXKEiSbY0vajKi4C28bKrCI0k7XxkV1m
4x5SvR66q9+skg58m7oAAAAAAAA=

--Apple-Mail-2-764092391--


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



From exim@www1.ietf.org  Mon Mar 22 20:20:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08467
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 20:20:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5aaN-0003cq-Nd
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 20:20:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2N1K7Nj013922
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 20:20:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5aaM-0003cN-I5
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 20:20:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08449
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 20:20:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5aaK-0004pu-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 20:20:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5aZM-0004io-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 20:19:05 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5aYS-0004aq-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 20:18:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5aYL-0003L8-Ah; Mon, 22 Mar 2004 20:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5aUY-0002kG-OX
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 20:14:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA08056
	for <asrg@ietf.org>; Mon, 22 Mar 2004 20:14:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5aUW-00042Q-00
	for asrg@ietf.org; Mon, 22 Mar 2004 20:14:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5aTV-0003uP-00
	for asrg@ietf.org; Mon, 22 Mar 2004 20:13:01 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5aT3-0003nJ-00
	for asrg@ietf.org; Mon, 22 Mar 2004 20:12:33 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B5aSP-0007S1-00; Mon, 22 Mar 2004 20:11:53 -0500
Received: from [68.244.170.93] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B5aSO-0006JT-00; Mon, 22 Mar 2004 20:11:53 -0500
Message-ID: <405F8EC7.3060601@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: mathew <meta@pobox.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com> <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com> <405B4591.4080808@Royer.com> <B3545D83-7A2B-11D8-B58D-000393CAA6AA@pobox.com> <405C9208.4050506@Royer.com> <1167864D-7C64-11D8-A507-00039380F1B6@pobox.com>
In-Reply-To: <1167864D-7C64-11D8-A507-00039380F1B6@pobox.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 20:11:35 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

mathew wrote:
> On Mar 20, 2004, at 13:48, Doug Royer wrote:
> 
>> mathew wrote:
>>
>>> On Mar 19, 2004, at 14:10, Doug Royer wrote:
>>>
>>>> A popular vendor broke their implementation of S/MIME, that was 
>>>> fixed years
>>>> ago and a simple upgrade will fix that.
>>>
>>>
>>> Well, your message signature doesn't seem valid to my mail program.
>>
>>
>> Again, your vendor being busted  does not mean that S/MIME is busted.
> 
> 
> No, but it's a good indication that S/MIME isn't ready for prime time 
> when the three different S/MIME packages available to me can't talk to 
> each other.
> 

I believe that OpenGroup is also working on an interoperability 
certification program for S/MIME specifically for that reason.

Yakov

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



From exim@www1.ietf.org  Mon Mar 22 21:56:07 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13220
	for <asrg-archive@odin.ietf.org>; Mon, 22 Mar 2004 21:56:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5c4o-0001h1-Tn
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 21:55:39 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2N2tcdp006500
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 21:55:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5c4o-0001gl-LF
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 21:55:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13142
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 21:55:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5c4l-00019V-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 21:55:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5c3b-0000vQ-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 21:54:24 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5c2R-0000hJ-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 21:53:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5c2H-00011A-3X; Mon, 22 Mar 2004 21:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5c1a-0000wr-Va
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 21:52:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12741
	for <asrg@ietf.org>; Mon, 22 Mar 2004 21:52:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5c1Y-0000Ta-00
	for asrg@ietf.org; Mon, 22 Mar 2004 21:52:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5c0I-0000CJ-00
	for asrg@ietf.org; Mon, 22 Mar 2004 21:50:59 -0500
Received: from royer.com ([4.23.9.161])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5bzL-0007me-00
	for asrg@ietf.org; Mon, 22 Mar 2004 21:49:59 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2N2nIFp008487
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Mon, 22 Mar 2004 18:49:19 -0800
Message-ID: <405FA5AE.90209@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com> <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com> <405B4591.4080808@Royer.com> <B3545D83-7A2B-11D8-B58D-000393CAA6AA@pobox.com> <405C9208.4050506@Royer.com> <1167864D-7C64-11D8-A507-00039380F1B6@pobox.com>
In-Reply-To: <1167864D-7C64-11D8-A507-00039380F1B6@pobox.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms010203010503060504030500"
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 19:49:18 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms010203010503060504030500
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



mathew wrote:

> On Mar 20, 2004, at 13:48, Doug Royer wrote:
>
>> mathew wrote:
>>
>>> On Mar 19, 2004, at 14:10, Doug Royer wrote:
>>>
>>>> A popular vendor broke their implementation of S/MIME, that was 
>>>> fixed years
>>>> ago and a simple upgrade will fix that.
>>>
>>>
>>> Well, your message signature doesn't seem valid to my mail program.
>>
>>
>> Again, your vendor being busted  does not mean that S/MIME is busted.
>
>
> No, but it's a good indication that S/MIME isn't ready for prime time 
> when the three different S/MIME packages available to me can't talk to 
> each other.

I can name 4 popular ones that can interoperate with each other. So it 
looks ready to me.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms010203010503060504030500
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzIzMDI0OTE4WjAjBgkqhkiG9w0BCQQxFgQUErRVD8zEJlH7JGYWR/S7
xy4sgvMwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAAtlXIo97uMBpny4sXxf9Q59m3oZfN9CqyCdvfDMlzAybDXGbXCNx4hEaIeGte73y
lm4E74Afix8VK5OtM9goOqRR698pxhmdUn+EeW1WFqbQ7sb8+53l0iD+RTeHV8yHfyTvz6AZ
1f87cUwihe6tWpVRg+9mocRanYyGWfRt9dbQrjBLILahkdFTmo3EKlCBr7FaUQElcGyZTq53
rOnwY1SMw6X2TsWoK1VEDGm5AcK+j+wEacWJQZJJVBnMC7oBKMNYVpE8EFflSoAhwWnK00kd
U5mpzxsRKc+uMv4v00cwGwFrWUG8ELvc92BPJFuyNGFIVA9GONg/eNxCyNuGhQAAAAAAAA==
--------------ms010203010503060504030500--


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



From exim@www1.ietf.org  Tue Mar 23 04:41:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14270
	for <asrg-archive@odin.ietf.org>; Tue, 23 Mar 2004 04:41:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5iPK-0001JU-UF
	for asrg-archive@odin.ietf.org; Tue, 23 Mar 2004 04:41:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2N9fEcD005044
	for asrg-archive@odin.ietf.org; Tue, 23 Mar 2004 04:41:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5iPK-0001JH-KZ
	for asrg-web-archive@optimus.ietf.org; Tue, 23 Mar 2004 04:41:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14245
	for <asrg-web-archive@ietf.org>; Tue, 23 Mar 2004 04:41:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5iPH-0003Im-00
	for asrg-web-archive@ietf.org; Tue, 23 Mar 2004 04:41:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5iOJ-0003AF-00
	for asrg-web-archive@ietf.org; Tue, 23 Mar 2004 04:40:11 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5iNT-000328-00
	for asrg-web-archive@ietf.org; Tue, 23 Mar 2004 04:39:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5iND-00011t-Cm; Tue, 23 Mar 2004 04:39:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5iMJ-0000r2-EX
	for asrg@optimus.ietf.org; Tue, 23 Mar 2004 04:38:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14098
	for <asrg@ietf.org>; Tue, 23 Mar 2004 04:38:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5iMG-0002rg-00
	for asrg@ietf.org; Tue, 23 Mar 2004 04:38:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5iLL-0002kD-00
	for asrg@ietf.org; Tue, 23 Mar 2004 04:37:08 -0500
Received: from smtp.rol.ru ([194.67.21.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5iKQ-0002Y3-00
	for asrg@ietf.org; Tue, 23 Mar 2004 04:36:10 -0500
Received: from ariel.sovam.com ([194.67.3.216]:3714 "EHLO ariel.sovam.com"
	smtp-auth: "egc@online.ru" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits
	256/256 version TLSv1/SSLv3" TLS-PEER-CN1: <none>)
	by gnome07.net.rol.ru with ESMTP id S9915302AbUCWJf3 (ORCPT
	<rfc822;asrg@ietf.org>); Tue, 23 Mar 2004 12:35:29 +0300
Subject: Re: [Asrg] S/MIME
From: Eugene Crosser <crosser@rol.ru>
To: Yakov Shafranovich <research@solidmatrix.com>
Cc: asrg@ietf.org
In-Reply-To: <405DF753.3020404@solidmatrix.com>
References: <20040321150043.BD4DD170BB@mail.nitros9.org>
	 <405DED1E.6010102@Royer.com> <405DF02E.6050905@solidmatrix.com>
	 <405DF381.6020006@Royer.com>  <405DF753.3020404@solidmatrix.com>
Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-cWK+PuiRqXCJuWB5VYRh"
Organization: Sovintel
Message-Id: <1080034527.1166.44.camel@ariel.sovam.com>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 
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/mail-archive/working-groups/asrg/>
Date: Tue, 23 Mar 2004 12:35:28 +0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--=-cWK+PuiRqXCJuWB5VYRh
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Sun, 2004-03-21 at 23:13, Yakov Shafranovich wrote:

> However, this is an anti-spam group and within the context of fighting=20
> spam, how will this help? The problem that I have is that there are=20
> several identity schemes here and none of them address the point of what=20
> do you do, once the identity is established. There is IP identity,=20
> domain/IP identity (LMAP/MARID), more heavier cryptographic identities,=20
> etc. All of these lead into the same point - once the identity has been=20
> established, what happens then?

I beleive that authentication and reputation services can and should be
separated.  Authentication services (that include protocols like LMAP
and certification authorities) establish solid facts about senders, and
thus are policy agnostic.  On the contrary, reputation services may
differ greatly in their listing/delisting policy, "level of certaintly"
etc.

Thus, mail system administrators can use a single way to authenticate
senders, or one of limited number of ways.  Once sender identity is
established, it can be checked against a subset of potentially very
large number of reputation services, selected in accordance with local
policy/preferences.

Eugene

--=-cWK+PuiRqXCJuWB5VYRh
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQBAYATftQFsU5rTNjcRAi/1AKCOj7SOXeY8Yb03W+GodXMx1XSHOgCdEqXk
LDMQgK2R3oRBECbWbVfBeqE=
=+gp7
-----END PGP SIGNATURE-----

--=-cWK+PuiRqXCJuWB5VYRh--


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



From exim@www1.ietf.org  Tue Mar 23 15:51:08 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28148
	for <asrg-archive@odin.ietf.org>; Tue, 23 Mar 2004 15:51:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5srA-0004Fm-N3
	for asrg-archive@odin.ietf.org; Tue, 23 Mar 2004 15:50:40 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2NKoeXq016346
	for asrg-archive@odin.ietf.org; Tue, 23 Mar 2004 15:50:40 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5srA-0004FZ-HM
	for asrg-web-archive@optimus.ietf.org; Tue, 23 Mar 2004 15:50:40 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28065
	for <asrg-web-archive@ietf.org>; Tue, 23 Mar 2004 15:50:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5sr8-00067P-00
	for asrg-web-archive@ietf.org; Tue, 23 Mar 2004 15:50:38 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5sq2-0005wA-00
	for asrg-web-archive@ietf.org; Tue, 23 Mar 2004 15:49:31 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5soS-0005cn-00
	for asrg-web-archive@ietf.org; Tue, 23 Mar 2004 15:47:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5sml-0002up-DQ; Tue, 23 Mar 2004 15:46:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5smA-0002o5-OA
	for asrg@optimus.ietf.org; Tue, 23 Mar 2004 15:45:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27133
	for <asrg@ietf.org>; Tue, 23 Mar 2004 15:45:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5sm9-000589-00
	for asrg@ietf.org; Tue, 23 Mar 2004 15:45:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5skZ-0004lh-00
	for asrg@ietf.org; Tue, 23 Mar 2004 15:43:52 -0500
Received: from mail.crlf.net ([216.126.92.195])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5shP-0004Jw-00
	for asrg@ietf.org; Tue, 23 Mar 2004 15:40:35 -0500
Received: from localhost (localhost [127.0.0.1])
	by mail.crlf.net (Postfix) with ESMTP
	id 6C6A11F001; Tue, 23 Mar 2004 15:44:49 -0500 (EST)
From: David Maxwell <david@crlf.net>
To: Barry Shein <bzs@world.std.com>
Cc: Mark Baugher <mbaugher@cisco.com>, asrg@ietf.org
Subject: Re: [Asrg] S/MIME
Message-ID: <20040323204449.GH13098@mail>
References: <20040321150043.BD4DD170BB@mail.nitros9.org> <405DED1E.6010102@Royer.com> <405DF02E.6050905@solidmatrix.com> <405DF381.6020006@Royer.com> <405DF753.3020404@solidmatrix.com> <6.0.0.22.2.20040321150759.03dbbcc8@mira-sjc5-6.cisco.com> <16479.12343.923405.180@world.std.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <16479.12343.923405.180@world.std.com>
User-Agent: Mutt/1.4.2i
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/mail-archive/working-groups/asrg/>
Date: Tue, 23 Mar 2004 15:44:49 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

On Mon, 22 Mar 2004, Barry Shein wrote:
> 
> On March 21, 2004 at 15:10 mbaugher@cisco.com (Mark Baugher) wrote:
>  > 
>  > If we get forgery under control, then it is possible to apply reputation, 
>  > accreditation, blacklisting and other techniques to manage spam.  What am I 
>  > missing?
> 
> That the USPS (and no doubt others) haven't been able to make much of
> a dent in this in 200+ years?

I bet that if USPS did want to do this, the first
thing that they would do is to close down public mailboxes, and only
pickup mail from a locked box.

You and USPS would be the only entities with keys to your box. USPS
picking up mail there would know it was from you.

However, USPS has a goal of 'convienience', so that you can drop mail
into any mailbox anywhere, and (For a fee) have it go to anyone.

Sounds a lot like SMTP, hmm? (except for the fee)

-- 
David Maxwell, david@vex.net|david@maxwell.net -->
(About an Amiga rendering landscapes) It's not thinking, it's being artistic!
					      - Jamie Woods


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



From exim@www1.ietf.org  Tue Mar 23 21:43:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21100
	for <asrg-archive@odin.ietf.org>; Tue, 23 Mar 2004 21:43:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5yLr-0005fp-JW
	for asrg-archive@odin.ietf.org; Tue, 23 Mar 2004 21:42:43 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2O2ghxq021805
	for asrg-archive@odin.ietf.org; Tue, 23 Mar 2004 21:42:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5yLr-0005fc-Et
	for asrg-web-archive@optimus.ietf.org; Tue, 23 Mar 2004 21:42:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20918
	for <asrg-web-archive@ietf.org>; Tue, 23 Mar 2004 21:42:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5yLo-0003di-00
	for asrg-web-archive@ietf.org; Tue, 23 Mar 2004 21:42:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5yKS-0003Km-00
	for asrg-web-archive@ietf.org; Tue, 23 Mar 2004 21:41:17 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5yJZ-0003Bn-00
	for asrg-web-archive@ietf.org; Tue, 23 Mar 2004 21:40:21 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B5y95-0006zs-VE
	for asrg-web-archive@ietf.org; Tue, 23 Mar 2004 21:29:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5y8a-0004Mh-UX; Tue, 23 Mar 2004 21:29:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5y7n-0004Fs-7c
	for asrg@optimus.ietf.org; Tue, 23 Mar 2004 21:28:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20502
	for <asrg@ietf.org>; Tue, 23 Mar 2004 21:28:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5y7k-0002Q8-00
	for asrg@ietf.org; Tue, 23 Mar 2004 21:28:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5y7B-0002Ik-00
	for asrg@ietf.org; Tue, 23 Mar 2004 21:27:33 -0500
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5y69-00025z-00
	for asrg@ietf.org; Tue, 23 Mar 2004 21:26:29 -0500
X-Sasl-enc: Jg93Ax+JjxeYxKUYDi+9QA 1080094883
Received: from elvey.com (ns.nextbus.com [64.164.28.194])
	by mail.messagingengine.com (Postfix) with ESMTP id 19B37840774;
	Tue, 23 Mar 2004 21:21:22 -0500 (EST)
Message-ID: <4060F0A0.3070003@elvey.com>
From: Matthew Elvey <matthew@elvey.com>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
Cc: Hector Santos <winserver.support@winserver.com>
References: <002e01c40ea4$ea73f5b0$6401a8c0@hdev1> <405CE880.8020805@zemos.net> <002801c40f0c$60dda860$6401a8c0@hdev1> <405E21E8.6010107@zemos.net>
In-Reply-To: <405E21E8.6010107@zemos.net>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] FPs: Hector's winserver.com won't deliver my mail.
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/mail-archive/working-groups/asrg/>
Date: Tue, 23 Mar 2004 18:21:20 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-8.0 required=5.0 tests=HABEAS_SWE autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hector Santos wrote:

>>>>  No Spams this week! <pondering: something is wrong? checking
>>>> logs... nope, all spammers!>
>>>
Groan.  When I've tried to email you, my email has bounced.  I suspect 
tons of FPs.

> This is certainly worthwhile discussion, although I'm not sure it 
> should be happening here. Perhaps we should move this to ASRG? Please 
> simply redirect your response, or split this thread into scoped parts, 
> if you agree.

Responding there.

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



From exim@www1.ietf.org  Wed Mar 24 02:02:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04808
	for <asrg-archive@odin.ietf.org>; Wed, 24 Mar 2004 02:02:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62Op-00066D-H7
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 02:02:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2O723un023437
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 02:02:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62Oo-00065o-Vs
	for asrg-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 02:02:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA04254
	for <asrg-web-archive@ietf.org>; Wed, 24 Mar 2004 02:02:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62Ol-0006Fn-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 02:01:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B62Nq-00064L-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 02:01:03 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62NC-0005rw-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 02:00:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62Mt-0004wy-Bl; Wed, 24 Mar 2004 02:00:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B62M4-0004uL-VN
	for asrg@optimus.ietf.org; Wed, 24 Mar 2004 01:59:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA02149
	for <asrg@ietf.org>; Wed, 24 Mar 2004 01:59:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62M1-0005eF-00
	for asrg@ietf.org; Wed, 24 Mar 2004 01:59:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B62L5-0005RB-00
	for asrg@ietf.org; Wed, 24 Mar 2004 01:58:12 -0500
Received: from plounts.uits.indiana.edu ([129.79.1.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B62K9-0005DC-00
	for asrg@ietf.org; Wed, 24 Mar 2004 01:57:13 -0500
Received: from fontz.uits.indiana.edu (fontz.uits.indiana.edu [129.79.1.76])
	by plounts.uits.indiana.edu (8.12.10/8.12.10/IUPO) with ESMTP id i2O6vDxI009006
	for <asrg@ietf.org>; Wed, 24 Mar 2004 01:57:13 -0500 (EST)
Received: from [10.0.2.2] (dial-64-151-128-172.bton.kiva.net [64.151.128.172])
	(authenticated bits=0)
	by fontz.uits.indiana.edu (8.12.10/8.12.10/IUPO) with ESMTP id i2O6v74w022759
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <asrg@ietf.org>; Wed, 24 Mar 2004 01:57:10 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <20040323170008.3669.17897.Mailman@www1.ietf.org>
References: <20040323170008.3669.17897.Mailman@www1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <7534FED2-7D60-11D8-B129-000393DC31DA@bloomington.in.us>
Content-Transfer-Encoding: 7bit
From: Jim Witte <jswitte@bloomington.in.us>
To: asrg@ietf.org
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Subject: [Asrg] S/MIME irony...
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/mail-archive/working-groups/asrg/>
Date: Wed, 24 Mar 2004 01:57:04 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> No, but it's a good indication that S/MIME isn't ready for prime time
> <snip>
> -- 
> <URL:http://www.pobox.com/~meta/>
> --Apple-Mail-2-764092391
> Content-Type: application/pkcs7-signature;
> 	name=smime.p7s
> Content-Disposition: attachment;
> 	filename=smime.p7s
> Content-Transfer-Encoding: base64
>
> MIAGCSqGSIb3DQEHAqCAMIACAQE
> <S-NIIIIPPP!>

   Ironic how in a discussion on S/MIME and it's role in curtailing spam 
on the Interent that almost 40KB of the digest is composed of 
non-human-readable p7s attachments, which is about 81% (estimate based 
on ~39846 p7s bytes/49026 total bytes)


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



From exim@www1.ietf.org  Wed Mar 24 11:15:02 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03723
	for <asrg-archive@odin.ietf.org>; Wed, 24 Mar 2004 11:15:02 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6B1V-00013u-4h
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 11:14:33 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OGEXlQ004078
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 11:14:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6B1U-00013h-UY
	for asrg-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 11:14:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03698
	for <asrg-web-archive@ietf.org>; Wed, 24 Mar 2004 11:14:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6B1U-00000W-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 11:14:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6B0g-0007jp-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 11:13:42 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6B01-0007eB-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 11:13:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Az1-0000WG-Os; Wed, 24 Mar 2004 11:11:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6AyS-0000Pe-3D
	for asrg@optimus.ietf.org; Wed, 24 Mar 2004 11:11:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03380
	for <asrg@ietf.org>; Wed, 24 Mar 2004 11:11:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6AyJ-0007Sn-00
	for asrg@ietf.org; Wed, 24 Mar 2004 11:11:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6AxQ-0007MI-00
	for asrg@ietf.org; Wed, 24 Mar 2004 11:10:21 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6AwS-00079u-00
	for asrg@ietf.org; Wed, 24 Mar 2004 11:09:20 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2OG8eFp000576
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Wed, 24 Mar 2004 08:08:43 -0800
Message-ID: <4061B288.8010307@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] S/MIME irony...
References: <20040323170008.3669.17897.Mailman@www1.ietf.org> <7534FED2-7D60-11D8-B129-000393DC31DA@bloomington.in.us>
In-Reply-To: <7534FED2-7D60-11D8-B129-000393DC31DA@bloomington.in.us>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms070502060308000607010508"
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/mail-archive/working-groups/asrg/>
Date: Wed, 24 Mar 2004 09:08:40 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms070502060308000607010508
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



Jim Witte wrote:

>> No, but it's a good indication that S/MIME isn't ready for prime time
>> <snip> 
>
>
>   Ironic how in a discussion on S/MIME and it's role in curtailing 
> spam on the Interent that almost 40KB of the digest is composed of 
> non-human-readable p7s attachments, which is about 81% (estimate based 
> on ~39846 p7s bytes/49026 total bytes) 

Why does this bother you?

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms070502060308000607010508
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzI0MTYwODQwWjAjBgkqhkiG9w0BCQQxFgQU72AEMUBOjcHdgPNPu8ki
wGcEQcUwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAGBUfxZiiqRXRheU//2nHNeaUM9IwFL7rdUFbS97ElifZo/YMCl3oyXf+Sf3Y8+rQ
rDgEgxs5IG3nlDX/5v4IjTlH/EXyTHQsk62lL+baTnMQu1jGPLtPD5mSesIMV4fIVYRrcGSz
1i9H189rosmUdCEmgCWclkGHecoOaZS4q6lf4p1H3L3uSBuqNuwOZ6VirgPOvKAu+HEznlcQ
7f/xIwltMf9X0gau4xR6YyeQdtOoK6WPW514dQonBrhwg+qlf87NUyD5BX/1LO9vmh34nj4U
hJWnkT44lE3ztUZXvsWCkR4XpevYMcj19TivHwDB1rL6a6LEhF4NlNTbDnVg+QAAAAAAAA==
--------------ms070502060308000607010508--


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



From exim@www1.ietf.org  Wed Mar 24 11:39:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05313
	for <asrg-archive@odin.ietf.org>; Wed, 24 Mar 2004 11:39:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6BPL-0004Pj-Cl
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 11:39:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OGdB26016961
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 11:39:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6BPL-0004PU-7R
	for asrg-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 11:39:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05267
	for <asrg-web-archive@ietf.org>; Wed, 24 Mar 2004 11:39:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6BPK-0001mC-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 11:39:10 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6BOM-0001jM-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 11:38:11 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6BNT-0001fy-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 11:37:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6BNG-0003pI-FP; Wed, 24 Mar 2004 11:37:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6BMY-0003mC-6V
	for asrg@optimus.ietf.org; Wed, 24 Mar 2004 11:36:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05097
	for <asrg@ietf.org>; Wed, 24 Mar 2004 11:36:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6BMX-0001bZ-00
	for asrg@ietf.org; Wed, 24 Mar 2004 11:36:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6BLb-0001Xf-00
	for asrg@ietf.org; Wed, 24 Mar 2004 11:35:20 -0500
Received: from bsdsgr04.sagres.com.br ([200.140.134.134])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6BKl-0001Qd-00
	for asrg@ietf.org; Wed, 24 Mar 2004 11:34:28 -0500
Received: from ntsgr07.sagres.com.br (NTsgr07.sagres.com.br [10.0.17.7])
	by BSDsgr04.sagres.com.br (8.12.8p1/8.12.10) with ESMTP id i2OGY30i034763
	for <asrg@ietf.org>; Wed, 24 Mar 2004 16:34:03 GMT
	(envelope-from saurwein@uniwares.com)
Received: from leonone.uniwares.com ([200.103.112.80])
          by ntsgr07.sagres.com.br (Lotus Domino Release 5.0.12)
          with ESMTP id 2004032413424557:6446 ;
          Wed, 24 Mar 2004 13:42:45 -0300 
Message-Id: <6.0.3.0.0.20040324132907.01f2dec0@mail.uniwares.com>
X-Sender: saurwein.uniwares@mail.uniwares.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
To: asrg@ietf.org
From: Andreas Saurwein <saurwein@uniwares.com>
Subject: Re: [Asrg] S/MIME irony...
In-Reply-To: <4061B288.8010307@Royer.com>
References: <20040323170008.3669.17897.Mailman@www1.ietf.org>
 <7534FED2-7D60-11D8-B129-000393DC31DA@bloomington.in.us>
 <4061B288.8010307@Royer.com>
Mime-Version: 1.0
X-MIMETrack: Itemize by SMTP Server on ntsgr07/SAGRES(Release 5.0.12  |February 13, 2003) at
 24/03/2004 13:42:45,
	Serialize by Router on ntsgr07/SAGRES(Release 5.0.12  |February 13, 2003) at
 24/03/2004 13:42:47,
	Serialize complete at 24/03/2004 13:42:47
Content-Type: text/plain; charset="us-ascii"; format=flowed
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/mail-archive/working-groups/asrg/>
Date: Wed, 24 Mar 2004 13:33:46 -0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL autolearn=no version=2.60

At 24/3/2004 13:08 Wednesday, Doug Royer wrote:
>Jim Witte wrote:
>>>No, but it's a good indication that S/MIME isn't ready for prime time
>>><snip>
>>
>>   Ironic how in a discussion on S/MIME and it's role in curtailing spam 
>> on the Interent that almost 40KB of the digest is composed of 
>> non-human-readable p7s attachments, which is about 81% (estimate based 
>> on ~39846 p7s bytes/49026 total bytes)
>
>Why does this bother you?

The same way as it bothers me when people attach to their replies the 
original mail instead of quoting it. The attachments folder of my Eudora 
inbox is filled with hundreds of useless winmail.dat, smime.* and other 
similar files.
One could blame it of course onto the mail client(s), but I think it rather 
falls in the same category as the discussion about upgrading/replacing mail 
servers.

However, keep sending your smime.p7s, they might become useful one day.

Andreas 


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



From exim@www1.ietf.org  Wed Mar 24 12:41:56 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08583
	for <asrg-archive@odin.ietf.org>; Wed, 24 Mar 2004 12:41:56 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6CMz-00030N-9G
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 12:41:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OHed44011489
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 12:40:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6CMe-0002xm-N5
	for asrg-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 12:40:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08400
	for <asrg-web-archive@ietf.org>; Wed, 24 Mar 2004 12:40:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6CMN-0006Bn-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 12:40:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6CL8-00061q-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 12:38:54 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6CJx-0005sm-03
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 12:37:41 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B6CBe-0002z1-Tp
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 12:29:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6CBb-0001rw-3I; Wed, 24 Mar 2004 12:29:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6CAw-0001r9-Kt
	for asrg@optimus.ietf.org; Wed, 24 Mar 2004 12:28:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07856
	for <asrg@ietf.org>; Wed, 24 Mar 2004 12:28:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6CAv-0005TX-00
	for asrg@ietf.org; Wed, 24 Mar 2004 12:28:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6C9z-0005Qm-00
	for asrg@ietf.org; Wed, 24 Mar 2004 12:27:24 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6C9c-0005OP-00
	for asrg@ietf.org; Wed, 24 Mar 2004 12:27:01 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i2OHQuRo025687;
        Wed, 24 Mar 2004 09:26:56 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <GYB3KBB0>; Wed, 24 Mar 2004 09:26:56 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E5DBAAD@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Andreas Saurwein'" <saurwein@uniwares.com>, asrg@ietf.org
Subject: RE: [Asrg] S/MIME irony...
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
MIME-Version: 1.0
Content-Type: multipart/signed;
	micalg=SHA1;
	boundary="----=_NextPart_000_001E_01C4119B.48FD9D40";
	protocol="application/x-pkcs7-signature"
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Wed, 24 Mar 2004 09:26:51 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,MISSING_OUTLOOK_NAME 
	autolearn=no version=2.60

This is a multi-part message in MIME format.

------=_NextPart_000_001E_01C4119B.48FD9D40
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

> One could blame it of course onto the mail client(s), but I 
> think it rather 
> falls in the same category as the discussion about 
> upgrading/replacing mail 
> servers.

That would be the right thing to do.

S/MIME has been an industry standard for at least five years. Eudora
is the only MUA with a significant user base that does not support 
S/MIME. Even the pagers now know enough to strip out S/MIME envelopes.


------=_NextPart_000_001E_01C4119B.48FD9D40
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Disposition: attachment;
	filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIC7jCCAuow
ggJToAMCAQICED2s0mK8XU4zCRAcjDjmsFcwDQYJKoZIhvcNAQEEBQAwUTELMAkGA1UEBhMCVVMx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMRYwFAYDVQQLEw1Db3Jwb3JhdGUgSVNHMREwDwYDVQQD
EwhJUFNlYyBDQTAeFw0wMzEyMDYwMDAwMDBaFw0wNDEyMTYyMzU5NTlaMHgxFzAVBgNVBAoUDlZl
cmlTaWduLCBJbmMuMRswGQYDVQQLFBJSZW1vdGUgQWNjZXNzIFVzZXIxHDAaBgNVBAMTE1BoaWxp
cCBIYWxsYW0tQmFrZXIxIjAgBgkqhkiG9w0BCQEWE3BiYWtlckB2ZXJpc2lnbi5jb20wgZ8wDQYJ
KoZIhvcNAQEBBQADgY0AMIGJAoGBAOuUwPW8C3kxcYqOXcmdQWl4/Zf/shRRxUA4idRzTxOVETkZ
QXEeQPlqhOeyD0F4Vmj3nnz51eJxiL5x2NBjAntT4sQ4+6Grt5OSYGEyYKGf5bNUmzwaD1IsFyj+
8oudnbThaTm9sSuVrhrJLL8Qc7Vpw/Lw0t5ddU2Eci/YQZMVAgMBAAGjgZswgZgwCQYDVR0TBAIw
ADALBgNVHQ8EBAMCBaAwEQYJYIZIAYb4QgEBBAQDAgeAMFgGA1UdHwRRME8wTaBLoEmGR2h0dHA6
Ly9vbnNpdGVjcmwudmVyaXNpZ24uY29tL1ZlcmlTaWduSW5jUmVtb3RlQWNjZXNzVXNlci9MYXRl
c3RDUkwuY3JsMBEGCmCGSAGG+EUBBgkEAwEB/zANBgkqhkiG9w0BAQQFAAOBgQAEgPxZKQGnvpiT
rYpiEUUMZEpjFxlwUqeVYOTdCfE8trQ/n3/hIFJgQLzlWfaziKKg2HsVtrTwSEiWgkmQTvoSdzxS
Wdk2BrIt/x1B2mtL+pF9Gn2OLGuadwc6qkh9WpfNdl1JtH3E3QFDK1xaWKjUy0idPFY8obUWwBLN
3lAQMTGCAlowggJWAgEBMGUwUTELMAkGA1UEBhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMu
MRYwFAYDVQQLEw1Db3Jwb3JhdGUgSVNHMREwDwYDVQQDEwhJUFNlYyBDQQIQPazSYrxdTjMJEByM
OOawVzAJBgUrDgMCGgUAoIIBSzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJ
BTEPFw0wNDAzMjQxNzI2NTFaMCMGCSqGSIb3DQEJBDEWBBSDpWZ/58FGVhZuLckCoQCt2PCm1jB0
BgkrBgEEAYI3EAQxZzBlMFExCzAJBgNVBAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEW
MBQGA1UECxMNQ29ycG9yYXRlIElTRzERMA8GA1UEAxMISVBTZWMgQ0ECED2s0mK8XU4zCRAcjDjm
sFcwdgYJKoZIhvcNAQkPMWkwZzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwBwYFKw4DAgcw
BwYFKw4DAgcwDQYIKoZIhvcNAwICASgwBwYFKw4DAhowBwYFKw4DAhowCgYIKoZIhvcNAgUwCgYI
KoZIhvcNAgUwDQYJKoZIhvcNAQEBBQAEgYDUwXKuN/+Uvf5jTWKmWOsHT2rhJHACP1dma+xAkWiO
brCI3ZBt9Ir/BihlLYix+YzWtE4o8LM8JjzJ8H4c5udZHMxYz/4rQiCxZ7eOGjIP3ehKytDCFLz0
uuaSYD6mfRQImNOAq15r9YMq4PvU/Ury0vNcTBoVEZGwFqxqpmyf5QAAAAAAAA==

------=_NextPart_000_001E_01C4119B.48FD9D40--


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



From exim@www1.ietf.org  Wed Mar 24 13:10:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10393
	for <asrg-archive@odin.ietf.org>; Wed, 24 Mar 2004 13:10:43 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6CpT-0005uX-39
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 13:10:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OIAFsm022715
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 13:10:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6CpS-0005uI-Pd
	for asrg-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 13:10:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10281
	for <asrg-web-archive@ietf.org>; Wed, 24 Mar 2004 13:10:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6CpQ-0000g0-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 13:10:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Cnf-0000NP-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 13:08:24 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Cmh-0000I0-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 13:07:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6CmM-0005HN-C7; Wed, 24 Mar 2004 13:07:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Cli-0005Fr-N5
	for asrg@optimus.ietf.org; Wed, 24 Mar 2004 13:06:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10066
	for <asrg@ietf.org>; Wed, 24 Mar 2004 13:06:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Clg-0000EP-00
	for asrg@ietf.org; Wed, 24 Mar 2004 13:06:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Ckr-0000Be-00
	for asrg@ietf.org; Wed, 24 Mar 2004 13:05:29 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Ck4-000047-00
	for asrg@ietf.org; Wed, 24 Mar 2004 13:04:41 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2OI42Fp002011
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO)
	for <asrg@ietf.org>; Wed, 24 Mar 2004 10:04:04 -0800
Message-ID: <4061CD91.70106@Royer.com>
From: Doug Royer <Doug@Royer.com>
Reply-To: asrg@ietf.org
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com> <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com> <405B4591.4080808@Royer.com> <B3545D83-7A2B-11D8-B58D-000393CAA6AA@pobox.com> <405C9208.4050506@Royer.com> <1167864D-7C64-11D8-A507-00039380F1B6@pobox.com> <405FA5AE.90209@Royer.com> <96B658DE-7DB7-11D8-85F6-00039380F1B6@pobox.com>
In-Reply-To: <96B658DE-7DB7-11D8-85F6-00039380F1B6@pobox.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms020100020606020603080101"
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/mail-archive/working-groups/asrg/>
Date: Wed, 24 Mar 2004 11:04:01 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms020100020606020603080101
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



mathew wrote:

> On Mar 22, 2004, at 21:49, Doug Royer wrote:
>
>>> No, but it's a good indication that S/MIME isn't ready for prime 
>>> time when the three different S/MIME packages available to me can't 
>>> talk to each other.
>>
>>
>> I can name 4 popular ones that can interoperate with each other. So 
>> it looks ready to me.
>
>
> Go on then.
>
> Here are three that don't: Lotus Notes, Mozilla, and Apple Mail.

I have exchanged HUNDREDS of S/MIME messages with IBM/Lotus
developers in the last year that use Lotus notes- so perhaps you have a 
buggy version?
We always sign our email and often encrypt it. I know it works with at least
newer versions of Lotus Notes.

I have never used Apple mail nor do I own an Apple system so I am unable 
to test
for issues with that implementation.

It works with (1) Outlook, (2) Exchange (which really are separate 
implementations)
(2) Lotus Notes , (3) Mozilla and Netscape Communicator (mostly the same
implementation) - that is what I use,  (4) Evolution , (5) TheBat,  and (6)
OpenSSL signature verification scanners. They also work with sendmails.org
milter filters interface for verifying S/MIME messages on the way in or out.

I own all of the above and have done testing of S/MIME with them.
I have tested both S/MIME digital signatures and encryption.

There are some older versions of Outlook that can not reply to an S/MIME
message, but can verify them. That is a bug in Outlook. Even older
versions of Outlook can not verify them. Both bugs are due to the
fact that someone at MS thought that you needed to have your own
cert in order to validate and reply to one. That was fixed a year
or two ago.

Older versions of Lotus Notes checked too many of the headers
and got validation errors. That was fixed about two years ago.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms020100020606020603080101
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzI0MTgwNDAxWjAjBgkqhkiG9w0BCQQxFgQUF/aGD/HsKoQ8+cjHwuIB
sCCN0CgwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAuR+gf4xzES2IexJlCzr+UEOwpHlybbbxfPpQJUBpYrvVgWUP5MCeyTakAjAXS2o5
Hi+G1IBbEekkxPffUcFNDzW9Ka3OsjpwpuLpRYG7HkkM2BI+pZplStg3dyjWKWeY5OcpPPbn
1E+RpJnEc6fvb6ojtATnwUkHNcmvtZvIqm0Y2FRwbuktADdpF+ZQ8VLi+5BmV/qBSgruD675
MRBvL7z5zGxYLxnhMzQ9iEKChz8vKEpM1iEd29ax3SBqE52pdpe2WNscZjmIoMXcjF9t6NlN
GGzFE6AuZzx8rcpbPXvkzrcLgYw57X0RrnL+F0NBX3E347xiBQt3MpzBPg6EGgAAAAAAAA==
--------------ms020100020606020603080101--


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



From exim@www1.ietf.org  Wed Mar 24 13:22:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11492
	for <asrg-archive@odin.ietf.org>; Wed, 24 Mar 2004 13:22:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6D0Y-00074i-Nz
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 13:21:43 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OILg9i027195
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 13:21:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6CMp-0002y0-DB
	for asrg-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 12:40:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA08424
	for <asrg-web-archive@ietf.org>; Wed, 24 Mar 2004 12:40:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6CMY-0006EW-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 12:40:22 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6CLN-00064D-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 12:39:10 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6CK1-0005sl-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 12:37:45 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B6C7A-0002pC-CX
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 12:24:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6C6i-0001Ia-V7; Wed, 24 Mar 2004 12:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6C62-0001Gg-0Y
	for asrg@optimus.ietf.org; Wed, 24 Mar 2004 12:23:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07656
	for <asrg@ietf.org>; Wed, 24 Mar 2004 12:23:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6C60-0005EH-00
	for asrg@ietf.org; Wed, 24 Mar 2004 12:23:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6C59-0005AF-00
	for asrg@ietf.org; Wed, 24 Mar 2004 12:22:23 -0500
Received: from rwcrmhc11.comcast.net ([204.127.198.35])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6C4E-00053H-00
	for asrg@ietf.org; Wed, 24 Mar 2004 12:21:26 -0500
Received: from [192.168.0.3] (h00095b86f221.ne.client2.attbi.com[24.61.46.50])
          by comcast.net (rwcrmhc11) with SMTP
          id <2004032417205301300dstuse>; Wed, 24 Mar 2004 17:20:54 +0000
Message-Id: <96B658DE-7DB7-11D8-85F6-00039380F1B6@pobox.com>
X-Habeas-Swe-6: email in exchange for a license for this Habeas
X-Habeas-Swe-3: like Habeas SWE (tm)
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
X-Habeas-Swe-8: Message (HCM) and not spam. Please report use of this
From: mathew <meta@pobox.com>
X-Habeas-Swe-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-Swe-2: brightly anticipated
In-Reply-To: <405FA5AE.90209@Royer.com>
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com> <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com> <405B4591.4080808@Royer.com> <B3545D83-7A2B-11D8-B58D-000393CAA6AA@pobox.com> <405C9208.4050506@Royer.com> <1167864D-7C64-11D8-A507-00039380F1B6@pobox.com> <405FA5AE.90209@Royer.com>
To: asrg@ietf.org
X-Habeas-Swe-7: warrant mark warrants that this is a Habeas Compliant
Mime-Version: 1.0 (Apple Message framework v613)
X-Habeas-Swe-4: Copyright 2002 Habeas (tm) 
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-1-909915436; protocol="application/pkcs7-signature"
X-Habeas-Swe-1: winter into spring
X-Habeas-Swe-9: mark in spam to <http://www.habeas.com/report/>.
X-Mailer: Apple Mail (2.613)
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/mail-archive/working-groups/asrg/>
Date: Wed, 24 Mar 2004 12:20:46 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--Apple-Mail-1-909915436
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

On Mar 22, 2004, at 21:49, Doug Royer wrote:
>> No, but it's a good indication that S/MIME isn't ready for prime time 
>> when the three different S/MIME packages available to me can't talk 
>> to each other.
>
> I can name 4 popular ones that can interoperate with each other. So it 
> looks ready to me.

Go on then.

Here are three that don't: Lotus Notes, Mozilla, and Apple Mail.


mathew
--Apple-Mail-1-909915436
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGEDCCAskw
ggIyoAMCAQICAwtCvTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDMxMjAzMTUwOTU3WhcNMDQxMjAyMTUwOTU3WjBAMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMR0wGwYJKoZIhvcNAQkBFg5tZXRhQHBvYm94LmNvbTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANA40G+RMi0LMG++Lz6J4LpIaXkydRxJoLjz
9EPfZGLn6dPBumvzLVWDaQrOshYuyViOW+oPk62xz6HBnarbOX3VoiFVyGCjqkZz+TToHDDlya/z
D8l/WF92nvsEPFPKE6Fw/Lg13/g9zzBlxrjwW98bL6dI1tKvdokMH91++35sC0Yu5oZjuBF4ydUA
1n7pX2KgEDhRRP5b/RhQPrdpbZhO5fwzthiD0VlCG9zkloNJ8GOFxMFd2lpVpV1ISySCHYwEtA1n
zxR7Kq4oRaMvAodHj8NHRPDjE+vyALzi0mCZ+JlQAyKr+Li5YvKZNRobyYBQGLLOyt31ZAj9vfSS
g2cCAwEAAaMrMCkwGQYDVR0RBBIwEIEObWV0YUBwb2JveC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQQFAAOBgQCVJDuVViVm9t4++qdMFmiF4yfAowCy3/bauIAcxAJXvd21LnorWF+49YJk
jBZO74MDPrsYb5M9ybKMy04vxNuXXHM9TVLUWJjz5PUCcaNIj9DqGIW9eAPWj/Pvn6j5qSP8OcoK
mwwrKcurmSi+sJqajLjET0wzsuvgRFNE4pkOyDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEF
BQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg
VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24g
U2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAw
MDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3Vs
dGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWlu
ZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me
7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r
1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCB
kTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3Rl
LmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAg
pB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPq
Cy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUa
C4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx
0x1G/11fZU8xggLnMIIC4wIBATBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u
c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz
dWluZyBDQQIDC0K9MAkGBSsOAwIaBQCgggFTMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJ
KoZIhvcNAQkFMQ8XDTA0MDMyNDE3MjA0N1owIwYJKoZIhvcNAQkEMRYEFJEnGgT9Jlz1V5bZ9M/y
DWm0qxBpMHgGCSsGAQQBgjcQBDFrMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBD
b25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAgMLQr0wegYLKoZIhvcNAQkQAgsxa6BpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK
ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQQIDC0K9MA0GCSqGSIb3DQEBAQUABIIBAAzWmhUzE3Npto6aaXJF
V+6UsLCB1NHpqMnkHqvePiZ1z6ZwIB7Z+h3KMtO22OMgzOMqXh6KkKxu9JkoNSsNsECnS+15dGJo
aZTsDJQa18ZsALAPIPPt/0lbiuFrzy5DX0Ped2kY2UvRYOWG8NkF/eWJ9fRjqhJvZVDl12yaGyXH
GQ6d7QKQzdHjQwsFpprgFeeEx0cfV8PimlcyoUaFWoKxHxrXttSrrZVSSgkAQtygkWQtmuId8wHg
8xnR2ygsCr8ZBo2I6l2gS60gUMIgzUaZUxV8MFpHrnKBImYIVHUilo+Of0nPucibfrsO6G7gqf53
DE5R1P1FNberJtnXpV4AAAAAAAA=

--Apple-Mail-1-909915436--


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



From exim@www1.ietf.org  Wed Mar 24 14:40:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15789
	for <asrg-archive@odin.ietf.org>; Wed, 24 Mar 2004 14:40:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6EEN-0000nD-Mr
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 14:40:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OJe3vH003041
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 14:40:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6EEN-0000mw-Ez
	for asrg-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 14:40:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15734
	for <asrg-web-archive@ietf.org>; Wed, 24 Mar 2004 14:40:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6EEK-0000pI-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 14:40:00 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6EDK-0000gU-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 14:38:58 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ECR-0000Y6-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 14:38:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6EBR-0008GH-OS; Wed, 24 Mar 2004 14:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6EB0-00089b-V6
	for asrg@optimus.ietf.org; Wed, 24 Mar 2004 14:36:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15419
	for <asrg@ietf.org>; Wed, 24 Mar 2004 14:36:32 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6EAy-0000NG-00
	for asrg@ietf.org; Wed, 24 Mar 2004 14:36:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6EA4-0000IZ-00
	for asrg@ietf.org; Wed, 24 Mar 2004 14:35:37 -0500
Received: from chromatix.demon.co.uk ([80.177.102.173] helo=lithium.chromatix.org.uk)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6E9d-0000EB-00
	for asrg@ietf.org; Wed, 24 Mar 2004 14:35:09 -0500
Received: from dolphin.chromatix.org.uk ([192.168.239.105])
	by lithium.chromatix.org.uk with esmtp (Exim 4.21)
	id 1B6E9c-00045D-Uy
	for asrg@ietf.org; Wed, 24 Mar 2004 19:35:08 +0000
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <4061CD91.70106@Royer.com>
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com> <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com> <405B4591.4080808@Royer.com> <B3545D83-7A2B-11D8-B58D-000393CAA6AA@pobox.com> <405C9208.4050506@Royer.com> <1167864D-7C64-11D8-A507-00039380F1B6@pobox.com> <405FA5AE.90209@Royer.com> <96B658DE-7DB7-11D8-85F6-00039380F1B6@pobox.com> <4061CD91.70106@Royer.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <5BD1DDB2-7DCA-11D8-9A94-003065664B7C@chromatix.demon.co.uk>
Content-Transfer-Encoding: 7bit
From: Jonathan Morton <chromi@chromatix.demon.co.uk>
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
To: asrg@ietf.org
X-Mailer: Apple Mail (2.613)
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/mail-archive/working-groups/asrg/>
Date: Wed, 24 Mar 2004 19:35:08 +0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>>>> No, but it's a good indication that S/MIME isn't ready for prime 
>>>> time when the three different S/MIME packages available to me can't 
>>>> talk to each other.
>>>
>>> I can name 4 popular ones that can interoperate with each other. So 
>>> it looks ready to me.
>>
>> Go on then.
>>
>> Here are three that don't: Lotus Notes, Mozilla, and Apple Mail.
>
> I have exchanged HUNDREDS of S/MIME messages with IBM/Lotus
> developers in the last year that use Lotus notes- so perhaps you have 
> a buggy version?
> We always sign our email and often encrypt it. I know it works with at 
> least
> newer versions of Lotus Notes.
>
> I have never used Apple mail nor do I own an Apple system so I am 
> unable to test
> for issues with that implementation.

Just for the record, my copy of Apple Mail (on Panther) correctly 
verifies Doug's and Phillip's mails, but not mathew's.  It says that 
mathew's mails have been modified or tampered with.  Given that 
mathew's mail appears to have been *sent* from Apple Mail, I would 
suggest that his problem stems from somewhere in his own setup.

--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     chromi@chromatix.demon.co.uk
website:  http://www.chromatix.uklinux.net/
tagline:  The key to knowledge is not to rely on people to teach you it.


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



From exim@www1.ietf.org  Wed Mar 24 16:18:54 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21900
	for <asrg-archive@odin.ietf.org>; Wed, 24 Mar 2004 16:18:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Fla-00089E-Ed
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 16:18:26 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2OLIQWH031312
	for asrg-archive@odin.ietf.org; Wed, 24 Mar 2004 16:18:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6FlZ-00088x-ND
	for asrg-web-archive@optimus.ietf.org; Wed, 24 Mar 2004 16:18:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21893
	for <asrg-web-archive@ietf.org>; Wed, 24 Mar 2004 16:18:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6FlY-0001pP-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 16:18:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Fkj-0001mX-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 16:17:34 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Fjz-0001jF-00
	for asrg-web-archive@ietf.org; Wed, 24 Mar 2004 16:16:47 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6FjG-0007oZ-6u; Wed, 24 Mar 2004 16:16:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Fih-0007nq-B6
	for asrg@optimus.ietf.org; Wed, 24 Mar 2004 16:15:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21780
	for <asrg@ietf.org>; Wed, 24 Mar 2004 16:15:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Fif-0001dM-00
	for asrg@ietf.org; Wed, 24 Mar 2004 16:15:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Fhn-0001aL-00
	for asrg@ietf.org; Wed, 24 Mar 2004 16:14:32 -0500
Received: from ns2.ohmi.org ([216.187.106.200] helo=ohmi.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6FhL-0001WS-00
	for asrg@ietf.org; Wed, 24 Mar 2004 16:14:03 -0500
Received: from smart (smart.ohmi.org [192.168.1.151])
	by ohmi.org (8.11.6/8.11.6) with ESMTP id i2OLDTD10669;
	Wed, 24 Mar 2004 16:13:29 -0500
From: "Radu Hociung" <radu.asrg@ohmi.org>
To: "'Eric Dean'" <eric@purespeed.com>, <asrg@ietf.org>
Subject: RE: [Asrg] asrg-cri - spam to mailing lists ?
Message-ID: <016501c411e4$dd2d5d90$9701a8c0@smart>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
In-Reply-To: <00f001c40e8a$b71c7df0$6701a8c0@sohonotebook>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
Content-Transfer-Encoding: quoted-printable
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/mail-archive/working-groups/asrg/>
Date: Wed, 24 Mar 2004 16:13:29 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Exactly. If the process of deleting such spam is not automated, then the
spam protection is not really protecting anything, and in fact it makes =
the
spam problem worse by providing a mechanism of guaranteed delivery.

Is it not the consensus that spam should be prevented from reaching the
mailbox?



>If a spammer included exempt headers then the process would not be
>automated and the message would be subject to manual deletion.  The
>intent is that valid email would automatically be delivered=20
>and anything
>else would do something else.
>
>=20
>> 2. About the contents: If a spammer would add headers to his=20
>> message to make it look like a mailing list, this message=20
>> would then not be subject to the other provisions of the=20
>> draft? Is there a separate draft/RFC to deal with the mailing=20
>> list/CR combination, or do you intend to address this in some way?


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



From exim@www1.ietf.org  Thu Mar 25 11:04:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03287
	for <asrg-archive@odin.ietf.org>; Thu, 25 Mar 2004 11:04:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XKh-0005ee-AZ
	for asrg-archive@odin.ietf.org; Thu, 25 Mar 2004 11:03:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PG3pgJ021733
	for asrg-archive@odin.ietf.org; Thu, 25 Mar 2004 11:03:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XKf-0005dt-TE
	for asrg-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 11:03:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA03100
	for <asrg-web-archive@ietf.org>; Thu, 25 Mar 2004 11:03:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XKZ-00034N-00
	for asrg-web-archive@ietf.org; Thu, 25 Mar 2004 11:03:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6XI8-0002XN-00
	for asrg-web-archive@ietf.org; Thu, 25 Mar 2004 11:01:14 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XGC-0002Il-0E
	for asrg-web-archive@ietf.org; Thu, 25 Mar 2004 10:59:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6X2p-0002WW-I9; Thu, 25 Mar 2004 10:45:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Wxi-00016A-4E
	for asrg@optimus.ietf.org; Thu, 25 Mar 2004 10:40:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01173
	for <asrg@ietf.org>; Thu, 25 Mar 2004 10:40:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Wxf-00014K-00
	for asrg@ietf.org; Thu, 25 Mar 2004 10:40:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Wwk-00012G-00
	for asrg@ietf.org; Thu, 25 Mar 2004 10:39:06 -0500
Received: from [216.200.145.38] (helo=omta12.mta.everyone.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Ww3-00010B-00
	for asrg@ietf.org; Thu, 25 Mar 2004 10:38:23 -0500
Received: from rmta02.mta.everyone.net (bigip1-snat [216.200.145.29])
	by omta12.mta.everyone.net (Postfix) with ESMTP
	id 4D1E241EF9; Thu, 25 Mar 2004 07:38:05 -0800 (PST)
Received: from sohonotebook (ip68-100-37-118.dc.dc.cox.net [68.100.37.118])
	by rmta02.mta.everyone.net (Postfix) with ESMTP
	id 0AF7C184A9; Thu, 25 Mar 2004 07:38:03 -0800 (PST)
From: "Eric Dean" <eric@purespeed.com>
To: "'Radu Hociung'" <radu.asrg@ohmi.org>, <asrg@ietf.org>
Subject: RE: [Asrg] asrg-cri - spam to mailing lists ?
Message-ID: <019a01c4127f$2aaaf510$6701a8c0@sohonotebook>
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: <016501c411e4$dd2d5d90$9701a8c0@smart>
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/mail-archive/working-groups/asrg/>
Date: Thu, 25 Mar 2004 10:38:04 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.4 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Certainly that is implied.  And anyone building CR systems would be wise
in doing so.

We are merely specifying a protocol.  The actual implementation of that
protocol and the actions that are taken based upon specific messages are
up to individuals.

The intent was to see if this protocol provided a comprehensive set of
messages for CRI.

> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On 
> Behalf Of Radu Hociung
> Sent: Wednesday, March 24, 2004 4:13 PM
> To: 'Eric Dean'; asrg@ietf.org
> Subject: RE: [Asrg] asrg-cri - spam to mailing lists ?
> 
> 
> Exactly. If the process of deleting such spam is not 
> automated, then the spam protection is not really protecting 
> anything, and in fact it makes the spam problem worse by 
> providing a mechanism of guaranteed delivery.
> 
> Is it not the consensus that spam should be prevented from 
> reaching the mailbox?
> 
> 
> 
> >If a spammer included exempt headers then the process would not be 
> >automated and the message would be subject to manual deletion.  The 
> >intent is that valid email would automatically be delivered and 
> >anything else would do something else.
> >
> > 
> >> 2. About the contents: If a spammer would add headers to his
> >> message to make it look like a mailing list, this message 
> >> would then not be subject to the other provisions of the 
> >> draft? Is there a separate draft/RFC to deal with the mailing 
> >> list/CR combination, or do you intend to address this in some way?
> 
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
> 


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



From exim@www1.ietf.org  Thu Mar 25 11:20:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04760
	for <asrg-archive@odin.ietf.org>; Thu, 25 Mar 2004 11:20:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xaj-00088n-OS
	for asrg-archive@odin.ietf.org; Thu, 25 Mar 2004 11:20:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2PGKPqe031289
	for asrg-archive@odin.ietf.org; Thu, 25 Mar 2004 11:20:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6Xaj-00088a-If
	for asrg-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 11:20:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04686
	for <asrg-web-archive@ietf.org>; Thu, 25 Mar 2004 11:20:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6Xai-0004YK-00
	for asrg-web-archive@ietf.org; Thu, 25 Mar 2004 11:20:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6Xa4-0004VK-00
	for asrg-web-archive@ietf.org; Thu, 25 Mar 2004 11:19:45 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XYx-0004SL-00
	for asrg-web-archive@ietf.org; Thu, 25 Mar 2004 11:18:35 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XYQ-0007oK-KM; Thu, 25 Mar 2004 11:18:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6XXx-0007lT-WF
	for asrg@optimus.ietf.org; Thu, 25 Mar 2004 11:17:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04491
	for <asrg@ietf.org>; Thu, 25 Mar 2004 11:17:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XXx-0004MO-00
	for asrg@ietf.org; Thu, 25 Mar 2004 11:17:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6XX7-0004HY-00
	for asrg@ietf.org; Thu, 25 Mar 2004 11:16:42 -0500
Received: from ns2.ohmi.org ([216.187.106.200] helo=ohmi.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6XWO-00049U-00
	for asrg@ietf.org; Thu, 25 Mar 2004 11:15:56 -0500
Received: from smart (smart.ohmi.org [192.168.1.151])
	by ohmi.org (8.11.6/8.11.6) with ESMTP id i2PGFIX14839;
	Thu, 25 Mar 2004 11:15:18 -0500
From: "Radu Hociung" <radu.asrg@ohmi.org>
To: "'Eric Dean'" <eric@purespeed.com>, <asrg@ietf.org>
Subject: RE: [Asrg] asrg-cri - spam to mailing lists ?
Message-ID: <000001c41284$5cdb8590$9701a8c0@smart>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <019a01c4127f$2aaaf510$6701a8c0@sohonotebook>
Content-Transfer-Encoding: quoted-printable
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/mail-archive/working-groups/asrg/>
Date: Thu, 25 Mar 2004 11:15:17 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

In that case, I really think the proposed protocol should have =
provisions
for the mailing-list corner case; otherwise, this corner case will =
become
the path of least resistance for spam to get through. Just as an =
electrical
current, spam will then follow this path - perhaps not immediately, but
eventually, when it is one of the last opportunities left open.

'A solution is only as strong as it's weakest link'

Radu.

PS. I had the pleasure to go through your C/R procedure, and I =
appreciate
the ease of use from my end. How many mailboxes does your software =
protect?


>We are merely specifying a protocol.  The actual implementation of that
>protocol and the actions that are taken based upon specific=20
>messages are
>up to individuals.
>
>The intent was to see if this protocol provided a comprehensive set of
>messages for CRI.

>> Exactly. If the process of deleting such spam is not=20
>> automated, then the spam protection is not really protecting=20
>> anything, and in fact it makes the spam problem worse by=20
>> providing a mechanism of guaranteed delivery.
>>=20
>> Is it not the consensus that spam should be prevented from=20
>> reaching the mailbox?
>>=20
>>=20
>>=20
>> >If a spammer included exempt headers then the process would not be=20
>> >automated and the message would be subject to manual deletion.  The=20
>> >intent is that valid email would automatically be delivered and=20
>> >anything else would do something else.
>> >
>> >=20
>> >> 2. About the contents: If a spammer would add headers to his
>> >> message to make it look like a mailing list, this message=20
>> >> would then not be subject to the other provisions of the=20
>> >> draft? Is there a separate draft/RFC to deal with the mailing=20
>> >> list/CR combination, or do you intend to address this in some way?


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



From exim@www1.ietf.org  Sat Mar 27 07:10:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09365
	for <asrg-archive@odin.ietf.org>; Sat, 27 Mar 2004 07:10:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7CdM-0002Cc-BG
	for asrg-archive@odin.ietf.org; Sat, 27 Mar 2004 07:09:52 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2RC9q8k008462
	for asrg-archive@odin.ietf.org; Sat, 27 Mar 2004 07:09:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7CdM-0002CP-50
	for asrg-web-archive@optimus.ietf.org; Sat, 27 Mar 2004 07:09:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09356
	for <asrg-web-archive@ietf.org>; Sat, 27 Mar 2004 07:09:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7CdH-00000D-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 07:09:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7CcN-0007j5-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 07:08:52 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7Cbq-0007dq-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 07:08:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7Cba-0001p7-Ef; Sat, 27 Mar 2004 07:08:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7CbT-0001nA-JZ
	for asrg@optimus.ietf.org; Sat, 27 Mar 2004 07:07:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09293
	for <asrg@ietf.org>; Sat, 27 Mar 2004 07:07:50 -0500 (EST)
From: spharion@directnet.com.br
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7CbP-0007d7-00
	for asrg@ietf.org; Sat, 27 Mar 2004 07:07:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7CaR-0007YC-00
	for asrg@ietf.org; Sat, 27 Mar 2004 07:06:51 -0500
Received: from [200.218.224.15] (helo=smtp.cam.directnet.com.br)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7CZq-0007TI-00
	for asrg@ietf.org; Sat, 27 Mar 2004 07:06:14 -0500
Received: from aptiva.directnet.com.br (unknown [10.24.47.99])
	by smtp.cam.directnet.com.br (Postfix) with ESMTP id 8AD4EC17E
	for <asrg@ietf.org>; Sat, 27 Mar 2004 10:02:49 -0300 (BRT)
To: asrg@ietf.org
MIME-Version: 1.0
Message-ID: <406544E0.5420.2D654D3@localhost>
Priority: normal
X-mailer: Pegasus Mail for Windows (v4.12a)
Content-type: Multipart/Alternative; boundary="Alt-Boundary-19338.47600858"
Subject: [Asrg] spf
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/mail-archive/working-groups/asrg/>
Date: Sat, 27 Mar 2004 09:09:52 -0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,HTML_50_60,HTML_MESSAGE,
	HTML_TITLE_EMPTY,NO_REAL_NAME autolearn=no version=2.60

--Alt-Boundary-19338.47600858
Content-type: text/plain; charset=US-ASCII
Content-description: Mail message body
Content-Transfer-Encoding: 7BIT

this is a tentative option to spf, but does not
seem to break forwarding:

http://nucleo.freeservers.com/mba/

have fun. gone, ricardo.




--Alt-Boundary-19338.47600858
Content-type: text/html; charset=US-ASCII
Content-description: Mail message body
Content-Transfer-Encoding: 7BIT

<?xml  version="1.0" ?><html>
<head>
<title></title>
</head>
<body>
<div align="left"><font face="Arial"><span style="font-size:10pt">this is a tentative option to spf, but does not</span></font></div>
<div align="left"><font face="Arial"><span style="font-size:10pt">seem to break forwarding:</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Arial"><span style="font-size:10pt">http://nucleo.freeservers.com/mba/</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><font face="Arial"><span style="font-size:10pt">have fun. gone, ricardo.</span></font></div>
<div align="left"><br/>
</div>
<div align="left"><br/>
</div>
<div align="left"></div>
</body>
</html>

--Alt-Boundary-19338.47600858--

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



From exim@www1.ietf.org  Sat Mar 27 21:27:51 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12170
	for <asrg-archive@odin.ietf.org>; Sat, 27 Mar 2004 21:27:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7Q1D-00020d-Vd
	for asrg-archive@odin.ietf.org; Sat, 27 Mar 2004 21:27:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2S2RNFk007719
	for asrg-archive@odin.ietf.org; Sat, 27 Mar 2004 21:27:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7Q1D-00020Q-O8
	for asrg-web-archive@optimus.ietf.org; Sat, 27 Mar 2004 21:27:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12157
	for <asrg-web-archive@ietf.org>; Sat, 27 Mar 2004 21:27:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7Q1B-0002wJ-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 21:27:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7Q0B-0002pZ-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 21:26:20 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7PzW-0002jZ-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 21:25:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7Pyv-0001s5-NT; Sat, 27 Mar 2004 21:25:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7IMf-0002QS-7K
	for asrg@optimus.ietf.org; Sat, 27 Mar 2004 13:17:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23573
	for <asrg@ietf.org>; Sat, 27 Mar 2004 13:16:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7IMd-0007QH-00
	for asrg@ietf.org; Sat, 27 Mar 2004 13:16:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7ILd-0007KM-00
	for asrg@ietf.org; Sat, 27 Mar 2004 13:15:57 -0500
Received: from smtp1.andrew.cmu.edu ([128.2.10.81])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7IKn-0007EI-00
	for asrg@ietf.org; Sat, 27 Mar 2004 13:15:05 -0500
Received: from webmail.andrew.cmu.edu (WEBMAIL3.andrew.cmu.edu [128.2.10.93])
	by smtp1.andrew.cmu.edu (8.12.10/8.12.10) with SMTP id i2RIF1xt015898
	for <asrg@ietf.org>; Sat, 27 Mar 2004 13:15:01 -0500
Received: from 24.80.237.33
        (SquirrelMail authenticated user lin3@ANDREW.CMU.EDU)
        by webmail.andrew.cmu.edu with HTTP;
        Sat, 27 Mar 2004 13:15:00 -0500 (EST)
Message-ID: <61681.24.80.237.33.1080411300.squirrel@webmail.andrew.cmu.edu>
Subject: Re: [Asrg] asrg-cri - spam to mailing lists ?
From: "Christopher Lin" <lin3+finger@andrew.cmu.edu>
To: asrg@ietf.org
User-Agent: SquirrelMail/1.4.3 [CVS]
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-Priority: 3
Importance: Normal
References: <002801c40c42$f27b2cb0$9701a8c0@smart>  
    <40588953.6070503@solidmatrix.com>
In-Reply-To: <40588953.6070503@solidmatrix.com>
Content-Transfer-Encoding: 8bit
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/mail-archive/working-groups/asrg/>
Date: Sat, 27 Mar 2004 13:15:00 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=PRIORITY_NO_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit

Hello,
I am currently looking at the draft document and would like to keep it
'live'. I'm implementing a C/R javamail program and making this a standard
could help alot.

> Radu Hociung wrote:
>> Hello all,
>> I've been following the group for a while, and I can't find the answer I'm
>> looking for:
>> 1. About the challenge-response draft document: Are your intentions to
make
>> it into an RFC? Is it a possibilty that it can/will become a mainstream
standard?
>
> I am assuming you are refering to the following:
>
> http://www.ietf.org/internet-drafts/draft-irtf-asrg-cri-00.txt
>
> There has been very little feedback at all on this document, so it looks
to me that there is very little interest in this kind of stuff.
> Something only has a chance of becoming a standard if people are willing
to support it and so far no one has been.
>
>> 2. About the contents: If a spammer would add headers to his message to
make it look like a mailing list, this message would then not be
subject
>> to
>> the other provisions of the draft? Is there a separate draft/RFC to
deal
>> with the mailing list/CR combination, or do you intend to address this in
>> some way?
>
> As the draft is written now in section 4.2 lists can be exempt, but we
were planning on dealing with this in the future, IF sufficient interest
would be shown in the idea. So far no interest was shown and as a matter
of fact, the document is about to expire.
>
> Yakov
>
>
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
>
>




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



From exim@www1.ietf.org  Sat Mar 27 22:01:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13039
	for <asrg-archive@odin.ietf.org>; Sat, 27 Mar 2004 22:01:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QXw-0005ln-Jz
	for asrg-archive@odin.ietf.org; Sat, 27 Mar 2004 22:01:13 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2S31C7r022175
	for asrg-archive@odin.ietf.org; Sat, 27 Mar 2004 22:01:12 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QXw-0005la-Fz
	for asrg-web-archive@optimus.ietf.org; Sat, 27 Mar 2004 22:01:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13008
	for <asrg-web-archive@ietf.org>; Sat, 27 Mar 2004 22:01:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QXt-0006OF-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 22:01:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7QWw-0006Ha-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 22:00:10 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QVy-0006Bo-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 21:59:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QVp-0005G7-NK; Sat, 27 Mar 2004 21:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QNN-0004eA-Mc
	for asrg@optimus.ietf.org; Sat, 27 Mar 2004 21:50:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12739
	for <asrg@ietf.org>; Sat, 27 Mar 2004 21:50:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QNK-0005HR-00
	for asrg@ietf.org; Sat, 27 Mar 2004 21:50:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7QMN-0005CH-00
	for asrg@ietf.org; Sat, 27 Mar 2004 21:49:15 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QLt-00056y-00
	for asrg@ietf.org; Sat, 27 Mar 2004 21:48:45 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B7QLu-0000iE-00
	for asrg@ietf.org; Sat, 27 Mar 2004 21:48:46 -0500
Received: from [68.244.160.156] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B7QLt-0000C9-00
	for asrg@ietf.org; Sat, 27 Mar 2004 21:48:46 -0500
Message-ID: <40663D00.2030400@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 3c. Message Verification - S/MIME
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/mail-archive/working-groups/asrg/>
Date: Sat, 27 Mar 2004 21:48:32 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

After seeing some debate on the use of S/MIME for anti-spam efforts, I 
would like to offer a suggestion. If anybody wants to volunteer, it 
would be helpful is a draft is written outlining how S/MIME would 
hypothetically be used for fighting spam including addressing some of 
the concerns that were raised. We can then continue discussion around a 
concrete document.

The ASRG happens to have a closed subgroup for message verification 
which includes S/MIME. This subgroup is currently dormant but I make it 
available for those who want to start working on this document.

Yakov


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



From exim@www1.ietf.org  Sat Mar 27 22:02:50 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13090
	for <asrg-archive@odin.ietf.org>; Sat, 27 Mar 2004 22:02:50 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QZ5-0005rR-JM
	for asrg-archive@odin.ietf.org; Sat, 27 Mar 2004 22:02:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2S32NVo022523
	for asrg-archive@odin.ietf.org; Sat, 27 Mar 2004 22:02:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QZ5-0005rC-FA
	for asrg-web-archive@optimus.ietf.org; Sat, 27 Mar 2004 22:02:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13081
	for <asrg-web-archive@ietf.org>; Sat, 27 Mar 2004 22:02:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QZ2-0006XZ-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 22:02:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7QYI-0006RW-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 22:01:35 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QXl-0006K2-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 22:01:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QXm-0005dZ-Gj; Sat, 27 Mar 2004 22:01:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QW7-0005PU-7v
	for asrg@optimus.ietf.org; Sat, 27 Mar 2004 21:59:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12982
	for <asrg@ietf.org>; Sat, 27 Mar 2004 21:59:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QW4-0006CU-00
	for asrg@ietf.org; Sat, 27 Mar 2004 21:59:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7QV8-000670-00
	for asrg@ietf.org; Sat, 27 Mar 2004 21:58:18 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QUw-00061T-00
	for asrg@ietf.org; Sat, 27 Mar 2004 21:58:06 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B7QUw-0001zK-00; Sat, 27 Mar 2004 21:58:06 -0500
Received: from [68.244.160.156] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B7QUv-0000MP-00; Sat, 27 Mar 2004 21:58:06 -0500
Message-ID: <40663F32.4050401@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Christopher Lin <lin3+finger@andrew.cmu.edu>
CC: asrg@ietf.org
Subject: Re: [Asrg] asrg-cri - spam to mailing lists ?
References: <002801c40c42$f27b2cb0$9701a8c0@smart>      <40588953.6070503@solidmatrix.com> <61681.24.80.237.33.1080411300.squirrel@webmail.andrew.cmu.edu>
In-Reply-To: <61681.24.80.237.33.1080411300.squirrel@webmail.andrew.cmu.edu>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Sat, 27 Mar 2004 21:57:54 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

There hasn't been much interest in the last six months about this from 
anyone in the C/R community. We are inclined to discontinue working on 
this draft due to lack of feedback.

Yakov

Christopher Lin wrote:
> Hello,
> I am currently looking at the draft document and would like to keep it
> 'live'. I'm implementing a C/R javamail program and making this a standard
> could help alot.
> 
> 
>>Radu Hociung wrote:
>>
>>>Hello all,
>>>I've been following the group for a while, and I can't find the answer I'm
>>>looking for:
>>>1. About the challenge-response draft document: Are your intentions to
> 
> make
> 
>>>it into an RFC? Is it a possibilty that it can/will become a mainstream
> 
> standard?
> 
>>I am assuming you are refering to the following:
>>
>>http://www.ietf.org/internet-drafts/draft-irtf-asrg-cri-00.txt
>>
>>There has been very little feedback at all on this document, so it looks
> 
> to me that there is very little interest in this kind of stuff.
> 
>>Something only has a chance of becoming a standard if people are willing
> 
> to support it and so far no one has been.
> 
>>>2. About the contents: If a spammer would add headers to his message to
> 
> make it look like a mailing list, this message would then not be
> subject
> 
>>>to
>>>the other provisions of the draft? Is there a separate draft/RFC to
> 
> deal
> 
>>>with the mailing list/CR combination, or do you intend to address this in
>>>some way?
>>
>>As the draft is written now in section 4.2 lists can be exempt, but we
> 
> were planning on dealing with this in the future, IF sufficient interest
> would be shown in the idea. So far no interest was shown and as a matter
> of fact, the document is about to expire.
> 
>>Yakov
>>
>>
>>_______________________________________________
>>Asrg mailing list
>>Asrg@ietf.org
>>https://www1.ietf.org/mailman/listinfo/asrg
>>
>>
> 
> 
> 
> 
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
> 


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



From exim@www1.ietf.org  Sat Mar 27 22:02:51 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13107
	for <asrg-archive@odin.ietf.org>; Sat, 27 Mar 2004 22:02:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QZ6-0005rh-5s
	for asrg-archive@odin.ietf.org; Sat, 27 Mar 2004 22:02:24 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2S32O4P022541
	for asrg-archive@odin.ietf.org; Sat, 27 Mar 2004 22:02:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QZ6-0005rU-1x
	for asrg-web-archive@optimus.ietf.org; Sat, 27 Mar 2004 22:02:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13085
	for <asrg-web-archive@ietf.org>; Sat, 27 Mar 2004 22:02:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QZ3-0006Xh-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 22:02:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7QYJ-0006Re-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 22:01:36 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QXl-0006K3-00
	for asrg-web-archive@ietf.org; Sat, 27 Mar 2004 22:01:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QXl-0005co-Q8; Sat, 27 Mar 2004 22:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7QVz-0005LS-OF
	for asrg@optimus.ietf.org; Sat, 27 Mar 2004 21:59:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12973
	for <asrg@ietf.org>; Sat, 27 Mar 2004 21:59:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QVw-0006BP-00
	for asrg@ietf.org; Sat, 27 Mar 2004 21:59:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7QV0-00065k-00
	for asrg@ietf.org; Sat, 27 Mar 2004 21:58:11 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7QU3-00060P-00
	for asrg@ietf.org; Sat, 27 Mar 2004 21:57:11 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B7QU2-0001u0-00; Sat, 27 Mar 2004 21:57:10 -0500
Received: from [68.244.160.156] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B7QU1-0000Ls-00; Sat, 27 Mar 2004 21:57:10 -0500
Message-ID: <40663EF9.3010702@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Radu Hociung <radu.asrg@ohmi.org>
CC: "'Eric Dean'" <eric@purespeed.com>, asrg@ietf.org
Subject: Re: [Asrg] asrg-cri - spam to mailing lists ?
References: <000001c41284$5cdb8590$9701a8c0@smart>
In-Reply-To: <000001c41284$5cdb8590$9701a8c0@smart>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Sat, 27 Mar 2004 21:56:57 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

We got very little feedback on this draft. If there is a desire from the 
community to work on this, than we will gladly continue editing and 
writing the draft. Otherwise, there is no point.

Yakov

Radu Hociung wrote:
> In that case, I really think the proposed protocol should have provisions
> for the mailing-list corner case; otherwise, this corner case will become
> the path of least resistance for spam to get through. Just as an electrical
> current, spam will then follow this path - perhaps not immediately, but
> eventually, when it is one of the last opportunities left open.
> 
> 'A solution is only as strong as it's weakest link'
> 
> Radu.
> 
> PS. I had the pleasure to go through your C/R procedure, and I appreciate
> the ease of use from my end. How many mailboxes does your software protect?
> 
> 
> 
>>We are merely specifying a protocol.  The actual implementation of that
>>protocol and the actions that are taken based upon specific 
>>messages are
>>up to individuals.
>>
>>The intent was to see if this protocol provided a comprehensive set of
>>messages for CRI.
> 
> 
>>>Exactly. If the process of deleting such spam is not 
>>>automated, then the spam protection is not really protecting 
>>>anything, and in fact it makes the spam problem worse by 
>>>providing a mechanism of guaranteed delivery.
>>>
>>>Is it not the consensus that spam should be prevented from 
>>>reaching the mailbox?
>>>
>>>
>>>
>>>
>>>>If a spammer included exempt headers then the process would not be 
>>>>automated and the message would be subject to manual deletion.  The 
>>>>intent is that valid email would automatically be delivered and 
>>>>anything else would do something else.
>>>>
>>>>
>>>>
>>>>>2. About the contents: If a spammer would add headers to his
>>>>>message to make it look like a mailing list, this message 
>>>>>would then not be subject to the other provisions of the 
>>>>>draft? Is there a separate draft/RFC to deal with the mailing 
>>>>>list/CR combination, or do you intend to address this in some way?
> 
> 
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
> 


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



From exim@www1.ietf.org  Sun Mar 28 00:27:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17083
	for <asrg-archive@odin.ietf.org>; Sun, 28 Mar 2004 00:27:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7Soh-0002kn-I7
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 00:26:39 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2S5Qdmw010585
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 00:26:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7Soh-0002ke-C4
	for asrg-web-archive@optimus.ietf.org; Sun, 28 Mar 2004 00:26:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17028
	for <asrg-web-archive@ietf.org>; Sun, 28 Mar 2004 00:26:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7Soe-0005Ha-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 00:26:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7SnO-00051U-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 00:25:18 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7SmO-0004pA-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 00:24:16 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7SmB-0001oH-Ol; Sun, 28 Mar 2004 00:24:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7S0z-00063D-7g
	for asrg@optimus.ietf.org; Sat, 27 Mar 2004 23:35:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15386
	for <asrg@ietf.org>; Sat, 27 Mar 2004 23:35:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7S0w-0007kJ-00
	for asrg@ietf.org; Sat, 27 Mar 2004 23:35:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7Rzz-0007f0-00
	for asrg@ietf.org; Sat, 27 Mar 2004 23:34:16 -0500
Received: from sccrmhc13.comcast.net ([204.127.202.64])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7Rz3-0007UT-00
	for asrg@ietf.org; Sat, 27 Mar 2004 23:33:17 -0500
Received: from [192.168.0.7] (h00095b86f221.ne.client2.attbi.com[24.61.46.50])
          by comcast.net (sccrmhc13) with SMTP
          id <2004032804324701600htut2e>; Sun, 28 Mar 2004 04:32:47 +0000
Message-Id: <F6EB2391-8070-11D8-98B1-000393CAA6AA@pobox.com>
X-Habeas-Swe-6: email in exchange for a license for this Habeas
X-Habeas-Swe-3: like Habeas SWE (tm)
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
X-Habeas-Swe-8: Message (HCM) and not spam. Please report use of this
From: mathew <meta@pobox.com>
X-Habeas-Swe-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-Swe-2: brightly anticipated
In-Reply-To: <4061CD91.70106@Royer.com>
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com> <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com> <405B4591.4080808@Royer.com> <B3545D83-7A2B-11D8-B58D-000393CAA6AA@pobox.com> <405C9208.4050506@Royer.com> <1167864D-7C64-11D8-A507-00039380F1B6@pobox.com> <405FA5AE.90209@Royer.com> <96B658DE-7DB7-11D8-85F6-00039380F1B6@pobox.com> <4061CD91.70106@Royer.com>
To: asrg@ietf.org
X-Habeas-Swe-7: warrant mark warrants that this is a Habeas Compliant
Mime-Version: 1.0 (Apple Message framework v613)
X-Habeas-Swe-4: Copyright 2002 Habeas (tm) 
Content-Type: multipart/signed; micalg=sha1; boundary=Apple-Mail-2--938047582; protocol="application/pkcs7-signature"
X-Habeas-Swe-1: winter into spring
X-Habeas-Swe-9: mark in spam to <http://www.habeas.com/report/>.
X-Mailer: Apple Mail (2.613)
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/mail-archive/working-groups/asrg/>
Date: Sat, 27 Mar 2004 23:32:47 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60


--Apple-Mail-2--938047582
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed
Content-Transfer-Encoding: 7bit

On Mar 24, 2004, at 13:04, Doug Royer wrote:
>> Here are three that don't: Lotus Notes, Mozilla, and Apple Mail.
>
> I have exchanged HUNDREDS of S/MIME messages with IBM/Lotus
> developers in the last year that use Lotus notes- so perhaps you have 
> a buggy version?

I've been trying to interest development in investigating the Mozilla, 
Notes and Apple Mail interoperability problems, but not having much 
luck. I'm running the latest gold code; I don't generally touch the 
beta stuff.

> Older versions of Lotus Notes checked too many of the headers
> and got validation errors. That was fixed about two years ago.

Well, I have problems with the latest gold code releases of all three 
programs.

On Mar 24, 2004, at 14:35, Jonathan Morton wrote:
> Just for the record, my copy of Apple Mail (on Panther) correctly 
> verifies Doug's and Phillip's mails, but not mathew's.  It says that 
> mathew's mails have been modified or tampered with.  Given that 
> mathew's mail appears to have been *sent* from Apple Mail, I would 
> suggest that his problem stems from somewhere in his own setup.

Well, that's very strange. For me, Apple Mail, also running on Panther, 
doesn't verify Doug's or Phillip's mails--on either of two completely 
different machines. Maybe the e-mails really *have* been tampered with 
by some broken e-mail MTA somewhere?

I can send signed e-mail to myself at work and have Notes verify the 
signature correctly, so I have good reason to believe my mail is signed 
OK when I send it.

So again, it's pretty clear to me that this stuff just isn't reliable 
enough yet.


mathew
--Apple-Mail-2--938047582
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Disposition: attachment;
	filename=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGEDCCAskw
ggIyoAMCAQICAwtCvTANBgkqhkiG9w0BAQQFADBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhh
d3RlIENvbnN1bHRpbmcgKFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVt
YWlsIElzc3VpbmcgQ0EwHhcNMDMxMjAzMTUwOTU3WhcNMDQxMjAyMTUwOTU3WjBAMR8wHQYDVQQD
ExZUaGF3dGUgRnJlZW1haWwgTWVtYmVyMR0wGwYJKoZIhvcNAQkBFg5tZXRhQHBvYm94LmNvbTCC
ASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBANA40G+RMi0LMG++Lz6J4LpIaXkydRxJoLjz
9EPfZGLn6dPBumvzLVWDaQrOshYuyViOW+oPk62xz6HBnarbOX3VoiFVyGCjqkZz+TToHDDlya/z
D8l/WF92nvsEPFPKE6Fw/Lg13/g9zzBlxrjwW98bL6dI1tKvdokMH91++35sC0Yu5oZjuBF4ydUA
1n7pX2KgEDhRRP5b/RhQPrdpbZhO5fwzthiD0VlCG9zkloNJ8GOFxMFd2lpVpV1ISySCHYwEtA1n
zxR7Kq4oRaMvAodHj8NHRPDjE+vyALzi0mCZ+JlQAyKr+Li5YvKZNRobyYBQGLLOyt31ZAj9vfSS
g2cCAwEAAaMrMCkwGQYDVR0RBBIwEIEObWV0YUBwb2JveC5jb20wDAYDVR0TAQH/BAIwADANBgkq
hkiG9w0BAQQFAAOBgQCVJDuVViVm9t4++qdMFmiF4yfAowCy3/bauIAcxAJXvd21LnorWF+49YJk
jBZO74MDPrsYb5M9ybKMy04vxNuXXHM9TVLUWJjz5PUCcaNIj9DqGIW9eAPWj/Pvn6j5qSP8OcoK
mwwrKcurmSi+sJqajLjET0wzsuvgRFNE4pkOyDCCAz8wggKooAMCAQICAQ0wDQYJKoZIhvcNAQEF
BQAwgdExCzAJBgNVBAYTAlpBMRUwEwYDVQQIEwxXZXN0ZXJuIENhcGUxEjAQBgNVBAcTCUNhcGUg
VG93bjEaMBgGA1UEChMRVGhhd3RlIENvbnN1bHRpbmcxKDAmBgNVBAsTH0NlcnRpZmljYXRpb24g
U2VydmljZXMgRGl2aXNpb24xJDAiBgNVBAMTG1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBDQTEr
MCkGCSqGSIb3DQEJARYccGVyc29uYWwtZnJlZW1haWxAdGhhd3RlLmNvbTAeFw0wMzA3MTcwMDAw
MDBaFw0xMzA3MTYyMzU5NTlaMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3Vs
dGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWlu
ZyBDQTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAxKY8VXNV+065yplaHmjAdQRwnd/p/6Me
7L3N9VvyGna9fww6YfK/Uc4B1OVQCjDXAmNaLIkVcI7dyfArhVqqP3FWy688Cwfn8R+RNiQqE88r
1fOCdz0Dviv+uxg+B79AgAJk16emu59l0cUqVIUPSAR/p7bRPGEEQB5kGXJgt/sCAwEAAaOBlDCB
kTASBgNVHRMBAf8ECDAGAQH/AgEAMEMGA1UdHwQ8MDowOKA2oDSGMmh0dHA6Ly9jcmwudGhhd3Rl
LmNvbS9UaGF3dGVQZXJzb25hbEZyZWVtYWlsQ0EuY3JsMAsGA1UdDwQEAwIBBjApBgNVHREEIjAg
pB4wHDEaMBgGA1UEAxMRUHJpdmF0ZUxhYmVsMi0xMzgwDQYJKoZIhvcNAQEFBQADgYEASIzRUIPq
Cy7MDaNmrGcPf6+svsIXoUOWlJ1/TCG4+DYfqi2fNi/A9BxQIJNwPP2t4WFiw9k6GX6EsZkbAMUa
C4J0niVQlGLH2ydxVyWN3amcOY6MIE9lX5Xa9/eH1sYITq726jTlEBpbNU1341YheILcIRk13iSx
0x1G/11fZU8xggLnMIIC4wIBATBpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29u
c3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNz
dWluZyBDQQIDC0K9MAkGBSsOAwIaBQCgggFTMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJ
KoZIhvcNAQkFMQ8XDTA0MDMyODA0MzI0N1owIwYJKoZIhvcNAQkEMRYEFKYwkZfg6ujEdGh7u+Vp
OkEr7okmMHgGCSsGAQQBgjcQBDFrMGkwYjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBD
b25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBAgMLQr0wegYLKoZIhvcNAQkQAgsxa6BpMGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK
ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg
RnJlZW1haWwgSXNzdWluZyBDQQIDC0K9MA0GCSqGSIb3DQEBAQUABIIBAJtQ/0T2fCv7E/rbg2nS
g4uJgiDTQ8yGzPFn/rR/dB4i1P0h/gSvFKYlkY/2oTMCT2bxGcqKPOM0vq5S7TypQ0fl74OOS4+M
jYGOamc6VX1jyzP5tYT6roJq5UvSU0X54yWKYU/6UUT7HiUFgFfGySYTPNeEOBEjX6IKwc4l1rOE
YXSdnRhpYykMjwh6lehJ5j4sHMZq0B7HoG/Q+WW9y+lM+R3pFICcFYknA6jn4Sy/3e9JswG+Y9sW
4D6aCk6/BKaxIRRw77sPY4b0FmnV6aS9nTPYhxA8NtALiC3LGyKBLjOs1YayQ05BBBOz6ZMKS8iM
pjtaUjJrBkbM3IUGs3wAAAAAAAA=

--Apple-Mail-2--938047582--


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



From exim@www1.ietf.org  Sun Mar 28 00:28:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17282
	for <asrg-archive@odin.ietf.org>; Sun, 28 Mar 2004 00:28:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7SqL-00032x-2t
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 00:28:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2S5SLwI011705
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 00:28:21 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7SqK-00032h-Vc
	for asrg-web-archive@optimus.ietf.org; Sun, 28 Mar 2004 00:28:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA17239
	for <asrg-web-archive@ietf.org>; Sun, 28 Mar 2004 00:28:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7SqI-0005cO-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 00:28:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7SpM-0005Rh-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 00:27:21 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7So4-00058P-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 00:26:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7So5-0002c4-49; Sun, 28 Mar 2004 00:26:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7SiZ-0001eV-Qq
	for asrg@optimus.ietf.org; Sun, 28 Mar 2004 00:20:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA16565
	for <asrg@ietf.org>; Sun, 28 Mar 2004 00:20:16 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7SiX-0004Bx-00
	for asrg@ietf.org; Sun, 28 Mar 2004 00:20:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7Shg-000466-00
	for asrg@ietf.org; Sun, 28 Mar 2004 00:19:25 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7ShQ-00040T-00
	for asrg@ietf.org; Sun, 28 Mar 2004 00:19:08 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B7ShR-0003Tf-00
	for asrg@ietf.org; Sun, 28 Mar 2004 00:19:09 -0500
Received: from [68.244.225.155] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B7ShQ-0005iL-00
	for asrg@ietf.org; Sun, 28 Mar 2004 00:19:09 -0500
Message-ID: <4066603F.2000805@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 3b. SMTP Session Verification - Trust model
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/mail-archive/working-groups/asrg/>
Date: Sun, 28 Mar 2004 00:18:55 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

There has been talk about reputation and accreditation surrounding the 
identity discussions involving LMAP proposals. In the SMTP Verify 
subgroup there was talk of a general trust model or framework for 
exchanging reputation/accreditation information unifying the various 
schemes in use today and being proposed. In particular the following 
message outlines one proposal:

http://article.gmane.org/gmane.ietf.asrg.smtpverify/329

-------- Original Message --------
Subject: Re: Defining Trust and Reputation

To begin:

Define all the input information streams in the proposed
protocol/method. Identify what allows the *recipient* to
rely on each one -- these are the trusted introducers.
Cross-reference the list of trust introducers and inputs.
Present for discussion.

Then, we need to work on things such as the list of trusted
witnesses, the parametrized trust model starting from "trust
no one" and the parametrized risk model. We need to choose
a risk model too.


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



From exim@www1.ietf.org  Sun Mar 28 13:03:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26593
	for <asrg-archive@odin.ietf.org>; Sun, 28 Mar 2004 13:03:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7ecc-0002uN-Bd
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 13:02:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2SI2wbn011175
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 13:02:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7ecc-0002uA-5x
	for asrg-web-archive@optimus.ietf.org; Sun, 28 Mar 2004 13:02:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26590
	for <asrg-web-archive@ietf.org>; Sun, 28 Mar 2004 13:02:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7eca-0005iO-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 13:02:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7ebS-0005bS-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 13:01:47 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7eb0-0005Uo-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 13:01:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7eaj-0002lF-S2; Sun, 28 Mar 2004 13:01:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7eaP-0002gj-4E
	for asrg@optimus.ietf.org; Sun, 28 Mar 2004 13:00:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26527
	for <asrg@ietf.org>; Sun, 28 Mar 2004 13:00:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7eaN-0005St-00
	for asrg@ietf.org; Sun, 28 Mar 2004 13:00:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7eZO-0005Kj-00
	for asrg@ietf.org; Sun, 28 Mar 2004 12:59:39 -0500
Received: from ns2.ohmi.org ([216.187.106.200] helo=ohmi.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7eYR-00051t-00
	for asrg@ietf.org; Sun, 28 Mar 2004 12:58:39 -0500
Received: from smart (smart.ohmi.org [192.168.1.151])
	by ohmi.org (8.11.6/8.11.6) with ESMTP id i2SHw3X25650;
	Sun, 28 Mar 2004 12:58:03 -0500
From: "Radu Hociung" <radu.asrg@ohmi.org>
To: <spharion@directnet.com.br>, <asrg@ietf.org>
Subject: RE: [Asrg] spf
Message-ID: <005d01c414ee$37c33b10$9701a8c0@smart>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_005E_01C414C4.4EED3310"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <406544E0.5420.2D654D3@localhost>
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/mail-archive/working-groups/asrg/>
Date: Sun, 28 Mar 2004 12:58:03 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,HTML_50_60,
	HTML_FONTCOLOR_BLUE,HTML_MESSAGE autolearn=no version=2.60

This is a multi-part message in MIME format.

------=_NextPart_000_005E_01C414C4.4EED3310
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Unfortunately,
 
A spammer can just as well set this up. This system does not discriminate
based on the intention or identity of the sender.
 
Also, I think a good test to any anti-spam proposal is this: Would this be
a sustainable model if it became mainstream?
 
Your approach relies on a lot of wasted resources at the DNS cache level;
imagine what would happen to Hotmail's caching DNS servers if they would
cache two entries for every 2.5B spam messages they receive every day?
 
I didn't like the pop-ups.
I appreciate the effort, though; you may have something, but it needs more
work.
Radu.
--
Radu Hociung                                                 radu@ohmi.org
  

-----Original Message-----
From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On Behalf Of
spharion@directnet.com.br
Sent: Saturday, March 27, 2004 7:10 AM
To: asrg@ietf.org
Subject: [Asrg] spf


this is a tentative option to spf, but does not
seem to break forwarding:

http://nucleo.freeservers.com/mba/

have fun. gone, ricardo.




------=_NextPart_000_005E_01C414C4.4EED3310
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<?xml  version=3D"1.0" ?><HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<TITLE>Message</TITLE>

<META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D619245117-28032004><FONT face=3DArial color=3D#0000ff =

size=3D2>Unfortunately,</FONT></SPAN></DIV>
<DIV><SPAN class=3D619245117-28032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D619245117-28032004><FONT face=3DArial color=3D#0000ff =
size=3D2>A=20
spammer can just as well set this up. This system does not discriminate =
based on=20
the intention or identity of the sender.</FONT></SPAN></DIV>
<DIV><SPAN class=3D619245117-28032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D619245117-28032004><FONT face=3DArial color=3D#0000ff =
size=3D2>Also,=20
I think a good test to any anti-spam proposal is this: Would this be a=20
sustainable model if it became mainstream?</FONT></SPAN></DIV>
<DIV><SPAN class=3D619245117-28032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D619245117-28032004><FONT face=3DArial color=3D#0000ff =
size=3D2>Your=20
approach relies on a lot of wasted resources at the DNS cache level; =
imagine=20
what would happen to Hotmail's caching DNS servers if they would cache =
two=20
entries for every 2.5B spam messages they receive every =
day?</FONT></SPAN></DIV>
<DIV><SPAN class=3D619245117-28032004><FONT face=3DArial color=3D#0000ff =

size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D619245117-28032004><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
didn't like the pop-ups.</FONT></SPAN></DIV>
<DIV><SPAN class=3D619245117-28032004><FONT face=3DArial color=3D#0000ff =
size=3D2>I=20
appreciate the effort, though; you may have something, but it needs more =

work.</FONT></SPAN></DIV>
<DIV><SPAN class=3D619245117-28032004><FONT face=3DArial color=3D#0000ff =

size=3D2>Radu.</FONT></SPAN></DIV>
<DIV><FONT size=3D2>--<BR>Radu=20
Hociung&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;=20
radu@ohmi.org<BR>&nbsp;</FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV></DIV>
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr =
align=3Dleft><FONT=20
  face=3DTahoma size=3D2>-----Original Message-----<BR><B>From:</B>=20
  asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] <B>On Behalf Of=20
  </B>spharion@directnet.com.br<BR><B>Sent:</B> Saturday, March 27, 2004 =
7:10=20
  AM<BR><B>To:</B> asrg@ietf.org<BR><B>Subject:</B> [Asrg]=20
  spf<BR><BR></FONT></DIV>
  <DIV align=3Dleft><FONT face=3DArial><SPAN style=3D"FONT-SIZE: =
10pt">this is a=20
  tentative option to spf, but does not</SPAN></FONT></DIV>
  <DIV align=3Dleft><FONT face=3DArial><SPAN style=3D"FONT-SIZE: =
10pt">seem to break=20
  forwarding:</SPAN></FONT></DIV>
  <DIV align=3Dleft><BR></DIV>
  <DIV align=3Dleft><FONT face=3DArial><SPAN=20
  style=3D"FONT-SIZE: =
10pt">http://nucleo.freeservers.com/mba/</SPAN></FONT></DIV>
  <DIV align=3Dleft><BR></DIV>
  <DIV align=3Dleft><FONT face=3DArial><SPAN style=3D"FONT-SIZE: =
10pt">have fun. gone,=20
  ricardo.</SPAN></FONT></DIV>
  <DIV align=3Dleft><BR></DIV>
  <DIV align=3Dleft><BR></DIV>
  <DIV align=3Dleft></DIV></BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_005E_01C414C4.4EED3310--


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



From exim@www1.ietf.org  Sun Mar 28 14:37:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00366
	for <asrg-archive@odin.ietf.org>; Sun, 28 Mar 2004 14:37:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7g5T-0005PM-9z
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 14:36:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2SJapjm020780
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 14:36:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7g5S-0005P5-Vt
	for asrg-web-archive@optimus.ietf.org; Sun, 28 Mar 2004 14:36:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00356
	for <asrg-web-archive@ietf.org>; Sun, 28 Mar 2004 14:36:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7g5Q-0002uc-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 14:36:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7g4T-0002nf-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 14:35:49 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7g3q-0002hH-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 14:35:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7g3h-0005DC-Ac; Sun, 28 Mar 2004 14:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7g3R-0005CO-FN
	for asrg@optimus.ietf.org; Sun, 28 Mar 2004 14:34:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00277
	for <asrg@ietf.org>; Sun, 28 Mar 2004 14:34:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7g3O-0002f1-00
	for asrg@ietf.org; Sun, 28 Mar 2004 14:34:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7g2R-0002XN-00
	for asrg@ietf.org; Sun, 28 Mar 2004 14:33:44 -0500
Received: from inet-consulting.com ([4.23.9.166] helo=royer.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7g1V-0002Kc-00
	for asrg@ietf.org; Sun, 28 Mar 2004 14:32:50 -0500
Received: from Royer.com (doug@69-20-163-158.ida.net [69.20.163.158])
	(authenticated bits=0)
	by royer.com (8.12.2/8.12.2) with ESMTP id i2SJW2Fp024438
	(version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO);
	Sun, 28 Mar 2004 11:32:03 -0800
Message-ID: <40672831.2020707@Royer.com>
From: Doug Royer <Doug@Royer.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030624 Netscape/7.1
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mathew <meta@pobox.com>, asrg@ietf.org
Subject: Re: [Asrg] Re: 2. Uselessness of C/R
References: <2A1D4C86842EE14CA9BC80474919782E011133B5@mou1wnexm02.vcorp.ad.vrsn.com> <401850EC.3080803@solidmatrix.com> <CED41815-7960-11D8-816D-000393CAA6AA@pobox.com> <405B4591.4080808@Royer.com> <B3545D83-7A2B-11D8-B58D-000393CAA6AA@pobox.com> <405C9208.4050506@Royer.com> <1167864D-7C64-11D8-A507-00039380F1B6@pobox.com> <405FA5AE.90209@Royer.com> <96B658DE-7DB7-11D8-85F6-00039380F1B6@pobox.com> <4061CD91.70106@Royer.com> <F6EB2391-8070-11D8-98B1-000393CAA6AA@pobox.com>
In-Reply-To: <F6EB2391-8070-11D8-98B1-000393CAA6AA@pobox.com>
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=sha1; boundary="------------ms030104010801080208060203"
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/mail-archive/working-groups/asrg/>
Date: Sun, 28 Mar 2004 12:32:01 -0700
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

This is a cryptographically signed message in MIME format.

--------------ms030104010801080208060203
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit



mathew wrote:

> On Mar 24, 2004, at 13:04, Doug Royer wrote:
>
>>> Here are three that don't: Lotus Notes, Mozilla, and Apple Mail.
>>
>>
>> I have exchanged HUNDREDS of S/MIME messages with IBM/Lotus
>> developers in the last year that use Lotus notes- so perhaps you have 
>> a buggy version?
>
>
> I've been trying to interest development in investigating the Mozilla, 
> Notes and Apple Mail interoperability problems, but not having much 
> luck. I'm running the latest gold code; I don't generally touch the 
> beta stuff. 

I have sent this message to you directly AND to the list. It would be 
interesting
to see if one verifies and the other does not.

>> Older versions of Lotus Notes checked too many of the headers
>> and got validation errors. That was fixed about two years ago.
>
>
> Well, I have problems with the latest gold code releases of all three 
> programs. 

I have Bcc'd a friend at Lotus, perhaps he can send you a signed email. 
I helped
him fix their S/MIME problem a couple of years ago by sending him several
signed emails so he could test Notes when he noticed a problem  two 
years ago.

>
> On Mar 24, 2004, at 14:35, Jonathan Morton wrote:
>
>> Just for the record, my copy of Apple Mail (on Panther) correctly 
>> verifies Doug's and Phillip's mails, but not mathew's.  It says that 
>> mathew's mails have been modified or tampered with.  Given that 
>> mathew's mail appears to have been *sent* from Apple Mail, I would 
>> suggest that his problem stems from somewhere in his own setup.
>
>
> Well, that's very strange. For me, Apple Mail, also running on 
> Panther, doesn't verify Doug's or Phillip's mails--on either of two 
> completely different machines. Maybe the e-mails really *have* been 
> tampered with by some broken e-mail MTA somewhere? 

That could be, this email also being sent to you directly may tell us.  
If you can, save
the entire email that fails to a file (headers and all) and send it to 
me as an attachment. I can
use a stand alone tool to look at it and its signature and compare them 
to what was sent.

>
> I can send signed e-mail to myself at work and have Notes verify the 
> signature correctly, so I have good reason to believe my mail is 
> signed OK when I send it.
>
> So again, it's pretty clear to me that this stuff just isn't reliable 
> enough yet.

Or something is tampering and it is so reliable it is telling you that. 
Perhaps some
spam or anit-virus software is adding or changing something that breaks 
the signatures?
I have been using S/MIME signed email for years and this is the first
I have heard of any problem in years.

-- 

Doug Royer                     |   http://INET-Consulting.com
-------------------------------|-----------------------------
Doug@Royer.com                 | Office: (208)520-4044
http://Royer.com/People/Doug   | Fax:    (866)594-8574
                               | Cell:   (208)520-4044

              We Do Standards - You Need Standards



--------------ms030104010801080208060203
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINcDCC
A2IwggLLoAMCAQICEAvaCxfBP4mOqwl0erTOLjMwDQYJKoZIhvcNAQECBQAwXzELMAkGA1UE
BhMCVVMxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMTcwNQYDVQQLEy5DbGFzcyAxIFB1Ymxp
YyBQcmltYXJ5IENlcnRpZmljYXRpb24gQXV0aG9yaXR5MB4XDTk4MDUxMjAwMDAwMFoXDTA4
MDUxMjIzNTk1OVowgcwxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJp
U2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRv
cnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2ln
biBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0
ZWQwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALtaRIoEFrtV/QN6ii2UTxV4NrgNSrJv
nFS/vOh3Kp258Gi7ldkxQXB6gUu5SBNWLccI4YRCq8CikqtEXKpC8IIOAukv+8I7u77JJwpd
trA2QjO1blSIT4dKvxna+RXoD4e2HOPMxpqOf2okkuP84GW6p7F+78nbN2rISsgJBuSZAgMB
AAGjgbAwga0wDwYDVR0TBAgwBgEB/wIBADBHBgNVHSAEQDA+MDwGC2CGSAGG+EUBBwEBMC0w
KwYIKwYBBQUHAgEWH3d3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEwMQYDVR0fBCow
KDAmoCSgIoYgaHR0cDovL2NybC52ZXJpc2lnbi5jb20vcGNhMS5jcmwwCwYDVR0PBAQDAgEG
MBEGCWCGSAGG+EIBAQQEAwIBBjANBgkqhkiG9w0BAQIFAAOBgQACfZ5vRUs4oLje6VNkIbzk
TCuPHv6SQKzYCjlqoTIhLAebq1n+0mIafVU4sDdz3PQHZmNiveFTcFKH56jYUulbLarh3s+s
MVTUixnI2COo7wQrMn0sGBzIfImoLnfyRNFlCk10te7TG5JzdC6JOzUTcudAMZrTssSr51a+
i+P7FTCCBQEwggRqoAMCAQICEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEEBQAwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQwHhcNMDMwOTA1MDAw
MDAwWhcNMDQwOTE3MjM1OTU5WjCCAQsxFzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYD
VQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29t
L3JlcG9zaXRvcnkvUlBBIEluY29ycC4gYnkgUmVmLixMSUFCLkxURChjKTk4MR4wHAYDVQQL
ExVQZXJzb25hIE5vdCBWYWxpZGF0ZWQxMzAxBgNVBAsTKkRpZ2l0YWwgSUQgQ2xhc3MgMSAt
IE5ldHNjYXBlIEZ1bGwgU2VydmljZTETMBEGA1UEAxQKRG91ZyBSb3llcjEdMBsGCSqGSIb3
DQEJARYOZG91Z0Byb3llci5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDi
FrziCN+FurdNQ/2OjWQ2cPma6FA/JclI72S1HGVR4O26cGshcVxF+88JJrmaUzq+6+gtwYdb
MjxtcxhaR7EZNyxXA/f212YKUPeJ3pS78c+DHECtoI7lh+bumUBG9PjZwpoTu6bPP3wnubWg
X8BhyF+4GGUd0bivtJ3qUtc3HeN2WQYgeThrGkfiPr4iRMkb1WEQOyH5Mh6RH6LxZeDPu3gE
1LEFltsW4nzIbvJKQpsBRTMTa3ydV9xt/IPb3IGXwYVp+3U+/NXszPq1OWPZkPeBSwKnZb91
OpY1Ojc+WYxyQnIeVe25KwRvd6SEzEZeQUl/+UQMiDyaIYxJNIb9AgMBAAGjggEcMIIBGDAJ
BgNVHRMEAjAAMIGsBgNVHSAEgaQwgaEwgZ4GC2CGSAGG+EUBBwEBMIGOMCgGCCsGAQUFBwIB
FhxodHRwczovL3d3dy52ZXJpc2lnbi5jb20vQ1BTMGIGCCsGAQUFBwICMFYwFRYOVmVyaVNp
Z24sIEluYy4wAwIBARo9VmVyaVNpZ24ncyBDUFMgaW5jb3JwLiBieSByZWZlcmVuY2UgbGlh
Yi4gbHRkLiAoYyk5NyBWZXJpU2lnbjARBglghkgBhvhCAQEEBAMCB4AwFAYKYIZIAYb4RQEG
BwQGFgROb25lMDMGA1UdHwQsMCowKKAmoCSGImh0dHA6Ly9jcmwudmVyaXNpZ24uY29tL2Ns
YXNzMS5jcmwwDQYJKoZIhvcNAQEEBQADgYEAg54AMDj1T1zZRJE0VFN59HFABYyC0jOHaXE4
X11kw5EsaYc4pWpQ9oAvIDxxYO+chYmzuDQ4P6ZClUUFOKw/XhMriZeGgcjL4oewSkMwzpqz
ZjnXXLc/Z/nudGdYcrB/ziy9Ea5I4ba4JZUpJbOBtAkaPeMEDZO2Kx52oEDnNKIwggUBMIIE
aqADAgECAhAx/45t+4N8u/W/18pTNBTCMA0GCSqGSIb3DQEBBAUAMIHMMRcwFQYDVQQKEw5W
ZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1c3QgTmV0d29yazFGMEQGA1UE
CxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1JQQSBJbmNvcnAuIEJ5IFJlZi4sTElB
Qi5MVEQoYyk5ODFIMEYGA1UEAxM/VmVyaVNpZ24gQ2xhc3MgMSBDQSBJbmRpdmlkdWFsIFN1
YnNjcmliZXItUGVyc29uYSBOb3QgVmFsaWRhdGVkMB4XDTAzMDkwNTAwMDAwMFoXDTA0MDkx
NzIzNTk1OVowggELMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNp
Z24gVHJ1c3QgTmV0d29yazFGMEQGA1UECxM9d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
L1JQQSBJbmNvcnAuIGJ5IFJlZi4sTElBQi5MVEQoYyk5ODEeMBwGA1UECxMVUGVyc29uYSBO
b3QgVmFsaWRhdGVkMTMwMQYDVQQLEypEaWdpdGFsIElEIENsYXNzIDEgLSBOZXRzY2FwZSBG
dWxsIFNlcnZpY2UxEzARBgNVBAMUCkRvdWcgUm95ZXIxHTAbBgkqhkiG9w0BCQEWDmRvdWdA
cm95ZXIuY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA4ha84gjfhbq3TUP9
jo1kNnD5muhQPyXJSO9ktRxlUeDtunBrIXFcRfvPCSa5mlM6vuvoLcGHWzI8bXMYWkexGTcs
VwP39tdmClD3id6Uu/HPgxxAraCO5Yfm7plARvT42cKaE7umzz98J7m1oF/AYchfuBhlHdG4
r7Sd6lLXNx3jdlkGIHk4axpH4j6+IkTJG9VhEDsh+TIekR+i8WXgz7t4BNSxBZbbFuJ8yG7y
SkKbAUUzE2t8nVfcbfyD29yBl8GFaft1PvzV7Mz6tTlj2ZD3gUsCp2W/dTqWNTo3PlmMckJy
HlXtuSsEb3ekhMxGXkFJf/lEDIg8miGMSTSG/QIDAQABo4IBHDCCARgwCQYDVR0TBAIwADCB
rAYDVR0gBIGkMIGhMIGeBgtghkgBhvhFAQcBATCBjjAoBggrBgEFBQcCARYcaHR0cHM6Ly93
d3cudmVyaXNpZ24uY29tL0NQUzBiBggrBgEFBQcCAjBWMBUWDlZlcmlTaWduLCBJbmMuMAMC
AQEaPVZlcmlTaWduJ3MgQ1BTIGluY29ycC4gYnkgcmVmZXJlbmNlIGxpYWIuIGx0ZC4gKGMp
OTcgVmVyaVNpZ24wEQYJYIZIAYb4QgEBBAQDAgeAMBQGCmCGSAGG+EUBBgcEBhYETm9uZTAz
BgNVHR8ELDAqMCigJqAkhiJodHRwOi8vY3JsLnZlcmlzaWduLmNvbS9jbGFzczEuY3JsMA0G
CSqGSIb3DQEBBAUAA4GBAIOeADA49U9c2USRNFRTefRxQAWMgtIzh2lxOF9dZMORLGmHOKVq
UPaALyA8cWDvnIWJs7g0OD+mQpVFBTisP14TK4mXhoHIy+KHsEpDMM6as2Y511y3P2f57nRn
WHKwf84svRGuSOG2uCWVKSWzgbQJGj3jBA2TtisedqBA5zSiMYIEqjCCBKYCAQEwgeEwgcwx
FzAVBgNVBAoTDlZlcmlTaWduLCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3
b3JrMUYwRAYDVQQLEz13d3cudmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4g
QnkgUmVmLixMSUFCLkxURChjKTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIElu
ZGl2aWR1YWwgU3Vic2NyaWJlci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/X
ylM0FMIwCQYFKw4DAhoFAKCCAp0wGAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG
9w0BCQUxDxcNMDQwMzI4MTkzMjAxWjAjBgkqhkiG9w0BCQQxFgQU6YF5c7K40RFkpIPFMD9V
0jjUYQYwUgYJKoZIhvcNAQkPMUUwQzAKBggqhkiG9w0DBzAOBggqhkiG9w0DAgICAIAwDQYI
KoZIhvcNAwICAUAwBwYFKw4DAgcwDQYIKoZIhvcNAwICASgwgfIGCSsGAQQBgjcQBDGB5DCB
4TCBzDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0
IE5ldHdvcmsxRjBEBgNVBAsTPXd3dy52ZXJpc2lnbi5jb20vcmVwb3NpdG9yeS9SUEEgSW5j
b3JwLiBCeSBSZWYuLExJQUIuTFREKGMpOTgxSDBGBgNVBAMTP1ZlcmlTaWduIENsYXNzIDEg
Q0EgSW5kaXZpZHVhbCBTdWJzY3JpYmVyLVBlcnNvbmEgTm90IFZhbGlkYXRlZAIQMf+ObfuD
fLv1v9fKUzQUwjCB9AYLKoZIhvcNAQkQAgsxgeSggeEwgcwxFzAVBgNVBAoTDlZlcmlTaWdu
LCBJbmMuMR8wHQYDVQQLExZWZXJpU2lnbiBUcnVzdCBOZXR3b3JrMUYwRAYDVQQLEz13d3cu
dmVyaXNpZ24uY29tL3JlcG9zaXRvcnkvUlBBIEluY29ycC4gQnkgUmVmLixMSUFCLkxURChj
KTk4MUgwRgYDVQQDEz9WZXJpU2lnbiBDbGFzcyAxIENBIEluZGl2aWR1YWwgU3Vic2NyaWJl
ci1QZXJzb25hIE5vdCBWYWxpZGF0ZWQCEDH/jm37g3y79b/XylM0FMIwDQYJKoZIhvcNAQEB
BQAEggEAAM7OfNe/D9BC9mGuxnJvWmQ//owBmgjWEzP4Ibr6zbUaLajEPqgVg2aJod8R8fgG
q7eWnxjaTKON2nR4IBCezFAoUzOo/FCcWsXnvhURe6X/CIVvoFVTznxN5LMtTTCcADYLrV/0
F7HoNqj/c+03fPjLrhkCJGFMgCNT85Uz7Tf1CioN3ogG9ueworYTpwEE+GaL2/JZIGdOvbQM
7jA17Ui/0wJiYMVYV8WfnzYEVE/Ph91tJ9HOjBoAE/+4/5ci/X0t4UJjgJmr5gHdhXPiuFWj
eoWC5big/WqTqI9ByL2T5kTfuhiIEkLipzeq5sW42PnXvQVyUCzLjW6F86yQtgAAAAAAAA==
--------------ms030104010801080208060203--


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



From exim@www1.ietf.org  Sun Mar 28 15:51:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04181
	for <asrg-archive@odin.ietf.org>; Sun, 28 Mar 2004 15:51:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hFB-0005QI-On
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 15:50:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2SKovkS020842
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 15:50:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hFB-0005Q5-Iu
	for asrg-web-archive@optimus.ietf.org; Sun, 28 Mar 2004 15:50:57 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04171
	for <asrg-web-archive@ietf.org>; Sun, 28 Mar 2004 15:50:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hFA-0004gv-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 15:50:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7hEE-0004ZY-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 15:49:59 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hDU-0004S8-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 15:49:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hDJ-0005CI-C1; Sun, 28 Mar 2004 15:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hDB-0005Bh-Df
	for asrg@optimus.ietf.org; Sun, 28 Mar 2004 15:48:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04087
	for <asrg@ietf.org>; Sun, 28 Mar 2004 15:48:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hD9-0004Pu-00
	for asrg@ietf.org; Sun, 28 Mar 2004 15:48:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7hCI-0004Iu-00
	for asrg@ietf.org; Sun, 28 Mar 2004 15:47:58 -0500
Received: from [200.218.224.15] (helo=smtp.cam.directnet.com.br)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hC0-0004Bc-00
	for asrg@ietf.org; Sun, 28 Mar 2004 15:47:40 -0500
Received: from aptiva.directnet.com.br (unknown [10.24.47.99])
	by smtp.cam.directnet.com.br (Postfix) with SMTP
	id 7CDA3C0E5; Sun, 28 Mar 2004 18:44:07 -0300 (BRT)
Message-ID: <007a01c41506$6b6fe9a0$632f180a@directnet.com.br>
From: "Ricardo Dirani" <spharion@directnet.com.br>
To: "Yakov Shafranovich" <research@solidmatrix.com>,
        "Radu Hociung" <radu.asrg@ohmi.org>
Cc: <asrg@ietf.org>
References: <005d01c414ee$37c33b10$9701a8c0@smart> <406728E8.70405@solidmatrix.com>
Subject: message-body-authenticator (was: Re: [Asrg] spf)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
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/mail-archive/working-groups/asrg/>
Date: Sun, 28 Mar 2004 17:51:17 -0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

MBA doesn't fit in MXCOMP. "A mechanism to identify authorized senders for a
domain". Both LMAP and SPF do that. MBA doesn't. MBA identifies if a message
was actually sent by a domain. If MBA works as intended, spammers won't use
it, because by using it, their domains would be promptly recognized and
easily blocked by most mail hosting providers. Assuming MBA is widely
adopted, a picky receiving MTA could choose to only accept mba-authenticated
mails.

Ricardo

----- Original Message -----
From: Yakov Shafranovich <research@solidmatrix.com>
To: Radu Hociung <radu.asrg@ohmi.org>
Cc: <spharion@directnet.com.br>; <asrg@ietf.org>
Sent: Sunday, March 28, 2004 4:35 PM
Subject: Re: [Asrg] spf


> LMAP-related discussions for SPF and other proposals have moved to the
> MXCOMP list (http://www.imc.org/ietf-mxcomp/).
>
> Yakov
>
> Radu Hociung wrote:
> >
> > Unfortunately,
> >
> > A spammer can just as well set this up. This system does not
> > discriminate based on the intention or identity of the sender.
> >
> > Also, I think a good test to any anti-spam proposal is this: Would this
> > be a sustainable model if it became mainstream?
> >
> > Your approach relies on a lot of wasted resources at the DNS cache
> > level; imagine what would happen to Hotmail's caching DNS servers if
> > they would cache two entries for every 2.5B spam messages they receive
> > every day?
> >
> > I didn't like the pop-ups.
> > I appreciate the effort, though; you may have something, but it needs
> > more work.
> > Radu.
> > --
> > Radu Hociung
radu@ohmi.org
> >
> >
> >     -----Original Message-----
> >     *From:* asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] *On Behalf
> >     Of *spharion@directnet.com.br
> >     *Sent:* Saturday, March 27, 2004 7:10 AM
> >     *To:* asrg@ietf.org
> >     *Subject:* [Asrg] spf
> >
> >     this is a tentative option to spf, but does not
> >     seem to break forwarding:
> >
> >     http://nucleo.freeservers.com/mba/
> >
> >     have fun. gone, ricardo.
> >
> >
>
>


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



From exim@www1.ietf.org  Sun Mar 28 16:01:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04539
	for <asrg-archive@odin.ietf.org>; Sun, 28 Mar 2004 16:01:31 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hOx-0006OP-Tl
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 16:01:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2SL137j024568
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 16:01:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hOx-0006OB-Pf
	for asrg-web-archive@optimus.ietf.org; Sun, 28 Mar 2004 16:01:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04502
	for <asrg-web-archive@ietf.org>; Sun, 28 Mar 2004 16:01:00 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hOw-0005zf-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 16:01:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7hNu-0005rK-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 15:59:59 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hN3-0005k4-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 15:59:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hMz-00061R-Ak; Sun, 28 Mar 2004 15:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7g6P-0005ay-8B
	for asrg@optimus.ietf.org; Sun, 28 Mar 2004 14:37:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00392
	for <asrg@ietf.org>; Sun, 28 Mar 2004 14:37:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7g6M-00031d-00
	for asrg@ietf.org; Sun, 28 Mar 2004 14:37:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7g5Q-0002uh-00
	for asrg@ietf.org; Sun, 28 Mar 2004 14:36:49 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7g4T-0002nk-00
	for asrg@ietf.org; Sun, 28 Mar 2004 14:35:49 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B7g4O-00037A-00; Sun, 28 Mar 2004 14:35:44 -0500
Received: from [68.244.211.62] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B7g4M-0000mF-00; Sun, 28 Mar 2004 14:35:44 -0500
Message-ID: <406728E8.70405@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Radu Hociung <radu.asrg@ohmi.org>
CC: spharion@directnet.com.br, asrg@ietf.org
Subject: Re: [Asrg] spf
References: <005d01c414ee$37c33b10$9701a8c0@smart>
In-Reply-To: <005d01c414ee$37c33b10$9701a8c0@smart>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Sun, 28 Mar 2004 14:35:04 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

LMAP-related discussions for SPF and other proposals have moved to the 
MXCOMP list (http://www.imc.org/ietf-mxcomp/).

Yakov

Radu Hociung wrote:
> 
> Unfortunately,
>  
> A spammer can just as well set this up. This system does not 
> discriminate based on the intention or identity of the sender.
>  
> Also, I think a good test to any anti-spam proposal is this: Would this 
> be a sustainable model if it became mainstream?
>  
> Your approach relies on a lot of wasted resources at the DNS cache 
> level; imagine what would happen to Hotmail's caching DNS servers if 
> they would cache two entries for every 2.5B spam messages they receive 
> every day?
>  
> I didn't like the pop-ups.
> I appreciate the effort, though; you may have something, but it needs 
> more work.
> Radu.
> --
> Radu Hociung                                                 radu@ohmi.org
>  
> 
>     -----Original Message-----
>     *From:* asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] *On Behalf
>     Of *spharion@directnet.com.br
>     *Sent:* Saturday, March 27, 2004 7:10 AM
>     *To:* asrg@ietf.org
>     *Subject:* [Asrg] spf
> 
>     this is a tentative option to spf, but does not
>     seem to break forwarding:
> 
>     http://nucleo.freeservers.com/mba/
> 
>     have fun. gone, ricardo.
> 
> 


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



From exim@www1.ietf.org  Sun Mar 28 16:10:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05166
	for <asrg-archive@odin.ietf.org>; Sun, 28 Mar 2004 16:10:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hXm-0008PW-B6
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 16:10:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2SLAAeF032324
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 16:10:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hXm-0008PH-4s
	for asrg-web-archive@optimus.ietf.org; Sun, 28 Mar 2004 16:10:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05158
	for <asrg-web-archive@ietf.org>; Sun, 28 Mar 2004 16:10:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hXk-0007Wu-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 16:10:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7hWj-0007Ih-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 16:09:05 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hVk-00073M-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 16:08:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hVh-0007Qo-5t; Sun, 28 Mar 2004 16:08:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hSb-0006gc-7T
	for asrg@optimus.ietf.org; Sun, 28 Mar 2004 16:04:49 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04745
	for <asrg@ietf.org>; Sun, 28 Mar 2004 16:04:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hSZ-0006Yg-00
	for asrg@ietf.org; Sun, 28 Mar 2004 16:04:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7hRc-0006Q7-00
	for asrg@ietf.org; Sun, 28 Mar 2004 16:03:49 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hQh-0006I0-00
	for asrg@ietf.org; Sun, 28 Mar 2004 16:02:51 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B7hQg-0007hD-00; Sun, 28 Mar 2004 16:02:50 -0500
Received: from [68.244.211.62] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B7hQf-00037s-00; Sun, 28 Mar 2004 16:02:50 -0500
Message-ID: <40673D68.90007@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Ricardo Dirani <spharion@directnet.com.br>
CC: Radu Hociung <radu.asrg@ohmi.org>, asrg@ietf.org
References: <005d01c414ee$37c33b10$9701a8c0@smart> <406728E8.70405@solidmatrix.com> <007a01c41506$6b6fe9a0$632f180a@directnet.com.br>
In-Reply-To: <007a01c41506$6b6fe9a0$632f180a@directnet.com.br>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: message-body-authenticator
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/mail-archive/working-groups/asrg/>
Date: Sun, 28 Mar 2004 16:02:32 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Why is this better than DomainKeys which authenticates the message body 
against a public key in DNS? In this scheme, a separate MD5 would have 
to be stored in DNS for every message, with DomainKeys it is enough to 
store the public key.

Yakov

Ricardo Dirani wrote:
> MBA doesn't fit in MXCOMP. "A mechanism to identify authorized senders for a
> domain". Both LMAP and SPF do that. MBA doesn't. MBA identifies if a message
> was actually sent by a domain. If MBA works as intended, spammers won't use
> it, because by using it, their domains would be promptly recognized and
> easily blocked by most mail hosting providers. Assuming MBA is widely
> adopted, a picky receiving MTA could choose to only accept mba-authenticated
> mails.
> 
> Ricardo
> 
> ----- Original Message -----
> From: Yakov Shafranovich <research@solidmatrix.com>
> To: Radu Hociung <radu.asrg@ohmi.org>
> Cc: <spharion@directnet.com.br>; <asrg@ietf.org>
> Sent: Sunday, March 28, 2004 4:35 PM
> Subject: Re: [Asrg] spf
> 
> 
> 
>>LMAP-related discussions for SPF and other proposals have moved to the
>>MXCOMP list (http://www.imc.org/ietf-mxcomp/).
>>
>>Yakov
>>
>>Radu Hociung wrote:
>>
>>>Unfortunately,
>>>
>>>A spammer can just as well set this up. This system does not
>>>discriminate based on the intention or identity of the sender.
>>>
>>>Also, I think a good test to any anti-spam proposal is this: Would this
>>>be a sustainable model if it became mainstream?
>>>
>>>Your approach relies on a lot of wasted resources at the DNS cache
>>>level; imagine what would happen to Hotmail's caching DNS servers if
>>>they would cache two entries for every 2.5B spam messages they receive
>>>every day?
>>>
>>>I didn't like the pop-ups.
>>>I appreciate the effort, though; you may have something, but it needs
>>>more work.
>>>Radu.
>>>--
>>>Radu Hociung
> 
> radu@ohmi.org
> 
>>>
>>>    -----Original Message-----
>>>    *From:* asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] *On Behalf
>>>    Of *spharion@directnet.com.br
>>>    *Sent:* Saturday, March 27, 2004 7:10 AM
>>>    *To:* asrg@ietf.org
>>>    *Subject:* [Asrg] spf
>>>
>>>    this is a tentative option to spf, but does not
>>>    seem to break forwarding:
>>>
>>>    http://nucleo.freeservers.com/mba/
>>>
>>>    have fun. gone, ricardo.
>>>
>>>
>>
>>
> 
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
> 


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



From exim@www1.ietf.org  Sun Mar 28 16:34:37 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA06041
	for <asrg-archive@odin.ietf.org>; Sun, 28 Mar 2004 16:34:37 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7huz-0001jI-SJ
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 16:34:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2SLY9LL006644
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 16:34:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7huz-0001j5-Nh
	for asrg-web-archive@optimus.ietf.org; Sun, 28 Mar 2004 16:34:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05936
	for <asrg-web-archive@ietf.org>; Sun, 28 Mar 2004 16:34:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hux-0002bP-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 16:34:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7htp-0002KH-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 16:32:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hsr-0002DR-04
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 16:31:57 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hqz-0001Po-Fj; Sun, 28 Mar 2004 16:30:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7hqo-0001Oq-G4
	for asrg@optimus.ietf.org; Sun, 28 Mar 2004 16:29:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05790
	for <asrg@ietf.org>; Sun, 28 Mar 2004 16:29:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hqm-00021h-00
	for asrg@ietf.org; Sun, 28 Mar 2004 16:29:48 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7hpw-0001vq-00
	for asrg@ietf.org; Sun, 28 Mar 2004 16:28:56 -0500
Received: from sokol.elan.net ([216.151.192.200])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7hpH-0001p8-00
	for asrg@ietf.org; Sun, 28 Mar 2004 16:28:15 -0500
Received: from sokol.elan.net (localhost.localdomain [127.0.0.1])
	by sokol.elan.net (8.12.5/8.12.5) with ESMTP id i2SMaidw015223;
	Sun, 28 Mar 2004 14:36:44 -0800
Received: from localhost (william@localhost)
	by sokol.elan.net (8.12.5/8.12.5/Submit) with ESMTP id i2SMahnk015219;
	Sun, 28 Mar 2004 14:36:43 -0800
X-Authentication-Warning: sokol.elan.net: william owned process doing -bs
From: "william(at)elan.net" <william@elan.net>
To: Yakov Shafranovich <research@solidmatrix.com>
cc: Radu Hociung <radu.asrg@ohmi.org>, <spharion@directnet.com.br>,
        <asrg@ietf.org>
Subject: Re: [Asrg] spf
In-Reply-To: <406728E8.70405@solidmatrix.com>
Message-ID: <Pine.LNX.4.44.0403281413500.8875-100000@sokol.elan.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
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/mail-archive/working-groups/asrg/>
Date: Sun, 28 Mar 2004 14:36:43 -0800 (PST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


> >     http://nucleo.freeservers.com/mba/

This is actually not LMAP, what is proposed there is simplistic type of 
message tracking. But the way its describes has 0 chance of being workable 
in the real life when millions of emails are exchanged. DNS is simply not 
capable of being used for such purposes.

Where as tracking has number of positive implications and provides for 
pretty good way to verify that some particular message did indeed come 
through such and such mail server, it does have its drawbacks in necessity
for servers to maintain this information (which all of the MTAs already do 
in the logs in reality) and provide public access to it in real-time on 
the net (which itself does break existing mail system since its peer-peer 
and there is no guarantee that recepient mail server is on the same 
network as sender and that they could contact each other in real-time) 
and such system could also be exploited for possible DoS attacks (although
that is true about standard email or dns or many other protocols and is 
something that can be dealt with with carefull engineering of protocol 
and implementation programs). But in any case message tracking would need 
to be its own protocol or built in as part of MTA callback verification 
and not in any way done with dns which is not scalable for such system.

Another way to do message tracking that does not require separate running 
service to confirm the message data is to do use cryptography. Several 
possibilities exist there from signing original message from the sender
end (PGP, S/MIME) to adding some type of cryptographically verifiable 
tracking information by MTAs, such as signing received header data or 
having MTAs compute some has for the message and sign that (this is 
what Yahoo has proposed with DomainKeys - I'd love to see the details as 
this really looks like a good proposal which does not break existing 
infrastructure).

On Sun, 28 Mar 2004, Yakov Shafranovich wrote:

> LMAP-related discussions for SPF and other proposals have moved to the 
> MXCOMP list (http://www.imc.org/ietf-mxcomp/).
> 
> Yakov
> 
> Radu Hociung wrote:
> > 
> > Unfortunately,
> >  
> > A spammer can just as well set this up. This system does not 
> > discriminate based on the intention or identity of the sender.
> >  
> > Also, I think a good test to any anti-spam proposal is this: Would this 
> > be a sustainable model if it became mainstream?
> >  
> > Your approach relies on a lot of wasted resources at the DNS cache 
> > level; imagine what would happen to Hotmail's caching DNS servers if 
> > they would cache two entries for every 2.5B spam messages they receive 
> > every day?
> >  
> > I didn't like the pop-ups.
> > I appreciate the effort, though; you may have something, but it needs 
> > more work.
> > Radu.
> > --
> > Radu Hociung                                                 radu@ohmi.org
> >  
> > 
> >     -----Original Message-----
> >     *From:* asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] *On Behalf
> >     Of *spharion@directnet.com.br
> >     *Sent:* Saturday, March 27, 2004 7:10 AM
> >     *To:* asrg@ietf.org
> >     *Subject:* [Asrg] spf
> > 
> >     this is a tentative option to spf, but does not
> >     seem to break forwarding:
> > 
> >     http://nucleo.freeservers.com/mba/
> > 
> >     have fun. gone, ricardo.
> > 
> > 
> 
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg


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



From exim@www1.ietf.org  Sun Mar 28 19:20:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13285
	for <asrg-archive@odin.ietf.org>; Sun, 28 Mar 2004 19:20:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7kVP-0006o6-RV
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 19:19:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2T0JtFD026162
	for asrg-archive@odin.ietf.org; Sun, 28 Mar 2004 19:19:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7kVP-0006nt-MZ
	for asrg-web-archive@optimus.ietf.org; Sun, 28 Mar 2004 19:19:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13224
	for <asrg-web-archive@ietf.org>; Sun, 28 Mar 2004 19:19:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7kVO-0000Jr-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 19:19:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7kUV-0000Ch-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 19:19:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7kTr-00006D-00
	for asrg-web-archive@ietf.org; Sun, 28 Mar 2004 19:18:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7kTZ-0006Xb-5z; Sun, 28 Mar 2004 19:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7kTX-0006Wg-1B
	for asrg@optimus.ietf.org; Sun, 28 Mar 2004 19:17:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13119
	for <asrg@ietf.org>; Sun, 28 Mar 2004 19:17:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7kTV-00004U-00
	for asrg@ietf.org; Sun, 28 Mar 2004 19:17:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7kSd-0007l8-00
	for asrg@ietf.org; Sun, 28 Mar 2004 19:17:04 -0500
Received: from ns2.ohmi.org ([216.187.106.200] helo=ohmi.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7kRo-0007YD-00
	for asrg@ietf.org; Sun, 28 Mar 2004 19:16:12 -0500
Received: from smart (smart.ohmi.org [192.168.1.151])
	by ohmi.org (8.11.6/8.11.6) with ESMTP id i2T0FaX04878;
	Sun, 28 Mar 2004 19:15:36 -0500
From: "Radu Hociung" <radu.asrg@ohmi.org>
To: "'Ricardo Dirani'" <spharion@directnet.com.br>,
        "'Radu Hociung'" <radu.asrg@ohmi.org>
Cc: <asrg@ietf.org>
Subject: RE: message-body-authenticator (was: Re: [Asrg] spf)
Message-ID: <008601c41522$f613a350$9701a8c0@smart>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.4510
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Importance: Normal
In-Reply-To: <007a01c41506$6b6fe9a0$632f180a@directnet.com.br>
Content-Transfer-Encoding: quoted-printable
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/mail-archive/working-groups/asrg/>
Date: Sun, 28 Mar 2004 19:15:37 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Perhaps I didn't understand something.

What I meant is that spammers can use a through-away domain or a =
temporary
subdomain (say "Mar282004.spamnet.net"), run a DNS server with enough
capacity to authenticate the day's spam-run. To block emails verified by
such a system, one would need to use some blacklisting technology =
against
Mar282004.spamnet.net or spamnet.net. But if you need a blacklist to =
enable
this message-body-authenticator technology, where's the value of the =
'mba'
technology?

There are many other real-world problems with this - roaming senders,
centralized DNS database vs. decentralized outgoing MTA's, etc.

A system that relies to any extent on the DNS system should take into
account that authoritative slave name-servers cannot perform periodic, =
but
not necessarily frequent zone-transfers. Thus, there are propagation =
delays
between the DNS servers of any domain. The DNS system was not designed =
for
publishing real-time-like information.

Radu.



> If MBA works as intended,=20
>spammers won't use
>it, because by using it, their domains would be promptly recognized and
>easily blocked by most mail hosting providers. Assuming MBA is widely
>adopted, a picky receiving MTA could choose to only accept=20
>mba-authenticated
>mails.
>
>Ricardo
>
>----- Original Message -----
>From: Yakov Shafranovich <research@solidmatrix.com>
>To: Radu Hociung <radu.asrg@ohmi.org>
>Cc: <spharion@directnet.com.br>; <asrg@ietf.org>
>Sent: Sunday, March 28, 2004 4:35 PM
>Subject: Re: [Asrg] spf
>
>
>> LMAP-related discussions for SPF and other proposals have=20
>moved to the
>> MXCOMP list (http://www.imc.org/ietf-mxcomp/).
>>
>> Yakov
>>
>> Radu Hociung wrote:
>> >
>> > Unfortunately,
>> >
>> > A spammer can just as well set this up. This system does not
>> > discriminate based on the intention or identity of the sender.
>> >
>> > Also, I think a good test to any anti-spam proposal is=20
>this: Would this
>> > be a sustainable model if it became mainstream?
>> >
>> > Your approach relies on a lot of wasted resources at the DNS cache
>> > level; imagine what would happen to Hotmail's caching DNS=20
>servers if
>> > they would cache two entries for every 2.5B spam messages=20
>they receive
>> > every day?
>> >
>> > I didn't like the pop-ups.
>> > I appreciate the effort, though; you may have something,=20
>but it needs
>> > more work.
>> > Radu.
>> > --
>> > Radu Hociung
>radu@ohmi.org
>> >
>> >
>> >     -----Original Message-----
>> >     *From:* asrg-admin@ietf.org=20
>[mailto:asrg-admin@ietf.org] *On Behalf
>> >     Of=20
>*spharion@directnet.com.br
>> >     *Sent:* Saturday, March 27, 2004 7:10 AM
>> >     *To:* asrg@ietf.org
>> >     *Subject:* [Asrg] spf
>> >
>> >     this is a tentative option to spf, but does not
>> >     seem to break forwarding:
>> >
>> >     http://nucleo.freeservers.com/mba/
>> >
>> >     have fun. gone, ricardo.
>> >
>> >
>>
>>
>
>
>


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



From exim@www1.ietf.org  Mon Mar 29 01:33:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28545
	for <asrg-archive@odin.ietf.org>; Mon, 29 Mar 2004 01:33:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7qKg-0001r9-IY
	for asrg-archive@odin.ietf.org; Mon, 29 Mar 2004 01:33:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2T6XEYT007132
	for asrg-archive@odin.ietf.org; Mon, 29 Mar 2004 01:33:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7qKg-0001qu-Ba
	for asrg-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 01:33:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28397
	for <asrg-web-archive@ietf.org>; Mon, 29 Mar 2004 01:33:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7qKd-0003aW-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 01:33:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7qJ8-0003Ba-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 01:31:39 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7qIC-00030X-0A
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 01:30:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7qDg-00013M-LX; Mon, 29 Mar 2004 01:26:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B7q8z-0000of-T5
	for asrg@optimus.ietf.org; Mon, 29 Mar 2004 01:21:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28168
	for <asrg@ietf.org>; Mon, 29 Mar 2004 01:21:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7q8w-00023b-00
	for asrg@ietf.org; Mon, 29 Mar 2004 01:21:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B7q81-0001xc-00
	for asrg@ietf.org; Mon, 29 Mar 2004 01:20:10 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B7q7S-0001rP-00
	for asrg@ietf.org; Mon, 29 Mar 2004 01:19:34 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B7q7T-0001H1-00
	for asrg@ietf.org; Mon, 29 Mar 2004 01:19:35 -0500
Received: from [68.24.217.1] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B7q7S-0001i9-00
	for asrg@ietf.org; Mon, 29 Mar 2004 01:19:35 -0500
Message-ID: <4067BFE8.5030207@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 0. General - Recent virus posting to the list
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/mail-archive/working-groups/asrg/>
Date: Mon, 29 Mar 2004 01:19:20 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Some of you have probably seen a virus slip by onto the ASRG list a few 
minutes ago (Bagle.U for interested parties). Even though the IETF does 
employ a virus scanner to scan all incoming list email, this one got 
through somehow (could be because ASRG is exempt from some list 
policies). I will drop a line to the IETF mail admin to let them know 
and I would like to apologize for any inconvience this has caused.

Sincerely,
Yakov Shafranovich
Co-chair, ASRG

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



From exim@www1.ietf.org  Mon Mar 29 12:16:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12833
	for <asrg-archive@odin.ietf.org>; Mon, 29 Mar 2004 12:16:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B80MQ-0000CR-Kj
	for asrg-archive@odin.ietf.org; Mon, 29 Mar 2004 12:15:42 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2THFgPs000766
	for asrg-archive@odin.ietf.org; Mon, 29 Mar 2004 12:15:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B80MP-0000CH-Qj
	for asrg-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 12:15:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12829
	for <asrg-web-archive@ietf.org>; Mon, 29 Mar 2004 12:15:38 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B80MO-00033d-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 12:15:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B80LN-0002wj-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 12:14:38 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B80L9-0002ph-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 12:14:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B80Jp-0008Mb-39; Mon, 29 Mar 2004 12:13:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B80JQ-0008Lm-VT
	for asrg@optimus.ietf.org; Mon, 29 Mar 2004 12:12:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12735
	for <asrg@ietf.org>; Mon, 29 Mar 2004 12:12:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B80JP-0002hi-00
	for asrg@ietf.org; Mon, 29 Mar 2004 12:12:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B80IR-0002b3-00
	for asrg@ietf.org; Mon, 29 Mar 2004 12:11:36 -0500
Received: from sj-iport-5.cisco.com ([171.68.10.87])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B80IC-0002U9-00
	for asrg@ietf.org; Mon, 29 Mar 2004 12:11:20 -0500
Received: from sj-core-4.cisco.com (171.68.223.138)
  by sj-iport-5.cisco.com with ESMTP; 29 Mar 2004 09:11:06 -0800
Received: from mbaugher-w2k07.cisco.com (sjc-vpn3-720.cisco.com [10.21.66.208])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i2THAlex001646;
	Mon, 29 Mar 2004 09:10:47 -0800 (PST)
Message-Id: <6.0.0.22.2.20040329090921.03d0a628@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
To: Barry Shein <bzs@world.std.com>
From: Mark Baugher <mbaugher@cisco.com>
Subject: Re: [Asrg] S/MIME
Cc: asrg@ietf.org
In-Reply-To: <16479.12343.923405.180@world.std.com>
References: <20040321150043.BD4DD170BB@mail.nitros9.org>
 <405DED1E.6010102@Royer.com>
 <405DF02E.6050905@solidmatrix.com>
 <405DF381.6020006@Royer.com>
 <405DF753.3020404@solidmatrix.com>
 <6.0.0.22.2.20040321150759.03dbbcc8@mira-sjc5-6.cisco.com>
 <16479.12343.923405.180@world.std.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
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/mail-archive/working-groups/asrg/>
Date: Mon, 29 Mar 2004 09:10:45 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60


At 10:28 AM 3/22/2004, Barry Shein wrote:

>On March 21, 2004 at 15:10 mbaugher@cisco.com (Mark Baugher) wrote:
>  >
>  > If we get forgery under control, then it is possible to apply reputation,
>  > accreditation, blacklisting and other techniques to manage spam.  What 
> am I
>  > missing?
>
>That the USPS (and no doubt others) haven't been able to make much of
>a dent in this in 200+ years?

ietf-mxcomp is addressing this issue.

Mark


>There's a paradox here. Authentication etc costs money, even if just
>microcents it adds up in some contexts. People want e-mail to be
>essentially free.
>
>I think we can probably find ways to prevent people from bringing fork
>lifts into the all you can eat buffet. But fraud and authentication in
>general is a huge topic which probably is best solved by someone
>figuring out a model for a "charging for authentication business",
>akin to registered or certified mail.
>
>Put another way, it's one of those problems that seems to be easy on a
>very small scale (exchange PGP keys with your friends), but becomes
>very hard as you scale it up, particularly if the first criteria is
>that it must not cost anything.
>
>           -b



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



From exim@www1.ietf.org  Mon Mar 29 14:00:12 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17835
	for <asrg-archive@odin.ietf.org>; Mon, 29 Mar 2004 14:00:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B81z6-0008CI-SK
	for asrg-archive@odin.ietf.org; Mon, 29 Mar 2004 13:59:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TIxiTC031504
	for asrg-archive@odin.ietf.org; Mon, 29 Mar 2004 13:59:44 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B81z6-0008C3-O6
	for asrg-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 13:59:44 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17813
	for <asrg-web-archive@ietf.org>; Mon, 29 Mar 2004 13:59:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B81z4-00033I-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 13:59:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B81yH-0002wC-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 13:58:54 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B81xi-0002nk-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 13:58:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B81xR-0007vW-AW; Mon, 29 Mar 2004 13:58:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B81xE-0007ue-Ur
	for asrg@optimus.ietf.org; Mon, 29 Mar 2004 13:57:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17755
	for <asrg@ietf.org>; Mon, 29 Mar 2004 13:57:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B81xC-0002mw-00
	for asrg@ietf.org; Mon, 29 Mar 2004 13:57:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B81wJ-0002f5-00
	for asrg@ietf.org; Mon, 29 Mar 2004 13:56:52 -0500
Received: from [200.218.224.15] (helo=smtp.cam.directnet.com.br)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B81vf-0002WT-00
	for asrg@ietf.org; Mon, 29 Mar 2004 13:56:12 -0500
Received: from aptiva.directnet.com.br (unknown [10.24.47.99])
	by smtp.cam.directnet.com.br (Postfix) with SMTP id D6B6FC10B
	for <asrg@ietf.org>; Mon, 29 Mar 2004 16:52:33 -0300 (BRT)
Message-ID: <011601c415c0$0374b1e0$632f180a@directnet.com.br>
From: "Ricardo Dirani" <spharion@directnet.com.br>
To: <asrg@ietf.org>
References: <005d01c414ee$37c33b10$9701a8c0@smart> <406728E8.70405@solidmatrix.com> <007a01c41506$6b6fe9a0$632f180a@directnet.com.br> <40673D68.90007@solidmatrix.com>
Subject: Re: [Asrg] Re: message-body-authenticator
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
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/mail-archive/working-groups/asrg/>
Date: Mon, 29 Mar 2004 15:59:50 -0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Everton Marques tends to avoid cryptografy in his work due to the CPU cost.
MBA moves that cost towards RAM. But after reading your mail he became a
sudden enthusiast of DomainKeys and apparently dropped MBA. His only lasting
concern about DomainKeys is wether it is patent encumbered.

Ricardo

----- Original Message -----
From: Yakov Shafranovich <research@solidmatrix.com>
To: Ricardo Dirani <spharion@directnet.com.br>
Cc: Radu Hociung <radu.asrg@ohmi.org>; <asrg@ietf.org>
Sent: Sunday, March 28, 2004 6:02 PM
Subject: [Asrg] Re: message-body-authenticator


> Why is this better than DomainKeys which authenticates the message body
> against a public key in DNS? In this scheme, a separate MD5 would have
> to be stored in DNS for every message, with DomainKeys it is enough to
> store the public key.
>
> Yakov
>
> Ricardo Dirani wrote:
> > MBA doesn't fit in MXCOMP. "A mechanism to identify authorized senders
for a
> > domain". Both LMAP and SPF do that. MBA doesn't. MBA identifies if a
message
> > was actually sent by a domain. If MBA works as intended, spammers won't
use
> > it, because by using it, their domains would be promptly recognized and
> > easily blocked by most mail hosting providers. Assuming MBA is widely
> > adopted, a picky receiving MTA could choose to only accept
mba-authenticated
> > mails.
> >
> > Ricardo
> >
> > ----- Original Message -----
> > From: Yakov Shafranovich <research@solidmatrix.com>
> > To: Radu Hociung <radu.asrg@ohmi.org>
> > Cc: <spharion@directnet.com.br>; <asrg@ietf.org>
> > Sent: Sunday, March 28, 2004 4:35 PM
> > Subject: Re: [Asrg] spf
> >
> >
> >
> >>LMAP-related discussions for SPF and other proposals have moved to the
> >>MXCOMP list (http://www.imc.org/ietf-mxcomp/).
> >>
> >>Yakov
> >>
> >>Radu Hociung wrote:
> >>
> >>>Unfortunately,
> >>>
> >>>A spammer can just as well set this up. This system does not
> >>>discriminate based on the intention or identity of the sender.
> >>>
> >>>Also, I think a good test to any anti-spam proposal is this: Would this
> >>>be a sustainable model if it became mainstream?
> >>>
> >>>Your approach relies on a lot of wasted resources at the DNS cache
> >>>level; imagine what would happen to Hotmail's caching DNS servers if
> >>>they would cache two entries for every 2.5B spam messages they receive
> >>>every day?
> >>>
> >>>I didn't like the pop-ups.
> >>>I appreciate the effort, though; you may have something, but it needs
> >>>more work.
> >>>Radu.
> >>>--
> >>>Radu Hociung
> >
> > radu@ohmi.org
> >
> >>>
> >>>    -----Original Message-----
> >>>    *From:* asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] *On Behalf
> >>>    Of *spharion@directnet.com.br
> >>>    *Sent:* Saturday, March 27, 2004 7:10 AM
> >>>    *To:* asrg@ietf.org
> >>>    *Subject:* [Asrg] spf
> >>>
> >>>    this is a tentative option to spf, but does not
> >>>    seem to break forwarding:
> >>>
> >>>    http://nucleo.freeservers.com/mba/
> >>>
> >>>    have fun. gone, ricardo.
> >>>
> >>>
> >>
> >>
> >
> >
> > _______________________________________________
> > Asrg mailing list
> > Asrg@ietf.org
> > https://www1.ietf.org/mailman/listinfo/asrg
> >
>
>
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
>


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



From exim@www1.ietf.org  Mon Mar 29 21:26:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10004
	for <asrg-archive@odin.ietf.org>; Mon, 29 Mar 2004 21:26:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B88wx-0000dg-5V
	for asrg-archive@odin.ietf.org; Mon, 29 Mar 2004 21:25:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2U2PxSh002452
	for asrg-archive@odin.ietf.org; Mon, 29 Mar 2004 21:25:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B88wx-0000dT-1G
	for asrg-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 21:25:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09998
	for <asrg-web-archive@ietf.org>; Mon, 29 Mar 2004 21:25:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B88wu-0004C7-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 21:25:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B88vz-000442-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 21:25:00 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B88vZ-0003vq-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 21:24:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B88v3-0000KT-De; Mon, 29 Mar 2004 21:24:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B88uu-0000Jc-Ae
	for asrg@optimus.ietf.org; Mon, 29 Mar 2004 21:23:52 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09934
	for <asrg@ietf.org>; Mon, 29 Mar 2004 21:23:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B88ur-0003tO-00
	for asrg@ietf.org; Mon, 29 Mar 2004 21:23:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B88ty-0003m4-00
	for asrg@ietf.org; Mon, 29 Mar 2004 21:22:54 -0500
Received: from sitemail3.everyone.net ([216.200.145.37] helo=omta14.mta.everyone.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B88tI-0003ej-00
	for asrg@ietf.org; Mon, 29 Mar 2004 21:22:12 -0500
Received: from rmta03.mta.everyone.net (bigip1-snat [216.200.145.29])
	by omta14.mta.everyone.net (Postfix) with ESMTP
	id AE1C843098; Mon, 29 Mar 2004 18:22:00 -0800 (PST)
Received: from sohonotebook (ip68-100-37-118.dc.dc.cox.net [68.100.37.118])
	by rmta03.mta.everyone.net (Postfix) with ESMTP
	id D27A782D5E; Mon, 29 Mar 2004 18:21:59 -0800 (PST)
From: "Eric Dean" <eric@purespeed.com>
To: "'Christopher Lin'" <lin3+finger@andrew.cmu.edu>, <asrg@ietf.org>
Subject: RE: [Asrg] asrg-cri - spam to mailing lists ?
Message-ID: <002d01c415fd$ce7f87b0$6701a8c0@sohonotebook>
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
Importance: Normal
In-Reply-To: <61681.24.80.237.33.1080411300.squirrel@webmail.andrew.cmu.edu>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Mon, 29 Mar 2004 21:22:09 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

It's very simple to implement...it's also nice for loop avoidance.  Just
add the headers...don't expect any back 8-)

> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On 
> Behalf Of Christopher Lin
> Sent: Saturday, March 27, 2004 1:15 PM
> To: asrg@ietf.org
> Subject: Re: [Asrg] asrg-cri - spam to mailing lists ?
> 
> 
> Hello,
> I am currently looking at the draft document and would like 
> to keep it 'live'. I'm implementing a C/R javamail program 
> and making this a standard could help alot.
> 
> > Radu Hociung wrote:
> >> Hello all,
> >> I've been following the group for a while, and I can't find the 
> >> answer I'm looking for: 1. About the challenge-response draft 
> >> document: Are your intentions to
> make
> >> it into an RFC? Is it a possibilty that it can/will become a 
> >> mainstream
> standard?
> >
> > I am assuming you are refering to the following:
> >
> > http://www.ietf.org/internet-drafts/draft-irtf-asrg-cri-00.txt
> >
> > There has been very little feedback at all on this document, so it 
> > looks
> to me that there is very little interest in this kind of stuff.
> > Something only has a chance of becoming a standard if people are 
> > willing
> to support it and so far no one has been.
> >
> >> 2. About the contents: If a spammer would add headers to 
> his message 
> >> to
> make it look like a mailing list, this message would then not 
> be subject
> >> to
> >> the other provisions of the draft? Is there a separate draft/RFC to
> deal
> >> with the mailing list/CR combination, or do you intend to address 
> >> this in some way?
> >
> > As the draft is written now in section 4.2 lists can be 
> exempt, but we
> were planning on dealing with this in the future, IF 
> sufficient interest would be shown in the idea. So far no 
> interest was shown and as a matter of fact, the document is 
> about to expire.
> >
> > Yakov
> >
> >
> > _______________________________________________
> > Asrg mailing list
> > Asrg@ietf.org
> > https://www1.ietf.org/mailman/listinfo/asrg
> >
> >
> 
> 
> 
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
> 


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



From exim@www1.ietf.org  Mon Mar 29 21:27:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10051
	for <asrg-archive@odin.ietf.org>; Mon, 29 Mar 2004 21:27:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B88xr-0000es-VN
	for asrg-archive@odin.ietf.org; Mon, 29 Mar 2004 21:26:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2U2Qtkp002526
	for asrg-archive@odin.ietf.org; Mon, 29 Mar 2004 21:26:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B88xr-0000ef-Rl
	for asrg-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 21:26:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10034
	for <asrg-web-archive@ietf.org>; Mon, 29 Mar 2004 21:26:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B88xp-0004KO-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 21:26:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B88wy-0004Cs-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 21:26:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B88w5-00044Y-00
	for asrg-web-archive@ietf.org; Mon, 29 Mar 2004 21:25:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B88w1-0000Qr-VF; Mon, 29 Mar 2004 21:25:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B88vy-0000QB-9d
	for asrg@optimus.ietf.org; Mon, 29 Mar 2004 21:24:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09961
	for <asrg@ietf.org>; Mon, 29 Mar 2004 21:24:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B88vv-00043E-00
	for asrg@ietf.org; Mon, 29 Mar 2004 21:24:55 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B88v1-0003vM-00
	for asrg@ietf.org; Mon, 29 Mar 2004 21:24:00 -0500
Received: from sitemail3.everyone.net ([216.200.145.37] helo=omta06.mta.everyone.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B88ul-0003n3-00
	for asrg@ietf.org; Mon, 29 Mar 2004 21:23:43 -0500
Received: from rmta01.mta.everyone.net (bigip1-snat [216.200.145.29])
	by omta06.mta.everyone.net (Postfix) with ESMTP
	id 6D40943F6D; Mon, 29 Mar 2004 18:23:44 -0800 (PST)
Received: from sohonotebook (ip68-100-37-118.dc.dc.cox.net [68.100.37.118])
	by rmta01.mta.everyone.net (Postfix) with ESMTP
	id 8FA316B0BC; Mon, 29 Mar 2004 18:23:43 -0800 (PST)
From: "Eric Dean" <eric@purespeed.com>
To: "'Radu Hociung'" <radu.asrg@ohmi.org>, <asrg@ietf.org>
Subject: RE: [Asrg] asrg-cri - spam to mailing lists ?
Message-ID: <002e01c415fe$0c51cb20$6701a8c0@sohonotebook>
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
Importance: Normal
In-Reply-To: <000001c41284$5cdb8590$9701a8c0@smart>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Mon, 29 Mar 2004 21:23:53 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

If someone adds some challenge suppression Exempt headers, this does not
mean that the email simply goes through.  In many cases, it's simply
quarantined.  There is no advantage to adding an exempt..if anything, it
only subjects the email to more scrutiny.

> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org] On 
> Behalf Of Radu Hociung
> Sent: Thursday, March 25, 2004 11:15 AM
> To: 'Eric Dean'; asrg@ietf.org
> Subject: RE: [Asrg] asrg-cri - spam to mailing lists ?
> 
> 
> In that case, I really think the proposed protocol should 
> have provisions for the mailing-list corner case; otherwise, 
> this corner case will become the path of least resistance for 
> spam to get through. Just as an electrical current, spam will 
> then follow this path - perhaps not immediately, but 
> eventually, when it is one of the last opportunities left open.
> 
> 'A solution is only as strong as it's weakest link'
> 
> Radu.
> 
> PS. I had the pleasure to go through your C/R procedure, and 
> I appreciate the ease of use from my end. How many mailboxes 
> does your software protect?
> 
> 
> >We are merely specifying a protocol.  The actual 
> implementation of that 
> >protocol and the actions that are taken based upon specific messages 
> >are up to individuals.
> >
> >The intent was to see if this protocol provided a 
> comprehensive set of 
> >messages for CRI.
> 
> >> Exactly. If the process of deleting such spam is not
> >> automated, then the spam protection is not really protecting 
> >> anything, and in fact it makes the spam problem worse by 
> >> providing a mechanism of guaranteed delivery.
> >> 
> >> Is it not the consensus that spam should be prevented from
> >> reaching the mailbox?
> >> 
> >> 
> >> 
> >> >If a spammer included exempt headers then the process would not be
> >> >automated and the message would be subject to manual 
> deletion.  The 
> >> >intent is that valid email would automatically be delivered and 
> >> >anything else would do something else.
> >> >
> >> > 
> >> >> 2. About the contents: If a spammer would add headers to his 
> >> >> message to make it look like a mailing list, this message would 
> >> >> then not be subject to the other provisions of the 
> draft? Is there 
> >> >> a separate draft/RFC to deal with the mailing list/CR 
> combination, 
> >> >> or do you intend to address this in some way?
> 
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
> 


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



From exim@www1.ietf.org  Tue Mar 30 17:54:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21349
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:54:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rje-0006YH-65
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:30 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HL5JMJ014548
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 16:05:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3iDs-0003le-2n
	for asrg-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 16:05:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07372
	for <asrg-web-archive@ietf.org>; Wed, 17 Mar 2004 16:04:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3iDa-0001Su-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 16:04:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3iCi-0001LZ-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 16:03:57 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3iCK-0001Ds-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 16:03:32 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3iBp-0003Zv-Ek; Wed, 17 Mar 2004 16:03:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3iBX-0003XS-7Z
	for asrg@optimus.ietf.org; Wed, 17 Mar 2004 16:02:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA07282
	for <asrg@ietf.org>; Wed, 17 Mar 2004 16:02:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3iBV-0001BP-00
	for asrg@ietf.org; Wed, 17 Mar 2004 16:02:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3iAW-00012t-00
	for asrg@ietf.org; Wed, 17 Mar 2004 16:01:41 -0500
Received: from bsdsgr04.sagres.com.br ([200.140.134.134])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3i9Y-0000pc-00
	for asrg@ietf.org; Wed, 17 Mar 2004 16:00:40 -0500
Received: from ntsgr07.sagres.com.br (NTsgr07.sagres.com.br [10.0.17.7])
	by BSDsgr04.sagres.com.br (8.12.10/8.12.10) with ESMTP id i2HL0OGq048513
	for <asrg@ietf.org>; Wed, 17 Mar 2004 21:00:24 GMT
	(envelope-from saurwein@uniwares.com)
Received: from leonone.uniwares.com ([200.101.110.127])
          by ntsgr07.sagres.com.br (Lotus Domino Release 5.0.12)
          with ESMTP id 2004031718085602:13211 ;
          Wed, 17 Mar 2004 18:08:56 -0300 
Message-Id: <6.0.3.0.0.20040317175416.01cf5ec0@mail.uniwares.com>
X-Sender: saurwein.uniwares@mail.uniwares.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
To: asrg@ietf.org
From: Andreas Saurwein <saurwein@uniwares.com>
Subject: Re: [Asrg] 1a. Inventory of Problems - new spam channels
In-Reply-To: <4058B839.3060002@solidmatrix.com>
References: <20040317195459.587BB170C4@mail.nitros9.org>
 <4058B839.3060002@solidmatrix.com>
Mime-Version: 1.0
X-MIMETrack: Itemize by SMTP Server on ntsgr07/SAGRES(Release 5.0.12  |February 13, 2003) at
 03/17/2004 06:08:56 PM,
	Serialize by Router on ntsgr07/SAGRES(Release 5.0.12  |February 13, 2003) at
 03/17/2004 06:08:57 PM,
	Serialize complete at 03/17/2004 06:08:57 PM
Content-Type: text/plain; charset="us-ascii"; format=flowed
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 18:00:01 -0300
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.8 required=5.0 tests=AWL autolearn=no version=2.60

At 17/3/2004 17:42 Wednesday, Yakov wrote:
>>Andreas Saurwein <saurwein@uniwares.com> wrote:
>>
>>>I believe it is only a matter of a few month until we see serious spam 
>>>in online games. Most games have, as far as I can see, no protection 
>>>against this type of misuse.
>"It is important that this is "For the Internet," and does not include 
>everything that happens to use IP. IP is being used in a myriad of 
>real-world applications, such as controlling street lights, but the IETF 
>does not standardize those applications."

Point taken.

>>   Online games may be viewed as private networks layered on top of the
>>Internet.  So are we interested in solving their spam problems, or
>>are they out of scope:
>
>Now if game sites were using a standard protocol to talk to each other, or 
>between players AND that protocol would be standardized on the Internet 
>level and not proprietary to each company; then it would be in scope.

So, as some games (and other applications) use already VoIP, which is a 
"standard" I'd say, it might come into the scope of the IETF/ASRG sooner or 
later.

Not that we dont have enough to do to solve the current spam problems, but 
there are new, yet unexplored and unexploited possibilities to spam which 
might benefit from what we do here.

Andreas 


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



From exim@www1.ietf.org  Tue Mar 30 17:54:49 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21509
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:54:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rjd-0006ZK-Hw
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:29 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2I80S87000410
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 03:00:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sRy-000067-U5
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 03:00:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25676
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 03:00:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sRu-0001kC-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 03:00:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3sQx-0001bu-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 02:59:19 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sQ7-0001Tg-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 02:58:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sPi-000840-Lr; Thu, 18 Mar 2004 02:58:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sLx-0007pF-RT
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 02:54:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25429
	for <asrg@ietf.org>; Thu, 18 Mar 2004 02:54:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sLu-0000rx-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:54:06 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3sKu-0000iY-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:53:05 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sJw-0000ZT-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:52:05 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B3sJu-0002Em-00; Thu, 18 Mar 2004 02:52:02 -0500
Received: from [68.244.163.173] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B3sJt-0004y2-00; Thu, 18 Mar 2004 02:52:02 -0500
Message-ID: <40595501.9040009@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: Andreas Saurwein <saurwein@uniwares.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] 1a. Inventory of Problems - new spam channels
References: <20040317195459.587BB170C4@mail.nitros9.org> <4058B839.3060002@solidmatrix.com> <6.0.3.0.0.20040317175416.01cf5ec0@mail.uniwares.com>
In-Reply-To: <6.0.3.0.0.20040317175416.01cf5ec0@mail.uniwares.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 02:51:29 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Andreas Saurwein wrote:
> At 17/3/2004 17:42 Wednesday, Yakov wrote:
>>> Andreas Saurwein <saurwein@uniwares.com> wrote:
>>>
...
>>>   Online games may be viewed as private networks layered on top of the
>>> Internet.  So are we interested in solving their spam problems, or
>>> are they out of scope:
>>
>> Now if game sites were using a standard protocol to talk to each 
>> other, or between players AND that protocol would be standardized on 
>> the Internet level and not proprietary to each company; then it would 
>> be in scope.
> 
> 
> So, as some games (and other applications) use already VoIP, which is a 
> "standard" I'd say, it might come into the scope of the IETF/ASRG sooner 
> or later.
> 

For the IETF that is the true, for the ASRG with a charter modification 
that could become true.

An interesting side point - someone on the MXCOMP list pointed out that 
he has been getting spam SIP calls.

> Not that we dont have enough to do to solve the current spam problems, 
> but there are new, yet unexplored and unexploited possibilities to spam 
> which might benefit from what we do here.

Agreed.

Yakov

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



From exim@www1.ietf.org  Tue Mar 30 17:55:39 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21655
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:55:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rjd-0006ZK-Fv
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:29 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2I80ScH000409
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 03:00:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sRy-000066-SD
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 03:00:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25673
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 03:00:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sRt-0001k7-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 03:00:18 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3sQw-0001bm-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 02:59:19 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sQ7-0001Tf-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 02:58:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sPj-00084C-Cy; Thu, 18 Mar 2004 02:58:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sNt-0007vq-Ho
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 02:56:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25524
	for <asrg@ietf.org>; Thu, 18 Mar 2004 02:56:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sNp-0001Ac-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:56:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3sMt-00011n-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:55:07 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sLy-0000sc-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:54:10 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B3sLy-0002Ub-00; Thu, 18 Mar 2004 02:54:10 -0500
Received: from [68.244.163.173] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B3sLw-0004zg-00; Thu, 18 Mar 2004 02:54:09 -0500
Message-ID: <40595594.5000608@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: Alan DeKok <aland@ox.org>, asrg@ietf.org
Subject: Re: [Asrg] 1a. Inventory of Problems - new spam channels
References: <C6DDA43B91BFDA49AA2F1E473732113E0A19FB@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A19FB@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 02:53:56 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hallam-Baker, Phillip wrote:
> 
> Regardless of what happens in MARID people will take the same principles and
> apply them. You can even recycle the same syntax and even the same RRs the
> same way MX was generalized first to SRV and then to NAPTR.

This brings to mind an interesting discussion. There has been some 
discussion at MXCOMP list, main IETF list, here and in the SMTP-VERIFY 
subgroup about trust, protocols for negotiating trust and querying third 
party reputation/accredidation providers to verify trust. This sounds 
like something that should be pursued at some point, maybe as a general 
non-email mechanism.

Yakov

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



From exim@www1.ietf.org  Tue Mar 30 17:57:10 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22068
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:57:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rjc-0006ZK-JU
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:28 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IHwZgw011241
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 12:58:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41mt-0002vE-Ev
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 12:58:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27655
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 12:58:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41mr-0007NN-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:58:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41m3-0007Kr-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:57:44 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41lO-0007HU-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:57:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41lN-0002RS-Lw; Thu, 18 Mar 2004 12:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3slK-0001gd-6J
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 03:20:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26531
	for <asrg@ietf.org>; Thu, 18 Mar 2004 03:20:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3slH-0004Le-00
	for asrg@ietf.org; Thu, 18 Mar 2004 03:20:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3skO-0004DX-00
	for asrg@ietf.org; Thu, 18 Mar 2004 03:19:24 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sjV-000451-00
	for asrg@ietf.org; Thu, 18 Mar 2004 03:18:29 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B3sjU-0005Pn-00; Thu, 18 Mar 2004 03:18:28 -0500
Received: from [68.244.163.173] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B3sjT-0005cu-00; Thu, 18 Mar 2004 03:18:28 -0500
Message-ID: <40595B43.3010009@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] Accreditation Mechanism Proposal
References: <C6DDA43B91BFDA49AA2F1E473732113E0A19E4@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E0A19E4@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 03:18:11 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hallam-Baker, Phillip wrote:
> 	A proposal for an accreditation mechanism is attached. This proposal
> is based on the earlier RBL scheme proposed by Vixie, and designed to be
> compatible with CallerID. I will submit as an ID later on today.
> 

Is the other consent proposal being submitted as well?

> 
> 	I believe that we should have some facility here for a description
> of the accreditation service. This is because the receiver has to arrive at
> an evaluation of the accreditation service before the information can
> converge. The ability to use learning systems is very attractive here.
> Telling the learning system basic information about the format of the data
> is pretty useful, what is the basis that the info was collected on, is the
> data bit field formatted or in some other form?
> 
> 	I provide the start of a description language here but on second
> thoughts the best approach here would be to write the data structure in XML,
> stick it up on a web site and put the URL in the DNS. The format is not a
> big priority for me at the moment since it only really affects the
> accreditation services and the filter writers. I don't think that either
> community will be particularly large (10 to 20 at most). It is not something
> we need to make a priority when we are using our limited standards track
> bandwidth.
>

There has been talk in at least four forums (ASRG, SMTP-VERIFY, MXCOMP 
and main IETF list) about trust, establishing trust between two parties 
and quering third party providers of information. The SMTP-VERIFY 
subgroup is also talking about exchanging information on neutral metrics 
like MTA volume via some protocol.

All of this brings question - can these ideas be somehow unified?

Yakov


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



From exim@www1.ietf.org  Tue Mar 30 17:57:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22181
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:57:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rjc-0006ZK-De
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:28 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IHwYxE011225
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 12:58:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41ms-0002us-Sq
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 12:58:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27652
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 12:58:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41mr-0007NI-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:58:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41m2-0007Kj-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:57:43 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41lO-0007HT-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:57:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41lO-0002SA-Sk; Thu, 18 Mar 2004 12:57:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41bT-00012J-3i
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 12:46:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26738
	for <asrg@ietf.org>; Thu, 18 Mar 2004 12:46:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41bR-0006Us-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:46:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41aL-0006Qv-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:45:37 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41Ze-0006Of-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:44:54 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B41Zd-0000TO-00; Thu, 18 Mar 2004 12:44:53 -0500
Received: from [68.244.172.97] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B41Zb-0001e4-00; Thu, 18 Mar 2004 12:44:52 -0500
Message-ID: <4059E008.3080803@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] Accreditation Mechanism Proposal
References: <C6DDA43B91BFDA49AA2F1E473732113E5DBA58@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E5DBA58@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 12:44:40 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>>There has been talk in at least four forums (ASRG, 
>>SMTP-VERIFY, MXCOMP 
>>and main IETF list) about trust, establishing trust between 
>>two parties 
>>and quering third party providers of information. The SMTP-VERIFY 
>>subgroup is also talking about exchanging information on 
>>neutral metrics like MTA volume via some protocol.
> 
> 
> I will check the SMTP-VERIFY archives.
> 
> I think that the scope of trust exchange in this particular domain
> needs to be limited, there are trillions of emails sent each week, 
> there is no way that every one can be backed by an essay the 
> length of war and peace describing the trustworthiness.
> 
> On the other hand we do want more than binary data, there has to 
> be a gradation here. In practice I suspect we do not need a huge
> number of levels at this point in time.
> 

Whatever it is, we need a protocol and formats that two entities can 
exchange information about trust. For example, a sending MTA can pass 
via an ESMTP extension hints about accreditation and reputation, which 
the receiver can use to establish some form of trust. Of course the same 
can be done via DNS or some other protocol.

> 
> I think it is also useful to see a description of the domain. An
> ISP or university cannot be held to the same standard as a lawyers
> office. The lawyer should have very tight control over their 
> employees. If there are persistent spam runs then there is a real
> problem that is not really explainable. An ISP on the other hand cannot
> be expected to stop all spam outright, not without controlling their
> customers in an unacceptable way.

Ok that would be useful. Thoughts on how to proceed with this?

Yakov

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



From exim@www1.ietf.org  Tue Mar 30 17:59:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22730
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:59:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rjb-0006Xa-FV
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hBJ1KDvJ020884
	for asrg-archive@odin.ietf.org; Thu, 18 Dec 2003 20:20:13 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX9JG-0005NV-IJ
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Dec 2003 20:20:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04601
	for <asrg-web-archive@ietf.org>; Thu, 18 Dec 2003 20:20:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX9JE-00068s-00
	for asrg-web-archive@ietf.org; Thu, 18 Dec 2003 20:20:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX9JC-00068a-00
	for asrg-web-archive@ietf.org; Thu, 18 Dec 2003 20:20:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX9JC-00068X-00
	for asrg-web-archive@ietf.org; Thu, 18 Dec 2003 20:20:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX9JD-0005Im-2u; Thu, 18 Dec 2003 20:20:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AX9IH-0005AR-SK
	for asrg@optimus.ietf.org; Thu, 18 Dec 2003 20:19:05 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04552
	for <asrg@ietf.org>; Thu, 18 Dec 2003 20:19:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AX9IF-00067l-00
	for asrg@ietf.org; Thu, 18 Dec 2003 20:19:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AX9ID-00067W-00
	for asrg@ietf.org; Thu, 18 Dec 2003 20:19:03 -0500
Received: from ntbbs.winserver.com ([208.247.131.9] helo=winserver.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AX9ID-00067T-00
	for asrg@ietf.org; Thu, 18 Dec 2003 20:19:01 -0500
Received: by winserver.com (Wildcat! SMTP Router v5.7.450.9b10)
          for asrg@ietf.org; Thu, 18 Dec 2003 20:19:43 -0500
Received: from  ([68.158.208.108]) EHLO=FAMILY
          by winserver.com (Wildcat! SMTP v5.7.450.9b10) with SMTP
          id 4031248734; Thu, 18 Dec 2003 20:19:42 -0500
Message-ID: <000b01c3c5ce$15b0d0b0$6401a8c0@FAMILY>
From: "Hector Santos" <winserver.support@winserver.com>
To: "Anti-Spam" <asrg@ietf.org>
References: <3FE2340B.8070605@solidmatrix.com> <3FE235A5.30509@zemos.net> <004201c3c5c0$7c137af0$6401a8c0@FAMILY> <20031218235222.GB68195@Space.Net> <005301c3c5c8$91422c70$6401a8c0@FAMILY> <20031219004720.GA73579@Space.Net>
Subject: Re: [Asrg] 0. General - For Markus
Organization: Santronics Software, Inc
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Dec 2003 20:18:59 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

First thing first, what  is nonsense is to first CORRECT your god damn
BLACKLIST and remove our ADDRESS from that RBL list!

Second,  My fault.  I understand what is a PTR and A record.   I miswrote
the wrong log item in the logger - It should say, "NO A RECORD or DNS domain
lookup failure".    It was the error reported by an DNS MX lookup.  DNS
returned the error. I can't explain why it happen that one time.  But it
seems to be working ok now for
ZEMOS.NET

No, I am not doing a PTR lookup.   I mistakenly enter the wrong info the
log.    WCSAP does offer a PTR lookup option, and that the log line was
copied over. It has been correctly for the next update.

-- Hector


----- Original Message ----- 
From: "Markus Stumpf" <maex-lists-spam-ietf-asrg@Space.Net>
To: "Anti-Spam" <asrg@ietf.org>
Sent: Thursday, December 18, 2003 7:47 PM
Subject: Re: [Asrg] 0. General - For Hector Santos


> On Thu, Dec 18, 2003 at 07:39:29PM -0500, Hector Santos wrote:
> > A domain name pointer record?
>
> And what would that be?
>
> > Lets use NT's NSLOOKUP:
> > WC5 L:\wc5>nslookup -querytype=ptr zemos.net
> > Server:  ns.santronics.com
> > Address:  208.247.131.10
> >
> > *** No domain name pointer (PTR) records available for zemos.net
>
> What you are doing here is nonsense.
> PTR records do the mapping from IP addresses to hostnames. I.e. you get
> a connection from 195.30.0.8 then you lookup the PTR record for
>     8.0.30.195.in-addr.arpa
> and you get   mail.space.net.
> A PTR record can be thought of as the reverse of an A(ddress) record.
>
> moebius2.space.net(1:4725) $ nslookup -querytype=ptr winserver.com
> Server:  ns2.Space.Net
> Address:  195.30.0.2
> *** No domain name pointer (PTR) records available for winserver.com
>
> So you expect others to have records that you don't have yourself?
>
>  \Maex
>
> -- 
> SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
> Research & Development |       D-80807 Muenchen    | Fax: +49 (89)
32356-299
> "The security, stability and reliability of a computer system is
reciprocally
>  proportional to the amount of vacuity between the ears of the admin"
>
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
>



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



From exim@www1.ietf.org  Tue Mar 30 18:00:11 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22843
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:00:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rjb-0006Xa-DG
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:27 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2I80SiA000408
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 03:00:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sRy-00005x-SA
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 03:00:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25670
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 03:00:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sRt-0001k2-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 03:00:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3sQv-0001bd-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 02:59:18 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sQ7-0001Te-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 02:58:27 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sPh-00083q-LP; Thu, 18 Mar 2004 02:58:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3sK7-0007jb-Vq
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 02:52:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25321
	for <asrg@ietf.org>; Thu, 18 Mar 2004 02:52:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sK4-0000aQ-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:52:12 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3sJ9-0000Rs-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:51:16 -0500
Received: from mout.perfora.net ([217.160.230.40])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3sIE-0000KP-00
	for asrg@ietf.org; Thu, 18 Mar 2004 02:50:18 -0500
Received: from [217.160.230.50] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B3sI6-0001wx-00; Thu, 18 Mar 2004 02:50:10 -0500
Received: from [68.244.163.173] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B3sI5-0004ve-00; Thu, 18 Mar 2004 02:50:10 -0500
Message-ID: <405954A5.1010007@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
CC: asrg@ietf.org
Subject: Re: [Asrg] Update on Querying IADB
References: <3DC625B6-77F8-11D8-AD47-000A95AC5778@isipp.com>
In-Reply-To: <3DC625B6-77F8-11D8-AD47-000A95AC5778@isipp.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 02:49:57 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Anne P. Mitchell, Esq. wrote:
> For those interested in seeing how this has evolved, and what exactly 
> this particular accreditation database provides, our query pages have 
> been expanded, and include a link to the full suggested DNSL data 
> response codes.
> 

All of these codes bring to mind an interesting question. The current 
systems of this kind, both blacklist and whitelist, do not have a 
standard set of codes outside the 127.0.0.1 - present. Wouldn't a 
standard set help? Or perhaps a whole new trust protocol for negotiating 
trust among two entities and quering third parties?

Yakov

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



From exim@www1.ietf.org  Tue Mar 30 18:03:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23861
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:03:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjZ-0006ZK-Sa
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:25 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1KbtGZ001321
	for asrg-archive@odin.ietf.org; Mon, 1 Dec 2003 15:37:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQunp-0000L5-Qa
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 15:37:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28052
	for <asrg-web-archive@ietf.org>; Mon, 1 Dec 2003 15:37:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQuno-00007Z-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 15:37:52 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQunn-00007V-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 15:37:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQun0-0008S1-NE; Mon, 01 Dec 2003 15:37:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQumx-0008RW-IX
	for asrg@optimus.ietf.org; Mon, 01 Dec 2003 15:36:59 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28022
	for <asrg@ietf.org>; Mon, 1 Dec 2003 15:36:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQumw-00006X-00
	for asrg@ietf.org; Mon, 01 Dec 2003 15:36:58 -0500
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQumv-00006R-00
	for asrg@ietf.org; Mon, 01 Dec 2003 15:36:57 -0500
X-Sasl-enc: ZTmM1iRP2KAcC00VrGiGOQ 1070311014
Received: from elvey.com (adsl-63-195-86-147.dsl.snfc21.pacbell.net [63.195.86.147])
	by mail.messagingengine.com (Postfix) with ESMTP id 6FA86455B2C;
	Mon,  1 Dec 2003 15:36:52 -0500 (EST)
Message-ID: <3FCBA663.3060808@elvey.com>
From: Matthew Elvey <matthew@elvey.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>, ASRG <asrg@ietf.org>,
        "Eric S. Raymond" <esr@thyrsus.com>
Subject: Re: [Asrg] 6. Proposals - Legal - Subject labeling
References: <2A1D4C86842EE14CA9BC80474919782E024253B7@mou1wnexm02.vcorp.ad.vrsn.com>
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E024253B7@mou1wnexm02.vcorp.ad.vrsn.com>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Mon, 01 Dec 2003 12:36:51 -0800
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On 12/1/2003 11:04 AM, Eric S. Raymond sent forth electrons to convey:

>I have a draft RFC for labeling; I haven't seen any arguments with the
>content of the draft, it's all metadiscussion of whether we should
>have a labeling standard or do something else.  But there is no reason
>for that to be an exclusive-or -- we need to have a labeling standard
>ready to hand the FTC in case CAN-SPAM passes.
>  
>
I suggested some things that should be in the standard - in the email 
I'm quoted from below.
I guess my wording was too unclear (it was convoluted - sorry), you 
missed 'em or rejected 'em, Eric.
e.g. "The IETF ...[should] ... create such a standard, one that 
self-identifies UCE could be useful."

In terms of law that is frea speach challenge-proof, and may keep the 
EFF ostensibly happy, while doing something about spam, the rules that 
prohibit just false advertising, including misleading header content are 
better than laws requiring labeling, though yes they could work together. 

On 12/1/2003 9:57 AM, Hallam-Baker, Phillip sent forth electrons to convey:

> Eric is completely right about this. If you look into the legal issues 
> it is
>
>very easy to see why the bill has a labelling requirement. 
>
>Labelling makes no sense in the context of technical enforcement. It makes a
>great deal of sense if you are dealling with first ammendment issues and
>enforcement.
>  
>
I don't think frea speach spammer defenders see forced speech as any 
better than censored speech.
I don't know of any legal precedent that sees them as different either.
Thus I don't see labels as terribly helpful, 1st amendment and law 
enforcement-wise.

>>Matthew:
>>    
>>
>>>  1. This was tried already in California, and failed abysmally. It
>>>     won't be enforced or effective.
>>>      
>>>
>>California ain't the Feds.
>>    
>>
>The California bill has only been signed a few months. It is far too soon to
>know what effect it will have. At the FTC workshop the lawyers for the
>states mostly stated that they were acting in order to spur federal action.
>  
>
Uh, no, labeling law has been on the books for years.
I'm talking about the current California law, not the law that SB 186 
will make law and S.877 will render powerless 1/1/04.
See <http://law.spamcon.org/us-laws/states/ca/lawindex.shtml> 
Abstract excerpt: Requires senders of Unsolicited Commercial E-mail to 
(a) include the text "ADV:ADLT" at the beginning of the subject line for 
"adult" UCE, (b) include the text "ADV:" at the beginning of the subject 
line of all other UCE...
Clearly, it failed abysmally!  And it's better than S877's labeling 
feature because at least it's UCE, not all CE (Commercial Email) that 
must be labeled.
(I don't want the purchase confirmation when I buy a plane ticket 
labeled ADV:!  The label should only be required on spam!!!)
Eric, if your draft continues to offer a labeling scheme for CE instead 
of UCE, I'm going to create a competing draft.





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



From exim@www1.ietf.org  Tue Mar 30 18:06:38 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24683
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:06:38 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjX-0006Xa-W2
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G7L8qU003431
	for asrg-archive@odin.ietf.org; Fri, 16 Jan 2004 02:21:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhOHz-0000t8-VE
	for asrg-web-archive@optimus.ietf.org; Fri, 16 Jan 2004 02:21:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03339
	for <asrg-web-archive@ietf.org>; Fri, 16 Jan 2004 02:21:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOHw-0000hy-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:21:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhOH0-0000f1-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:20:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOG5-0000c6-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:19:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhOG0-0000Ba-BH; Fri, 16 Jan 2004 02:19:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhO4a-0006vN-3D
	for asrg@optimus.ietf.org; Fri, 16 Jan 2004 02:07:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25786
	for <asrg@ietf.org>; Fri, 16 Jan 2004 02:07:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhO4S-0000C4-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:07:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhO3U-00009C-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:06:09 -0500
Received: from smtp.sprintpcs.com ([63.167.114.16] helo=dedicated59-bos.wh.sprintip.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhO37-000066-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:05:45 -0500
Received: from solidmatrix.com (000-382-198.area3.spcsdns.net [68.29.207.40])
 by dedicated59-bos.wh.sprintip.net
 (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
 with ESMTPA id <0HRK00MW9MCH91@dedicated59-bos.wh.sprintip.net> for
 asrg@ietf.org; Fri, 16 Jan 2004 07:05:15 +0000 (GMT)
From: Yakov Shafranovich <research@solidmatrix.com>
To: ASRG <asrg@ietf.org>
Message-id: <40078D22.6080805@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en, he, ru
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)
 Gecko/20031007
X-Enigmail-Version: 0.82.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Transfer-Encoding: 7BIT
Subject: [Asrg] 2a. Best Current Practices - Description of New Subgroup
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/mail-archive/working-groups/asrg/>
Date: Fri, 16 Jan 2004 02:05:06 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL,CASHCASHCASH autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

This information can also be found at:
http://asrg.sp.am/subgroups/bcp.shtml

---------------------------------------------------------------------------
Description:
This subgroup will research and document best practices for spam management.

Goals:
1. Review RFC 2505 - "Anti-Spam Recommendations for SMTP MTAs", and 
produce an outline and prototypes of suggested changes.
2. Review RFCs 2635 - "DON'T SPEW A Set of Guidelines for Mass 
Unsolicited Mailings and Postings (spam*)"3098 - "How to Advertise 
Responsibly Using E-Mail and Newsgroups or - how NOT to $$$$$ MAKE 
ENEMIES FAST! $$$$", and either produce an outline of changes with 
suggestions, or a recommendation to make the RFCs historical with an 
explanation.
3. Research BCPs for other areas including community support, sufficient 
interest, prototype documents, and draft charters for IETF WGs. Possible 
BCPs include end users, ISPs, blacklists, abuse desk staff, MUAs, MTAs, 
etc.
4. At some point transfer documents to the IETF for standardization.

Status:
Previous BCP subgroup has been active from September of 2003 until 
December of 2003 when it was shutdown due to lack of active members. 
This subgroup is currently in formation, will be restarting in February
of 2004.

Membership:
This subgroup has a closed membership policy, to join contact the ASRG 
chairs

Intended Participants:
o ISPs and MTA administrators including abuse desk staff
o Blacklist operators and anti-spam databases of spammers such as SpamHaus
o Developers of abuse help desk systems such as Abacus, AbusePipe, etc.
o Email senders/advertisers
o End users
o Developers of MTAs and MUAs
---------------------------------------------------------------------------

Sincerely,
Yakov Shafranovich
Co-Chair, ASRG
-------
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"I ate your Web page. / Forgive me. It was juicy / And tart on my 
tongue." (MIT's 404 Message)
-------


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



From exim@www1.ietf.org  Tue Mar 30 18:06:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24725
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:06:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjX-0006YH-IM
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G7L9sT003511
	for asrg-archive@odin.ietf.org; Fri, 16 Jan 2004 02:21:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhOI1-0000uS-5p
	for asrg-web-archive@optimus.ietf.org; Fri, 16 Jan 2004 02:21:09 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03345
	for <asrg-web-archive@ietf.org>; Fri, 16 Jan 2004 02:21:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOHx-0000i8-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:21:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhOH2-0000fH-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:20:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOG6-0000cA-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:19:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhOG3-0000DJ-HH; Fri, 16 Jan 2004 02:19:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhOB8-0008B5-88
	for asrg@optimus.ietf.org; Fri, 16 Jan 2004 02:14:02 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01352
	for <asrg@ietf.org>; Fri, 16 Jan 2004 02:13:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOB4-0000S6-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:13:58 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhOA8-0000QZ-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:13:01 -0500
Received: from smtp.sprintpcs.com ([63.167.114.16] helo=dedicated60-bos.wh.sprintip.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhO9D-0000N8-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:12:03 -0500
Received: from solidmatrix.com (000-382-198.area3.spcsdns.net [68.29.207.40])
 by dedicated60-bos.wh.sprintip.net
 (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
 with ESMTPA id <0HRK00CX6MIYWS@dedicated60-bos.wh.sprintip.net> for
 asrg@ietf.org; Fri, 16 Jan 2004 07:09:02 +0000 (GMT)
From: Yakov Shafranovich <research@solidmatrix.com>
To: ASRG <asrg@ietf.org>
Message-id: <40078E0C.1000404@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en, he, ru
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)
 Gecko/20031007
X-Enigmail-Version: 0.82.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Transfer-Encoding: 7BIT
Subject: [Asrg] 2c. Abuse Reporting Standards - Description of New Subgroup
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/mail-archive/working-groups/asrg/>
Date: Fri, 16 Jan 2004 02:09:00 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

This information can also be found at:
http://asrg.sp.am/subgroups/abuse_reports.shtml

---------------------------------------------------------------------------
Description:
This subgroup will investigate standards for email and network abuse 
reports. It will coordinate with similar efforts in the IETF (IDWG and 
INCH).

Goals:
1. Research the requirements for abuse reporting format and protocol - 
what information should be included, standard replies, multiple vs. 
single messages being reported, incomplete reports, how should reports 
be exchanged, what types of network abuse are covered, etc.
2. Research possible formats - XML vs. MIME, etc. Since this is a 
research group, multiple proposals are possible.
3. Research possible protocols - via email, via SOAP/HTTP, etc. Since 
this is a research group, multiple proposals are possible.
4. Research a BCP for both reporters and receivers of abuse reports, 
including standard procedures, standard abuse contact information, etc.
5. At some point transfer documents to the IETF for standardization.

Status:
Currently in formation, will be starting in February of 2004.

Membership:
This subgroup has a closed membership policy, to join contact the ASRG 
chairs

Intended Participants:
o ISPs and MTA administrators
o Blacklist operators and databases of spammers such as SpamHaus (which 
store evidence and test open relays)
o Systems that assist with abuse reports such as SpamCop, Abuse.net, etc.
o Developers of abuse help desk systems such as Abacus, AbusePipe, etc.

Possible other participants:
o Law enforcement and legal representatives, i.e. FTC, Cyveliance, etc. 
IF this format is also used to report spammers for prosecution
o RIR and ICANN representatives IF we need to investigate ways to store 
contact information
---------------------------------------------------------------------------

Sincerely,
Yakov Shafranovich
Co-Chair, ASRG

-------
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety" (Benjamin Franklin)
-------


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



From exim@www1.ietf.org  Tue Mar 30 18:07:08 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24813
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:07:08 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjX-0006WI-Fn
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G7L656003399
	for asrg-archive@odin.ietf.org; Fri, 16 Jan 2004 02:21:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhOHy-0000sg-K2
	for asrg-web-archive@optimus.ietf.org; Fri, 16 Jan 2004 02:21:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03331
	for <asrg-web-archive@ietf.org>; Fri, 16 Jan 2004 02:21:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOHu-0000hf-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:21:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhOGy-0000ej-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:20:05 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOG5-0000c2-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:19:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhOFy-0000BD-Oa; Fri, 16 Jan 2004 02:19:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhNye-0006LA-4Y
	for asrg@optimus.ietf.org; Fri, 16 Jan 2004 02:01:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21056
	for <asrg@ietf.org>; Fri, 16 Jan 2004 02:01:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhNya-0007iu-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:01:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhNxi-0007gy-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:00:11 -0500
Received: from smtp.sprintpcs.com ([63.167.114.16] helo=dedicated59-bos.wh.sprintip.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhNxS-0007dZ-00
	for asrg@ietf.org; Fri, 16 Jan 2004 01:59:54 -0500
Received: from solidmatrix.com (000-382-198.area3.spcsdns.net [68.29.207.40])
 by dedicated59-bos.wh.sprintip.net
 (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
 with ESMTPA id <0HRK00DVNM2XE5@dedicated59-bos.wh.sprintip.net> for
 asrg@ietf.org; Fri, 16 Jan 2004 06:59:25 +0000 (GMT)
From: Yakov Shafranovich <research@solidmatrix.com>
To: ASRG <asrg@ietf.org>
Message-id: <40078BC9.3020607@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en, he, ru
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)
 Gecko/20031007
X-Enigmail-Version: 0.82.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Transfer-Encoding: 7BIT
Subject: [Asrg] 1a. Inventory of Problems - Description of New Subgroup
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/mail-archive/working-groups/asrg/>
Date: Fri, 16 Jan 2004 01:59:21 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

This information can also be found at:
http://asrg.sp.am/subgroups/problems.shtml

----------------------------------------------------------------------
Description:
This subgroup will research and list problems in the current email 
architechture relevant to spam.

Goals:
1. Research into why email allows easier abuse than other messaging 
systems, including comparison with other systems.
2. Research into why SMTP is subject to abuse more than other protocols.
3. Research into which related areas need to be addressed, including 
viruses, worms, DDOS attacks, etc. This will not involve actual research 
into these areas, rather determining whether some of these areas require 
attention by the IETF/IRTF and the wider Internet community.
4. Produce a document listing areas in the current email architechture 
that faciliate junk email and network abuse, and the impact of each area 
on the overall problem

Status:
Currently in formation

Membership:
This subgroup has a closed membership policy, to join contact the ASRG 
chairs

Intended Participants:
o IETF and Internet experts knowledgeable in SMTP, DNS and other 
relevant protocols
o People knowledgeable in architechtural issues surrounding email and 
the Internet, and with experience in deploying, managing and changing 
large scale systems
o Security experts, especially knowledgable in securing large scale systems
----------------------------------------------------------------------

Sincerely,
Yakov Shafranovich
Co-Chair, ASRG

-------
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"Be liberal in what you accept, and conservative in what you send" (Jon 
Postel)
-------


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



From exim@www1.ietf.org  Tue Mar 30 18:07:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24904
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:07:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjX-0006WI-DM
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G7L73j003416
	for asrg-archive@odin.ietf.org; Fri, 16 Jan 2004 02:21:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhOHz-0000sr-D1
	for asrg-web-archive@optimus.ietf.org; Fri, 16 Jan 2004 02:21:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03334
	for <asrg-web-archive@ietf.org>; Fri, 16 Jan 2004 02:21:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOHv-0000ht-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:21:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhOGz-0000et-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:20:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOG5-0000c4-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:19:09 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhOFz-0000BN-Mb; Fri, 16 Jan 2004 02:19:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhO2Y-0006ch-8J
	for asrg@optimus.ietf.org; Fri, 16 Jan 2004 02:05:10 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24194
	for <asrg@ietf.org>; Fri, 16 Jan 2004 02:05:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhO2T-00005h-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:05:05 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhO1Y-00002m-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:04:09 -0500
Received: from smtp.sprintpcs.com ([63.167.114.16] helo=dedicated59-bos.wh.sprintip.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhO0q-0007lH-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:03:24 -0500
Received: from solidmatrix.com (000-382-198.area3.spcsdns.net [68.29.207.40])
 by dedicated59-bos.wh.sprintip.net
 (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
 with ESMTPA id <0HRK00DFUM8PDG@dedicated59-bos.wh.sprintip.net> for
 asrg@ietf.org; Fri, 16 Jan 2004 07:02:55 +0000 (GMT)
From: Yakov Shafranovich <research@solidmatrix.com>
To: ASRG <asrg@ietf.org>
Message-id: <40078C9A.6000800@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en, he, ru
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)
 Gecko/20031007
X-Enigmail-Version: 0.82.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Transfer-Encoding: 7BIT
Subject: [Asrg] 1. Problem Analysis - Description of Analysis Subgroup
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/mail-archive/working-groups/asrg/>
Date: Fri, 16 Jan 2004 02:02:50 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

This subgroup is currently active, and is being headed by Terry Sullivan 
and Peter Kay.

This information can also be found at:
http://asrg.sp.am/subgroups/analysis.shtml

--------------------------------------------------------------------------
Description:
Adequate solutions to any problem (including spam) require a rich and 
precise understanding of the nature of the problem itself, an 
understanding firmly grounded in observation and measurement.

The Analysis & Characterization Group (ACG) applies empirical and 
quantitative methods to problems and issues surrounding spam--where it 
comes from, what it looks like, ways to eliminate it. The focus and 
contribution of the ACG is more diffuse than specific, more 
methodological than technical. Areas of interest include (but are not 
limited to):
Data acqusition and dissemination
Research design
Measurement & metrics
Data analysis and interpretation
(ASRG ACG Draft Charter, Rev0.2, October 13, 2003)

Status:
Formed in October of 2003, currently active.

Chairs:
Peter Kay (Titan Key)
Dr. Terry Sullivan (Pantos.org)

Membership:
This subgroup has a closed membership policy, to join, contact the ASRG 
chairs.
--------------------------------------------------------------------------

Sincerely,
Yakov Shafranovich
Co-Chair, ASRG


-------
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"Be liberal in what you accept, and conservative in what you send" (Jon 
Postel)
-------


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



From exim@www1.ietf.org  Tue Mar 30 18:07:47 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24985
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:07:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjX-0006Xa-Ci
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:23 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i0G7L8Xl003496
	for asrg-archive@odin.ietf.org; Fri, 16 Jan 2004 02:21:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhOI0-0000tw-NA
	for asrg-web-archive@optimus.ietf.org; Fri, 16 Jan 2004 02:21:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03342
	for <asrg-web-archive@ietf.org>; Fri, 16 Jan 2004 02:21:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOHw-0000i3-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:21:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhOH1-0000f9-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:20:08 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhOG6-0000c7-00
	for asrg-web-archive@ietf.org; Fri, 16 Jan 2004 02:19:10 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhOG1-0000D2-NV; Fri, 16 Jan 2004 02:19:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AhO7F-0007bF-T0
	for asrg@optimus.ietf.org; Fri, 16 Jan 2004 02:10:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA27921
	for <asrg@ietf.org>; Fri, 16 Jan 2004 02:09:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhO7B-0000J2-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:09:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AhO6D-0000GG-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:08:57 -0500
Received: from smtp.sprintpcs.com ([63.167.114.16] helo=dedicated59-bos.wh.sprintip.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AhO5G-0000DD-00
	for asrg@ietf.org; Fri, 16 Jan 2004 02:07:58 -0500
Received: from solidmatrix.com (000-382-198.area3.spcsdns.net [68.29.207.40])
 by dedicated59-bos.wh.sprintip.net
 (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
 with ESMTPA id <0HRK00D8KMGCD5@dedicated59-bos.wh.sprintip.net> for
 asrg@ietf.org; Fri, 16 Jan 2004 07:07:29 +0000 (GMT)
From: Yakov Shafranovich <research@solidmatrix.com>
To: ASRG <asrg@ietf.org>
Message-id: <40078DAD.6030108@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en, he, ru
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)
 Gecko/20031007
X-Enigmail-Version: 0.82.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Transfer-Encoding: 7BIT
Subject: [Asrg] 2b. Filtering Standards - Description of New Subgroup
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/mail-archive/working-groups/asrg/>
Date: Fri, 16 Jan 2004 02:07:25 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

This information can also be found at:
http://asrg.sp.am/subgroups/filtering.shtml

---------------------------------------------------------------------------
Description:
This subgroup will investigate standards for filtering for automatic 
updates and sharing of filtering information, and better interaction 
between filters, MTAs and MUAs.

Goals:
1. Investigate the requirements for a common header to be produced by 
filters (something like "Filtered-By"), so MUAs do not have to look for 
different types of headers. Included in this is research, are ways to 
deal with possible forging of these headers by spammers.
2. Research requirements for a filter specification format and possibly 
protocol, to be used for dynamic updates for filters. This will include 
research into whether existing formats and languages for filter rules 
such as SIEVE (RFC 3028) can be used for this purpose.
3. Provide one or more draft charters for an IETF WG and associated 
documents.

Status:
Currently in formation, will be starting in February of 2004.

Membership:
This subgroup has a closed membership policy, to join contact the ASRG 
chairs

Intendended Participants:
o Developers of filters
o ISPs and MTA administrators
o Developers of MTAs and MUAs
---------------------------------------------------------------------------

Sincerely,
Yakov Shafranovich
Co-Chair, ASRG


-------
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"I ate your Web page. / Forgive me. It was juicy / And tart on my 
tongue." (MIT's 404 Message)
-------


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



From exim@www1.ietf.org  Tue Mar 30 18:09:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25383
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:09:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjW-0006Xa-QK
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:22 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IFuVQd029641
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 10:56:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3zsj-0007hi-9C
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 10:56:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21359
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 10:56:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3zsb-0007XJ-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 10:56:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3zre-0007Ux-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 10:55:22 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3zqf-0007Rs-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 10:54:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3zpN-0007TM-2F; Thu, 18 Mar 2004 10:53:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3zor-0007RV-HU
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 10:52:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21165
	for <asrg@ietf.org>; Thu, 18 Mar 2004 10:52:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3zoo-0007MD-00
	for asrg@ietf.org; Thu, 18 Mar 2004 10:52:26 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3znw-0007K8-00
	for asrg@ietf.org; Thu, 18 Mar 2004 10:51:32 -0500
Received: from mercury.mv.net ([199.125.85.40])
	by ietf-mx with smtp (Exim 4.12)
	id 1B3znI-0007I5-00
	for asrg@ietf.org; Thu, 18 Mar 2004 10:50:53 -0500
Received: (qmail 13093 invoked from network); 18 Mar 2004 10:50:41 -0500
Received: from iridium.mv.net (HELO mv.mv.com) (199.125.85.17)
  by mercury.mv.net with SMTP; 18 Mar 2004 10:50:49 -0500
X-Peer-Info: remote-ip 199.125.85.17 local-ip 199.125.85.40
  local-name mercury.mv.net
Received: (qmail 25092 invoked by uid 101); 18 Mar 2004 10:50:41 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
To: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
Cc: Yakov Shafranovich <research@solidmatrix.com>, asrg@ietf.org
Subject: Re: [Asrg] Update on Querying IADB
Message-ID: <20040318155041.GA12873@iridium.mv.net>
References: <3DC625B6-77F8-11D8-AD47-000A95AC5778@isipp.com> <405954A5.1010007@solidmatrix.com> <DA07C4E0-78B1-11D8-9C3A-000A95AC5778@isipp.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DA07C4E0-78B1-11D8-9C3A-000A95AC5778@isipp.com>
User-Agent: Mutt/1.4.2.1i
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 10:50:41 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

On Wed, Mar 17, 2004 at 11:57:06PM -0800, Anne P. Mitchell, Esq. wrote:
> >
> Actually the codes we use are a subset of the proposed standardized 
> codeset we developed with Craig Hughes (SpamAssassin) (Craig actually 
> did the initial development, with after-input from us, and tweaking a 
> bit for the needs of ISPs, from whom we also had input).  We worked 
> very closely with Craig as well as the ISP community because we wanted 
> to be sure to provide a product which was completely useful, 

Curious: which ISPs, and what community?  We're listed in the EDDB and
I would have welcomed the opportunity to at least comment; I'm also on
a lot of ISP-related lists and did not notice any requests for input.
That's not all that much of a complaint as much as it is a question
(because I predict you did indeed have a reasonable set of sources):
but I really would like to know what ISP sources you turned to and how
you identified this community.

BTW I just browsed the "query signup" form and it suffers from one
of the things I have remarked to you about before.  There's a
single choice of classification:  "I am representing: " [pick one].
I suspect there are a lot of organizations who (like us) fall into
multiple categories.  My brain freezes when trying to pick one.

-mm-

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



From exim@www1.ietf.org  Tue Mar 30 18:10:10 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25613
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:10:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjW-0006a4-IY
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:22 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB19xFX4027757
	for asrg-archive@odin.ietf.org; Mon, 1 Dec 2003 04:59:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQkpm-0007Db-NL
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 04:59:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03579
	for <asrg-web-archive@ietf.org>; Mon, 1 Dec 2003 04:58:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQkpj-0006UY-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 04:59:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQkpj-0006UV-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 04:59:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQkpf-00079a-3A; Mon, 01 Dec 2003 04:59:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQkoy-00070g-R4
	for asrg@optimus.ietf.org; Mon, 01 Dec 2003 04:58:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03537
	for <asrg@ietf.org>; Mon, 1 Dec 2003 04:58:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQkov-0006TH-00
	for asrg@ietf.org; Mon, 01 Dec 2003 04:58:21 -0500
Received: from ntbbs.winserver.com ([208.247.131.9] helo=winserver.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AQkov-0006TD-00
	for asrg@ietf.org; Mon, 01 Dec 2003 04:58:21 -0500
Received: by winserver.com (Wildcat! SMTP Router v5.7.450.9b10)
          for asrg@ietf.org; Mon, 01 Dec 2003 04:58:42 -0500
Received: from  ([68.211.198.96]) EHLO=FAMILY
          by winserver.com (Wildcat! SMTP v5.7.450.9b10) with SMTP
          id 2507187125; Mon, 01 Dec 2003 04:58:41 -0500
Message-ID: <009601c3b7f1$b94fec50$60c6d344@FAMILY>
From: "Hector Santos" <winserver.support@winserver.com>
To: "ASRG" <asrg@ietf.org>
References: <001601c3b724$64015360$60c6d344@FAMILY> <1031130165110.ZM2870@candle.brasslantern.com> <010901c3b798$84c96910$60c6d344@FAMILY> <3FCA81B1.9080808@solidmatrix.com> <011301c3b7a1$818831b0$60c6d344@FAMILY> <3FCA9582.2080602@solidmatrix.com> <20031201041154.GA32587@thyrsus.com> <1031201050104.ZM3624@candle.brasslantern.com> <20031201063419.GA29153@thyrsus.com> <1031201070857.ZM3841@candle.brasslantern.com> <20031201071708.GB30032@thyrsus.com>
Subject: Re: [Asrg] 0. General - anti-harvesting (was Inquiry about CallerID Verification)
Organization: Santronics Software, Inc
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Dec 2003 04:58:46 -0500
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


----- Original Message ----- 
From: "Eric S. Raymond" <esr@thyrsus.com>
To: "Bart Schaefer" <schaefer@brasslantern.com>

> > Yakov's point (unless I'm completely confused) is that it would
constitute
> > a new requirement for *sending* systems if the return-path "MUST" always
be
> > a valid address.  Hector says that it would not be a new requirement,
and I
> > still haven't been convinced that Hector is correct.
>
> Yakov is correct that that would be a new requiremwnt.  But "MUST
> always be a valid address" is not what I am maintaining, nor is it
> Hector's position unless I have misunderstood him.

No, we are there! (pointing finger head to head back and forth) <g>

> We are simply maintaining that sending MTAs MUST issue a valid return
> path at time of transmission.

Lets put it this way.

SMTP server software vendors have no provisional logic that presumes the
return path address is NOT valid until a natural BOUNCE logic occurs prove
that is invalid.    You can only determine if it is indeed invalid by
PRESUMING it is valid in the first place.

Someone sends you a snail letter.   You look at the envelope, the first
thing you will see ask yourself is

            "Who sent this letter?"
            "Who is from?

I don't know about you.  For the most part, I am a skeptic.  But even then I
am not going to make any initial presumption that address is possibly false.
I am naturally going to presume it is valid and the only way to find out is
to check it out.

Now, this raises an very interesting point.  Here is something I did.  I put
a survey out there on my support mailing list last week about TRUST.

By far, the results was that people will put more TRUST into they recognize
as standard behavior over that is different.

The survey question ask was:

Scenario:

You are in your home sitting on the couch and you can see out the window
where you can see in front of your home your Mail Box near the street.
Everyday, almost at the same exact time, you see your friendly US Postal man
dressed in his official US Postal uniform drive up in his US Postal truck
and put something into the mail box.  You go out and get your mail.

One day, something very strange happens, you see the following happen:

a) An uniformed person, in a US Postal truck drop of mail,
b) An uniformed person, in a unknown car, drop of mail,
c) An non-uniformed person, in a US Postal truck drop of mail,
d) An non-uniformed person, in a unknown car, drop of mail,

What is common between ALL persons is that they drop off the SAME piece of
mail.

Questions:

1)  Please give the ORDER of mail delivery from Highest trust to lowest
trust.   In other words, who do you trust more delivering your mail?

2)  Please give the ORDER of mail scrutiny from highest TRUST to lowest
trust.  In other words, each person has delivered/dropped off the same exact
letter.  Whose mail will you scrutinize less or more?  Whose mail will you
open and  whose mail will you throw away?

I didn't tell them what I was intending to get from this.

My goal was to see if there is a level of trust that can be applied to:

  - BRAND of VENDOR software  (Truck/Company)
  - With a PERMIT to send mail (Uniform/Badge)

The most common address were:

A C B D in both questions.

Between B and C, people tend to trust a delivery person have a truck over
being uniformed. :-)

What I found most interesting is that many people indicated that in their
neck of the woods, there is no uniform or truck.  But a recognizable person
whose job is to be the post-person.  So if they did indeed see a change to a
UNIFORM and/or TRUCK, they will scrutinize the who delivered it and the mail
content.

Pretty natural I think, but  basically, in short,  people will react to what
is different and not standard behavior.

We can apply this basic "change in behavior" idea to SMTP as well.

---
Hector Santos, CTO
WINSERVER "Wildcat! Interactive Net Server"
support: http://www.winserver.com
sales: http://www.santronics.com



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



From exim@www1.ietf.org  Tue Mar 30 18:11:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25968
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:11:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjV-0006a4-Sm
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB19padj024087
	for asrg-archive@odin.ietf.org; Mon, 1 Dec 2003 04:51:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQkiN-0006Ev-NB
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 04:51:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03346
	for <asrg-web-archive@ietf.org>; Mon, 1 Dec 2003 04:51:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQkiI-0006OM-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 04:51:30 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQkiH-0006OJ-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 04:51:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQki4-0006BT-95; Mon, 01 Dec 2003 04:51:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQkhk-00069S-AV
	for asrg@optimus.ietf.org; Mon, 01 Dec 2003 04:50:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03305
	for <asrg@ietf.org>; Mon, 1 Dec 2003 04:50:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQkhh-0006N9-00
	for asrg@ietf.org; Mon, 01 Dec 2003 04:50:53 -0500
Received: from snjpca1-ar2-4-33-218-017.snjpca1.dsl-verizon.net ([4.33.218.17] helo=candle.brasslantern.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQkhg-0006N6-00
	for asrg@ietf.org; Mon, 01 Dec 2003 04:50:52 -0500
Received: (from schaefer@localhost)
	by candle.brasslantern.com (8.11.6/8.11.6) id hB19or304101
	for asrg@ietf.org; Mon, 1 Dec 2003 01:50:53 -0800
X-Authentication-Warning: candle.brasslantern.com: schaefer set sender to schaefer@closedmail.com using -f
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <1031201095053.ZM4100@candle.brasslantern.com>
In-Reply-To: <20031201093547.GA21449@thyrsus.com>
Comments: In reply to "Eric S. Raymond" <esr@thyrsus.com>
        "Re: [Asrg] 0. General - anti-harvesting (was Inquiry about CallerID Verification)" (Dec  1,  4:35am)
References: <010901c3b798$84c96910$60c6d344@FAMILY> 
	<3FCA81B1.9080808@solidmatrix.com> 
	<011301c3b7a1$818831b0$60c6d344@FAMILY> 
	<3FCA9582.2080602@solidmatrix.com> 
	<20031201041154.GA32587@thyrsus.com> 
	<1031201050104.ZM3624@candle.brasslantern.com> 
	<20031201063419.GA29153@thyrsus.com> 
	<1031201070857.ZM3841@candle.brasslantern.com> 
	<20031201071708.GB30032@thyrsus.com> 
	<1031201091349.ZM3967@candle.brasslantern.com> 
	<20031201093547.GA21449@thyrsus.com>
X-Mailer: Z-Mail (5.0.0 30July97)
To: asrg@ietf.org
Subject: Re: [Asrg] 0. General - anti-harvesting (was Inquiry about CallerID Verification)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Dec 2003 09:50:53 +0000

On Dec 1,  4:35am, Eric S. Raymond wrote:
}
} Bart Schaefer <schaefer@brasslantern.com>:
} > Suppose the (not uncommon case) of a sending MTA that is not the
} > same host as the MX for the sender's domain. Call these MTA1 and
} > MX1. A message is transmitted via MTA1 to the recipient's MX, which
} > I'll call MX2. If the sender mailbox is valid at MTA1 -- that is,
} > MTA1 can successfully deliver a DSN to that mailbox in the event of
} > a 5xx response from MX2 -- where is the requirement that the mailbox
} > also be valid when presented as a RCPT TO: at MX1?
}
} RFC2821 says the Return-Path has to be the same address that was
} presented to the MAIL command.

So what?  MX1 isn't any party to the protocol exchange between MTA1 and
MX2.  The reverse-path is completely valid as far as MTA1 can tell; if
MX2 responds 5xx, MTA1 will do the right thing.  You still haven't shown
me how or why any of this affects what happens if MX1 becomes party to
a separate SMTP transaction initiated by MX2, whether involving the same
or any other mailbox.

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



From exim@www1.ietf.org  Tue Mar 30 18:11:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26056
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:11:53 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjU-0006Zv-VX
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:21 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i220P3Gx019871
	for asrg-archive@odin.ietf.org; Mon, 1 Mar 2004 19:25:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AxxiW-0005AP-Qf
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 19:25:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15063
	for <asrg-web-archive@ietf.org>; Mon, 1 Mar 2004 19:24:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AxxiV-0006hJ-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:24:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AxxhZ-0006aY-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:24:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axxgd-0006Uc-00
	for asrg-web-archive@ietf.org; Mon, 01 Mar 2004 19:23:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axxgb-0004Q0-BR; Mon, 01 Mar 2004 19:23:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axxfg-0004O9-H9
	for asrg@optimus.ietf.org; Mon, 01 Mar 2004 19:22:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14856
	for <asrg@ietf.org>; Mon, 1 Mar 2004 19:22:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axxfe-0006MJ-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:22:02 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axxee-0006CX-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:21:00 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axxdf-00064L-00
	for asrg@ietf.org; Mon, 01 Mar 2004 19:19:59 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.11/) with ESMTP id i220JqrA021925;
        Mon, 1 Mar 2004 16:19:52 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <F2HV1LFT>; Mon, 1 Mar 2004 16:19:52 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A1900@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Yakov Shafranovich'" <research@solidmatrix.com>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'Larry Seltzer'" <larry@larryseltzer.com>, sami.suomalainen@bigpond.com,
        "'ASRG'" <asrg@ietf.org>
Subject: RE: [Asrg] Sendmail CEO Backs Yahoo DK and MS CID
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Mar 2004 16:19:51 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60

Thanks for the pointer, it may not be exactly what I am after, I 
will look further.

> I believe that RFC 1183 defines an RP RR for a similar 
> purpose. But in 
> most cases it is already known who the owner of the network is either 
> via abuse.net or WHOIS information for the IP addresses. When spam is 
> reported, most of the time it is reported to the right 
> responsible party.

The issue came up in the context of phishing at a meeting attending
by leading banks. It can take a substantial length of time to get
a site taken down even with the full assistance of the FBI etc.

Some of these issues are jurisdictional, but others are pure
communication issues.

> Nevertheless, standards for abuse reporting including possible DNS 
> implications would be very useful assuming that the ISPs will take 
> action on it and actually do something. That has not always 
> been the case.

I think what has to happen here is to give people a real value 
prpoposition. people are now very concerned about the problem 
of having hijacked machines on their networks. I don't think those
were at all common back in 1990.
 

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



From exim@www1.ietf.org  Tue Mar 30 18:15:13 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27025
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:15:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjT-0006Xa-FG
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:19 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2472RRK000906
	for asrg-archive@odin.ietf.org; Thu, 4 Mar 2004 02:02:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AymsE-0000ER-H3
	for asrg-web-archive@optimus.ietf.org; Thu, 04 Mar 2004 02:02:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA10048
	for <asrg-web-archive@ietf.org>; Thu, 4 Mar 2004 02:02:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AymsA-0003n6-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 02:02:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Aymr9-0003ZF-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 02:01:19 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aymq7-0003DE-00
	for asrg-web-archive@ietf.org; Thu, 04 Mar 2004 02:00:15 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Aympu-0007t2-Nv; Thu, 04 Mar 2004 02:00:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AympS-0007r6-N0
	for asrg@optimus.ietf.org; Thu, 04 Mar 2004 01:59:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07080
	for <asrg@ietf.org>; Thu, 4 Mar 2004 01:59:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AympP-00034n-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:59:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AymoN-0002qf-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:58:28 -0500
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Aymni-0002da-00
	for asrg@ietf.org; Thu, 04 Mar 2004 01:57:47 -0500
Received: from mbaugher-w2k07.cisco.com (sjc-vpn1-905.cisco.com [10.21.99.137])
	by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id i246vED2018563;
	Wed, 3 Mar 2004 22:57:15 -0800 (PST)
Message-Id: <6.0.0.22.2.20040303225250.037ddef0@mira-sjc5-6.cisco.com>
X-Sender: mbaugher@mira-sjc5-6.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22
To: Yakov Shafranovich <research@solidmatrix.com>
From: Mark Baugher <mbaugher@cisco.com>
Cc: "Hallam-Baker, Phillip" <pbaker@verisign.com>, asrg@ietf.org
In-Reply-To: <4046C5CF.3090206@solidmatrix.com>
References: <C6DDA43B91BFDA49AA2F1E473732113E0A191F@mou1wnexm05.vcorp.ad.vrsn.com>
 <4046C5CF.3090206@solidmatrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Asrg] Re: 3b. SMTP Session Verification - STARTTLS
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/mail-archive/working-groups/asrg/>
Date: Wed, 03 Mar 2004 22:56:12 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

At 09:59 PM 3/3/2004, Yakov Shafranovich wrote:
>[was Re: [Asrg] Its all over for Challenge Response]
>
>Hallam-Baker, Phillip wrote:
>>>>Sure they might be apples and oranges. But if you put apples
>>>>and oranges together you have a fruit salad.
>>>
>>>I do think STARTLS might have a role to play in antispam if
>>>there were some scalable way to do the authorization.
>>
>>The problem is advertising the fact you support STARTTLS in
>>the DNS.
>>it is not an authorization problem.
>
>The SMTP clients and servers exchange that information during the EHLO 
>session of the SMTP transaction. Why do you need to advertise that via DNS?
>
>Leaving all of this aside, how will the use of TLS with SMTP help resolve 
>the spam problem?

In principle, it could have a role to play by authenticating the MTA sender.

Mark


>Yakov



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



From exim@www1.ietf.org  Tue Mar 30 18:17:14 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27650
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:17:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjS-0006ZK-Fd
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MLgBCW017906
	for asrg-archive@odin.ietf.org; Mon, 22 Mar 2004 16:42:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5XBM-0004eO-EY
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 16:42:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26547
	for <asrg-web-archive@ietf.org>; Mon, 22 Mar 2004 16:41:56 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5XBF-0002mo-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 16:41:57 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5XAW-0002eM-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 16:41:13 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5X9Z-0002VP-00
	for asrg-web-archive@ietf.org; Mon, 22 Mar 2004 16:40:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5X9Q-0004RB-Ta; Mon, 22 Mar 2004 16:40:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5X9K-0004Og-Lb
	for asrg@optimus.ietf.org; Mon, 22 Mar 2004 16:39:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26317
	for <asrg@ietf.org>; Mon, 22 Mar 2004 16:39:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5X9I-0002TP-00
	for asrg@ietf.org; Mon, 22 Mar 2004 16:39:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5X8c-0002K6-00
	for asrg@ietf.org; Mon, 22 Mar 2004 16:39:15 -0500
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5X7K-00023p-00
	for asrg@ietf.org; Mon, 22 Mar 2004 16:37:54 -0500
X-Sasl-enc: C1niOfUcRt2zBIQkjX0DYg 1079990987
Received: from hirschk1 (unknown [12.145.89.80])
	by mail.messagingengine.com (Postfix) with ESMTP id 1D1D180DC34
	for <asrg@ietf.org>; Mon, 22 Mar 2004 16:29:46 -0500 (EST)
Message-ID: <050101c41054$d37abc70$6aae86a2@hirschk1>
From: "Ken Hirsch" <kenhirsch@myself.com>
To: <asrg@ietf.org>
References: <20040322151814.D9C0216FDF@mail.nitros9.org> <405F529B.9070202@Royer.com>
Subject: Re: [Asrg] S/MIME
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Mar 2004 16:29:56 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

From: "Doug Royer" <Doug@Royer.com>
> No the identity matches the cert. Your talking about content fraud not
> identity fraud.

Consider the following two scenarios.
1. A person lies to the CA about their identity, yet the CA issues them a
certificate.
E.g. http://www.microsoft.com/technet/security/bulletin/MS01-017.mspx

2. An email worm installs spyware which steals certificates off of PCs and
installs keystroke logging software to steal the password.  A spammer uses the
thousands of certificates to send email.

If either of these result in somebody sending mail claiming to be
"Doug@Royer.com", is this identity fraud or content fraud?



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



From exim@www1.ietf.org  Tue Mar 30 18:20:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28663
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:20:04 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjQ-0006a4-Qd
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:17 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2EK3aHX000483
	for asrg-archive@odin.ietf.org; Sun, 14 Mar 2004 15:03:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2bpg-00007R-FJ
	for asrg-web-archive@optimus.ietf.org; Sun, 14 Mar 2004 15:03:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04195
	for <asrg-web-archive@ietf.org>; Sun, 14 Mar 2004 15:03:33 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2bpd-0004F1-00
	for asrg-web-archive@ietf.org; Sun, 14 Mar 2004 15:03:33 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B2boe-00041l-00
	for asrg-web-archive@ietf.org; Sun, 14 Mar 2004 15:02:33 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2bmu-0003bT-00
	for asrg-web-archive@ietf.org; Sun, 14 Mar 2004 15:00:44 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2bkW-0003i7-3A; Sun, 14 Mar 2004 14:58:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B2aVy-0000BS-U4
	for asrg@optimus.ietf.org; Sun, 14 Mar 2004 13:39:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01266
	for <asrg@ietf.org>; Sun, 14 Mar 2004 13:39:08 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2aVw-000265-00
	for asrg@ietf.org; Sun, 14 Mar 2004 13:39:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B2aUy-00020X-00
	for asrg@ietf.org; Sun, 14 Mar 2004 13:38:08 -0500
Received: from eikenes.alvestrand.no ([158.38.152.233])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B2aU1-0001qj-00
	for asrg@ietf.org; Sun, 14 Mar 2004 13:37:09 -0500
Received: from halvestr-w2k1 (localhost.localdomain [127.0.0.1])
	by eikenes.alvestrand.no (Postfix) with ESMTP
	id 55C1061B9D; Sun, 14 Mar 2004 19:36:38 +0100 (CET)
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: Tom Petch <nwnetworks@dial.pipex.com>, "'ASRG'" <asrg@ietf.org>
Subject: Re: [Asrg] trojans in the IETF ?
Message-ID: <659508993.1079260597@[192.168.1.51]>
In-Reply-To: <000a01c40842$25597560$0301a8c0@tom3>
References: <000a01c40842$25597560$0301a8c0@tom3>
X-Mailer: Mulberry/3.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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/mail-archive/working-groups/asrg/>
Date: Sun, 14 Mar 2004 10:36:37 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



--On 12. mars 2004 14:54 +0000 Tom Petch <nwnetworks@dial.pipex.com> wrote:

> I just got an unwanted e-mail offering an improvement in performance
> directed to several IETF lists namely
> gsmp@ietf.org, hubmib-admin@ietf.org, hubmib@ietf.org,  iab@ietf.org,
> idr-admin@ietf.org, idr@ietf.org, ieprep-admin@ietf.org
>
> Three things puzzle me. I am subscribed to more than one of these lists
> but only received the mail on idr - why the inconsistency?

I guess the others were blocking nonsubscriber mails....

> Second, the e-mail contains a check saying hits 8.4 required 5 so  why did
> it get sent it at all?

Spamassassin is run in test mode - mark, but do not block. Switching to 
blocking mode is being considered, but people wanted experience with the 
rate of false positives. (note - it seems to be low)

> And, I extracted enough of the header to identify the mail and sent it off
> to idr-admin to get back a message saying blocked by s p a m control; err
> yes, the IETF can send it to me but I cannot tell the IETF what they are
> doing.

Some individual mailboxes at IETF secretariat utilize mailblocking, even 
while the list does not..... I'm not even sure idr-admin is at the 
secretariat; it might be the list moderators (often the WG chairs).
>
> Explanations, especially conspiracy theories, appreciated.

sad to disappoint :-)


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



From exim@www1.ietf.org  Tue Mar 30 18:22:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29198
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:22:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjQ-0006a4-8Q
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2HMUrAr010747
	for asrg-archive@odin.ietf.org; Wed, 17 Mar 2004 17:30:53 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3jYr-0002nG-L4
	for asrg-web-archive@optimus.ietf.org; Wed, 17 Mar 2004 17:30:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12508
	for <asrg-web-archive@ietf.org>; Wed, 17 Mar 2004 17:30:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3jYp-0006dW-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 17:30:51 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3jXw-0006Up-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 17:29:58 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3jX1-0006Mw-00
	for asrg-web-archive@ietf.org; Wed, 17 Mar 2004 17:28:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3jWX-0002bz-JQ; Wed, 17 Mar 2004 17:28:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3jVs-0002aZ-86
	for asrg@optimus.ietf.org; Wed, 17 Mar 2004 17:27:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12377
	for <asrg@ietf.org>; Wed, 17 Mar 2004 17:27:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3jVp-0006CU-00
	for asrg@ietf.org; Wed, 17 Mar 2004 17:27:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3jUp-00063c-00
	for asrg@ietf.org; Wed, 17 Mar 2004 17:26:45 -0500
Received: from pigeon.verisign.com ([65.205.251.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3jTo-0005qQ-00
	for asrg@ietf.org; Wed, 17 Mar 2004 17:25:40 -0500
Received: from mou1wnexc01.vcorp.ad.vrsn.com (verisign.com [65.205.251.53])
        by pigeon.verisign.com (8.12.11/) with ESMTP id i2HMLtNC028529
        for <asrg@ietf.org>; Wed, 17 Mar 2004 14:25:24 -0800 (PST)
Received: by mou1wnexc01.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2657.72)
	id <G5F2L9Y7>; Wed, 17 Mar 2004 14:14:30 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A19FC@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: asrg@ietf.org
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: multipart/mixed;
	boundary="----_=_NextPart_000_01C40C6D.37643DD3"
Subject: [Asrg] 3 Proof of consent spec
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/mail-archive/working-groups/asrg/>
Date: Wed, 17 Mar 2004 14:14:29 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_000_01C40C6D.37643DD3
Content-Type: text/plain;
	charset="iso-8859-1"

All,

	One of the big problems in any authentication scheme (SPF etc) is
trying to deal with mail forwarded from mailing lists, or forwarding
relationships.

	I believe that these relationships are better authenticated by
reference to the original consent to accept mail from the list. Pretty much
every relationship of this type uses a C/R style opt-in mechanism. This spec
simply extends the concept to make it double ended, user to mailing list,
mailing list to user.

	The scheme can be introduced retrospectively, requires little effort
on the part of mailing list admins (indeed should help their work a lot).

	Using the spec means that arguments over whether someone opted in
can be eliminated. It also allows the 'challenge spam' hole to be closed.
The only reason these challenges are sent is to subscribe to a mailing list.
The amount of data that needs to be presented to the user is very small
indeed.

	It is possible to use RSS to achieve the same effect, but mailing
lists will be arround for many years yet, we have to live with them. And I
still need this technology to authenticate the link from my RSS aggregator
to my email pager.

		Phill


------_=_NextPart_000_01C40C6D.37643DD3
Content-Type: text/plain;
	name="proofofconsent.txt"
Content-Disposition: attachment;
	filename="proofofconsent.txt"
Content-Transfer-Encoding: quoted-printable







                                                            P. Hallam-
                                                                  Baker =

               Internet Draft                            VeriSign Inc.=20
               Document: draft-hallam-baker-                March 2004=20
               proofconsent-00.txt=20
               Expires: October 2004                                  =20
            =20
                               Proof of Consent Mechanism=20
            =20
            Status of this Memo=20
               =20
               This document is an Internet-Draft and is NOT offered in =

               accordance with Section 10 of RFC2026, and the author=20
               does not provide the IETF with any rights other than to=20
               publish as an Internet-Draft =20
               =20
               Internet-Drafts are working documents of the Internet=20
               Engineering Task Force (IETF), its areas, and its=20
               working groups.  Note that      other groups may also=20
               distribute working documents as Internet-Drafts.=20
               =20
               Internet-Drafts are draft documents valid for a maximum=20
               of six months and may be updated, replaced, or obsoleted =

               by other documents at any time.  It is inappropriate to=20
               use Internet-Drafts as reference material or to cite=20
               them other than as "work in progress."=20
               =20
               The list of current Internet-Drafts can be accessed at=20
                    http://www.ietf.org/ietf/1id-abstracts.txt =20
               The list of Internet-Draft Shadow Directories can be=20
               accessed at=20
                    http://www.ietf.org/shadow.html. =20
            =20
            Abstract=20
               =20
               We propose a mechanism Proof of Consent that allows an=20
               email recipient to provide verifiable proof of =
=91opt-in=92=20
               consent to receive email. Proof of Consent may be used=20
               to automatically whitelist email from mailing lists and=20
               email forwarded from another email server.=20
               =20
               Proof of Consent is designed to require minimal state=20
               maintenance by both the email sender and the recipient=20
               and to be deployable with minimal impact on existing=20
               email infrastructure.=20
               =20
            1. Requirements=20
            =20
            The Proof of Consent mechanism provides a verifiable and=20
            revocable proof that a recipient consented to receive email =

            from a specified source. It is designed to address several=20
            of the existing problems of maintaining mailing lists and=20
=0C            other consent based bulk mail such as newsletters and=20
            solicited advertisements.=20
            =20
            We note that other protocols such as Really Simple=20
            Syndication (RSS) and Network News Transport Protocol=20
            (NNTP) offer facilities that are similar to mailing lists=20
            without the need for a proof of consent mechanism. Despite=20
            the existence of these mechanisms email remains the most=20
            commonly used means of obtaining data of this type and it=20
            is appropriate to address these requirements in the context =

            of email mailing lists despite the existence of alternative =

            protocols that already meet them.=20
            =20
            1.1 Subscription Consent Problem=20
            =20
            The SMTP protocol does not provide a means to allow a mail=20
            server receiving a message alleged to have been sent to a=20
            mailing list message to determine whether it was solicited=20
            or not.=20
            =20
            1.2 Reputation Attacks =20
               =20
            An SMTP mail server may be falsely accused of having sent=20
            messages to a non-subscriber. =20
            =20
            As the situation currently stands there is no way to=20
            determine the truth or falsehood of such allegations. A=20
            party may even sign up for a newsletter with opposing views =

            so as to be able to complain about the messages sent and=20
            hope to cause the mailing list to be put on a blacklist.=20
            =20
            Events of this type have occurred in connection with=20
            mailing lists of every political persuasion. When=20
            complaints are made about a blacklisting they are typically =

            met with further hearsay accusations that the accused was=20
            =91notorious=92.=20
            =20
            1.3 Unsubscribe Problem=20
            =20
            Mailing list users often find it difficult to unsubscribe.=20
            In many cases requests to be unsubscribed are sent to the=20
            entire list.=20
            =20
            The un-subscription problem can be a serious problem when=20
            an intermediary such as a mailing list gateway is involved. =

            =20
            1.4 Abandoned Subscription Problem=20
            =20
=0C            Users often fail to unsubscribe from mailing lists, =
causing=20
            huge volumes of mail to accumulate unread in an unused=20
            account or an unread mail folder. In some cases the=20
            subscribed email account is also abandoned.=20
            =20
            Often a mail user will subscribe to a mailing list on a=20
            speculative basis and find that they do not read the list=20
            often.=20
            =20
            1.5 Abandoned List Problem=20
            =20
            Mailing lists are often created and then abandoned after a=20
            period of time after falling into disuse. This can create=20
            serious problems if a spammer after discovers an abandoned=20
            list without an administrator and starts to send messages=20
            to the list.=20
            =20
            1.6 Maintenance Problem=20
            =20
            The management of a high volume mailing list requires a=20
            considerable amount of effort, largely because of the need=20
            to manage the problems of subscribers who are unable to=20
            unsubscribe, have abandoned subscriptions etc. Another=20
            increasing concern for mailing list administrators is that=20
            their lists may be blocked by blacklists, often through no=20
            fault of their own due to reputation attacks.=20
            =20
            2. Deployment Constraints=20
            =20
            The deployed email infrastructure is the result of more=20
            than twenty years of development, much of which has taken=20
            place in an ad-hoc fashion. As such it is vital that any=20
            proposal to change that infrastructure be compatible with=20
            the infrastructure as deployed and not merely as it is=20
            described in theoretical specifications.=20
            =20
            2.1 SMTP Deployment Limitations=20
            =20
            Many SMTP servers are poorly configured and perform=20
            arbitrary and in many cases capricious modifications to=20
            messages as they are transmitted.=20
            =20
            2.2 SMTP Client Limitations=20
            =20
            Adding features to SMTP clients is a slow process. The=20
            features offered by mail readers have not changed=20
            significantly in the past five years, basic principles of=20
            mail delivery have been unchanged for almost ten years. As=20
=0C            a result few end users are likely to upgrade their mail=20
            client in order to be able to take advantage of a protocol=20
            meeting the requirements described.=20
            =20
            2.3 Separate Servers for Incoming and Outgoing Mail=20
            =20
            Enterprises are increasingly using separate mail servers=20
            for incoming and outgoing mail. Even if the end user=20
            interacts with a single server it is likely that incoming=20
            mail will be pre-processed by some form of mail proxy,=20
            particularly if anti-spam filtering is being performed.=20
            =20
            2.4 Network Protocol Access Limitations=20
            =20
            Many ISPs limit or block completely use of certain Internet =

            protocols. These blocks may be imposed for a variety of=20
            reasons that include preventing spam, service=20
            differentiation and caprice.=20
            =20
            2.5 Existing Features Insufficiently Observed=20
            =20
            Many of the problems with mailing lists could be addressed=20
            by simply deploying the existing proposals in [RFC2369].=20
            These provide a mechanism that allows mailing lists to use=20
            URIs to specify how users can perform functions unsubscribe =

            from a list.=20
            =20
            A header of particular interest in this specification is=20
            the Mailing-List header that uniquely identifies a mailing=20
            list.=20
            =20
            3. The Proof of Consent Protocol=20
            =20
            The chief deficiency in the email protocols with respect to =

            the requirements is that an incoming mail server has no=20
            means of determining whether a recipient did legitimately=20
            consent to opt-in. =20
            =20
            Most mailing list applications support the use of a=20
            challenge/response protocol to verify subscription=20
            requests. The mailing list sends the subscriber a challenge =

            token consisting of a string of characters. To confirm=20
            subscription to the list the subscriber returns the token=20
            to the mailing list.=20
            =20
            The Proof of Consent mechanism proposes the use of a second =

            token that is created by the subscriber=92s incoming mail=20
            server and forwarded together with the challenge token to=20
=0C            the mailing list. The mailing list then includes a copy =
of=20
            the token in every email message sent to provide the proof=20
            that it was solicited.=20
            =20
            This mechanism minimizes the need for state maintenance at=20
            each stage in the mail transfer protocol, avoiding the need =

            for additional per user records to be stored at either the=20
            incoming or outgoing servers.=20
            =20
            3.1 Initialization=20
            =20
            The incoming mail server establishes a shared secret k. In=20
            the case that there are multiple incoming servers the=20
            shared secret may be established manually or by means of=20
            some form of key agreement protocol using public key based=20
            credentials.=20
            =20
            Once established, the shared secret is maintained for an=20
            extended time period such as a year. Incoming mail servers=20
            must keep a record of all shared secrets that have ever=20
            been used and the validity intervals in which they were=20
            used.=20
            =20
            3.2 Confirmation Code=20
            =20
            During the subscription process we establish a confirmation =

            code that is cryptographically bound to the mailing list=20
            name, the recipient email address and the date of=20
            subscription by means of the shared secret:=20
            =20
            Code =3D MAC (mailing-list, recipient, date)=20
            =20
            Where:=20
            =20
                  list=20
                     The string the mailing list will use in the=20
                     Mailing-List header=20
                  recipient=20
                     The email address of the recipient=20
                  date=20
                     The day on which the subscription took place.=20
            =20
            Each message sent from the mailing list contains a=20
            Confirmation-Code header as follows:=20
            =20
                  Confirmation-Code: <date> <confirmation>=20
            =20
=0C            The mailing list already needs to maintain a =
per-subscriber=20
            record of mailing addresses. The additional state required=20
            to support the confirmation code protocol is negligible.=20
            =20
            We require the subscription date to be stored explicitly=20
            for two reasons, first it requires the mailing list=20
            administrator to take notice of the age of subscriptions,=20
            secondly it allows the incoming mail server to reject mail=20
            with a stale confirmation code that is many years old. This =

            allows a mail server to reject mail sent to a mailing list=20
            that a previous holder of an account name subscribed to.=20
            =20
            The incoming mail server can authenticate a confirmation=20
            code (but not the attached message) by means of the shared=20
            secret. Note that it is not necessary for the MAC algorithm =

            to be standardized, it is sufficient for the sender and=20
            receiver to use the same one.=20
            =20
            3.3 Subscription Process=20
            =20
            The confirmation code is generated during the subscription=20
            process and communicated to the mailing list server.=20
            =20
            We assume that any subscription process involves a=20
            confirmation process by means of an email callback loop=20
            challenge. The incoming mail server detects a mailing list=20
            request for subscription confirmation and causes it to be=20
            redirected so that the appropriate confirmation code can be =

            added.=20
            =20
            The callback loop challenge contains a new header=20
            constructed as follows:=20
            =20
            Challenge-Code: <mailing-list> <recipient> <opaque>=20
            =20
                  Where=20
                  mailing-list=20
                     The string the mailing list will use in the=20
                     Mailing-List header=20
                  recipient=20
                     The email address of the recipient=20
                  opaque=20
                     An opaque code defined by the mailing list=20
                     confirmation server to be used for confirmation=20
                     purposes.=20
            =20
=0C            If the user responds to the confirmation request the=20
            appropriate challenge code is generated and forwarded to=20
            the indicated address along with the opaque code to=20
            establish that the user did intend to subscribe.=20
            =20
            3.4 Legacy Subscriptions=20
            =20
            The confirmation code protocol must support gradual=20
            introduction. It must be possible for a mailing list to=20
            deploy the protocol without having to re-subscribe existing =

            users. It would be advantageous if this can be achieved in=20
            such a way that allows a mailing list administrator to be=20
            able to deploy the protocol incrementally and still be able =

            to establish that unsolicited messages are never sent.=20
            =20
            When a mailing list server sends a message to a legacy=20
            subscriber the confirmation-code header is still present=20
            but only the date field is filled, the confirmation field=20
            is absent. This alerts the incoming server to the fact that =

            the message is purported to be a legacy subscription.=20
            =20
            If the incoming server supports the confirmation code=20
            protocol it may query the user to determine whether the=20
            subscription is actually authorized and if so provide the=20
            relevant confirmation code to the mailing list server to=20
            avoid the need for subsequent authorizations. =20
            =20
            A similar procedure may be employed when the confirmation=20
            code protocol is deployed on an existing incoming mail=20
            server. In this case it is recommended that the service=20
            provide some mechanism to allow the user to send=20
            confirmation codes to a group of mailing lists at the same=20
            time.=20
            =20
            Mailing list administrators may defend themselves against=20
            malicious allegations by having a copy of the mailing list=20
            signed by a digital notary at the time the protocol is=20
            deployed. The signature format may be chosen in such a way=20
            that validity of each entry in the list may be determined=20
            independently without revealing any information about any=20
            other list member. Various schemes suggest themselves=20
            including use of Merkle hash trees or the XML Signature=20
            manifest object. It is recommended that any mechanism=20
            chosen use a random mask value within each entry to prevent =

            attackers from finding out that a specified party has=20
            subscribed to a list.=20
            =20
=0C            This information could be made available through some =
form=20
            of protocol, however it is likely that requiring existing=20
            users to re-subscribe will prove more attractive.=20
            =20
            3.5 Revocation of Confirmation Codes=20
            =20
            The mechanism described only provides for the authenticity=20
            of subscription requests to be established. No assurance is =

            provided for un-subscription requests, nor is the protocol=20
            easily modified to achieve this directly.=20
            =20
            The confirmation code is cryptographically bound to the=20
            mailing list identifier. An incoming mail server or spam=20
            filtering application can filter incoming mail on the basis =

            of the mailing list identifier. Although this requires the=20
            service to maintain state the overhead is minimal and saves =

            considerable resources in the long run. A mailing list may=20
            choose not to observe requests to unsubscribe but there is=20
            no incentive to do so if the messages are unlikely to be=20
            read.=20
            =20
            4. Security Considerations=20
            =20
            4.1 Replay Attack=20
            =20
            The consent to receive mechanism provides proof that the=20
            recipient of an email message has consented to receive=20
            messages from a specified source. It does not provide=20
            definitive proof that a particular message originates from=20
            the source specified.=20
            =20
            An attacker that obtains a consent token for a particular=20
            recipient/sender combination can generate an arbitrary=20
            volume of messages containing the token. =20
            =20
            This vulnerability is unlikely to represent a significant=20
            risk in the context of spam mitigation. It is highly=20
            unlikely that a spammer could obtain a sufficiently large=20
            number of consent tokens to make bulk distribution of spam=20
            through this mechanism feasible. =20
            =20
            The vulnerability may be eliminated through use of the=20
            consent token mechanism in combination with an=20
            authentication mechanism.=20
            =20
            References=20
            =20
            [RFC2369] http://www.ietf.org/rfc/rfc2369.txt =20
=0C            =20
            [ListSpec]          http://www.nisto.com/listspec/ =20
            =20
=0C
------_=_NextPart_000_01C40C6D.37643DD3--

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



From exim@www1.ietf.org  Tue Mar 30 18:22:36 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29383
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:22:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjQ-0006YH-0y
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i19HPPQe001059
	for asrg-archive@odin.ietf.org; Mon, 9 Feb 2004 12:25:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqF9x-0000H0-NH
	for asrg-web-archive@optimus.ietf.org; Mon, 09 Feb 2004 12:25:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29272
	for <asrg-web-archive@ietf.org>; Mon, 9 Feb 2004 12:25:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqF9w-0003wD-00
	for asrg-web-archive@ietf.org; Mon, 09 Feb 2004 12:25:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqF91-0003py-00
	for asrg-web-archive@ietf.org; Mon, 09 Feb 2004 12:24:28 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqF8f-0003jd-00
	for asrg-web-archive@ietf.org; Mon, 09 Feb 2004 12:24:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqF8a-0008FW-NB; Mon, 09 Feb 2004 12:24:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AqF7u-00084A-6Q
	for asrg@optimus.ietf.org; Mon, 09 Feb 2004 12:23:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29062
	for <asrg@ietf.org>; Mon, 9 Feb 2004 12:23:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqF7s-0003hP-00
	for asrg@ietf.org; Mon, 09 Feb 2004 12:23:16 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AqF6u-0003ad-00
	for asrg@ietf.org; Mon, 09 Feb 2004 12:22:16 -0500
Received: from peacock.verisign.com ([65.205.251.73])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AqF5y-0003VO-00
	for asrg@ietf.org; Mon, 09 Feb 2004 12:21:18 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by peacock.verisign.com (8.12.10/) with ESMTP id i19HLBlH006211;
        Mon, 9 Feb 2004 09:21:17 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2653.19)
	id <13KV9V6M>; Mon, 9 Feb 2004 09:21:10 -0800
Message-ID: <C6DDA43B91BFDA49AA2F1E473732113E0A181A@mou1wnexm05.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Alan DeKok'" <aland@ox.org>, asrg@ietf.org
Subject: RE: [Fwd: [Asrg] Re: Documents for LMAP BOF] 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Mon, 9 Feb 2004 09:21:04 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL autolearn=no version=2.60

>   I would say "has permission to claim association with a domain"

linking in the identity issue in the other post. I would say that the
purpose of the authentication mechanism is to prove that the sender
has an association with an accreditation.

That the email does come from the sender address it purports to is
a fairly weak accreditation. But the sender address can quickly lead
to stronger ones. I can whitelist anyone from a domain that I put
on a whitelist. So I whitelist fred@example.com and everyone from the
domain can get some points by inference.

>[Devils advocate disclaimer]
>   Yes, and there are standard arguments against it:
> 
>  - it will take too long to deploy
>  - it won't stop spam.

The people that argue those points are usually the folk whose response
to everything is it will take too long lets not start.

If we had started treating spam seriously ten years ago then every mailer
would have been fixed long ago.


>   99.99% of the spam I get is forged.  Call me naive, but this says to
> me that spammers believe that forgery is an important part of the
> spamming process.

The way I look at it the spammers are using the forgery to get round the
existing filter technology and blacklists. Deny them that tool and the
existing mechanisms become more effective.

it is a geschtalt thing.


>   This addition would also get rid of the forged viruses & worms.  If
> nothing else, it would make it plainly obvious who's stupid enough to
> run a system which gets viruses.  Right now, I don't get viruses, but
> I get tons of spam from software by antivirus companies, claiming to
> have found a virus in a message I sent.  The fact that the viruses are
> forged, and that their "notifications" are spam, is something the
> virus companies apparently don't get.

Oh they get it, they just think it is a costless way to advertise their
product.

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



From exim@www1.ietf.org  Tue Mar 30 18:26:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00169
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:26:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjN-0006WI-QC
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:14 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h8M88gAY023867
	for asrg-archive@odin.ietf.org; Mon, 22 Sep 2003 04:08:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1LkP-0006Cn-JM
	for asrg-web-archive@optimus.ietf.org; Mon, 22 Sep 2003 04:08:41 -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 EAA05278
	for <asrg-web-archive@ietf.org>; Mon, 22 Sep 2003 04:08:33 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1LkM-0003ye-00
	for asrg-web-archive@ietf.org; Mon, 22 Sep 2003 04:08:39 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1LkH-0003ya-00
	for asrg-web-archive@ietf.org; Mon, 22 Sep 2003 04:08:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1Ljp-0005zb-5t; Mon, 22 Sep 2003 04:08:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1A1Lj1-0005oE-Bm
	for asrg@optimus.ietf.org; Mon, 22 Sep 2003 04:07:35 -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 EAA05190
	for <asrg@ietf.org>; Mon, 22 Sep 2003 04:07:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1Lit-0003wX-00
	for asrg@ietf.org; Mon, 22 Sep 2003 04:07:07 -0400
Received: from saci.ensmp.fr ([194.214.158.176])
	by ietf-mx with esmtp (Exim 4.12)
	id 1A1Lij-0003vu-00
	for asrg@ietf.org; Mon, 22 Sep 2003 04:06:57 -0400
Received: from ensmp.fr (xy6 [192.168.105.6])
	by saci.ensmp.fr (8.12.10.Beta2/8.12.9/JMMC) with ESMTP id h8M860gW012982;
	Mon, 22 Sep 2003 10:06:01 +0200 (MEST)
Message-ID: <3F6EB595.ED826925@ensmp.fr>
From: Jose Marcio Martins da Cruz <Jose-Marcio.Martins@ensmp.fr>
Reply-To: Jose-Marcio.Martins@ensmp.fr
Organization: Ecole des Mines de Paris
X-Mailer: Mozilla 4.79 [en] (X11; U; Linux 2.4.20-8 i686)
X-Accept-Language: fr-FR, en
MIME-Version: 1.0
To: Yakov Shafranovich <research@solidmatrix.com>
CC: Liam Meany <meanyl@eeng.dcu.ie>, terry@pantos.org, asrg@ietf.org
Subject: Re: [Asrg] Re: 2.a. Analysis - Honeypot!
References: <3F69E013.9060508@solidmatrix.com>
	 <01c401c37e0b$604301d0$1125ce88@LiamMeany> <3F69F160.8010500@solidmatrix.com>
	 <027c01c37e1a$f83072c0$1125ce88@LiamMeany> <3F6A633F.3070105@solidmatrix.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Miltered: at saci by Joe's j-chkmail ("http://j-chkmail.ensmp.fr")!
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/mail-archive/working-groups/asrg/>
Date: Mon, 22 Sep 2003 10:40:53 +0200
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit



Hello,

Yakov Shafranovich wrote:
> 
> Terry Sullivan is involved in the analysis area and can provide some
> statistical input on this.

I'm not on that group, but I have some (imho) interesting data.

> 
> Liam Meany wrote:
> 
> > Hello Yakov,
> >
> > Many thanks for the detailed reply. Point taken on the "subject" guidelines.
> > Apologies to all.
> >
> > A bit on my background
> > I'm currently working on a dissertation regarding spam - where it comes
> > from. To this end I've seeded 398 email addresses in various places on the
> > web including web pages, mailing lists and newsgroups. The honeypot is in
> > operation for about 3 months now and so far I have only received about 300
> > actual spam messages.

On april (five months ago), I created a honeypot on our webserver : a
false e-mail address inserted in a comment at the main page of our
webserver.

Less than four hours later, we begun to receive spam on the honeypot.

Now, there are 2067 messages inside. I've just looked to it and I noted
that there are two kind of messages in : spams and virus. I've not
really counted, but it seems to me that 1/4 or something like that are
virus. Amusing ! What does this means ?

Also, if I compare, for some time period, which gateways are sending
spam to and and which gateways are sending virus to us, the intersection
is allways not empty, but has many common entries (sometimes more than
half one set)...

Regards,

Jose-Marcio


-- 
 ---------------------------------------------------------------
 Jose Marcio MARTINS DA CRUZ           Tel. :(33) 01.40.51.93.41
 Ecole des Mines de Paris              http://j-chkmail.ensmp.fr
 60, bd Saint Michel                http://www.ensmp.fr/~martins
 75272 - PARIS CEDEX 06      mailto:Jose-Marcio.Martins@ensmp.fr

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



From exim@www1.ietf.org  Tue Mar 30 18:30:48 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01351
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:30:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjK-0006WI-VH
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAU0HXfx009251
	for asrg-archive@odin.ietf.org; Sat, 29 Nov 2003 19:17:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFHI-0002OW-L9
	for asrg-web-archive@optimus.ietf.org; Sat, 29 Nov 2003 19:17:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02866
	for <asrg-web-archive@ietf.org>; Sat, 29 Nov 2003 19:17:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFH6-00058A-00
	for asrg-web-archive@ietf.org; Sat, 29 Nov 2003 19:17:20 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFH4-000580-00
	for asrg-web-archive@ietf.org; Sat, 29 Nov 2003 19:17:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFGo-000258-2l; Sat, 29 Nov 2003 19:17:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFGL-00021Y-Ro
	for asrg@optimus.ietf.org; Sat, 29 Nov 2003 19:16:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02847
	for <Asrg@ietf.org>; Sat, 29 Nov 2003 19:16:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFGK-00054k-00
	for Asrg@ietf.org; Sat, 29 Nov 2003 19:16:32 -0500
Received: from mail.chariot.net.au ([203.87.95.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFGJ-00054X-00
	for Asrg@ietf.org; Sat, 29 Nov 2003 19:16:31 -0500
Received: from rebel (ppp-182.cust203-87-110.ghr.chariot.net.au [203.87.110.182])
	by mail.chariot.net.au (Postfix) with SMTP
	id 64315647B9; Sun, 30 Nov 2003 10:46:29 +1030 (CST)
From: "Chris" <asrg@rebel.com.au>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>,
        "'Scott A Crosby'" <scrosby@cs.rice.edu>,
        "Yakov Shafranovich" <research@solidmatrix.com>
Cc: "Chris" <asrg@rebel.com.au>, <Asrg@ietf.org>
Subject: RE: [Asrg] RE: 6. Proposals - Pull System (revisited)
Message-ID: <GPEMJLCHICHEGPOKJHHDCECMGNAA.asrg@rebel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <2A1D4C86842EE14CA9BC80474919782E01113232@mou1wnexm02.vcorp.ad.vrsn.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Sun, 30 Nov 2003 10:50:15 +1030
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> 
> 
> Whether or not pull eliminates spam is besides the point.
> 
> Pull eliminates false positives which are a serious problem for email
> broadcasters. It does not matter how good some spam filter might be in
> theory, if you are on the sending side you have to deal with the rubbish
> people use, or more accurately their ISP uses.
> 
> 

I am confused Phill. this sounds like a promotion of pull ?



Regards
Chris


> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org]On Behalf Of
> Hallam-Baker, Phillip
> Sent: Sunday, November 30, 2003 9:43 AM
> To: 'Scott A Crosby'; Yakov Shafranovich
> Cc: Chris; Hallam-Baker, Phillip; Asrg@ietf.org
> Subject: [Asrg] RE: 6. Proposals - Pull System (revisited)
> 		Phill
> 
> > -----Original Message-----
> > From: Scott A Crosby [mailto:scrosby@cs.rice.edu]
> > Sent: Saturday, November 29, 2003 1:34 AM
> > To: Yakov Shafranovich
> > Cc: Chris; Hallam-Baker, Phillip; Asrg@ietf.org
> > Subject: Re: 6. Proposals - Pull System (revisited)
> > 
> > 
> > On Wed, 26 Nov 2003 18:05:13 -0500, Yakov Shafranovich 
> > <research@solidmatrix.com> writes:
> > 
> > > Chris wrote:
> > > >>>this is a research group. we should research and then make
> > > >>>recommendations
> > > >>
> > > >>This is an engineering workgroup, not a fantasy land workgroup.
> > > >>The scope is
> > > >>control of spam. Any protocol changes have to be feasible.
> > > >>
> > > >>BEFORE you propose throwing out SMTP you have to explain 
> > exactly what is
> > > >>wrong with it and the reason why incremental change is 
> > not possible.
> > > > Please re read my original post
> > > 
> > > > I do not intend to throw out SMTP they are your words
> > > > pull *IS* smtp
> > > > with two extra steps outgoing request and incoming accept/deny
> > > > both can use the current infrastructure UNCHANGED
> > > >
> > > 
> > > 
> > > The question is how is going to help stem spam. That needs to be
> > > answered before going into minute details of implementation.
> > 
> > 
> > Pull might help stop spam. Right now, a sender system only has to
> > exist to inject a single message for it to get through. With a pull
> > mechanism, the sender must remain at a stable IP address for at least
> > a few hours to a few days. Sending systems can't be ephemeral anymore.
> > 
> > By a pull system what I mean is a system where a sender pushes an
> > announcement that a message is ready. A recipient then 'pulls' the
> > message from the sender at a later time just as they are. The push
> > message contains a nonce for retrieval and a cryptographic digest of
> > the message.
> > 
> > With a pull system, you can 'retroactively' block access to messages
> > sent from malicious serveres, by exploiting the hours or days between
> > being sent and being read. This is because the messages have yet to be
> > distributed to a million mailboxes.
> > 
> > Whether or not this is worth a protocol change I won't say, but it is
> > another mechanism.  I hate to say it, but from reading ASRG, people
> > seem unwilling to make hard choices. 
> > 
> > Scott
> > 
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg

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



From exim@www1.ietf.org  Tue Mar 30 18:31:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01409
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:31:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjJ-0006YH-FR
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:10 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB2H6X6v014614
	for asrg-archive@odin.ietf.org; Tue, 2 Dec 2003 12:06:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARDyr-0003nd-D4
	for asrg-web-archive@optimus.ietf.org; Tue, 02 Dec 2003 12:06:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27678
	for <asrg-web-archive@ietf.org>; Tue, 2 Dec 2003 12:06:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDyq-0004Vf-00
	for asrg-web-archive@ietf.org; Tue, 02 Dec 2003 12:06:32 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDyp-0004Vc-00
	for asrg-web-archive@ietf.org; Tue, 02 Dec 2003 12:06:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARDvX-0002rW-HY; Tue, 02 Dec 2003 12:03:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ARDue-0002Xl-MN
	for asrg@optimus.ietf.org; Tue, 02 Dec 2003 12:02:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27362
	for <asrg@ietf.org>; Tue, 2 Dec 2003 12:01:58 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDud-0004Og-00
	for asrg@ietf.org; Tue, 02 Dec 2003 12:02:11 -0500
Received: from smtp.sprintpcs.com ([63.167.114.16] helo=dedicated60-bos.wh.sprintip.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ARDuc-0004OJ-00
	for asrg@ietf.org; Tue, 02 Dec 2003 12:02:10 -0500
Received: from solidmatrix.com (000-372-156.area3.spcsdns.net [68.29.168.21])
 by dedicated60-bos.wh.sprintip.net
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTPA id <0HPA00IZV1X6MZ@dedicated60-bos.wh.sprintip.net> for
 asrg@ietf.org; Tue, 02 Dec 2003 17:00:47 +0000 (GMT)
From: Yakov Shafranovich <research@solidmatrix.com>
To: ASRG <asrg@ietf.org>
Cc: John R Levine <asrg@taugh.com>
Message-id: <3FCCC53D.8020708@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en, he, ru
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5)
 Gecko/20031007
X-Enigmail-Version: 0.82.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Transfer-Encoding: 7BIT
Subject: [Asrg] 6. Proposals - Pull vs. Push - New subgroup?
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/mail-archive/working-groups/asrg/>
Date: Tue, 02 Dec 2003 12:00:45 -0500
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Based on our internal discussions, review of the list discussion, and 
comments from other people, the chairs have come to a conclusion that at 
this time a "pull" group would not be created.

There are two arguments that were put forth in the list discussion. One 
contingent was arguing that providing "pull" channels for marketers, can 
help mitigate spam if most legit marketers switch over to "pull" leaving 
only spammers in the email realm. However, it seems to us that until 
"pull" standards are improved and there is better integration with 
email, that will not happen. The second contingent was arguing for 
overhauling the email infrastructure to do pull instead of push (this 
would include IM2000 proposal for example).

Both of these would require either changes in pull standards such as 
RSS, better integration between "pull" and email standards, or changes 
to existing email standards. All of these have very strenuous connection 
to the mission of the ASRG. Therefore, it seems to us that while there 
might exist significant reasons and motivations for these discussions, 
the ASRG would not be an appropriate forum for such subgroup. This work 
would be a more appropriate discussion for either the RSS folks, IRTF in 
general, ietf-smtp or ietf-822, or some other group.

Since these ideas are viable, I would suggest that interested parties 
organize themselves into their own group. If you wish want to pursue 
this topic as a new IRTF group than I will be happy to forward your 
request to the IRTF chair and provide background information. I will 
also be happy to provide background information if you want to take this 
to a different group.

Sincerely,
Yakov Shafranovich
Co-Chair, ASRG
-------
Yakov Shafranovich / asrg <at> shaftek.org
SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
"Power tends to corrupt, and absolute power corrupts absolutely" (Lord 
Acton)
-------


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



From exim@www1.ietf.org  Tue Mar 30 18:31:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01530
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:31:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjJ-0006YH-2y
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:09 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i12ABT7P019632
	for asrg-archive@odin.ietf.org; Mon, 2 Feb 2004 05:11:29 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Anb3A-00056L-4I
	for asrg-web-archive@optimus.ietf.org; Mon, 02 Feb 2004 05:11:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00448
	for <asrg-web-archive@ietf.org>; Mon, 2 Feb 2004 05:11:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Anb36-0007d2-00
	for asrg-web-archive@ietf.org; Mon, 02 Feb 2004 05:11:24 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Anb2D-0007TY-00
	for asrg-web-archive@ietf.org; Mon, 02 Feb 2004 05:10:29 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1Anb1H-0007Kb-00
	for asrg-web-archive@ietf.org; Mon, 02 Feb 2004 05:09:31 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Anb0q-0004af-HM; Mon, 02 Feb 2004 05:09:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Anb0D-0004Pb-1R
	for asrg@optimus.ietf.org; Mon, 02 Feb 2004 05:08:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA00218
	for <asrg@ietf.org>; Mon, 2 Feb 2004 05:08:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Anb09-0007BS-00
	for asrg@ietf.org; Mon, 02 Feb 2004 05:08:21 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AnazD-000749-00
	for asrg@ietf.org; Mon, 02 Feb 2004 05:07:24 -0500
Received: from argon.connectinternetsolutions.com ([193.110.243.33] helo=argon.connect.org.uk)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AnayM-0006uG-00
	for asrg@ietf.org; Mon, 02 Feb 2004 05:06:30 -0500
Received: from mmail by argon.connect.org.uk with local (connectmail/exim)
	id 1AnayI-0005QU-6z
	for asrg@ietf.org; Mon, 02 Feb 2004 10:06:26 +0000
In-Reply-To: <200402021322.45284.famous-asrg@nutters.org>
Subject: Re: [Asrg] Its all over for Challenge Response
To: "ASRG" <asrg@ietf.org>
From: "Jon Kyme" <jrk@merseymail.com>
X-Mailer: [ConnectMail 3.10.1]
X-connectmail-Originating-IP: 172.25.243.3
Message-Id: <E1AnayI-0005QU-6z@argon.connect.org.uk>
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/mail-archive/working-groups/asrg/>
Date: Mon, 02 Feb 2004 10:06:26 +0000
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

> Jon Kyme responds:
> > This is all getting silly.
> > Numbers?
> > Actual exploit?
> 
> I say:
> Does anyone still seriously doubt that spamming miscreants are using
> third
> party computers as their web, mail and DNS hosts? Jon? This is not a new 
> phenomenon anymore.
> 

[many links snipped]

The point was about paying for puzzle solving with porn views.
I'm still unaware of the existence of an exploit or a good discussion of
the economics.

I'm not saying it's impossible, just currently in the realm of theory.

I whole-heartedly agree with you when you say:
>Any anti-spam proposal (particularly those that
>propose
>a cost-burden to the sender) should take this fact into >consideration.

We see many variations of "sender-pays" and "proof-of-work" which make
unwarranted assumptions about how "costs" impact miscreants.

 




--

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



From exim@www1.ietf.org  Tue Mar 30 18:32:40 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01775
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:32:40 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjI-0006YH-8J
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9QJ7Rr5016448
	for asrg-archive@odin.ietf.org; Sun, 26 Oct 2003 14:07:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqEY-0004By-63
	for asrg-web-archive@optimus.ietf.org; Sun, 26 Oct 2003 14:07:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24650
	for <asrg-web-archive@ietf.org>; Sun, 26 Oct 2003 14:07:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEV-0007dJ-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:07:23 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEU-0007dC-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:07:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqEC-0003vc-CG; Sun, 26 Oct 2003 14:07:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqDk-0003sO-AG
	for asrg@optimus.ietf.org; Sun, 26 Oct 2003 14:06:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24632
	for <asrg@ietf.org>; Sun, 26 Oct 2003 14:06:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqDh-0007cU-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:06:33 -0500
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqDh-0007cR-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:06:33 -0500
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9QJ66CB038190;
	Sun, 26 Oct 2003 14:06:29 -0500 (EST)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002002bbc1ae10ddec@[203.121.161.48]>
In-Reply-To: <20031023171814.GM16254@mail>
References: <6.0.0.22.0.20031021115547.01c87838@mail.uniwares.com>
 <000001c39802$d4f553f0$19602241@viper1>
 <20031022035117.GF74735@Space.Net>
 <20031022040943.GL11687@gamerz.net>
 <p06002005bbbc7fff2e67@[200.10.10.62]>
 <20031022200726.GE16254@mail>
 <p06002004bbbd76118254@[203.121.161.48]>
 <20031023171814.GM16254@mail>
To: David Maxwell <david@crlf.net>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: [Asrg] 0. General
Cc: Brad Knowles <brad.knowles@skynet.be>, Asrg <asrg@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Mon, 27 Oct 2003 00:08:27 +0700

At 1:18 PM -0400 2003/10/23, David Maxwell wrote:

>>  	That's fine, but keep in mind that this has collateral damage
>>  	consequences.
>
>  It's my choice to accept those consequences - it's _my_ consent
>  decision.

	That's fine -- up until the time where you tell other people that 
they should be doing the same thing.

	If you want to insert lit explosive devices into your body, 
that's one thing.  But when you start encouraging other people to do 
the same, that's totally different.

>  That's not an abuse of DRIP. DRIP provides a layer upon which I can add
>  a white/grey/blacklist by domain. Without DRIP (or RMX, etc), I cannot
>  whitelist by domain, since spammers can forge spam claiming to be from
>  one of the domains I whitelist.

	They could do that anyway.  Remember the previous discussion of 
DNS cache poisoning?  Even if your servers are immune to cache 
poisoning, what are the odds that the advertised nameservers of all 
your whitelist domains are also secure?

>  Many of the viruses forge email source. If they didn't, I could easily
>  contact the sender and tell them to cleanup their machine.

	Just forge the username.  Unless you contact the system 
administrator at that ISP and get them to match the username against 
the IP address at that particular time, you'd never know (that's 
assuming they have accurate logs for that time, or that they're 
willing to do this for you since you're not a paying customer).  Or, 
forge the username within any of the other domains which are hosted 
by those machines.

	Of course, another issue with open caching/recursive servers is 
that you can get anyone in the world to effectively host your domain 
for you, and combined with wildcards they could appear to be hosts 
for virtually all domains on the Internet.

>  I'm not rejecting the mails in the SMTP phase - so the RFC specs are not
>  relevant - however, the fact that I cannot implement
>  white/grey/blacklists leaves content inspection as the only method to
>  identify spam. That 'guesswork' takes a lot of CPU time, and gives me a
>  very non-deterministic answer anyway.

	You're going to be forced to do that anyway.  You're just going 
to force the spammers to get that bit more crafty to by-pass your 
so-called protection mechanisms.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:32:48 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01814
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:32:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjI-0006YH-6E
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1KbtJ3001322
	for asrg-archive@odin.ietf.org; Mon, 1 Dec 2003 15:37:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQunp-0000L4-QI
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 15:37:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28053
	for <asrg-web-archive@ietf.org>; Mon, 1 Dec 2003 15:37:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQuno-00007c-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 15:37:52 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQunn-00007W-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 15:37:51 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQumz-0008Rt-VU; Mon, 01 Dec 2003 15:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQumt-0008RR-Au
	for asrg@optimus.ietf.org; Mon, 01 Dec 2003 15:36:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28003
	for <asrg@ietf.org>; Mon, 1 Dec 2003 15:36:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQumr-00006O-00
	for asrg@ietf.org; Mon, 01 Dec 2003 15:36:53 -0500
Received: from ntbbs.winserver.com ([208.247.131.9] helo=winserver.com)
	by ietf-mx with smtp (Exim 4.12)
	id 1AQumr-00006J-00
	for asrg@ietf.org; Mon, 01 Dec 2003 15:36:53 -0500
Received: by winserver.com (Wildcat! SMTP Router v5.7.450.9b10)
          for asrg@ietf.org; Mon, 01 Dec 2003 15:37:08 -0500
Received: from  ([68.211.198.96]) EHLO=FAMILY
          by winserver.com (Wildcat! SMTP v5.7.450.9b10) with SMTP
          id 2545493453; Mon, 01 Dec 2003 15:37:07 -0500
Message-ID: <007a01c3b84a$ebcedfc0$60c6d344@FAMILY>
From: "Hector Santos" <winserver.support@winserver.com>
To: "Fridrik Skulason" <frisk@f-prot.com>, <asrg@ietf.org>
References: <20031201180749.GE4067@f-prot.com>
Subject: Re: [Asrg] Re: 6. Proposals: LMTP proposals]]
Organization: Santronics Software, Inc
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Dec 2003 15:37:15 -0500
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Fridik,

I agree with your points,  however, I believe the issue of compromised
machines is outside the scope of SMTP.   The question becomes how these did
machines become compromised in the first place. That is an different issue
outside of SMTP.

If the question is "How can we use SMTP to detect compromised machines?"
then once again, like everything else it all boils down to two things:

       - Trusted Clients (who can we trust and how?)
       - Authentication (who is sending the mail and for whom?)

I am full agreement that the SMTP protocol can not by itself solve the
spammer problem.  In it present form, it will take a suite of ideas and
solutions each based on validation of each state point or combo of state
points.

A 100% (technical) solution to the access/authentication problem can be
achieved but not in the present form of SMTP or more specifically, support
for ESMTP extensions which means modifications to software.  (Note, I am not
attempting in any way, shape or form interpreting what is consider spam.  I
am purely looking at this as an access/authentication issue at the protocol
level).

Outside of this, with no change to SMTP or SOFTWARE,  I can only see an
utopian solution using a new Central Authority Network (farm) controlled by
some entity or group in association with the internet backbone.  My uplink
(UUNET) may adhere to this and if we want to offer a mail server on our
system,  we must comply with the network using compliant software, and
registration with the network, etc.   Don't believe it can't happen.  All is
takes a good proposal presentation to convince the big dogs to do this - in
the name of security and CyberTerrorism.   Never mind spam.

---
Hector Santos, CTO
WINSERVER "Wildcat! Interactive Net Server"
support: http://www.winserver.com
sales: http://www.santronics.com



----- Original Message ----- 
From: "Fridrik Skulason" <frisk@f-prot.com>
To: <asrg@ietf.org>
Sent: Monday, December 01, 2003 1:07 PM
Subject: Re: [Asrg] Re: 6. Proposals: LMTP proposals]]


> > Adding security in one are of the network changes the cost-benefit
> > ratio for attacks in other areas of the network.  This is a very
> > different statement than what you made.
>
> It seems you have misunderstood me - this is exactly what I was saying.
> If LMAP (or something like that) gets adopted, spammers will change their
> strategy to stay in business.  One of the strategies not affected by
> LMAP is the use of compromised machines - therefore I fear that we will
> see an increase in their use in the future.
>
> >> In other words, widespread implementation of LMAP (which would be a
good
> >> thing) would lead to more compromised machines (which would be a bad
> >> thing) ;-)
> >
> >  Tough sh*t for them.
>
> Nice to see how concerned you are about security.
>
> > By the same argument, I shouldn't put locks or an alarm in my house,
> > because that encourages thieves to go after my neighbour, instead of
> > me.
>
> Now this is just stupid.  I am not arguing that something like LMAP
> should not be implemented....quite the contrary - I would love to see
> something like that widely adopted.  All I am saying is that by itself,
> it may not have much effect on the overall spam volume - the spammers
> will switch to other methods, and to handle those we need different
> solutions.
>
> -- 
> Fridrik Skulason   Frisk Software International   phone: +354-540-7400
> Author of F-PROT   E-mail: frisk@f-prot.com       fax:   +354-540-7401
>
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
>



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



From exim@www1.ietf.org  Tue Mar 30 18:33:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01936
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:33:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjH-0006YH-OV
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAPHSRxG012469
	for asrg-archive@odin.ietf.org; Tue, 25 Nov 2003 12:28:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOgzC-0003F2-SN
	for asrg-web-archive@optimus.ietf.org; Tue, 25 Nov 2003 12:28:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28519
	for <asrg-web-archive@ietf.org>; Tue, 25 Nov 2003 12:28:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOgzB-0001b9-00
	for asrg-web-archive@ietf.org; Tue, 25 Nov 2003 12:28:25 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOgzA-0001b6-00
	for asrg-web-archive@ietf.org; Tue, 25 Nov 2003 12:28:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOgyp-00033m-2n; Tue, 25 Nov 2003 12:28:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOgyL-00032O-58
	for asrg@optimus.ietf.org; Tue, 25 Nov 2003 12:27:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28502
	for <asrg@ietf.org>; Tue, 25 Nov 2003 12:27:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOgyJ-0001ab-00
	for asrg@ietf.org; Tue, 25 Nov 2003 12:27:31 -0500
Received: from smtp.sprintpcs.com ([63.167.114.16] helo=dedicated60-bos.wh.sprintip.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOgyJ-0001Zz-00
	for asrg@ietf.org; Tue, 25 Nov 2003 12:27:31 -0500
Received: from solidmatrix.com (000-392-294.area3.spcsdns.net [68.29.246.113])
 by dedicated60-bos.wh.sprintip.net
 (iPlanet Messaging Server 5.2 HotFix 1.16 (built May 14 2003))
 with ESMTPA id <0HOX006FO4FQ9N@dedicated60-bos.wh.sprintip.net> for
 asrg@ietf.org; Tue, 25 Nov 2003 17:26:27 +0000 (GMT)
From: Yakov Shafranovich <research@solidmatrix.com>
To: ASRG <asrg@ietf.org>
Message-id: <3FC390B5.6050203@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
X-Accept-Language: en-us, en, he, ru
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5)
 Gecko/20031007
X-Enigmail-Version: 0.82.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Transfer-Encoding: 7BIT
Subject: [Asrg] 0. General - Posting Tips
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/mail-archive/working-groups/asrg/>
Date: Tue, 25 Nov 2003 12:26:13 -0500
Content-Transfer-Encoding: 7BIT
Content-Transfer-Encoding: 7BIT

Please make sure that your "From" address matches the one used to 
subscribe to the list. In the last week or so, there were about 25-30 
postings that were queued because of the "from" mismatch.

Yakov
-------
Yakov Shafranovich / PGP Key: 0x10D051E6 / www.shaftek.org
SolidMatrix Technologies, Inc. / www.solidmatrix.com
"And this too shall come to pass"
-------


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



From exim@www1.ietf.org  Tue Mar 30 18:33:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01972
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:33:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjH-0006WI-3d
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB19eQAX022181
	for asrg-archive@odin.ietf.org; Mon, 1 Dec 2003 04:40:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQkXZ-0005lX-HZ
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 04:40:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03076
	for <asrg-web-archive@ietf.org>; Mon, 1 Dec 2003 04:40:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQkXT-0006EF-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 04:40:19 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQkXS-0006EC-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 04:40:18 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQkXK-0005hf-O6; Mon, 01 Dec 2003 04:40:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQkWk-0005dw-3s
	for asrg@optimus.ietf.org; Mon, 01 Dec 2003 04:39:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03061
	for <asrg@ietf.org>; Mon, 1 Dec 2003 04:39:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQkWh-0006Du-00
	for asrg@ietf.org; Mon, 01 Dec 2003 04:39:31 -0500
Received: from snjpca1-ar2-4-33-218-017.snjpca1.dsl-verizon.net ([4.33.218.17] helo=candle.brasslantern.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQkWg-0006Dr-00
	for asrg@ietf.org; Mon, 01 Dec 2003 04:39:30 -0500
Received: (from schaefer@localhost)
	by candle.brasslantern.com (8.11.6/8.11.6) id hB19dVF04044
	for asrg@ietf.org; Mon, 1 Dec 2003 01:39:31 -0800
X-Authentication-Warning: candle.brasslantern.com: schaefer set sender to schaefer@closedmail.com using -f
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <1031201093931.ZM4043@candle.brasslantern.com>
In-Reply-To: <200312011854.43717.famous-asrg@nutters.org>
Comments: In reply to Brett Watson <famous-asrg@nutters.org>
        "Re: [Asrg] 0. General - anti-harvesting (was Inquiry about CallerID Verification)" (Dec  1,  6:54pm)
References: <200312011854.43717.famous-asrg@nutters.org>
X-Mailer: Z-Mail (5.0.0 30July97)
To: asrg@ietf.org
Subject: Re: [Asrg] 0. General - anti-harvesting (was Inquiry about CallerID Verification)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Dec 2003 09:39:31 +0000

On Dec 1,  6:54pm, Brett Watson wrote:
}
} Let me see if I can summarise the crux of the matter, here.
} 
} Regardless of what the RFCs say about return address validity, it
} seems like a reasonable local policy to reject mail that has an
} invalid return address.
} 
} The problem arises in actually determining the validity of any address.

The real question, as Yakov has asked repeatedly, is what benefit is
gained from validating the address rather than validating the source
of the message?

Hector responds that there is benefit now in using SMTP to validate the
address, because it doesn't require any additional protocols for source
validation, and that in turn is the case because the existing protocol
requires that the sender mailbox be deliverable.

} Or am I misunderstanding this argument?

I dispute that the existing protocol supports Hector's position.  As I
said in another message, I also dispute that VRFY can be adapted for this
purpose in any useful way.

This is not the same as disputing the policy of rejecting mail that can't
be validated.

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



From exim@www1.ietf.org  Tue Mar 30 18:34:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02176
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:34:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjG-0006WI-E0
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1AcFHs011846
	for asrg-archive@odin.ietf.org; Mon, 1 Dec 2003 05:38:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQlRW-00034s-7w
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 05:38:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05271
	for <asrg-web-archive@ietf.org>; Mon, 1 Dec 2003 05:37:54 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQlRO-0007Ie-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 05:38:06 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQlRN-0007Ib-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 05:38:05 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQlRL-00031H-1a; Mon, 01 Dec 2003 05:38:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQlQW-0002c5-Tj
	for asrg@optimus.ietf.org; Mon, 01 Dec 2003 05:37:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA05241
	for <asrg@ietf.org>; Mon, 1 Dec 2003 05:36:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQlQT-0007Hi-00
	for asrg@ietf.org; Mon, 01 Dec 2003 05:37:09 -0500
Received: from mercury.mv.net ([199.125.85.40])
	by ietf-mx with smtp (Exim 4.12)
	id 1AQlQS-0007Hf-00
	for asrg@ietf.org; Mon, 01 Dec 2003 05:37:08 -0500
Received: (qmail 12739 invoked from network); 1 Dec 2003 05:37:09 -0500
Received: from iridium.mv.net (HELO mv.mv.com) (199.125.85.17)
  by mercury.mv.net with SMTP; 1 Dec 2003 05:37:09 -0500
X-Peer-Info: remote-ip 199.125.85.17 local-ip 199.125.85.40
  local-name mercury.mv.net
Received: (qmail 12716 invoked by uid 101); 1 Dec 2003 05:37:08 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
To: Hector Santos <winserver.support@winserver.com>
Cc: Brett Watson <famous-asrg@nutters.org>, asrg@ietf.org
Subject: Re: [Asrg] 0. General - anti-harvesting (was Inquiry about CallerID Verification)
Message-ID: <20031201103708.GD24303@iridium.mv.net>
References: <200312011854.43717.famous-asrg@nutters.org> <006d01c3b7e8$57459720$60c6d344@FAMILY>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <006d01c3b7e8$57459720$60c6d344@FAMILY>
User-Agent: Mutt/1.4.1i
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Dec 2003 05:37:08 -0500

On Mon, Dec 01, 2003 at 03:51:40AM -0500, Hector Santos wrote:
> 
> Compliant servers must support VRFY as a way to validate return address.

(BTW, "must be valid" and "must be verifiable" are two different
things.)

There are various legitimate situations in which VRFY or RCPT TO
verification wouldn't presently work.  These would have to be solved.
For example:

- UUCP (mentioned elsewhere in this long thread.)  The host system
  doesn't have any chance of verifying users behind the UUCP connection.
  You'd get false positives here.

- As with UUCP, other sorts of disconnected delivery systems where the
  receiving MTA doesn't know anything about the usernames attached to
  a domain.  e.g. the user who has a catchall box for all
  *@example.com addresses, who periodically accesses that box and
  applies local filtering rules.  The user who just has a single
  maildrop from which mail is retrieved via something like fetchmail
  (or a number of equivalents).  Again, false positives.

- The recipient address that is only valid under certain circumstances
  (e.g. graylisted, or firewalled such that it only accepts mail from
  certain sources, or has a filter installed such that it only
  accepts mail from certain senders).  False negatives here.

- The system that accepts all mail so that it can update its
  'corpus' of spam mail.  False positives.

That's just a few.  A more imaginative mind can probably think of
many others.

Maybe they can be solved by extending the capabilities of VRFY,
but I doubt they can be solved by changing usage behaviour.
What would be another way?

-mm-

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



From exim@www1.ietf.org  Tue Mar 30 18:35:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02459
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:35:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjF-0006WI-Gq
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9QJ7Ral016449
	for asrg-archive@odin.ietf.org; Sun, 26 Oct 2003 14:07:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqEY-0004Go-S5
	for asrg-web-archive@optimus.ietf.org; Sun, 26 Oct 2003 14:07:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24660
	for <asrg-web-archive@ietf.org>; Sun, 26 Oct 2003 14:07:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEV-0007dQ-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:07:24 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEV-0007dE-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:07:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqED-0003vo-Av; Sun, 26 Oct 2003 14:07:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqE2-0003ss-Qr
	for asrg@optimus.ietf.org; Sun, 26 Oct 2003 14:06:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24635
	for <asrg@ietf.org>; Sun, 26 Oct 2003 14:06:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqE0-0007ce-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:06:52 -0500
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqDz-0007cZ-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:06:51 -0500
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9QJ66CD038190;
	Sun, 26 Oct 2003 14:06:45 -0500 (EST)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002003bbc1b07b6efd@[203.121.161.48]>
In-Reply-To: <20031024052033.GN16254@mail>
References: <200310221522.AA392036500@mail.figuerres.com>
 <p06002000bbbd729eb35c@[203.121.161.48]>
 <20031023160843.GI16254@mail> <20031023183955.GD18651@Space.Net>
 <20031024052033.GN16254@mail>
To: David Maxwell <david@crlf.net>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: FW: [Asrg] 0. General
Cc: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>,
        Brad Knowles <brad.knowles@skynet.be>, Asrg <asrg@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Mon, 27 Oct 2003 00:12:24 +0700

At 1:20 AM -0400 2003/10/24, David Maxwell wrote:

>  Every decent SMTP MTA adds a 'Received-by:' header, which includes the
>  IP of the host that made the SMTP connection. Even open relay MTAs add
>  this, so you'll still have the IP of the sender of the email.

	How many "decent" MTAs are open relays?  Not many.  Most "decent" 
MTAs these days will refuse to be an open relay unless explicitly 
configured that way.

	How many spammers use open relays anymore?  Not many.  Most use 
open proxies now.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:35:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02493
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:35:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjE-0006YH-8h
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:05 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAIATPrt004396
	for asrg-archive@odin.ietf.org; Tue, 18 Nov 2003 05:29:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AM36r-00018p-G8
	for asrg-web-archive@optimus.ietf.org; Tue, 18 Nov 2003 05:29:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13274
	for <asrg-web-archive@ietf.org>; Tue, 18 Nov 2003 05:29:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AM36n-00029j-00
	for asrg-web-archive@ietf.org; Tue, 18 Nov 2003 05:29:22 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AM36n-00029g-00
	for asrg-web-archive@ietf.org; Tue, 18 Nov 2003 05:29:21 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AM36U-00010U-2V; Tue, 18 Nov 2003 05:29:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AM35i-0000aA-On
	for asrg@optimus.ietf.org; Tue, 18 Nov 2003 05:28:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA13169
	for <asrg@ietf.org>; Tue, 18 Nov 2003 05:28:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AM35f-00027V-00
	for asrg@ietf.org; Tue, 18 Nov 2003 05:28:11 -0500
Received: from mail023.syd.optusnet.com.au ([211.29.132.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AM35e-000267-00
	for asrg@ietf.org; Tue, 18 Nov 2003 05:28:10 -0500
Received: from zen.fernhaven (c211-30-105-76.carlnfd1.nsw.optusnet.com.au [211.30.105.76])
	by mail023.syd.optusnet.com.au (8.11.6p2/8.11.6) with ESMTP id hAIARXP04432
	for <asrg@ietf.org>; Tue, 18 Nov 2003 21:27:34 +1100
Received: from [172.16.0.129] (helo=fred.fernhaven)
	by zen.fernhaven with esmtp (Exim 3.35 #1 (Debian))
	id 1AM351-00054q-00
	for <asrg@ietf.org>; Tue, 18 Nov 2003 21:27:31 +1100
From: Brett Watson <famous-asrg@nutters.org>
Organization: PhD Student, Macquarie University
To: asrg@ietf.org
Subject: Re: [Asrg] 3. Requirements and what is spam
User-Agent: KMail/1.5.3
MIME-Version: 1.0
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200311182128.25545.famous-asrg@nutters.org>
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/mail-archive/working-groups/asrg/>
Date: Tue, 18 Nov 2003 21:28:25 +1100
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Forget about defining "spam". At its broadest, "spam" is just "anything that I 
deem inappropriate for my inbox". In its narrower forms, "spam" is just a 
common specific instance of that, like "unsolicited bulk email", but the 
specific instance is not necessarily a pure subset of the general instance. 
The general instance has the benefit of satisfying all comers; the specific 
instance has the benefit of being recipient-independent.

In my view, the owner of a particular inbox is the proper authority on what is 
appropriate for that inbox, and anything which plans to be a solution to 
"spam" should therefore deal with the problem in its broadest sense. Is there 
a compelling reason to deal with recipient-specific instances of the problem 
(even common ones), rather than the problem in general?

The focus should be on how to empower mail *recipients* to set their own mail 
policies and make everyone else deal with it, as contrasted with the current 
situation in which the *senders* have the upper hand. Why should I, as a mail 
recipient, allow anything in my inbox that I don't want? A perfect 
implementation of such an ideal is almost certainly impossible, but that's 
the target we should be aiming for in the fight against "spam". (No doubt 
this implies a research direction, such as overcoming the ability of the 
sender to lie with impunity, hence the spirit of LMAP.)

It's possible that the fight against the general case will involve the 
development of many specific countermeasures (rather than a single general 
one), and the ability of recipients to choose which countermeasures they 
apply, but there is no question in my mind that the ASRG should approach 
"spam" in its broadest sense.

Regards,
TFBW


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



From exim@www1.ietf.org  Tue Mar 30 18:36:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02635
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:36:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjD-0006Yx-UC
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAU0HWQH009238
	for asrg-archive@odin.ietf.org; Sat, 29 Nov 2003 19:17:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFHI-0002OX-L9
	for asrg-web-archive@optimus.ietf.org; Sat, 29 Nov 2003 19:17:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02870
	for <asrg-web-archive@ietf.org>; Sat, 29 Nov 2003 19:17:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFH6-00058J-00
	for asrg-web-archive@ietf.org; Sat, 29 Nov 2003 19:17:20 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFH6-00058E-00
	for asrg-web-archive@ietf.org; Sat, 29 Nov 2003 19:17:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFGm-00022Z-Jc; Sat, 29 Nov 2003 19:17:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFGL-00021O-6G
	for asrg@optimus.ietf.org; Sat, 29 Nov 2003 19:16:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02841
	for <asrg@ietf.org>; Sat, 29 Nov 2003 19:16:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFGJ-00054c-00
	for asrg@ietf.org; Sat, 29 Nov 2003 19:16:31 -0500
Received: from mail.chariot.net.au ([203.87.95.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFGI-00054W-00
	for asrg@ietf.org; Sat, 29 Nov 2003 19:16:30 -0500
Received: from rebel (ppp-182.cust203-87-110.ghr.chariot.net.au [203.87.110.182])
	by mail.chariot.net.au (Postfix) with SMTP
	id C8B49647C8; Sun, 30 Nov 2003 10:46:27 +1030 (CST)
From: "Chris" <asrg@rebel.com.au>
To: "Jon Kyme" <jrk@merseymail.com>, "Dag Kihlman" <dag.kihlman@htu.se>
Cc: "ASRG" <asrg@ietf.org>
Subject: RE: [Asrg] Re: 6. Proposals - Pull System (revisited)
Message-ID: <GPEMJLCHICHEGPOKJHHDAECMGNAA.asrg@rebel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <E1AQ41G-0008Lg-7u@argon.connect.org.uk>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Sun, 30 Nov 2003 10:50:13 +1030
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

>
> What exactly is the specific failing of SMTP which is addressed by pull
> systems?
>
> Have I missed something?

yes you have

pull forces the id of the remote server *without* rewriting the entire mail
transport system

it can be implemented gradually

i.e. mail from non pull servers are given a grace period (1-2yrs?)

after that point all non pull mail is returned with an error message

most important....

PULL DOES NOT DECIDE WHAT IS OR WHAT ISN'T SPAM.

only the receiver is in the position to do that.

thats why I recommend a "class" system be instantiated at the same time (as
pull or whatever ID system)

so the user can set rules something like
"deny all messages from unknown"
"deny class::UCE"
"accept class::UCE::hardware::electrical_tools"
"accept class::personal"
(examples only)


this is my legal + technical argument

both must co-exist to get a spam *reduction* system working

there will never be a spam prevention system

because spam cannot be defined!

Regards
Chris



> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org]On Behalf Of Jon
> Kyme
> Sent: Saturday, November 29, 2003 10:46 PM
> To: Dag Kihlman
> Cc: ASRG
> Subject: [Asrg] Re: 6. Proposals - Pull System (revisited)
>
>
> What exactly is the specific failing of SMTP which is addressed by pull
> systems?
>
> Have I missed something?
>
>
>
>
>
>
>
>
>
>
>
> --
>
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg


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



From exim@www1.ietf.org  Tue Mar 30 18:36:20 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02653
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:36:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjE-0006YH-2X
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:04 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAU0HWha009237
	for asrg-archive@odin.ietf.org; Sat, 29 Nov 2003 19:17:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFHI-0002OV-L5
	for asrg-web-archive@optimus.ietf.org; Sat, 29 Nov 2003 19:17:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02865
	for <asrg-web-archive@ietf.org>; Sat, 29 Nov 2003 19:17:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFH6-00058B-00
	for asrg-web-archive@ietf.org; Sat, 29 Nov 2003 19:17:20 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFH4-00057z-00
	for asrg-web-archive@ietf.org; Sat, 29 Nov 2003 19:17:19 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFGn-000236-3q; Sat, 29 Nov 2003 19:17:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFGL-00021P-9A
	for asrg@optimus.ietf.org; Sat, 29 Nov 2003 19:16:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02843
	for <asrg@ietf.org>; Sat, 29 Nov 2003 19:16:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFGJ-00054d-00
	for asrg@ietf.org; Sat, 29 Nov 2003 19:16:31 -0500
Received: from mail.chariot.net.au ([203.87.95.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFGI-00054V-00
	for asrg@ietf.org; Sat, 29 Nov 2003 19:16:30 -0500
Received: from rebel (ppp-182.cust203-87-110.ghr.chariot.net.au [203.87.110.182])
	by mail.chariot.net.au (Postfix) with SMTP
	id 8D9FE60BEA; Sun, 30 Nov 2003 10:46:26 +1030 (CST)
From: "Chris" <asrg@rebel.com.au>
To: "Jon Kyme" <jrk@merseymail.com>, "John R Levine" <johnl@iecc.com>
Cc: "ASRG" <asrg@ietf.org>
Subject: RE: RE: [Asrg] 6. Proposals - Legal - Subject labelling (?)
Message-ID: <GPEMJLCHICHEGPOKJHHDOECLGNAA.asrg@rebel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <E1AQ1s6-0005u0-D7@argon.connect.org.uk>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Sun, 30 Nov 2003 10:50:12 +1030
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> > I think we should probably say that we don't recommend a spam labelling
> > standard.  I'd rather concentrate on NO UCE and labelling for MTAs that
> > don't accept spam.
> >
> >
>
> What does this mean? I have users who wish to receive commercial
> email that
> they haven't explicitly solicited. Does this mean I should have UCE PLEASE
> in my banners? I have other users who are more normal, so should I have NO
> UCE (FOR THE MOST PART) in my banners? Or what? This proposition is
> contrary to the recipient-consent basis that this group is chartered on.
> I'm very surprised that it should be proffered by one of the co-chairs.
>

I agree a blanket or scattergun (cluster bombs) approach is no good and will
never get accepted by those who send and those who receive.

this is one of the major problems with IP blacklists
they are counter productive and damage all they touch

an example I was doing a programming job for a university. they stopped
emailing me. when I looked harder I found they were being blocked by an IP
blacklist.
that was only last week!

the first thing that must be agreed on is that spam is not spam to everyone

once that is accepted as the truth then we can move on to better control
systems



Regards
Chris


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



From exim@www1.ietf.org  Tue Mar 30 18:36:48 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02779
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:36:48 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjD-0006Yx-Po
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1IMNMd031180
	for asrg-archive@odin.ietf.org; Mon, 1 Dec 2003 13:22:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQsgg-00086o-SN
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 13:22:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21261
	for <asrg-web-archive@ietf.org>; Mon, 1 Dec 2003 13:22:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsge-0006IV-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 13:22:20 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsge-0006IQ-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 13:22:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQsgL-0007rm-49; Mon, 01 Dec 2003 13:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQsfY-0007qO-GF
	for asrg@optimus.ietf.org; Mon, 01 Dec 2003 13:21:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21177
	for <Asrg@ietf.org>; Mon, 1 Dec 2003 13:20:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsfR-0006GK-00
	for Asrg@ietf.org; Mon, 01 Dec 2003 13:21:05 -0500
Received: from pigeon.verisign.com ([65.205.251.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsfQ-0006GH-00
	for Asrg@ietf.org; Mon, 01 Dec 2003 13:21:05 -0500
Received: from mou1wnexc01.vcorp.ad.vrsn.com (verisign.com [65.205.251.53])
        by pigeon.verisign.com (8.12.10/) with ESMTP id hB1IL2T1017670;
        Mon, 1 Dec 2003 10:21:02 -0800 (PST)
Received: by mou1wnexc01.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2653.19)
	id <XHBM0Z99>; Mon, 1 Dec 2003 10:21:02 -0800
Message-ID: <2A1D4C86842EE14CA9BC80474919782E01113235@mou1wnexm02.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Yakov Shafranovich'" <research@solidmatrix.com>,
        "Hallam-Baker, Phillip" <pbaker@verisign.com>
Cc: "'Scott A Crosby'" <scrosby@cs.rice.edu>, Chris <asrg@rebel.com.au>,
        Asrg@ietf.org
Subject: RE: [Asrg] RE: 6. Proposals - Pull System (revisited)
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Dec 2003 10:20:55 -0800



> From: Yakov Shafranovich [mailto:research@solidmatrix.com]

> It also provides full control to the receiver on whether to 
> "pull" the 
> data or not, and shifts the burden of storing the data to the 
> spammers.

It shifts that burden for all email senders.

It seems as if what you want is the ability to read just the headers of an
email message and then decide to reject it. 

This is possible in the existing SMTP deployment, just send a refusal code
and slam the connection shut as soon as you detect spam.

	Phill

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



From exim@www1.ietf.org  Tue Mar 30 18:36:55 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02834
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:36:55 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjD-0006Yx-Hm
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NCSFxv018353
	for asrg-archive@odin.ietf.org; Thu, 23 Oct 2003 08:28:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeZW-0004la-Qc
	for asrg-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 08:28:10 -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 IAA15596
	for <asrg-web-archive@ietf.org>; Thu, 23 Oct 2003 08:27:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeZT-0006SR-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:28:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeZT-0006SO-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:28:07 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeZQ-0004ez-6n; Thu, 23 Oct 2003 08:28:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYt-0004QF-IU
	for asrg@optimus.ietf.org; Thu, 23 Oct 2003 08:27:31 -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 IAA15570
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:27:21 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYs-0006Re-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:27:30 -0400
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYq-0006Rb-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:27:28 -0400
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9NCQYCH072103
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:27:20 -0400 (EDT)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002005bbbd777bd730@[203.121.161.48]>
In-Reply-To: <p0610032cbbbc9899dd6a@[192.168.1.104]>
References: <6.0.0.22.0.20031021115547.01c87838@mail.uniwares.com>
 <000001c39802$d4f553f0$19602241@viper1>
 <20031022035117.GF74735@Space.Net>
 <p0610032cbbbbbd21f587@[192.168.1.104]>
 <p06002006bbbc80b057f9@[200.10.10.62]>
 <p0610032cbbbc9899dd6a@[192.168.1.104]>
To: "Asrg" <asrg@ietf.org>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: [Asrg] 0. General
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Thu, 23 Oct 2003 19:23:31 +0700

At 4:32 PM -0400 2003/10/22, Kee Hinckley wrote:

>  Then you enter into an interesting resource battle.  Who has more
>  resources that they can afford to keep around doing nothing?

	Yup.

>                                                                That's
>  a dangerous game to play.

	It can be.  You need to know when to stop trying to play this 
game, and to instead change the rules (i.e., change your router 
filters so that they can't even get in at all).

>                             But in any case, my mail server doesn't
>  support it.

	I'm sorry to hear that.  ;-(

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:37:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02960
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:37:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjD-0006WI-BK
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NCRR3t016951
	for asrg-archive@odin.ietf.org; Thu, 23 Oct 2003 08:27:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYo-0004P8-Qj
	for asrg-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 08:27:26 -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 IAA15561
	for <asrg-web-archive@ietf.org>; Thu, 23 Oct 2003 08:27:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYn-0006RQ-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:27:25 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYm-0006RJ-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:27:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYQ-0004Bf-7S; Thu, 23 Oct 2003 08:27:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYB-00049P-7b
	for asrg@optimus.ietf.org; Thu, 23 Oct 2003 08:26:47 -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 IAA15542
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:26:37 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYA-0006Qp-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:26:46 -0400
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeY9-0006Qm-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:26:45 -0400
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9NCQYC9072103
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:26:43 -0400 (EDT)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002001bbbd73cbf9d1@[203.121.161.48]>
In-Reply-To: <20031022192634.GA18651@Space.Net>
References: <6.0.0.22.0.20031021115547.01c87838@mail.uniwares.com>
 <000001c39802$d4f553f0$19602241@viper1>
 <20031022035117.GF74735@Space.Net>
 <p0610032cbbbbbd21f587@[192.168.1.104]>
 <p06002006bbbc80b057f9@[200.10.10.62]>
 <20031022192634.GA18651@Space.Net>
To: "Asrg" <asrg@ietf.org>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: [Asrg] 0. General
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Thu, 23 Oct 2003 19:22:39 +0700

At 9:26 PM +0200 2003/10/22, Markus Stumpf wrote:

>  We have some busy mailservers running a connenction limit of 250 parallel
>  connections at all.

	Which is known to be a bad idea.

>  While I have noticed I have no problems with 50 connections in tarpit from
>  different hosts (some from the same) you can easily run in a homegrown
>  DoS if the number of concurrent tarpitted connections becomes too high.

	This is why.  Don't restrict yourself to a given number of 
simultaneous parallel connections, unless you understand the risks 
and are willing to live with the consequences.  This is laid out in 
the documentation for both sendmail and postfix, and presumably for 
other MTAs as well.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:37:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02980
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:37:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjD-0006Yx-9A
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9QJ7RQX016450
	for asrg-archive@odin.ietf.org; Sun, 26 Oct 2003 14:07:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqEY-0004DD-6F
	for asrg-web-archive@optimus.ietf.org; Sun, 26 Oct 2003 14:07:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24653
	for <asrg-web-archive@ietf.org>; Sun, 26 Oct 2003 14:07:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEV-0007dK-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:07:23 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEU-0007dB-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:07:22 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqEB-0003v4-0o; Sun, 26 Oct 2003 14:07:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqDY-0003rq-9a
	for asrg@optimus.ietf.org; Sun, 26 Oct 2003 14:06:24 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24629
	for <asrg@ietf.org>; Sun, 26 Oct 2003 14:06:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqDV-0007cO-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:06:21 -0500
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqDV-0007cL-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:06:21 -0500
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9QJ66C9038190;
	Sun, 26 Oct 2003 14:06:16 -0500 (EST)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002001bbc1ac106625@[203.121.161.48]>
In-Reply-To: <20031023161556.GJ16254@mail>
References: <p06002004bbbc7ec8e597@[200.10.10.62]>
 <20031022194603.5F58616FC7@jmason.org>
 <20031022200147.GD16254@mail>
 <p06002003bbbd752f4d57@[203.121.161.48]>
 <20031023161556.GJ16254@mail>
To: David Maxwell <david@crlf.net>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: FW: [Asrg] 0. General
Cc: Brad Knowles <brad.knowles@skynet.be>, Asrg <asrg@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Sun, 26 Oct 2003 23:59:08 +0700

At 12:15 PM -0400 2003/10/23, David Maxwell wrote:

>  I can separate the emotional issues in that situation from the technical
>  problems caused by spam which are affecting all users of email. Can you?

	I'm saying that there may be the most grave real-world 
consequences to actions taken by this group, and that any proposal to 
deal with the overall spam situation needs to take these matters 
seriously.  Even if the propose solution neither helps nor hinders 
people in this kind of situation, we need to be explicit about this 
effect.  We especially need to be explicit about the consequences 
when we do either help or hinder.

>  Instead of using your energy to try to prevent progress in solving the
>  spam problem, why don't you use it to develop a system that supports a
>  solution to this problem you feel strongly about.

	I'm not trying to prevent progress.  I'm trying to point out that 
there may be unintended side-effects to the recommendations made by 
this group, and we need to keep things like this in mind during the 
process.

>  If someone _consents_ to receiving mail from these activists, they can
>  configure an SMTP (or other protocol which might be less likely to
>  be sniffed!) server to accept connections from anyone, anonymously.

	Connection analysis.  The CIA and KGB have been very good at 
doing this sort of thing.  You don't need to know the content of the 
communication itself -- just finding out who is talking to whom is 
usually enough.

	When you "fix" the protocol to remove this kind of ability, you 
need to keep in mind the potential consequences.

>  That in no way implies that everyone on the planet should be FORCED to
>  'consent' to accepting mail from anyone, anonymously.

	Agreed.  But you need to keep in mind the consequences.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:37:43 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03012
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:37:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjD-0006WI-9e
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NCSFlT018355
	for asrg-archive@odin.ietf.org; Thu, 23 Oct 2003 08:28:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeZW-0004kv-Qc
	for asrg-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 08:28:10 -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 IAA15593
	for <asrg-web-archive@ietf.org>; Thu, 23 Oct 2003 08:27:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeZS-0006SL-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:28:06 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeZR-0006SE-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:28:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeZP-0004ep-HY; Thu, 23 Oct 2003 08:28:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYe-0004Ee-KR
	for asrg@optimus.ietf.org; Thu, 23 Oct 2003 08:27:16 -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 IAA15557
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:27:06 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYd-0006RF-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:27:15 -0400
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYd-0006RC-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:27:15 -0400
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9NCQYCF072103
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:27:11 -0400 (EDT)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002004bbbd76118254@[203.121.161.48]>
In-Reply-To: <20031022200726.GE16254@mail>
References: <6.0.0.22.0.20031021115547.01c87838@mail.uniwares.com>
 <000001c39802$d4f553f0$19602241@viper1>
 <20031022035117.GF74735@Space.Net>
 <20031022040943.GL11687@gamerz.net>
 <p06002005bbbc7fff2e67@[200.10.10.62]>
 <20031022200726.GE16254@mail>
To: "Asrg" <asrg@ietf.org>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: [Asrg] 0. General
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Thu, 23 Oct 2003 19:23:18 +0700

At 4:07 PM -0400 2003/10/22, David Maxwell wrote:

>  So, connections from nameless IPs probably deserve to be weighted as
>  'spam-likely' in your consent decision. Perhaps even 'spam, guaranteed'.

	That's fine, but keep in mind that this has collateral damage consequences.

	Use DRIP (or DRIP-like techniques) as a whitelist, and that can 
be abused, too -- Plenty of spammers are perfectly happy to 
authenticate in whatever way you want, and will make sure that their 
reverse DNS fully matches, etc... just to get their mail through. 
Then there are the virus/spammers who use victim machines distributed 
around the world, most of whom probably are properly configured to 
use outbound mail relays that are likewise correctly configured.

>  That design decision was made before the current situation came into
>  being. Now, my spamassassin installation spends far more time doing
>  content inspection on spam messages than the 'too much time' it would
>  take to validate the provided hostname.

	Then your spamassassin configuration is not correctly configured. 
You shouldn't be using it that way unless you can make sure that you 
can conform to the same kinds of situations and response times as 
were anticipated when the RFC was written.

>  The network environment has changed, the assumptions about overhead need
>  to be re-evaluated.

	Re-writing the RFC is a different matter, something which I 
believe we are also participating in.  However, until the RFC is 
re-written and gotten to at least the "Proposed Standard" stage, you 
should not be knowingly in violation of it.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:38:21 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03223
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:38:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjC-0006Yx-3a
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAU0IHM2009957
	for asrg-archive@odin.ietf.org; Sat, 29 Nov 2003 19:18:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFI1-0002aW-Of
	for asrg-web-archive@optimus.ietf.org; Sat, 29 Nov 2003 19:18:17 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02894
	for <asrg-web-archive@ietf.org>; Sat, 29 Nov 2003 19:17:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFHv-00059M-00
	for asrg-web-archive@ietf.org; Sat, 29 Nov 2003 19:18:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFHv-00059J-00
	for asrg-web-archive@ietf.org; Sat, 29 Nov 2003 19:18:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFHl-0002Rn-C5; Sat, 29 Nov 2003 19:18:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQFHE-0002OP-Tg
	for asrg@optimus.ietf.org; Sat, 29 Nov 2003 19:17:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02861
	for <asrg@ietf.org>; Sat, 29 Nov 2003 19:17:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFH5-000583-00
	for asrg@ietf.org; Sat, 29 Nov 2003 19:17:19 -0500
Received: from mail.chariot.net.au ([203.87.95.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQFH3-00057q-00
	for asrg@ietf.org; Sat, 29 Nov 2003 19:17:18 -0500
Received: from rebel (ppp-182.cust203-87-110.ghr.chariot.net.au [203.87.110.182])
	by mail.chariot.net.au (Postfix) with SMTP
	id 2D65762F85; Sun, 30 Nov 2003 10:47:13 +1030 (CST)
From: "Chris" <asrg@rebel.com.au>
To: "Alan DeKok" <aland@ox.org>, <asrg@ietf.org>
Subject: RE: [Asrg] Re: 6. Proposals - Pull System (revisited) 
Message-ID: <GPEMJLCHICHEGPOKJHHDIECNGNAA.asrg@rebel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <E1AQ7Un-0004VI-00@mail.nitros9.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Sun, 30 Nov 2003 10:50:59 +1030
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

> > Have I missed something?
> 
>   Reasons.  As in, none given for pull systems, other than "we think
> they'll work".  They will work, of course, but whether or not they'll
> stop spam is another question.

Please define spam

Regards
Chris



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



From exim@www1.ietf.org  Tue Mar 30 18:38:49 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03351
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:38:49 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjA-0006WI-UK
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1NguBX016846
	for asrg-archive@odin.ietf.org; Mon, 1 Dec 2003 18:42:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQxgu-0004NH-7I
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 18:42:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12056
	for <asrg-web-archive@ietf.org>; Mon, 1 Dec 2003 18:42:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQxgo-0005fI-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 18:42:50 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQxgo-0005fF-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 18:42:50 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQxg1-0004Hp-QF; Mon, 01 Dec 2003 18:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQxfM-0004HN-6K
	for asrg@optimus.ietf.org; Mon, 01 Dec 2003 18:41:20 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11996
	for <asrg@ietf.org>; Mon, 1 Dec 2003 18:41:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQxfJ-0005ed-00
	for asrg@ietf.org; Mon, 01 Dec 2003 18:41:17 -0500
Received: from mail.chariot.net.au ([203.87.95.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQxfF-0005eQ-00
	for asrg@ietf.org; Mon, 01 Dec 2003 18:41:15 -0500
Received: from rebel (ppp-069.cust203-87-110.ghr.chariot.net.au [203.87.110.69])
	by mail.chariot.net.au (Postfix) with SMTP id 20B9862745
	for <asrg@ietf.org>; Tue,  2 Dec 2003 10:11:10 +1030 (CST)
From: "Chris" <asrg@rebel.com.au>
To: <asrg@ietf.org>
Subject:  [Asrg] 0. To poll or not to poll
Message-ID: <GPEMJLCHICHEGPOKJHHDOEFJGNAA.asrg@rebel.com.au>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <20031201211458.9D56A1701D@mail.nitros9.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Tue, 2 Dec 2003 10:14:56 +1030
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


I have only been here a short time so I apologise if this has been suggested
or done before.

can we get some sort of poll going

set out each possible anti spam method

and then vote on each one from favourite to least favourite

from that list perhaps select the top two or three methods

then get the group to refine those methods

so if asked we don't all look like a bunch of arguing chidren and can put
forward a shortlist of potential candidates

I also suggest a website which keeps track of the state of play so that
newcomers like me can get up to speed quickly

I am not talking about an archive of mailings. as that is mostly just plain
confusing.


Regards
Chris



> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org]On Behalf Of Alan
> DeKok
> Sent: Tuesday, December 02, 2003 7:45 AM
> To: asrg@ietf.org
> Subject: Re: [Asrg] 0. General -- the state of play
>
>
> "Eric S. Raymond" <esr@thyrsus.com> wrote:
> > 4. LMAP seems neglected recently.  This is bad.
>
>   I've been busy, and the authors of the various related drafts have
> resisted combining their proposals.  I hope to have more LMAP updates
> in the future.
>
> >   We're being distracted by stuff that (I think) is less important
> > than putting an IETF stamp on *some* LMAP design.  I have my own
> > preferences but I'm not going to push them here.  The point is we
> > need to have a road forward.
>
>   <shrug> There is significant opposition to doing *anything*; with
> the excuse that the proposal (whatever it is) is not perfect, or will
> cost too much to deploy, or that it hasn't been demonstrated to be
> useful, etc.
>
>   There is so much opposition to LMAP related solutions that I'm
> skeptical if it (or any proposal) will ever be approved by anyone.
> I'm still involved in ASRG, because I have the naive belief that we
> can do *something* about the problem, other than sticking our
> collective heads in the sand.
>
>   Alan DeKok.
>
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg


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



From exim@www1.ietf.org  Tue Mar 30 18:39:22 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03501
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:39:22 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjA-0006WI-QF
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1AKHem003637
	for asrg-archive@odin.ietf.org; Mon, 1 Dec 2003 05:20:17 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQlA8-0000wa-0g
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 05:20:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04549
	for <asrg-web-archive@ietf.org>; Mon, 1 Dec 2003 05:19:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQlA3-0006xk-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 05:20:11 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQlA3-0006xh-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 05:20:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQl9u-0000sP-Pu; Mon, 01 Dec 2003 05:20:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQl9R-0000rK-QF
	for asrg@optimus.ietf.org; Mon, 01 Dec 2003 05:19:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04500
	for <asrg@ietf.org>; Mon, 1 Dec 2003 05:19:18 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQl9O-0006wk-00
	for asrg@ietf.org; Mon, 01 Dec 2003 05:19:30 -0500
Received: from mercury.mv.net ([199.125.85.40])
	by ietf-mx with smtp (Exim 4.12)
	id 1AQl9N-0006wf-00
	for asrg@ietf.org; Mon, 01 Dec 2003 05:19:29 -0500
Received: (qmail 24870 invoked from network); 1 Dec 2003 05:19:30 -0500
Received: from iridium.mv.net (HELO mv.mv.com) (199.125.85.17)
  by mercury.mv.net with SMTP; 1 Dec 2003 05:19:30 -0500
X-Peer-Info: remote-ip 199.125.85.17 local-ip 199.125.85.40
  local-name mercury.mv.net
Received: (qmail 5088 invoked by uid 101); 1 Dec 2003 05:19:29 -0500
From: "Mark E. Mallett" <mem@mv.mv.com>
To: Fridrik Skulason <frisk@f-prot.com>
Cc: asrg@ietf.org
Subject: Re: [Asrg] Re: 6. Proposals: LMTP proposals]
Message-ID: <20031201101929.GC24303@iridium.mv.net>
References: <20031201091632.GH30566@f-prot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031201091632.GH30566@f-prot.com>
User-Agent: Mutt/1.4.1i
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Dec 2003 05:19:29 -0500

On Mon, Dec 01, 2003 at 09:16:32AM +0000, Fridrik Skulason wrote:
> 
>    A spammer gains access to a compromised computer, and determines
>    the mail address of the owner of the machine.  The spam is then
>    sent out in the name of the owner of the machine, just as if
>    the real owner was actually pressing the keys.  
> 
> In other words, widespread implementation of LMAP (which would be a good
> thing) would lead to more compromised machines (which would be a bad 
> thing) ;-)

What solutions are there that don't suffer this problem?

(greylisting and other sorts of limiters might not, so much, but
that's the sort or things that "owning" machines get around, too.)

mm

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



From exim@www1.ietf.org  Tue Mar 30 18:39:52 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03672
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:39:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjA-0006YH-BM
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1IMNQB031194
	for asrg-archive@odin.ietf.org; Mon, 1 Dec 2003 13:22:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQsgg-00086p-Ui
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 13:22:22 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21263
	for <asrg-web-archive@ietf.org>; Mon, 1 Dec 2003 13:22:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsge-0006IX-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 13:22:20 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsge-0006IR-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 13:22:20 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQsgL-0007sJ-PI; Mon, 01 Dec 2003 13:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQsfy-0007qj-Tw
	for asrg@optimus.ietf.org; Mon, 01 Dec 2003 13:21:38 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21220
	for <asrg@ietf.org>; Mon, 1 Dec 2003 13:21:22 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsfw-0006Gj-00
	for asrg@ietf.org; Mon, 01 Dec 2003 13:21:36 -0500
Received: from guttormur.frisk-software.com ([213.220.100.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQsfw-0006GN-00
	for asrg@ietf.org; Mon, 01 Dec 2003 13:21:36 -0500
Received: by guttormur.frisk-software.com (Postfix, from userid 517)
	id 5963F38013; Mon,  1 Dec 2003 18:21:06 +0000 (GMT)
Received: from localhost.localdomain. (pc28.frisk-software.com [172.16.5.2])
	by guttormur.frisk-software.com (Postfix) with ESMTP id 2B98338006
	for <asrg@ietf.org>; Mon,  1 Dec 2003 18:21:06 +0000 (GMT)
Received: by localhost.localdomain. (8.9.3/client-1.3)
	id SAA04157; Mon, 1 Dec 2003 18:21:06 GMT
From: Fridrik Skulason <frisk@f-prot.com>
To: asrg@ietf.org
Subject: RE: [Asrg] 4. Survey of Solutions - Methods of Authentication -Trojans]]
Message-ID: <20031201182106.GF4067@f-prot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.27i
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/mail-archive/working-groups/asrg/>
Date: Mon, 1 Dec 2003 18:21:06 +0000

> But to trojan a machine to send spam. no way that becomes a federal crime,
> and today I believe it can be even classed as an act of terrorism.

You are forgetting one thing.  Most of the activity behind the zombie nets
is directed from countries where that is not the case, or where the laws
are weaker.  For example some of the East European countries have only
recently introduced copyright laws, similar to those in the western world.

In one country - I think it was Moldavia (but I may be mistaken), it is only
a crime to hack into a government-owned machine, for example.


> FIRST lets close the open system, not keep on thinking of reasons to boo hoo
> legitimate ideas.

I am all for that - as I have said before, I am all in favour of any
method of authentication that meets the following criteria:

  1) Has a realistic chance of being adopted globally.  It does not
     matter how elegant the method is, if none of the "big players"
     adopt it.

  2) Solves the problem of establishing with a reasonable degree of
     certainity that the sender is who he is.  Any such method will
     fail on a compromised system - there is no way any software on
     a different machine can deteremine whether the "right" human is
     actually pressing the keys.  We just have to acknowledge that
     limitation and move on - a "solution" to the problem of
     compromised systems is beyond the scope of this.

  3) Can not be (easily) abused to result in a DoS attack.

-- 
Fridrik Skulason   Frisk Software International   phone: +354-540-7400
Author of F-PROT   E-mail: frisk@f-prot.com       fax:   +354-540-7401

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



From exim@www1.ietf.org  Tue Mar 30 18:40:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03863
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:40:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj9-0006WI-S9
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:00 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9QJ7RNP016452
	for asrg-archive@odin.ietf.org; Sun, 26 Oct 2003 14:07:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqEY-0004Fb-H3
	for asrg-web-archive@optimus.ietf.org; Sun, 26 Oct 2003 14:07:26 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24656
	for <asrg-web-archive@ietf.org>; Sun, 26 Oct 2003 14:07:14 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEV-0007dO-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:07:23 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEV-0007dD-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:07:23 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqE9-0003uX-L5; Sun, 26 Oct 2003 14:07:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqDP-0003rX-T2
	for asrg@optimus.ietf.org; Sun, 26 Oct 2003 14:06:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24622
	for <asrg@ietf.org>; Sun, 26 Oct 2003 14:06:03 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqDN-0007cH-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:06:13 -0500
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqDN-0007cE-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:06:13 -0500
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9QJ66C7038190;
	Sun, 26 Oct 2003 14:06:09 -0500 (EST)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002000bbc1a92bb848@[203.121.161.48]>
In-Reply-To: 
 <IOEPKAPPDKHPENCKFNNGMEIDCNAA.tthomson@neosinteractive.com>
References: 
 <IOEPKAPPDKHPENCKFNNGMEIDCNAA.tthomson@neosinteractive.com>
To: "Tom Thomson" <tthomson@neosinteractive.com>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: RE: [Asrg] postings double?? (off ASRG topic)
Cc: "Asrg" <asrg@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Sun, 26 Oct 2003 23:51:11 +0700

At 4:12 PM +0100 2003/10/23, Tom Thomson wrote:

>                                         Some lists are designed to anonymise
>  the originator of the message; the design of such a list will be broken
>  instantly by a decision not to munge the Reply-To header.

	Those lists are very uncommon, and are not the audience that is 
being addressed by the previously mentioned page.  If you want to set 
up an anonymizing list, then obviously you would have some additional 
requirements that you would need to meet.

>                                                             For many lists,
>  the most commonly intended reply action is to send the reply to the list
>  without a second copy to the originator: as the most common action, it
>  should be achievable with a single mouse-click or key-stroke

	In an ideal world, that would be easily achievable.

	This is not an ideal world.

>                                                               - and almost
>  all the MUAs out there will not allow you to do that if the list software
>  doesn't munge the Reply-To header.

	So we break something for many users for whom there is no 
alternative, simply to make it easier for other users to do the 
"default" action, and for whom if they don't want the default action 
they're usually also screwed?

	This sounds like an extremely brain-damaged idea.

>                                      For other lists the most commonly
>  required reply action is a reply to the list moderator - again, Reply-To
>  header munging is required to make this the default action of most MUAs.

	Again, not the most common type of list, and for which the 
previously quoted page is not attempting to address.

>               Each list has its own requirements, the standardised message of
>  RFC2822 is not adequate to cover all these requirements without header
>  munging.

	Agreed -- you can't use header munging to conform to the issues 
and requirements of all mailing lists, especially not with all MUAs 
(since many are severely broken).

	Therefore, you should make no attempt to use header munging for 
this purpose.

>  What I want out of an MUA is to be able to chose between reply to
>  originator, reply to list, reply to list with copy to originator, reply to
>  list with copy to cc reipients of the original message, .... quite a few
>  options.

	Get a better MUA.  Don't try to fix this problem within the mailing list.

>            The headers provided by RFC2822 are not adequate to permit an MUA
>  to offer all these options in a simple and straightforward usable manner.

	Sounds like you need to write an RFC to detail all these issues 
and lay out the suggestions for MUA authors.

>                             So I think this list would probably be improved
>  by adding the munging

	That's assuming that no one on the list (currently or in the 
future) is/will be using an MUA that is known to be severely broken, 
in such a way that they are completely unable to reply to any message 
other than what is specified in the "Reply-To:" header.

	Not a valid assumption.

>                        - biut I don't think it's worth arguing about;

	Then why are we having this argument?

>                                                                       what I
>  do think is worth arguing about is someone claiming that as a general
>  principal such munging should not be done: the RFCs make no attenmpt to
>  dictate to me (or anyone else) what features I should put into applications
>  I supply to my users, and I don't like to see Chip claiming they do and
>  neither do I like to see Brad quoting him as if he were holy writ.

	His page hasn't been updated to make reference to the latest 
RFCs, but then it doesn't really need to.  The issues with regards to 
the broken MUAs haven't changed, and many sites are still running the 
same ten-year old software that was at the heart of the problem 
originally, which lead to Chip writing that page.

	If the problem hasn't changed, it doesn't make a whole lot of 
sense to try to update the description of the problem, or 
recommendations on how to avoid tickling the problem and making it 
even worse.


	I make reference to this page because it's the best collection 
I've seen yet for the various problems and the ways to deal with them.

	Would you prefer that I write all this up as an RFC and really 
set things in stone?

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:41:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04056
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:41:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj9-0006YH-MJ
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hALL8S5k018441
	for asrg-archive@odin.ietf.org; Fri, 21 Nov 2003 16:08:28 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANIVv-0004nE-UO
	for asrg-web-archive@optimus.ietf.org; Fri, 21 Nov 2003 16:08:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03014
	for <asrg-web-archive@ietf.org>; Fri, 21 Nov 2003 16:08:15 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANIVu-0000uj-00
	for asrg-web-archive@ietf.org; Fri, 21 Nov 2003 16:08:26 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANIVt-0000uf-00
	for asrg-web-archive@ietf.org; Fri, 21 Nov 2003 16:08:25 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANIUZ-0004Ex-6q; Fri, 21 Nov 2003 16:07:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ANIUW-0004Du-HL
	for asrg@optimus.ietf.org; Fri, 21 Nov 2003 16:07:00 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02853
	for <asrg@ietf.org>; Fri, 21 Nov 2003 16:06:47 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ANIUU-0000qC-00
	for asrg@ietf.org; Fri, 21 Nov 2003 16:06:58 -0500
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx with smtp (Exim 4.12)
	id 1ANIUT-0000q4-00
	for asrg@ietf.org; Fri, 21 Nov 2003 16:06:57 -0500
Received: (qmail 21148 invoked by uid 1013); 21 Nov 2003 21:06:55 -0000
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: asrg@ietf.org
Subject: Re: 0. General - Spam survey [was Re: [Asrg] Help with academic research survey.]
Message-ID: <20031121210655.GQ18395@Space.Net>
References: <NNEJICFEOFJIDLGCHKBDEENJCLAA.sandeep@u.washington.edu> <3FBE500B.7070505@solidmatrix.com> <20031121185600.GA20306@iridium.mv.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20031121185600.GA20306@iridium.mv.net>
User-Agent: Mutt/1.4.1i
Organization: SpaceNet AG, Muenchen, Germany
X-PGP-Fingerprint: 66 F3 75 79 01 D0 B8 5F  1A C7 77 88 4A B6 70 DF
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/mail-archive/working-groups/asrg/>
Date: Fri, 21 Nov 2003 22:06:55 +0100

On Fri, Nov 21, 2003 at 01:56:00PM -0500, Mark E. Mallett wrote:
> I started on it, but too many questions include "you do not remember".
> It doesn't really matter what I remember, it matters what I actually
> did..
> 
> So I personally would mark all those as inconclusive, but since I bet
> that's not what you want, I just backed out.

I totally agree.

We receive enough complaints about mailinglists of customers that
are strictly double opt-in (and where I have logs that they have confirmed
per eMail) from people that "cannot remember having subscribed".

They all cry "spam spam spam".

Not having enough brain or not being able to track which lists someone
has subscribed to is not a valid base for marking a message spam, IMHO.

	\Maex

-- 
SpaceNet AG            | Joseph-Dollinger-Bogen 14 | Fon: +49 (89) 32356-0
Research & Development |       D-80807 Muenchen    | Fax: +49 (89) 32356-299
"The security, stability and reliability of a computer system is reciprocally
 proportional to the amount of vacuity between the ears of the admin"

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



From exim@www1.ietf.org  Tue Mar 30 18:41:57 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04210
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:41:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj9-0006ZK-13
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADFc89T018914
	for asrg-archive@odin.ietf.org; Thu, 13 Nov 2003 10:38:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKJXr-0004uz-BV
	for asrg-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 10:38:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03346
	for <asrg-web-archive@ietf.org>; Thu, 13 Nov 2003 10:37:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKJXo-00073k-00
	for asrg-web-archive@ietf.org; Thu, 13 Nov 2003 10:38:04 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKJXo-00073h-00
	for asrg-web-archive@ietf.org; Thu, 13 Nov 2003 10:38:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKJXl-0004qI-EH; Thu, 13 Nov 2003 10:38:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKJWp-0004XN-3T
	for asrg@optimus.ietf.org; Thu, 13 Nov 2003 10:37:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03290
	for <asrg@ietf.org>; Thu, 13 Nov 2003 10:36:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKJWm-00072Y-00
	for asrg@ietf.org; Thu, 13 Nov 2003 10:37:00 -0500
Received: from [209.216.76.58] (helo=mail.figuerres.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKJWl-00071h-00
	for asrg@ietf.org; Thu, 13 Nov 2003 10:37:00 -0500
Received: from viper1 [65.34.96.153] by mail.figuerres.com with ESMTP
  (SMTPD32-8.02) id A4C2113006C; Thu, 13 Nov 2003 10:35:30 -0500
Reply-To: <denny@figuerres.com>
From: "Denny Figuerres" <denny@figuerres.com>
To: <asrg@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.5510
Thread-Index: AcOp+816qSrJIEgWSS6xe8LZtrE42A==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-Id: <200311131035219.SM01928@viper1>
X-IMAIL-SPAM-VALHELO: (18022508)
X-IMAIL-SPAM-VALFROM: (18022508)
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 6. Proposals
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/mail-archive/working-groups/asrg/>
Date: Thu, 13 Nov 2003 10:35:44 -0500
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Excuse me if I may have missed this some where.....

Perhaps one part of the solution will be to recommend some (I think) small
changes to how companies send out email to customers. The common practice of
hiring a third party to send out such emails as newletters airline
confirmations and so forth are done now in a way the can make it difficult
to classify them as HAM not spam for a few reasons:

1) The "From" and the sending MTA's DNS often do not mtach.
2) the DNS / IP of the sender may be included in a DNS RBL as a SPAM DOMAIN
3) attempting to check the user@domain.com fails as it does not exist or the
test is done at the bulk senders domain which does not match.

So could the company that is "sending" the email and the "bulk delivery
provider" fix-up the dns records and the sending mta "HELO" to match the
"From abc@some.com" to make whitlisting simpler and tracking back via
headers a bit sane-er ?

If this would not cause major issues it would clear up a lot of issues with
bulk delivery of legit emails.

Just my idea based on some real world problems .....




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



From exim@www1.ietf.org  Tue Mar 30 18:42:26 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04303
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:42:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj7-0006ZK-Q4
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:58 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hADEvFqX028988
	for asrg-archive@odin.ietf.org; Thu, 13 Nov 2003 09:57:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKIuJ-0007XT-B4
	for asrg-web-archive@optimus.ietf.org; Thu, 13 Nov 2003 09:57:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29580
	for <asrg-web-archive@ietf.org>; Thu, 13 Nov 2003 09:57:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKIuH-0006CA-00
	for asrg-web-archive@ietf.org; Thu, 13 Nov 2003 09:57:13 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKIuH-0006C7-00
	for asrg-web-archive@ietf.org; Thu, 13 Nov 2003 09:57:13 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKIu5-0007Um-R4; Thu, 13 Nov 2003 09:57:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AKItP-0007Qr-1X
	for asrg@optimus.ietf.org; Thu, 13 Nov 2003 09:56:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29517
	for <asrg@ietf.org>; Thu, 13 Nov 2003 09:56:06 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKItM-0006A2-00
	for asrg@ietf.org; Thu, 13 Nov 2003 09:56:16 -0500
Received: from pigeon.verisign.com ([65.205.251.71])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AKItM-00069u-00
	for asrg@ietf.org; Thu, 13 Nov 2003 09:56:16 -0500
Received: from mou1wnexc02.vcorp.ad.vrsn.com (verisign.com [65.205.251.54])
        by pigeon.verisign.com (8.12.10/) with ESMTP id hADEu56L007979;
        Thu, 13 Nov 2003 06:56:05 -0800 (PST)
Received: by mou1wnexc02.vcorp.ad.vrsn.com with Internet Mail Service (5.5.2653.19)
	id <W4YCBKYZ>; Thu, 13 Nov 2003 06:56:05 -0800
Message-ID: <2A1D4C86842EE14CA9BC80474919782E011131D7@mou1wnexm02.vcorp.ad.vrsn.com>
From: "Hallam-Baker, Phillip" <pbaker@verisign.com>
To: "'Fridrik Skulason'" <frisk@f-prot.com>, asrg@ietf.org
Subject: RE: [Asrg] 6. Proposals - DNS-Based - LMAP]
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
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/mail-archive/working-groups/asrg/>
Date: Thu, 13 Nov 2003 06:55:55 -0800

What I could do which might help move us forward is to write a whitepaper
that has a table that lists the various incremental types of authentication
and accreditation that are possible in this space, the advantages and costs
associated with each.



> -----Original Message-----
> From: Fridrik Skulason [mailto:frisk@f-prot.com]
> Sent: Thursday, November 13, 2003 4:58 AM
> To: asrg@ietf.org
> Subject: Re: [Asrg] 6. Proposals - DNS-Based - LMAP]
> 
> 
> > The answer is that it will eliminate the worst types of 
> spam, impersonation
> > spam.
> 
> One point to consider: Anything that will eliminate 
> impersonation spam will
> also have a drastic effect on computer worms.  It might be 
> easier to push
> a solution that will not only help with one problem (spam) but another
> (worms) as well.  It will not eliminate either problem of 
> course, but it
> will help with both.
> 
> The reason this would work against worms is as follows: Many worms use
> the same methods as spamming software to forge the sender's identity,
> making it sometimes look to the recipient as if the sender is someone
> he already knows, this making it more likely he will believe 
> the message
> and open/execute the attachment, activating the worm.
> 
> The "worst" mail-borne worm incident was without any doubt the one
> involving W32/Sobig.F@mm.  That problem got "solved" on its 
> own, because the
> author included code to make the worm turn itself off globally on a 
> specific date.
> 
> What if the next worm author is not equally "considerate"?
> 
> If the worm would not have been able to forge the identity of 
> the sender,
> one can assume that fewer people would have fallen for it and fewer
> machines been infected and the problem would not have been as bad.
> 
> Therefore my suggestion is that anyone arguing for the implementation
> of LMAP should not only point out the benefit with regard to spam, but
> also the beneficial effects regarding worms.  This might for example
> make it easier to convince companies like Microsoft to endorse the
> proposal.
> 
> --
> Fridrik Skulason   Frisk Software International   phone: +354-540-7400
> Author of F-PROT   E-mail: frisk@f-prot.com       fax:   +354-540-7401
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
> 

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



From exim@www1.ietf.org  Tue Mar 30 18:42:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04432
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:42:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj7-0006ZK-13
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9QJ841L017776
	for asrg-archive@odin.ietf.org; Sun, 26 Oct 2003 14:08:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqFA-0004cV-B2
	for asrg-web-archive@optimus.ietf.org; Sun, 26 Oct 2003 14:08:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24681
	for <asrg-web-archive@ietf.org>; Sun, 26 Oct 2003 14:07:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqF7-0007e9-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:08:02 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqF7-0007e3-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:08:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqF7-0004Rm-Oq; Sun, 26 Oct 2003 14:08:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqEe-0004J2-Rs
	for asrg@optimus.ietf.org; Sun, 26 Oct 2003 14:07:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24663
	for <asrg@ietf.org>; Sun, 26 Oct 2003 14:07:20 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEc-0007de-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:07:30 -0500
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEb-0007da-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:07:29 -0500
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9QJ66CH038190;
	Sun, 26 Oct 2003 14:07:23 -0500 (EST)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002005bbc1b32e1101@[203.121.161.48]>
In-Reply-To: <3F9990A9.5070905@solidmatrix.com>
References: <3F9990A9.5070905@solidmatrix.com>
To: Yakov Shafranovich <research@solidmatrix.com>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: [Asrg] 7. BCP - Auto-Responders - IESG deadline on
 draft
Cc: ASRG list <asrg@ietf.org>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Mon, 27 Oct 2003 00:26:11 +0700

At 4:50 PM -0400 2003/10/24, Yakov Shafranovich wrote:

>  "Recommendations for Automatic Responses to Electronic Mail
>  (Proposed Standard)"
>
>  http://www.ietf.org/internet-drafts/draft-moore-auto-email-response-04.txt
>
>  Deadline for comments is October 31st, 2003, comments should be sent
>  to iesg@ietf.org or the main IETF list, ietf@ietf.org. Of course, a
>  discussion is welcome here but the IESG are the ones that need to hear
>  it.

	I've spoken to the author about this.  He has requested that all 
feedback be sent to ietf-822@imc.org, the mailing list where most of 
the discussion so far has taken place.  I hope to be able to forward 
to this mailing list the comments that we've seen so far, but it 
might be better for the people who've made those comments to do so 
themselves.

>  There are only a few days left for the comment period.

	Sorry, I've been unable to do as much as I should for the last 
several days.  I hope to be able to better address these issues this 
next week.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:42:57 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04468
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:42:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj7-0006WI-2y
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NCSF2c018354
	for asrg-archive@odin.ietf.org; Thu, 23 Oct 2003 08:28:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeZW-0004ka-Qd
	for asrg-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 08:28:10 -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 IAA15590
	for <asrg-web-archive@ietf.org>; Thu, 23 Oct 2003 08:27:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeZR-0006SG-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:28:05 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeZR-0006SB-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:28:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeZO-0004eh-QV; Thu, 23 Oct 2003 08:28:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYU-0004CA-Mi
	for asrg@optimus.ietf.org; Thu, 23 Oct 2003 08:27:06 -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 IAA15553
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:26:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYT-0006R9-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:27:05 -0400
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYT-0006R6-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:27:05 -0400
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9NCQYCD072103
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:27:00 -0400 (EDT)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002003bbbd752f4d57@[203.121.161.48]>
In-Reply-To: <20031022200147.GD16254@mail>
References: <p06002004bbbc7ec8e597@[200.10.10.62]>
 <20031022194603.5F58616FC7@jmason.org>
 <20031022200147.GD16254@mail>
To: "Asrg" <asrg@ietf.org>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: FW: [Asrg] 0. General
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Thu, 23 Oct 2003 19:23:08 +0700

At 4:01 PM -0400 2003/10/22, David Maxwell wrote:

>  If the choice is between 'all mail servers are open, and all users must
>  accept spam' and 'mail servers authenticate connections in some way, and
>  activists need to create their own infrastructure to get messages out' -
>  I'll pick the second.

	Would you be willing to bet your life on that?  The life of your 
family and friends?  Would you be willing to have them tortured to 
death while you watch, because you made this bet?

>  To _whom_ are the activists sending their messages? Are they spamming
>  them to random recipients, or to known contacts? If to known contacts,
>  why can't they use encryption to hide the content. If they're spamming
>  to unconsenting recipients, how is that any different (technically) from
>  commercial spam?

	Encryption is usually highly illegal (as in, a capital offense) 
in those places where the human rights workers are most likely to be 
needed.  Yes, they can use steganography techniques to try to hide 
the crypto, but they're still taking a serious risk.

	You get caught with this sort of stuff, and you get declared an 
enemy of the state, guilt of spying and high treason.  And then you 
get executed.

	That's after they torture you and make you watch while they 
torture your family and friends to death.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:43:58 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04712
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:43:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj5-0006a4-5A
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9QJ845b017791
	for asrg-archive@odin.ietf.org; Sun, 26 Oct 2003 14:08:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqFA-0004cs-Q0
	for asrg-web-archive@optimus.ietf.org; Sun, 26 Oct 2003 14:08:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24684
	for <asrg-web-archive@ietf.org>; Sun, 26 Oct 2003 14:07:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqF8-0007eI-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:08:02 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqF8-0007eD-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:08:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqF9-0004YC-B4; Sun, 26 Oct 2003 14:08:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqEo-0004M6-Rf
	for asrg@optimus.ietf.org; Sun, 26 Oct 2003 14:07:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24666
	for <asrg@ietf.org>; Sun, 26 Oct 2003 14:07:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEm-0007dn-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:07:40 -0500
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEl-0007dh-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:07:40 -0500
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9QJ66CJ038190;
	Sun, 26 Oct 2003 14:07:33 -0500 (EST)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002006bbc1b449537e@[203.121.161.48]>
In-Reply-To: <E1AD95H-0000Fu-00@mail.nitros9.org>
References: <E1AD95H-0000Fu-00@mail.nitros9.org>
To: "Alan DeKok" <aland@ox.org>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: 3. Requirements - Anonimity (was Re: FW: [Asrg] 0.
 General)
Cc: asrg@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Mon, 27 Oct 2003 00:29:52 +0700

At 5:02 PM -0400 2003/10/24, Alan DeKok wrote:

>    As I understand the RMX-style proposals, they do not remove any
>  anonymity.  They add accountability, but only under the mutual consent
>  of the message originator and recipient.  If the sender does not wish
>  to be accountable, they can choose to not send messages to the
>  recipient.

	If you don't want to be held accountable for telling the world 
about SARS II, you can choose not to speak.

	Sounds like a solution the Chinese government would love.

>    As was pointed out earlier, the "human rights activist" isn't
>  randomly spamming people.  Instead, (s)he's sending targeted messages
>  to people who want to receive them.  Mutual consent exists, so any
>  anonymity, privace, and accountability issues become whatever the two
>  parties agree to.

	How many recipients in this world have total control over the 
mail system that they use?  If the operator of their mail system 
chooses to filter all their mail through the Chinese government, what 
choice do they have?

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:44:16 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04763
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:44:15 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj4-0006ZK-U6
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NCRRT4016953
	for asrg-archive@odin.ietf.org; Thu, 23 Oct 2003 08:27:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYo-0004P6-Qj
	for asrg-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 08:27:26 -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 IAA15563
	for <asrg-web-archive@ietf.org>; Thu, 23 Oct 2003 08:27:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYn-0006RS-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:27:25 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYm-0006RK-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:27:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYP-0004BW-MQ; Thu, 23 Oct 2003 08:27:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeY5-00048J-SE
	for asrg@optimus.ietf.org; Thu, 23 Oct 2003 08:26:41 -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 IAA15539
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:26:31 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeY4-0006Qj-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:26:40 -0400
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeY3-0006Qg-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:26:40 -0400
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9NCQYC7072103
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:26:37 -0400 (EDT)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002000bbbd729eb35c@[203.121.161.48]>
In-Reply-To: <200310221522.AA392036500@mail.figuerres.com>
References: <200310221522.AA392036500@mail.figuerres.com>
To: "Asrg" <asrg@ietf.org>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: FW: [Asrg] 0. General
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Thu, 23 Oct 2003 19:22:26 +0700

At 3:22 PM -0400 2003/10/22, denny  wrote:

>  Well in part I will say that I have never sent an "Anon" email and
>  I would like to know just how "Anon" it is *unless* you have some kind
>  of "Man-in-the-middle" who changes the email headers to hide the sender.

	Okay, so for all the pieces of spam you have ever received, tell 
me precisely who sent each and every one of them.  Hell, just tell me 
who sent a random 1% sampling.

>  UA.o --> [ANON_SMTP_MANGLER] ---> DEST.MTA
>  where [ANON_SMTP_MANGLER] is a "Black box" to the reciver end but
>  has an address and can be found, may be more than one server, may
>  use more than one IP / server to do it's work.

	Penet.fi used to be thought of as a secure anonymous re-mailer, 
until recently it was discovered that they had been back-doored by 
the government.  So long as there are a countable number of anonymous 
remailers that you are dependant on to provide the only anonymizing 
services that exist, they can all be compromised.

>  so don't the senders of this email need to masq the content with say
>  PGP at the start??

	They may do that, but PGP allows you to sign first, and encrypt 
afterwards.  That means that the signer is not known, although you 
can tell what keys the message was encrypted for.  It also allows you 
to send encrypted messages that are not signed.  But if the sender 
can't send the encrypted message anonymously, then all that built-in 
privacy is blown.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:44:46 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04888
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:44:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj4-0006ZK-DL
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NCSWxe018957
	for asrg-archive@odin.ietf.org; Thu, 23 Oct 2003 08:28:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeZs-0004vQ-5m
	for asrg-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 08:28:32 -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 IAA15612
	for <asrg-web-archive@ietf.org>; Thu, 23 Oct 2003 08:28:18 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeZn-0006Ss-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:28:27 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeZm-0006So-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:28:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeZX-0004li-2V; Thu, 23 Oct 2003 08:28:11 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYz-0004Qd-O1
	for asrg@optimus.ietf.org; Thu, 23 Oct 2003 08:27:37 -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 IAA15573
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:27:27 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYy-0006Rp-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:27:36 -0400
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYy-0006Rj-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:27:36 -0400
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9NCQYCJ072103
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:27:30 -0400 (EDT)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002006bbbd7808f835@[203.121.161.48]>
In-Reply-To: <000001c39910$7167a450$df602241@viper1>
References: <000001c39910$7167a450$df602241@viper1>
To: "Asrg" <asrg@ietf.org>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: RE: [Asrg] postings double??
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Thu, 23 Oct 2003 19:21:54 +0700

At 10:50 PM -0400 2003/10/22, Denny Figuerres wrote:

>  The mailing list is a common place for us to exchange our comments
>  right?
>  Then reply to the list unless you want to start a "private" talk.

	Fair enough.

>  By the way IMHO the list is not sending the messages with the right
>  default:
>
>  The "Reply To"  should be to "the List" then you read, hit reply enter
>  comments and send.
>  Bingo everyone gets a copy and it's on the list.

	Wrong.  See <http://www.unicom.com/pw/reply-to-harmful.html>.

>  At least that's how I have seen serveral other lists work in the past...
>  And it was *MUCH* simpler.

	Those of us who have been in the business long enough to see 
severely broken MTAs (frequently from vendors like Lotus or 
Microsoft) will know that this is a bad idea.  Maybe somebody with 
more time on their hands will be able to explain to you the full 
depth of their broken-ness.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 18:48:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05761
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:48:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj1-0006a4-1l
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA69q3Qs013349
	for asrg-archive@odin.ietf.org; Thu, 6 Nov 2003 04:52:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgo7-0003TD-0E
	for asrg-web-archive@optimus.ietf.org; Thu, 06 Nov 2003 04:52:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA02051
	for <asrg-web-archive@ietf.org>; Thu, 6 Nov 2003 04:51:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgo3-00068o-00
	for asrg-web-archive@ietf.org; Thu, 06 Nov 2003 04:51:59 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgo3-00068l-00
	for asrg-web-archive@ietf.org; Thu, 06 Nov 2003 04:51:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgnH-00039s-4E; Thu, 06 Nov 2003 04:51:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AHgkS-0002eE-Qd
	for asrg@optimus.ietf.org; Thu, 06 Nov 2003 04:48:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01817
	for <asrg@ietf.org>; Thu, 6 Nov 2003 04:47:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgkI-00063j-00
	for asrg@ietf.org; Thu, 06 Nov 2003 04:48:06 -0500
Received: from argon.connectinternetsolutions.com ([193.110.243.33] helo=argon.connect.org.uk)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AHgkH-00063U-00
	for asrg@ietf.org; Thu, 06 Nov 2003 04:48:05 -0500
Received: from mmail by argon.connect.org.uk with local (connectmail/exim)
	id 1AHgk8-00064l-P8
	for asrg@ietf.org; Thu, 06 Nov 2003 09:47:56 +0000
In-Reply-To:  <E1AHbs0-0004HA-00@mail.nitros9.org>
Subject: Re: [Asrg] 1. Inventory of Problems - Input Needed 
To: "ASRG" <asrg@ietf.org>
From: "Jon Kyme" <jrk@merseymail.com>
X-Mailer: [ConnectMail 3.8.0]
X-connectmail-Originating-IP: 172.25.243.3
Message-Id: <E1AHgk8-00064l-P8@argon.connect.org.uk>
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/mail-archive/working-groups/asrg/>
Date: Thu, 06 Nov 2003 09:47:56 +0000

>   I believe that both the inventory of problems, and the technical
> considerations documents, are strongly related.  Both need more focus,
> and the diagrams in:
> 
> http://www.elan.net/~william/asrg-emailpathverification-presentation.pdf
> 
>   are a good start.
> 
>   That document needs to be expanded to talk about specific network
> configurations used to deliver mail, which protocols are involved
> where, and which fields of those protocols are open to what kind of
> abuse.  Once we have such a document, we can then proceed with
> "solving the problem in diagram X, protocol Y, abuse of field Z".
>

Isn't email path verification in the domain of the msgtrk group?
http://www.ietf.org/html.charters/msgtrk-charter.html
We don't wan't to duplicate this work do we - we'd like to refer to it I
guess.


Anyway - The inventory of problems really needs a wake-up and then some
editing and reformatting (?) what's the output to be? informational RFC? or
what?

I'd like to raise a couple of issues with it as it stands:
"False Claims - regarding opt-in" duplicates "Inadequate opt-in"
"Not a real business" doesn't seem to mean anything.







--

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



From exim@www1.ietf.org  Tue Mar 30 18:48:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05867
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:48:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj0-0006a4-Qb
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:50 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hACK4BDd018520
	for asrg-archive@odin.ietf.org; Wed, 12 Nov 2003 15:04:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1Dm-0004od-WC
	for asrg-web-archive@optimus.ietf.org; Wed, 12 Nov 2003 15:04:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04801
	for <asrg-web-archive@ietf.org>; Wed, 12 Nov 2003 15:03:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1Dj-0004tg-00
	for asrg-web-archive@ietf.org; Wed, 12 Nov 2003 15:04:07 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1Dj-0004td-00
	for asrg-web-archive@ietf.org; Wed, 12 Nov 2003 15:04:07 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1De-0004hF-Dd; Wed, 12 Nov 2003 15:04:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AK1D2-0004Vn-BT
	for asrg@optimus.ietf.org; Wed, 12 Nov 2003 15:03:25 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04699
	for <asrg@ietf.org>; Wed, 12 Nov 2003 15:03:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1Cy-0004rc-00
	for asrg@ietf.org; Wed, 12 Nov 2003 15:03:20 -0500
Received: from giles.striker.ottawa.on.ca
	([205.150.200.132] helo=mail.nitros9.org ident=root)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AK1Cy-0004rT-00
	for asrg@ietf.org; Wed, 12 Nov 2003 15:03:20 -0500
Received: from [127.0.0.1] (helo=giles.striker.ottawa.on.ca ident=aland)
	by mail.nitros9.org with esmtp (Exim 3.34 #1)
	id 1AK1Fv-0006Yx-00
	for asrg@ietf.org; Wed, 12 Nov 2003 15:06:23 -0500
From: "Alan DeKok" <aland@ox.org>
To: asrg@ietf.org
Subject: Re: [Asrg] 2a. Analysis - Spam Sample 
In-Reply-To: Your message of "Wed, 12 Nov 2003 14:51:48 EST."
             <3FB28F54.9070608@solidmatrix.com> 
Message-Id: <E1AK1Fv-0006Yx-00@mail.nitros9.org>
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/mail-archive/working-groups/asrg/>
Date: Wed, 12 Nov 2003 15:06:23 -0500

Yakov Shafranovich <research@solidmatrix.com> wrote:
> Below is a spam sample sent directly to the ASRG list and
> intercepted in the admin interface. My question to you is what
> purpose does this particular spam serve?

  Emotional satisfaction.

> Is this simply a case of two spammers fighting it out, or perhaps an
> attack on someone?

  Or crazy people.  It's happened before.

	http://www.jaedworks.com/shoebox/zumabot.html

  Usenet, Turkey, and Armenia...

  Alan DeKok.

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



From exim@www1.ietf.org  Tue Mar 30 18:54:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21670
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 17:55:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rjd-0006ZK-Dh
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:29 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IHwY9H011199
	for asrg-archive@odin.ietf.org; Thu, 18 Mar 2004 12:58:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41ms-0002uY-5m
	for asrg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 12:58:34 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27649
	for <asrg-web-archive@ietf.org>; Thu, 18 Mar 2004 12:58:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41mq-0007ND-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:58:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41m2-0007Ka-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:57:42 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41lO-0007HS-00
	for asrg-web-archive@ietf.org; Thu, 18 Mar 2004 12:57:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41lO-0002S2-7b; Thu, 18 Mar 2004 12:57:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41aB-0000tK-HL
	for asrg@optimus.ietf.org; Thu, 18 Mar 2004 12:45:27 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26692
	for <asrg@ietf.org>; Thu, 18 Mar 2004 12:45:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41a9-0006PE-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:45:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41ZC-0006NH-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:44:26 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41YG-0006MM-00
	for asrg@ietf.org; Thu, 18 Mar 2004 12:43:28 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B41YD-0007C5-00; Thu, 18 Mar 2004 12:43:25 -0500
Received: from [68.244.172.97] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B41YC-0001bi-00; Thu, 18 Mar 2004 12:43:25 -0500
Message-ID: <4059DFAB.6030307@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
CC: "Anne P. Mitchell, Esq." <amitchell@isipp.com>, asrg@ietf.org
Subject: Re: [Asrg] Update on Querying IADB
References: <C6DDA43B91BFDA49AA2F1E473732113E5DBA55@mou1wnexm05.vcorp.ad.vrsn.com>
In-Reply-To: <C6DDA43B91BFDA49AA2F1E473732113E5DBA55@mou1wnexm05.vcorp.ad.vrsn.com>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Thu, 18 Mar 2004 12:43:07 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hallam-Baker, Phillip wrote:
> I agree with Yakov here, the A record convention is widely used it has
> become a defacto extension to the specs. But the data being exchanged is
> essentially binary in nature.
> 
> Anne's proposal strikes me as trying to use the A record to do far too much.
> Once you start to try to move that amount of data it would be better to move
> to using the TXT record or get a whole new RR defined. As long as the
> overall record is shorter than 512 bytes there is no impact on performance.
> 

This issue is not limited to IADB, rather there are existing blacklists 
as well such as SORBS that are extending the original DNSBL protocol to 
do extra stuff. All of this can benefit from standards.

> This has another concrete benefit, the need for ad-hoc extensions of the
> code set as new accrediting agencies appear goes away. 
> 
> The big difference between Anne's approach and mine is that I am proposing
> that the accreditation data be separated into two parts, the accreditations
> themselves and a single master record that describes the accreditation
> service.
> 
> This ties in with what I think would be the data structures that filters
> would build up. Each accreditation service being tracked would be
> represented by some sort of master record that described the current
> evaluation of the service. The description provided by the service would
> provide part of that record, measurements of the performance of the service
> would then be added in.

Do you think that both parts need to be standardized?

Yakov

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



From exim@www1.ietf.org  Tue Mar 30 19:22:53 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02193
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:34:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8RjG-0006WI-9k
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:29:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hB1NguTq016845
	for asrg-archive@odin.ietf.org; Mon, 1 Dec 2003 18:42:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQxgu-0004NQ-7d
	for asrg-web-archive@optimus.ietf.org; Mon, 01 Dec 2003 18:42:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12060
	for <asrg-web-archive@ietf.org>; Mon, 1 Dec 2003 18:42:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQxgq-0005fP-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 18:42:52 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQxgo-0005fE-00
	for asrg-web-archive@ietf.org; Mon, 01 Dec 2003 18:42:52 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQxg1-0004Hh-79; Mon, 01 Dec 2003 18:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AQxfI-0004Fh-Dp
	for asrg@optimus.ietf.org; Mon, 01 Dec 2003 18:41:16 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11989
	for <asrg@ietf.org>; Mon, 1 Dec 2003 18:40:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQxfF-0005eT-00
	for asrg@ietf.org; Mon, 01 Dec 2003 18:41:13 -0500
Received: from mail.chariot.net.au ([203.87.95.38])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AQxfE-0005eP-00
	for asrg@ietf.org; Mon, 01 Dec 2003 18:41:12 -0500
Received: from rebel (ppp-069.cust203-87-110.ghr.chariot.net.au [203.87.110.69])
	by mail.chariot.net.au (Postfix) with SMTP
	id 3E93A5F83A; Tue,  2 Dec 2003 10:11:07 +1030 (CST)
From: "Chris" <asrg@rebel.com.au>
To: "Yakov Shafranovich" <research@solidmatrix.com>,
        "Chris" <asrg@rebel.com.au>
Cc: "Fridrik Skulason" <frisk@f-prot.com>, <asrg@ietf.org>
Subject: RE: [Asrg] 4. Survey of Solutions - Methods of Authentication -Trojans]
Message-ID: <GPEMJLCHICHEGPOKJHHDKEFJGNAA.asrg@rebel.com.au>
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 IMO, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <3FCB47AC.3070502@solidmatrix.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
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/mail-archive/working-groups/asrg/>
Date: Tue, 2 Dec 2003 10:14:53 +1030
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yakov wrote...

> This issues has been raised before. It is out of the scope of our group
> to consider how to solve the problem with zombies or trojans.

I totally agree with you

thats why I wrote...

>
> FIRST lets close the open system, not keep on thinking of reasons to boo
hoo
> legitimate ideas.
>

Trojans are another issue entirely.

Regards
Chris


> -----Original Message-----
> From: yshafranovich02@sprintpcs.com
> [mailto:yshafranovich02@sprintpcs.com]On Behalf Of Yakov Shafranovich
> Sent: Tuesday, December 02, 2003 12:23 AM
> To: Chris
> Cc: Fridrik Skulason; asrg@ietf.org
> Subject: Re: [Asrg] 4. Survey of Solutions - Methods of Authentication
> -Trojans]
>
>
> This issues has been raised before. It is out of the scope of our group
> to consider how to solve the problem with zombies or trojans. While
> there are some proposals (MTA MARK) that address the issue, it is
> addresses within the realm of dealing with spam.
>
> Yakov
>
> Chris wrote:
> >
> >>I am not sure how high the percentage of spam from zombie machines is,
> >>but it is growing...that much is certain.
> >>
> >
> >
> > Yes it is growing, but will it ever reach the proportions of todays mass
> > mailing?
> >
> > I sincerley doubt it. not even 100th of todays spam
> >
> > the other problem is that in effect we can never stop
> compromised machines
> > therefore we can never stop spam. so should we give up?
> >
> > We currently have spammers who have an open system. they can
> get bulkmail
> > software from anywhere.
> >
> > But to trojan a machine to send spam. no way that becomes a
> federal crime,
> > and today I believe it can be even classed as an act of terrorism.
> >
> > FIRST lets close the open system, not keep on thinking of
> reasons to boo hoo
> > legitimate ideas.
> >
> > then rename the ASRG to the ATRG (Anti Trojan Research group)
> >
> > Chris
> >
> >
> >>-----Original Message-----
> >>From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org]On Behalf Of
> >>Fridrik Skulason
> >>Sent: 1 December 2003 7:31 PM
> >>To: asrg@ietf.org
> >>Subject: Re: [Asrg] 4. Survey of Solutions - Methods of Authentication
> >>-Trojans]
> >>
> >>
> >>
> >>>If anyone think spammers will move en masse to trojan systems
> >>
> >>to continue
> >>
> >>>their habit, I believe they are sadly mistaken.
> >>
> >>I wouldn't be too sure about that.  I am looking at this problem from a
> >>anti-virus/anti-trojan perspective, and what I am seeing is the
> >>establisnment
> >>of several networks of "zombies", used for spam-related purposes - not
> >>only spamming, but also DoS attacks on anti-spam sites.
> >>
> >>The connection between spammers and compromised machines is becoming
> >>clearer and clearer.
> >>
> >>The spammers that just buy spam software from companies like
> >>www.saurabh.info,
> >>www.marketing-2000.net, www.massmailsoftware.com or other similar
> >>companies
> >>do not use the zombie nets, that's true...you have to look elsewhere,
> >>for example at the spammers with connections to the Russian criminal
> >>underground.
> >>
> >>I am not sure how high the percentage of spam from zombie machines is,
> >>but it is growing...that much is certain.
> >>
> -------
> Yakov Shafranovich / asrg <at> shaftek.org
> SolidMatrix Technologies, Inc. / research <at> solidmatrix.com
> "Power tends to corrupt, and absolute power corrupts absolutely" (Lord
> Acton)
> -------
>


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



From exim@www1.ietf.org  Tue Mar 30 19:29:35 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04715
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:43:58 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj5-0006a4-2x
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:55 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9QJ84IW017761
	for asrg-archive@odin.ietf.org; Sun, 26 Oct 2003 14:08:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqFA-0004cO-5W
	for asrg-web-archive@optimus.ietf.org; Sun, 26 Oct 2003 14:08:04 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24678
	for <asrg-web-archive@ietf.org>; Sun, 26 Oct 2003 14:07:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqF7-0007e2-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:08:01 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqF7-0007dy-00
	for asrg-web-archive@ietf.org; Sun, 26 Oct 2003 14:08:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqF7-0004Re-8t; Sun, 26 Oct 2003 14:08:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ADqEM-00040R-Lc
	for asrg@optimus.ietf.org; Sun, 26 Oct 2003 14:07:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24647
	for <asrg@ietf.org>; Sun, 26 Oct 2003 14:07:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEK-0007d2-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:07:12 -0500
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ADqEJ-0007cw-00
	for asrg@ietf.org; Sun, 26 Oct 2003 14:07:11 -0500
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9QJ66CF038190;
	Sun, 26 Oct 2003 14:07:06 -0500 (EST)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002004bbc1b190b014@[203.121.161.48]>
In-Reply-To: <E1AD8rD-0000Ej-00@mail.nitros9.org>
References: <E1AD8rD-0000Ej-00@mail.nitros9.org>
To: "Alan DeKok" <aland@ox.org>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: 3. Requirements - Anonimity (was Re: FW: [Asrg] 0.
 General)
Cc: asrg@ietf.org
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Mon, 27 Oct 2003 00:21:35 +0700

At 4:48 PM -0400 2003/10/24, Alan DeKok wrote:

>    My concern is that I don't see a requirement that SMTP should solve
>  all of the worlds problems.  I understand that SMTP should not
>  *remove* peoples privacy and anonymity.  But there is no requirement
>  (and there SHOULD be no requirement) that SMTP creates privacy and
>  anonymity, where there was none before.

	The problem is that the SMTP protocol exists, and in its current 
form, there are a number of "features" which can be extracted.  We're 
here to try to address some of these "features", which have 
manifested themselves as spam.  However, there are other groups in 
the world that have become dependant on some of these features (which 
may or may not overlap with the "spam" features).

	If we're going to talk about changing the SMTP protocol, or how 
we recommend that people administrate their mail servers which 
operate under the SMTP protocol, we need to be aware of these other 
uses of the protocol, and we need to be explicit in how our suggested 
changes may impact these other uses.

>    Further, I believe that the emotional appeal to human rights workers
>  is inappropriate in a professional forum.  Arguments of the form "If
>  you're for proposal X, then you're for killing people!" should be
>  explicitly outside of the scope of ASRG.

	I didn't say "If you're for proposal X, then you're for killing 
people!"  That is an unwarranted and inappropriate mis-representation 
of my statement.

	What I said was "Would you be willing to bet your life on that?" 
This is a very different statement.


	We're talking about making changes to the SMTP protocol (or the 
implementation thereof) which could have a profound effect on the 
lives of people around the world.

	Many people's lives could literally be at stake here, and no one 
has given any consideration to how they could be affected by the 
kinds of things we're talking about.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Tue Mar 30 19:34:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04891
	for <asrg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:44:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Rj3-0006ZK-S7
	for asrg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:54 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id h9NCRRdS016952
	for asrg-archive@odin.ietf.org; Thu, 23 Oct 2003 08:27:27 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYo-0004P9-Qh
	for asrg-web-archive@optimus.ietf.org; Thu, 23 Oct 2003 08:27:26 -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 IAA15565
	for <asrg-web-archive@ietf.org>; Thu, 23 Oct 2003 08:27:16 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYn-0006RU-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:27:25 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYm-0006RL-00
	for asrg-web-archive@ietf.org; Thu, 23 Oct 2003 08:27:24 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYQ-0004Br-Ri; Thu, 23 Oct 2003 08:27:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ACeYO-0004Ap-Bb
	for asrg@optimus.ietf.org; Thu, 23 Oct 2003 08:27:00 -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 IAA15545
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:26:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYK-0006Qv-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:26:56 -0400
Received: from vhost109.his.com ([216.194.225.101])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ACeYJ-0006Qs-00
	for asrg@ietf.org; Thu, 23 Oct 2003 08:26:55 -0400
Received: from [203.121.161.43] (localhost.his.com [127.0.0.1])
	by vhost109.his.com (8.12.6p3/8.12.3) with ESMTP id h9NCQYCB072103
	for <asrg@ietf.org>; Thu, 23 Oct 2003 08:26:51 -0400 (EDT)
	(envelope-from brad.knowles@skynet.be)
Mime-Version: 1.0
X-Sender: bs663385@pop.skynet.be
Message-Id: <p06002002bbbd745a1b6c@[203.121.161.48]>
In-Reply-To: <20031022194603.5F58616FC7@jmason.org>
References: <20031022194603.5F58616FC7@jmason.org>
To: "Asrg" <asrg@ietf.org>
From: Brad Knowles <brad.knowles@skynet.be>
Subject: Re: FW: [Asrg] 0. General
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
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/mail-archive/working-groups/asrg/>
Date: Thu, 23 Oct 2003 19:22:54 +0700

At 12:45 PM -0700 2003/10/22, Justin Mason wrote:

>  But IMO, something like the PGP remailers and/or hushmail are the key
>  systems to support this form of free speech -- it should *not* be part of
>  the core SMTP protocol.  Here's why:

	I disagree.  They are an important tool in the toolbox, but alone 
they are not sufficient to guarantee the security and privacy of that 
connection.  Until recently, penet.fi was believed to be a secure 
anonymous remailer -- until we found out that they'd been back-doored 
by the government.  Who knows how many other remailers have already 
been back-doored?

	Moreover, you don't need to completely back-door the remailer to 
compromise them -- you can watch traffic coming in and going out, and 
that alone will often tell you enough.  And there's no way that the 
remailers could prevent people from watching all incoming and 
outgoing traffic.

>  These can be volume-throttled, do not provide spammable bandwidth, or use
>  CAPTCHAs, so they become useless for bulk mail spamming -- but remain
>  *very* useful for free speech, since they *are* fully encrypted and
>  *designed* for whistleblowing activity.

	They remain very useful, so long as other options are not 
expressly eliminated by the protocol.  Once that happens, they become 
extremely vulnerable.

-- 
Brad Knowles, <brad.knowles@skynet.be>

"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
     -Benjamin Franklin, Historical Review of Pennsylvania.

GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+
!w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++)
tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)

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



From exim@www1.ietf.org  Wed Mar 31 00:39:27 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29611
	for <asrg-archive@odin.ietf.org>; Wed, 31 Mar 2004 00:39:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8YRJ-0003k4-Jp
	for asrg-archive@odin.ietf.org; Wed, 31 Mar 2004 00:39:01 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2V5d1YY014384
	for asrg-archive@odin.ietf.org; Wed, 31 Mar 2004 00:39:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8YRJ-0003jv-Fx
	for asrg-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 00:39:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29596
	for <asrg-web-archive@ietf.org>; Wed, 31 Mar 2004 00:38:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8YRG-0006Ik-00
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 00:38:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8YQK-0006EV-00
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 00:38:01 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8YPS-0006Al-00
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 00:37:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8YPN-0003E2-CX; Wed, 31 Mar 2004 00:37:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8YOU-0003Ak-Bw
	for asrg@optimus.ietf.org; Wed, 31 Mar 2004 00:36:06 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29516
	for <asrg@ietf.org>; Wed, 31 Mar 2004 00:36:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8YOR-00065v-00
	for asrg@ietf.org; Wed, 31 Mar 2004 00:36:03 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8YNS-00061s-00
	for asrg@ietf.org; Wed, 31 Mar 2004 00:35:03 -0500
Received: from mail1.panix.com ([166.84.1.72])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8YMv-0005y5-00
	for asrg@ietf.org; Wed, 31 Mar 2004 00:34:29 -0500
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail1.panix.com (Postfix) with ESMTP id 0DBFC489DB
	for <asrg@ietf.org>; Wed, 31 Mar 2004 00:34:29 -0500 (EST)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p2-a/8.8.8/PanixN1.1) id i2V5YS326966;
	Wed, 31 Mar 2004 00:34:28 -0500 (EST)
Message-Id: <200403310534.i2V5YS326966@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <406A4977.9080709@elvey.com> (message from Matthew Elvey on Tue,
	30 Mar 2004 20:30:47 -0800)
Subject: Re: [Asrg] spf
References: <406544E0.5420.2D654D3@localhost> <406A4977.9080709@elvey.com>
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/mail-archive/working-groups/asrg/>
Date: Wed, 31 Mar 2004 00:34:28 -0500 (EST)
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Matthew Elvey <matthew@elvey.com> wrote:
> On 3/27/2004 4:09 AM, spharion@directnet.com.br sent forth electrons to 
> convey:
>
>> this is a tentative option to spf, but does not
>> seem to break forwarding:
>>
>> http://nucleo.freeservers.com/mba/

> Interesting idea with probably fatal flaws.
> Maintaining a dynamic database is much harder than a static one, but 
> that's a minor issue.
> SPF allows mail to be authorized from servers that the domain in 
> question doesn't trust to do anything more than not spam.
> This proposal would require they be able to alter the database on the 
> DNS server!  Tricky.

That could be avoided via indirection; that is, if bobsite.tld is set
to trust panix.com, it could set an indirect record that says in
effect "Also look for _mba.bobsite.tld._indirectmba.panix.com".

However, that does break forwarding: the typical forwarding case is
one unpriveleged user at ISP1 has a mail account at ISP2 that he sets
to forward.  It is clearly not the case that everybody who sends mail
to him at ISP2 is willing to trust ISP2.  Nor is it necessarily the
case that even ISP1 is willing to trust ISP2, except for that one
user.

I don't see any way to handle that case with _mba.

Seth

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



From exim@www1.ietf.org  Wed Mar 31 00:42:34 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29893
	for <asrg-archive@odin.ietf.org>; Wed, 31 Mar 2004 00:42:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8YUJ-0003uh-DC
	for asrg-archive@odin.ietf.org; Wed, 31 Mar 2004 00:42:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2V5g7DC015039
	for asrg-archive@odin.ietf.org; Wed, 31 Mar 2004 00:42:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8YUJ-0003uQ-8g
	for asrg-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 00:42:07 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA29761
	for <asrg-web-archive@ietf.org>; Wed, 31 Mar 2004 00:42:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8YUG-0006nR-00
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 00:42:04 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8YSr-0006VR-00
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 00:40:38 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8YRm-0006Lp-03
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 00:39:30 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B8YDP-0006dR-W0
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 00:24:41 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8YCu-0001p0-JN; Wed, 31 Mar 2004 00:24:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8XS9-0006wT-Q2
	for asrg@optimus.ietf.org; Tue, 30 Mar 2004 23:35:50 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26234
	for <asrg@ietf.org>; Tue, 30 Mar 2004 23:35:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8XS7-00001k-00
	for asrg@ietf.org; Tue, 30 Mar 2004 23:35:47 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8XRD-0007gy-00
	for asrg@ietf.org; Tue, 30 Mar 2004 23:34:52 -0500
Received: from out2.smtp.messagingengine.com ([66.111.4.26])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8XQE-0007Vp-00
	for asrg@ietf.org; Tue, 30 Mar 2004 23:33:50 -0500
X-Sasl-enc: pcxgyjcdVxWFuEXh8Yt6rA 1080707450
Received: from elvey.com (ns.nextbus.com [64.164.28.194])
	by mail.messagingengine.com (Postfix) with ESMTP id D7EAD8DDA1B;
	Tue, 30 Mar 2004 23:30:49 -0500 (EST)
Message-ID: <406A4977.9080709@elvey.com>
From: Matthew Elvey <matthew@elvey.com>
User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: spharion@directnet.com.br
Cc: asrg@ietf.org
Subject: Re: [Asrg] spf
References: <406544E0.5420.2D654D3@localhost>
In-Reply-To: <406544E0.5420.2D654D3@localhost>
X-Habeas-SWE-1: winter into spring
X-Habeas-SWE-2: brightly anticipated
X-Habeas-SWE-3: like Habeas SWE (tm)
X-Habeas-SWE-4: Copyright 2002 Habeas (tm)
X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this
X-Habeas-SWE-6: email in exchange for a license for this Habeas
X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant
X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this
X-Habeas-SWE-9: mark in spam to <http://www.habeas.com/report/>.
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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/mail-archive/working-groups/asrg/>
Date: Tue, 30 Mar 2004 20:30:47 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=-8.0 required=5.0 tests=HABEAS_SWE autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On 3/27/2004 4:09 AM, spharion@directnet.com.br sent forth electrons to 
convey:

> this is a tentative option to spf, but does not
> seem to break forwarding:
>
> http://nucleo.freeservers.com/mba/
>
> have fun. gone, ricardo.
>
>
Interesting idea with probably fatal flaws.
Maintaining a dynamic database is much harder than a static one, but 
that's a minor issue.
SPF allows mail to be authorized from servers that the domain in 
question doesn't trust to do anything more than not spam.
This proposal would require they be able to alter the database on the 
DNS server!  Tricky.
E.g. I could set my SPF record to allow mail.panix.com to send email as 
elvey.com.  But then panix.com has to be willing and able to alter the 
elvey.com dns servers, and they have to be willing and able to allow 
it.  And I don't control either set of servers enough to make 'em do that.
Seems to me more effort than SRS/VERP, with approximately the same result.
All a domain's DNS servers have to be constantly syncing.  How would 
that happen?

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



From exim@www1.ietf.org  Wed Mar 31 12:40:42 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03574
	for <asrg-archive@odin.ietf.org>; Wed, 31 Mar 2004 12:40:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8jhH-0005kN-O9
	for asrg-archive@odin.ietf.org; Wed, 31 Mar 2004 12:40:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2VHeF84022087
	for asrg-archive@odin.ietf.org; Wed, 31 Mar 2004 12:40:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8jhH-0005kA-Ju
	for asrg-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 12:40:15 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03549
	for <asrg-web-archive@ietf.org>; Wed, 31 Mar 2004 12:40:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8jhG-0006Di-00
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 12:40:14 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8jgO-0006AH-00
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 12:39:21 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8jfd-00066r-00
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 12:38:33 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8jf6-0005R3-Ar; Wed, 31 Mar 2004 12:38:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8jeG-00058j-T0
	for asrg@optimus.ietf.org; Wed, 31 Mar 2004 12:37:08 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03343
	for <asrg@ietf.org>; Wed, 31 Mar 2004 12:37:04 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8jeF-00060I-00
	for asrg@ietf.org; Wed, 31 Mar 2004 12:37:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8jMx-0004tQ-00
	for asrg@ietf.org; Wed, 31 Mar 2004 12:19:16 -0500
Received: from a.mail.sonic.net ([64.142.16.245])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8jM6-0004oJ-00
	for asrg@ietf.org; Wed, 31 Mar 2004 12:18:22 -0500
Received: from [192.168.0.247] (adsl-64-165-36-235.dsl.snfc21.pacbell.net [64.165.36.235])
	(authenticated bits=0)
	by a.mail.sonic.net (8.12.11/8.12.11) with ESMTP id i2VHHpaM025417
	for <asrg@ietf.org>; Wed, 31 Mar 2004 09:17:51 -0800
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <20040331170010.7359.44428.Mailman@www1.ietf.org>
References: <20040331170010.7359.44428.Mailman@www1.ietf.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <56D2F516-8337-11D8-A54B-000A95AC5778@isipp.com>
Content-Transfer-Encoding: 7bit
From: "Anne P. Mitchell, Esq." <amitchell@isipp.com>
To: asrg@ietf.org
X-Mailer: Apple Mail (2.613)
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Update on Querying IADB
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/mail-archive/working-groups/asrg/>
Date: Wed, 31 Mar 2004 09:17:51 -0800
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL,OPT_IN_CAPS autolearn=no 
	version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

For those who are interested, IADB has been online for about a month 
now, and is fully operational.  We presently have listees accounting 
for approximately 100milliion pieces of email per month, and sites 
querying representing about 30million email boxes (not counting the two 
of the top 4 US ISPs to whom we spoon feed relevant listee data).

Querying remains free (and always will).

Data returned in response to a query to IADB now includes:

SPF publication status
Microsoft Caller I.D. for Email status
Level of Opt-In of mailing list mail
Whether they are vouched for by ISIPP
Participation in Bonded Sender
Participation in Habeas
Participation in EDDB
Participation in EPIA

(http://www.isipp.com/iadb.php and http://www.isipp.com/iadbquery.php)

Aggregate scores returned by IADB2 of a score of 30 or more is 
generally a sign of a responsible mailer  unlikely to be sending spam;  
a score of 50 or more is considered to have a high correlation to 
confirmed opt-in practices, or other such high standards as to be 
functionally equivalent.

http://www.isipp.com/iadb2codes.php


Anne


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



From exim@www1.ietf.org  Wed Mar 31 17:24:23 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16631
	for <asrg-archive@odin.ietf.org>; Wed, 31 Mar 2004 17:24:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8o7o-0004NG-HB
	for asrg-archive@odin.ietf.org; Wed, 31 Mar 2004 17:23:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2VMNuIO016814
	for asrg-archive@odin.ietf.org; Wed, 31 Mar 2004 17:23:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8o7n-0004N7-PP
	for asrg-web-archive@optimus.ietf.org; Wed, 31 Mar 2004 17:23:55 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16585
	for <asrg-web-archive@ietf.org>; Wed, 31 Mar 2004 17:23:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8o7l-0006Nw-00
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 17:23:53 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8o6g-0006HB-00
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 17:22:46 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8o5a-0006BT-00
	for asrg-web-archive@ietf.org; Wed, 31 Mar 2004 17:21:38 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8o50-0003ve-6S; Wed, 31 Mar 2004 17:21:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8o3n-0003bv-1W
	for asrg@optimus.ietf.org; Wed, 31 Mar 2004 17:19:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16360
	for <asrg@ietf.org>; Wed, 31 Mar 2004 17:19:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8o3k-00061K-00
	for asrg@ietf.org; Wed, 31 Mar 2004 17:19:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B8o2y-0005yZ-00
	for asrg@ietf.org; Wed, 31 Mar 2004 17:18:57 -0500
Received: from mout.perfora.net ([217.160.230.41])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B8o2P-0005tC-00
	for asrg@ietf.org; Wed, 31 Mar 2004 17:18:21 -0500
Received: from [217.160.230.52] (helo=smtp.perfora.net)
	by mout.perfora.net with esmtp (Exim 3.35 #1)
	id 1B8o2P-0005UX-00
	for asrg@ietf.org; Wed, 31 Mar 2004 17:18:21 -0500
Received: from [67.87.146.106] (helo=solidmatrix.com)
	by smtp.perfora.net with asmtp (TLSv1:RC4-MD5:128)
	(Exim 3.35 #1)
	id 1B8o2P-0005Q9-00
	for asrg@ietf.org; Wed, 31 Mar 2004 17:18:21 -0500
Message-ID: <406B43AE.4000408@solidmatrix.com>
From: Yakov Shafranovich <research@solidmatrix.com>
Organization: SolidMatrix Technologies, Inc.
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en, he, ru
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
X-Enigmail-Version: 0.83.2.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Asrg] 0. General - FCC and mobile spam followup
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/mail-archive/working-groups/asrg/>
Date: Wed, 31 Mar 2004 17:18:22 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

The FCC published details of its proposed rulemaking for wireless spam:

A good place to begin is the public-interest Washington Internet Project
web site, at http://www.cybertelecom.org/Spam.htm#04-52  The link to the
46-page Notice of Proposed Rule Making is on the right side of the page.

Above that, in the upper right corner, are links to more information on
how to participate in the FCC proceeding process and a link to more
information on the FCC's Electronic Comment Filing System (ECFS).  Note
that comments for this proceeding can also be filed using ECFS Express,
at http://gullfoss2.fcc.gov/ecfs/Upload/

If you go to the ECFS search page
http://gullfoss2.fcc.gov/prod/ecfs/comsrch_v2.cgi and search on the
proceeding "04-53" you'll be able to track all the public comments as
they are filed.



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



