From asrg-bounces@ietf.org  Fri Apr  1 10:06:26 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02325
	for <asrg-web-archive@ietf.org>; Fri, 1 Apr 2005 10:06:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHNqV-0005fZ-2n
	for asrg-web-archive@ietf.org; Fri, 01 Apr 2005 10:14:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHNey-0006H5-UF; Fri, 01 Apr 2005 10:02:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHNew-0006H0-T1
	for asrg@megatron.ietf.org; Fri, 01 Apr 2005 10:02:06 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02046
	for <Asrg@ietf.org>; Fri, 1 Apr 2005 10:02:04 -0500 (EST)
Received: from mx2.nic.fr ([192.134.4.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHNmG-0005XE-SH
	for Asrg@ietf.org; Fri, 01 Apr 2005 10:09:42 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx2.nic.fr (Postfix) with ESMTP id EF14426C0E2
	for <Asrg@ietf.org>; Fri,  1 Apr 2005 17:01:58 +0200 (CEST)
Received: from maya40.nic.fr (maya40.nic.fr [192.134.4.151])
	by mx2.nic.fr (Postfix) with ESMTP id B4D8D26C0C8
	for <Asrg@ietf.org>; Fri,  1 Apr 2005 17:01:57 +0200 (CEST)
Received: from batilda.nic.fr (postfix@batilda.nic.fr [192.134.4.69])
	by maya40.nic.fr (8.12.4/8.12.4) with ESMTP id j31F0jIm615644
	for <Asrg@ietf.org>; Fri, 1 Apr 2005 17:00:46 +0200 (CEST)
Received: by batilda.nic.fr (Postfix, from userid 1000)
	id 701BF16A9E5; Fri,  1 Apr 2005 17:01:57 +0200 (CEST)
Date: Fri, 1 Apr 2005 17:01:57 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Asrg@ietf.org
Message-ID: <20050401150157.GA19693@nic.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux 3.1
X-Kernel: Linux 2.6.8-2-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new at mx2.nic.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014
Subject: [Asrg] [draft-irtf-asrg-iar-howe-siq-01] Why not DNS?
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2

The draft seems to reivent the wheel with a new lightweight protocol
but the Rationale section does not address at all an obvious
alternative: the use of the DNS (like all RBLs currently do).

It is specially strange that the draft reuses HTTP (without regard to
RFC 3205) but does not reuse DNS, which already provides the needed
features.



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


From asrg-bounces@ietf.org  Fri Apr  1 10:09:00 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02581
	for <asrg-web-archive@ietf.org>; Fri, 1 Apr 2005 10:09:00 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DHNsy-0005l9-Ga
	for asrg-web-archive@ietf.org; Fri, 01 Apr 2005 10:16:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DHNjC-0006kl-9j; Fri, 01 Apr 2005 10:06:30 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DHNjB-0006ke-BU
	for asrg@megatron.ietf.org; Fri, 01 Apr 2005 10:06:29 -0500
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02337
	for <Asrg@ietf.org>; Fri, 1 Apr 2005 10:06:27 -0500 (EST)
Received: from mx2.nic.fr ([192.134.4.11])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DHNqW-0005ff-LH
	for Asrg@ietf.org; Fri, 01 Apr 2005 10:14:04 -0500
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mx2.nic.fr (Postfix) with ESMTP id BD64526C0E1
	for <Asrg@ietf.org>; Fri,  1 Apr 2005 17:06:27 +0200 (CEST)
Received: from maya40.nic.fr (maya40.nic.fr [192.134.4.151])
	by mx2.nic.fr (Postfix) with ESMTP id 8396C26C0C8
	for <Asrg@ietf.org>; Fri,  1 Apr 2005 17:06:26 +0200 (CEST)
Received: from batilda.nic.fr (postfix@batilda.nic.fr [192.134.4.69])
	by maya40.nic.fr (8.12.4/8.12.4) with ESMTP id j31F5EIm616812
	for <Asrg@ietf.org>; Fri, 1 Apr 2005 17:05:14 +0200 (CEST)
Received: by batilda.nic.fr (Postfix, from userid 1000)
	id 716B016A9E5; Fri,  1 Apr 2005 17:06:26 +0200 (CEST)
Date: Fri, 1 Apr 2005 17:06:26 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Asrg@ietf.org
Message-ID: <20050401150626.GA19961@nic.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux 3.1
X-Kernel: Linux 2.6.8-2-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new at mx2.nic.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Subject: [Asrg] [draft-irtf-asrg-iar-howe-siq-01] Privacy issues
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

6. Security Considerations

[...]

   The information passed using either the UDP packet queries or HTTP
   queries, such as the combination of sender's IP, MAIL FROM, and the
   RCPT TO domain may pose some privacy issues. Similar information
   already appears in message trace headers and those headers may have
   already been viewed and logged by intermediate MX servers during
   transit. Taking this perspective, the queries make use of
   information that may have already been revealed else where.

   However, with today's Internet privacy paranoia, a SIQ client MAY
   choose to make HTTP queries over a TLS/SSL connection at the sake
   of the speed and convenience offered by UDP queries or unencrypted
   HTTP queries.

********************

These two paragraphs should be deleted, not only because they
disregard privacy concerns as "paranoia" but also because they miss
the point: the problem is not with a sniffer between the SIQ client
and the SIQ server but with the SIQ server itself.

The SIQ server will learn a lot about the mail use of its
clients. The information you leak to a SIQ server is quite sensitive
and this is what should be mentioned in "Security Considerations".

For instance, one of the reasons many people copy locally DNS RBLs
(with AXFR or rsync or else) is to avoid this problem. (The SIQ
protocol does not seem to provide bulk transfer.)


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


From asrg-bounces@ietf.org  Mon Apr  4 19:13:54 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23765
	for <asrg-web-archive@ietf.org>; Mon, 4 Apr 2005 19:13:54 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DIatb-0005eW-J7
	for asrg-web-archive@ietf.org; Mon, 04 Apr 2005 19:22:15 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIaim-0003WO-5g; Mon, 04 Apr 2005 19:11:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DIaik-0003WD-17
	for asrg@megatron.ietf.org; Mon, 04 Apr 2005 19:11:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23534
	for <asrg@ietf.org>; Mon, 4 Apr 2005 19:10:58 -0400 (EDT)
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DIaqk-0005Xk-Kw
	for asrg@ietf.org; Mon, 04 Apr 2005 19:19:19 -0400
Received: (qmail 74738 invoked by uid 1013); 4 Apr 2005 23:10:58 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=testkey; d=space.net;
	b=qcx5FXHlGDKyBDmUI/r8aO1uhWhldFRJv8K0Yfa8L+MhM57eA4t9cxSzg6fGAZ3W  ;
Date: Tue, 5 Apr 2005 01:10:58 +0200
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: Douglas Campbell <doug.campbell@craniumpro.com>
Subject: Re: [Asrg] Re: Asrg Digest, Vol 11, Issue 12
Message-ID: <20050404231058.GL67979@Space.Net>
References: <200503251711.j2PHBscA004184@warthog.cantspam.us>
	<21553.192.45.66.48.1111774766.squirrel@mx.cantspam.us>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <21553.192.45.66.48.1111774766.squirrel@mx.cantspam.us>
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca

On Fri, Mar 25, 2005 at 10:19:26AM -0800, Douglas Campbell wrote:
> That said, consider the C/R system used in the titankey patent (yes, I
> know prior art exists, but that's the system I think everyone here is
> aware of); that system presents a problem they believe that only a human
> can solve.  If they are correct.  a human must perform the response.
> (they've chosen the sample problem of presenting 4 numbers in an image and
> requiring the human to send the numbers as characters back in a response;
> this is the identical C/R system used by godaddy.com to shield their whois
> service, for instance).

Such C/R systems will never be widely deployed.

The casual user will never ever be able to manage them. My mother has a
Linux box with email and web and is quite happy and able to manage what
she needs. Sometimes she and her friends notice that they both have email
access and exchange addresses.
I am 99.9% sure neither of them will successfully handle the C/R requests,
because they are simply to confused (and they are German language based,
their english is rather bad).
My mom sent an email to a french company to buy a special product.
It worked, even with the limited knowledge of english. But she received back
an automated message in french which she did not understand (neither did I,
a friend helped out, it was simply a reception ack). She would never have been
able to follow the instructions (nor would I have been) if this had been a C/R.

More and more sites follow the "trend" to make the contact to customers only
via web based forms and not accept email any longer (like the clueful ppl at paypal
where you send an email to abuse to notify them about an active phishing site
and you get back an auto answer which redirects you to a webbpage which you
can't use unless you are a paypal customer. So I stopped sending notifications
about paypal phishing attacks that hit my spamtrap accounts, and I will surely
never become a paypal customer with their "security" policy).
Now how would I ever know which eMail address to whitelist prior to making
contact in my C/R system? *@payal.com? *@*?
So I have to sit there and check all my dangling C/R requests to see if one of
them is from those website I want to make contact to. Really helpful.

Unless there are automated methods for handling C/R it is a system for some
freaks that mainly annoys everyone else.

	\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 asrg-bounces@ietf.org  Mon Apr  4 19:24:44 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24673
	for <asrg-web-archive@ietf.org>; Mon, 4 Apr 2005 19:24:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DIb45-00060U-MP
	for asrg-web-archive@ietf.org; Mon, 04 Apr 2005 19:33:05 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DIasV-0005hy-Sx; Mon, 04 Apr 2005 19:21:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DIasU-0005hq-72
	for asrg@megatron.ietf.org; Mon, 04 Apr 2005 19:21:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24414
	for <Asrg@ietf.org>; Mon, 4 Apr 2005 19:21:02 -0400 (EDT)
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DIb0V-0005ti-7h
	for Asrg@ietf.org; Mon, 04 Apr 2005 19:29:23 -0400
Received: (qmail 76729 invoked by uid 1013); 4 Apr 2005 23:21:01 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=testkey; d=space.net;
	b=GCmk7nKxNY5NPD2DDfWxBeGHuWkfC5EzWqbaMk7/WC/sAi9QLu4Mj9X1nmqcvFns  ;
Date: Tue, 5 Apr 2005 01:21:01 +0200
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: Asrg@ietf.org
Message-ID: <20050404232101.GM67979@Space.Net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Subject: [Asrg] effects of PKI
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228

Due to the fact that I have stumbled over a lot of PKI stuff in relation to email
messages lately, I wonder how widely deployed PKI mechanisms will affect the security
of the messages in a negative way.
Will PKI lead to more problems than it helps to solve?

Just think of virus scanning ... no scanner can check a message that is
encrypted with e.g. the public key of the recipient unless it knows the
corresponding private key.

Wider deployment of PKI will have viruses and spammers make advantage of
such information (probably stored on the infected host) and will disable
the scanners to scan/analyze the messages.
This will, however, increase the number of infected hosts, as e.g. ISPs will
not be able to scan the mailboxes or the transport traffic of their customers.
So the customers have either to run update AV software of their own (which we
know they don't) or we will have a massive increase of infected hosts.

What do you think?

	\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 asrg-bounces@ietf.org  Tue Apr 12 01:57:01 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA07308
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 01:57:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLEY0-0005HG-49
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 02:06:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLE6q-0000jm-1B; Tue, 12 Apr 2005 01:38:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLE6l-0000iV-5u
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 01:38:47 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA05556
	for <asrg@ietf.org>; Tue, 12 Apr 2005 01:38:23 -0400 (EDT)
Received: from linuxbox.org ([24.155.83.21] ident=root)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLEFy-0004nP-33
	for asrg@ietf.org; Tue, 12 Apr 2005 01:48:15 -0400
Received: from [192.115.22.106] (prometheus.solaris.org.il [192.115.22.106])
	(authenticated bits=0)
	by linuxbox.org (8.13.3/8.13.3/Debian-6) with ESMTP id j3C5cBGr013685
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT)
	for <asrg@ietf.org>; Tue, 12 Apr 2005 00:38:14 -0500
Message-ID: <425B50B2.3000305@linuxbox.org>
Date: Tue, 12 Apr 2005 08:38:10 +0400
From: Gadi Evron <ge@linuxbox.org>
User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "'asrg@ietf.org'" <asrg@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by
	milter-greylist-1.7.5 (linuxbox.org [24.155.83.21]);
	Tue, 12 Apr 2005 00:38:14 -0500 (CDT)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Content-Transfer-Encoding: 7bit
Subject: [Asrg] article: port 25 blocking
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit

Larry has been asking a ton of questions of people online, and
participating in professional discussions on the subject, on other
lists. Here is the result of the information he gathered:

http://www.eweek.com/article2/0,1759,1784276,00.asp

	Gadi.

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


From asrg-bounces@ietf.org  Tue Apr 12 02:45:36 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00857
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 02:45:36 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLFJ2-0006NQ-3R
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 02:55:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLF1Y-0003rB-EV; Tue, 12 Apr 2005 02:37:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLF1S-0003qE-P6
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 02:37:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00488
	for <asrg@ietf.org>; Tue, 12 Apr 2005 02:37:09 -0400 (EDT)
Message-Id: <200504120637.CAA00488@ietf.org>
Received: from smtp811.mail.sc5.yahoo.com ([66.163.170.81])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLFAq-0006CZ-Ak
	for asrg@ietf.org; Tue, 12 Apr 2005 02:47:01 -0400
Received: from unknown (HELO gous6120) (gcou@sbcglobal.net@69.110.14.65 with
	login)
	by smtp811.mail.sc5.yahoo.com with SMTP; 12 Apr 2005 06:37:07 -0000
From: "George Ou" <george_ou@netzero.com>
To: "'Gadi Evron'" <ge@linuxbox.org>, <asrg@ietf.org>
Subject: RE: [Asrg] article: port 25 blocking
Date: Mon, 11 Apr 2005 23:37:05 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcU/JwbIRTH6b1a+QwucMuKBQnR/qgAAHWlA
In-Reply-To: <425B50B2.3000305@linuxbox.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit

Blocking port 25 harms a lot of legitimate uses.  Why not do the following
to deal with the issue as a whole.

*  Start banning all non-SPF compliant domains within a certain deadline
which would effectively make port 25 blocking moot.
*  Then we deal with the problem of ISPs who don't implement SMTP AUTH and
who won't implement some reasonable rate limiting schemes.
*  Then start requiring some sort of official registration or bonding of
domains who bulk send (based on Distributed Checksum Clearinghouse
measurements) so that we can either easily track you down for prosecution or
we confiscate the bond for any kind of abuses from an SPF abusive domain.

These steps would seem to me a lot more effective and cause a lot less
collateral damage.  As the owner of a few small personal domains and someone
who uses outbound 25 for legitimate SMTP relay, I'd much rather you force me
to put in a few SPF records than blocking my outbound port 25 access.  We're
essentially talking about the same thing here only from different sides of
the problem.  Do we create an ACL (Access Control List) that denies all
non-SMTP servers of the world or do we create an ACL that permits all
legitimate SMTP servers of the world?  It would seem to me that the latter
is a much smaller database and much easier to implement than the former.


George Ou


-----Original Message-----
From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of Gadi
Evron
Sent: Monday, April 11, 2005 9:38 PM
To: 'asrg@ietf.org'
Subject: [Asrg] article: port 25 blocking

Larry has been asking a ton of questions of people online, and participating
in professional discussions on the subject, on other lists. Here is the
result of the information he gathered:

http://www.eweek.com/article2/0,1759,1784276,00.asp

	Gadi.

_______________________________________________
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 asrg-bounces@ietf.org  Tue Apr 12 03:50:00 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04788
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 03:49:59 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLGJN-0007wW-Ki
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 03:59:53 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLG2X-0006Jl-AQ; Tue, 12 Apr 2005 03:42:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLG2U-0006Ip-Bw
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 03:42:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA04251
	for <asrg@ietf.org>; Tue, 12 Apr 2005 03:42:16 -0400 (EDT)
Received: from tcp.com ([66.92.182.248])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLGBt-0007j7-CS
	for asrg@ietf.org; Tue, 12 Apr 2005 03:52:10 -0400
Received: from [192.168.2.20] (hoping.yemaozi.com [192.168.2.20])
	by tcp.com (8.12.10+Sun/8.12.10) with ESMTP id j3C7fxrN017559
	for <asrg@ietf.org>; Tue, 12 Apr 2005 00:42:01 -0700 (PDT)
Message-ID: <425B7BC2.2010105@drivel.com>
Date: Tue, 12 Apr 2005 15:41:54 +0800
From: James Lick <jlick@drivel.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking
References: <200504120637.CAA00488@ietf.org>
In-Reply-To: <200504120637.CAA00488@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by tcp.com id
	j3C7fxrN017559
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: quoted-printable
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: quoted-printable

George Ou wrote:

>Blocking port 25 harms a lot of legitimate uses.  Why not do the followi=
ng
>to deal with the issue as a whole.
> =20
>

Blocking open relays harmed a lot of legitimate uses.  In fact, quite a=20
lot of the complaints about port 25 blocking today sounds awfully=20
similiar to the complaints about blocking/closing open relays seven=20
years ago.  But it still happened, because the legitimate use of open=20
relays was vastly outweighed by the abuse of it.  I would argue that=20
unblocked port 25 on consumer level accounts has a similiar ratio of=20
abuse versus legitimate use that open relays did.  Those who had=20
legitimate use of open relays were able to find alternatives.  Those who=20
legitimately use outbound port 25 access have alternatives already which=20
include smtp auth, ssh tunneling, VPN, configuring your MTA to use your=20
ISP's mail server as outbound relay, asking your ISP for an exemption to=20
blocking, or simply using a premium ISP which offers static IP and=20
allows servers.=20

>As the owner of a few small personal domains and someone
>who uses outbound 25 for legitimate SMTP relay, I'd much rather you forc=
e me
>to put in a few SPF records than blocking my outbound port 25 access.
> =20
>

If you actually read the article, his suggestion would completely=20
accomodate your situation.  He proposes that port 25 be blocked by=20
default on dynamic address consumer level services, but that users can=20
apply for an exemption with their ISP.  Power user ISPs such as those=20
that offer static IP would not be blocked by default.  It also bears=20
considering that, present company excluded, the number of people who=20
legitimately use outbound port 25 on consumer ISPs is a vanishingly=20
small number.  Is it really worth allowing so much abuse to continue=20
just to preserve this luxury for a few people who could use one of the=20
alternatives above?

Similiarly, your suggestion to universally implement SPF would require=20
that every domain and mail server on the planet to implement your=20
solution, versus port 25 blocking which would only require a few power=20
users to make some changes.  Which is more likely to happen?

I agree with Larry.  It's well past time to implement this on all=20
consumer level ISPs.

--=20
James Lick -- =E9=BB=8E=E5=BB=BA=E6=BA=A5 -- jlick@jameslick.com -- http:=
//jameslick.com/

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


From asrg-bounces@ietf.org  Tue Apr 12 04:10:34 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA06051
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 04:10:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLGdI-0000Ab-59
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 04:20:28 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLGI3-0000QK-I6; Tue, 12 Apr 2005 03:58:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLGHz-0000Op-12
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 03:58:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05149
	for <asrg@ietf.org>; Tue, 12 Apr 2005 03:58:17 -0400 (EDT)
Received: from mail80.messagelabs.com ([195.245.230.163])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLGRN-0008Gc-Iu
	for asrg@ietf.org; Tue, 12 Apr 2005 04:08:11 -0400
X-VirusChecked: Checked
X-Env-Sender: Danny_Angus@slc.co.uk
X-Msg-Ref: server-13.tower-80.messagelabs.com!1113292680!14873292!1
X-StarScan-Version: 5.4.11; banners=slc.co.uk,-,-
X-Originating-IP: [195.99.121.125]
Received: (qmail 20864 invoked from network); 12 Apr 2005 07:58:03 -0000
Received: from mail1.slc.co.uk (HELO drsneaky.slc.co.uk) (195.99.121.125)
	by server-13.tower-80.messagelabs.com with SMTP;
	12 Apr 2005 07:58:03 -0000
Received: from emerald.slc.co.uk (emerald.slc.co.uk) by drsneaky.slc.co.uk 
	(Content Technologies SMTPRS 4.3.12) with ESMTP id 
	<T704209deadc0a864655a4@drsneaky.slc.co.uk>; Tue, 12 Apr 2005 08:58:00 
	+0100
Subject: Re: [Asrg] article: port 25 blocking
To: James Lick <jlick@drivel.com>
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFA4AF6EE1.C64711FB-ON80256FE1.002B65CC-80256FE1.002BC302@slc.co.uk>
From: Danny Angus <Danny_Angus@slc.co.uk>
Date: Tue, 12 Apr 2005 08:57:59 +0100
X-MIMETrack: Serialize by Router on Emerald/SLC (Release 6.5.2|June 01, 2004) 
	at 12/04/2005 08:58:00
MIME-Version: 1.0
Content-type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93238566e09e6e262849b4f805833007
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a


> Those who legitimately use outbound port 25 access
> have alternatives already which include
<snip/>
> asking your ISP for an exemption


If ISP's blocked port 25 and provided policed exemptions it would introduce
weak trust into an area where there is conspicuously no trust at all.

I don't see this as any more contentious than the blacklisting of ISP's
DHCP IP blocks, which stung some people at first but protected a whole lot
more in the long run.


d.


***************************************************************************
The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient (or responsible for delivery of the message to the intended recipient) please notify us immediately on 0141 306 2050 and delete the message from your computer. You may not copy or forward it or use or disclose its contents to any other person. As Internet communications are capable of data corruption Student Loans Company Limited does not accept any  responsibility for changes made to this message after it was sent. For this reason it may be inappropriate to rely on advice or opinions contained in an e-mail without obtaining written confirmation of it. Neither Student Loans Company Limited or the sender accepts any liability or responsibility for viruses as it is your responsibility to scan attachments (if any). Opinions and views expressed in this e-mail are those of the sender and may not reflect the opinions and views of The Student Loans Company Limi!
 ted.

This footnote also confirms that this email message has been swept for the presence of computer viruses.

**************************************************************************

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


From asrg-bounces@ietf.org  Tue Apr 12 05:11:41 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11294
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 05:11:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLHaS-00026k-G0
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 05:21:36 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLHGq-00044T-IR; Tue, 12 Apr 2005 05:01:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLHGh-000428-NV
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 05:01:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10732
	for <asrg@ietf.org>; Tue, 12 Apr 2005 05:01:08 -0400 (EDT)
Message-Id: <200504120901.FAA10732@ietf.org>
Received: from smtp807.mail.sc5.yahoo.com ([66.163.168.186])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLHQD-0001o4-Dy
	for asrg@ietf.org; Tue, 12 Apr 2005 05:11:03 -0400
Received: from unknown (HELO gous6120) (gcou@sbcglobal.net@69.110.14.65 with
	login)
	by smtp807.mail.sc5.yahoo.com with SMTP; 12 Apr 2005 09:01:07 -0000
From: "George Ou" <george_ou@netzero.com>
To: "'James Lick'" <jlick@drivel.com>, <asrg@ietf.org>
Subject: RE: [Asrg] article: port 25 blocking
Date: Tue, 12 Apr 2005 02:01:05 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcU/NrqFsWd9sBOJT/uZK7UlKzO0qwABX1/w
In-Reply-To: <425B7BC2.2010105@drivel.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.9 (/)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit

-----Original Message-----
From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of
James Lick
Sent: Tuesday, April 12, 2005 12:42 AM
To: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking

>Similiarly, your suggestion to universally implement SPF would require that
every domain and mail server on the planet to implement your solution,
versus port 25 blocking which would only require a few power users to make
some changes.  Which is more likely to happen?

>I agree with Larry.  It's well past time to implement this on all consumer
level ISPs.

>--
>James Lick -- ??? -- jlick@jameslick.com -- http://jameslick.com/


James,

I have to respectfully disagree with you.  I've read your take on spam
before and I agree with most of it.  This is one of the few areas where I
disagree with you.

Blocking port 25 or demanding SPF is conceptually the same by dealing with
the problem from the opposite ends of the spectrum.  The question is do we
use an ACL that forbids all non-SMTP servers or do we use an ACL that only
permits all legitimate SMTP servers?  It would seem to me that non-SMTP
nodes on the net vastly out weigh legitimate SMTP servers and therefore
would be a much smaller ACL to deal with.  Permitting only legitimate SMTP
servers via SenderID lookup follows the "least privileges" rule and is a
much more effective ACL.  Anyone who blocks all non-SPF compliant messages
blocks all illegitimate SMTP servers using a database (public DNS records)
that they don't need to personally manage.  Creating or managing a massive
database of non-SMTP servers is totally impractical.

What makes you think that it takes "ALL domains" to implement SPF?  Just the
top 50 domains in the world alone implementing it would pretty much force
the entire world to comply unless they don't care for their messages to be
delivered to the 50 largest domains.  Do you honestly believe you can get
all ISPs and hotspots to manage a much larger non-SMTP server ACL?


Here is a more detailed write up on this.
http://blogs.zdnet.com/Ou/index.php?p=51
Let me know what you think.


George Ou


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


From asrg-bounces@ietf.org  Tue Apr 12 06:31:14 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16454
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 06:31:14 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLIpS-0004A2-6K
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 06:41:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLIUd-0007Wp-OW; Tue, 12 Apr 2005 06:19:39 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLIUc-0007WT-J9
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 06:19:38 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15749
	for <asrg@ietf.org>; Tue, 12 Apr 2005 06:19:19 -0400 (EDT)
Received: from dsl081-214-187.nyc2.dsl.speakeasy.net ([64.81.214.187]
	helo=3comemail.larryseltzer.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLIdu-0003rN-Af
	for asrg@ietf.org; Tue, 12 Apr 2005 06:29:15 -0400
From: "Larry Seltzer" <larry@larryseltzer.com>
To: "'James Lick'" <jlick@drivel.com>, <asrg@ietf.org>
Subject: RE: [Asrg] article: port 25 blocking
Date: Tue, 12 Apr 2005 06:20:58 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <425B7BC2.2010105@drivel.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
Thread-Index: AcU/NwM88OZOeOzsTPCiEixa5Z6vYAAEbHcw
Message-ID: <6f3pjfer25drbae.120420050621@shayndel>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit

I had a thought yesterday that I wish I had before I hit the publish button
on the article: Perhaps the answer for people who need an exception case for
port 25 blocking is port 587 or even some non-standard port. I checked and
my own mail server supports both. Put SMTP on port 1125 or something like
that for your external users, or use 587 and require authentication. Is
there a reason this wouldn't work?

I'm also going to contact SBC and ask them how their opt-out system is
working so far.

LJS



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


From asrg-bounces@ietf.org  Tue Apr 12 07:20:34 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA20094
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 07:20:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLJbA-0005Ug-AB
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 07:30:31 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLJBp-0005L1-3I; Tue, 12 Apr 2005 07:04:17 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLJBn-0005KJ-Kl
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 07:04:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19138
	for <asrg@ietf.org>; Tue, 12 Apr 2005 07:04:04 -0400 (EDT)
Received: from guttormur.frisk-software.com ([213.220.100.9])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLJLD-00056k-Su
	for asrg@ietf.org; Tue, 12 Apr 2005 07:14:01 -0400
Received: by guttormur.frisk-software.com (Postfix, from userid 517)
	id 7DB96383CA; Tue, 12 Apr 2005 11:03:51 +0000 (GMT)
Received: from pc28.frisk-software.com. (pc28.frisk-software.com [172.16.5.2])
	by guttormur.frisk-software.com (Postfix) with ESMTP id 4C9E93801E
	for <asrg@ietf.org>; Tue, 12 Apr 2005 11:03:51 +0000 (GMT)
Received: by pc28.frisk-software.com. (8.11.6/client-1.3)
	id j3CB3px21175; Tue, 12 Apr 2005 11:03:51 GMT
Date: Tue, 12 Apr 2005 11:03:51 +0000
From: Fridrik Skulason <frisk@f-prot.com>
To: asrg@ietf.org
Subject: RE: [Asrg] article: port 25 blocking]
Message-ID: <20050412110351.GB19649@f-prot.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

> *  Then start requiring some sort of official registration or bonding of
> domains who bulk send (based on Distributed Checksum Clearinghouse
> measurements) so that we can either easily track you down for prosecution or
> we confiscate the bond for any kind of abuses from an SPF abusive domain.

The problem with that is the existence of Zombie networks.  A significant
part of spam (and worm) distribution is from compromised/infected
home computers, and with dynamic IP allocation you cannot justify blocking
the entire ISP just because some of their users have been infected - not
unless you are doing the blocking to FORCE them to implement port 25 
blocking, that is.

My proposal has always been that ISPs should block port 25 traffic from
"home" computers, but someone running a ttypical "small business" server
should not be blocked the same way.  

Given the huge amount of spam/worm traffic generated by compromised home
computers there is simply no good reason not to block port 25 for those
machines.

-- 
Fridrik Skulason   Frisk Software International   phone: +354-540-7400
                   E-mail: frisk@f-prot.com       fax:   +354-540-7401

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


From asrg-bounces@ietf.org  Tue Apr 12 07:48:30 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21587
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 07:48:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLK2D-0006Ax-HX
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 07:58:26 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLJk6-0001B8-Gn; Tue, 12 Apr 2005 07:39:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLJk4-00019g-Hc
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 07:39:40 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21143
	for <asrg@ietf.org>; Tue, 12 Apr 2005 07:39:31 -0400 (EDT)
Received: from mail1.nber.org ([66.251.72.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLJtW-0005yG-1Q
	for asrg@ietf.org; Tue, 12 Apr 2005 07:49:26 -0400
Received: from mail1 (root@localhost)
	by mail1.nber.org (8.12.8/8.12.8) with SMTP id j3CBdNMq002368
	for <asrg@ietf.org>; Tue, 12 Apr 2005 07:39:23 -0400
Received: from nber5.nber.org (nber5.nber.org [66.251.72.75])
	by mail1.nber.org (8.12.8/8.12.8) with ESMTP id j3CBdMvL002349;
	Tue, 12 Apr 2005 07:39:22 -0400
Date: Tue, 12 Apr 2005 07:39:22 -0400 (EDT)
From: Daniel Feenberg <feenberg@nber.org>
To: Danny Angus <Danny_Angus@slc.co.uk>
Subject: Re: [Asrg] article: port 25 blocking
In-Reply-To: <OFA4AF6EE1.C64711FB-ON80256FE1.002B65CC-80256FE1.002BC302@slc.co.uk>
Message-ID: <Pine.GSO.4.10.10504120733350.16835-100000@nber5.nber.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5
Cc: asrg@ietf.org, James Lick <jlick@drivel.com>
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0



On Tue, 12 Apr 2005, Danny Angus wrote:

> 
> > Those who legitimately use outbound port 25 access
> > have alternatives already which include
> <snip/>
> > asking your ISP for an exemption
> 
> 
> If ISP's blocked port 25 and provided policed exemptions it would introduce
> weak trust into an area where there is conspicuously no trust at all.
> 
> I don't see this as any more contentious than the blacklisting of ISP's
> DHCP IP blocks, which stung some people at first but protected a whole lot
> more in the long run.

Can you suggest a DNSBL that does this? We are using MAPS and Spamhaus,
but MAPS only lists a block if the ISP owning the block specifically
requests it, and Spamhaus seems to be very weak in this area also. For
example, we get several hundred messages from east.verizon.net every
day. Could there actually be legitimate MTAs in that block? 

An advantage of using DNSBLs for blocking port 25 rather than having the
ISP do it at the router is that it is what economists call "incentive
compatible". That is, the work and expense (such as they are) are borne
by the individual/organization that benefits most. The benefit to the
source ISP is mostly a reduction in abuse mail - which many ISPs seem to
ignore anyway. The benefit to the receiving ISP is a reduction in inbound
spam, which is a big incentive. 

Daniel Feenberg

> 
> 
> d.
> 
> 
> ***************************************************************************
> The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient (or responsible for delivery of the message to the intended recipient) please notify us immediately on 0141 306 2050 and delete the message from your computer. You may not copy or forward it or use or disclose its contents to any other person. As Internet communications are capable of data corruption Student Loans Company Limited does not accept any  responsibility for changes made to this message after it was sent. For this reason it may be inappropriate to rely on advice or opinions contained in an e-mail without obtaining written confirmation of it. Neither Student Loans Company Limited or the sender accepts any liability or responsibility for viruses as it is your responsibility to scan attachments (if any). Opinions and views expressed in this e-mail are those of the sender and may not reflect the opinions and views of The Student Loans Company Li!
mi!
>  ted.
> 
> This footnote also confirms that this email message has been swept for the presence of computer viruses.
> 
> **************************************************************************
> 
> _______________________________________________
> 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 asrg-bounces@ietf.org  Tue Apr 12 10:10:05 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02074
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 10:10:05 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLMFF-0001kQ-Ai
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 10:20:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLLo2-00059E-MQ; Tue, 12 Apr 2005 09:51:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLLo0-00058i-Uc
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 09:51:53 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29914
	for <asrg@ietf.org>; Tue, 12 Apr 2005 09:51:42 -0400 (EDT)
Received: from cwhois1.completewhois.com ([216.151.192.222]
	helo=mail.completewhois.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLLxS-0001F0-Iq
	for asrg@ietf.org; Tue, 12 Apr 2005 10:01:40 -0400
Received: by mail.completewhois.com (Postfix, from userid 500)
	id DB21118DC0; Tue, 12 Apr 2005 07:11:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1])
	by mail.completewhois.com (Postfix) with ESMTP
	id 9DBD54C460; Tue, 12 Apr 2005 07:11:54 -0700 (PDT)
Date: Tue, 12 Apr 2005 07:11:54 -0700 (PDT)
From: William Leibzon <william@completewhois.com>
To: Larry Seltzer <larry@larryseltzer.com>
Subject: RE: [Asrg] article: port 25 blocking
In-Reply-To: <6f3pjfer25drbae.120420050621@shayndel>
Message-ID: <Pine.LNX.4.60.0504120706550.15068@cwhois1.completewhois.com>
References: <6f3pjfer25drbae.120420050621@shayndel>
MIME-Version: 1.0
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da
Cc: asrg@ietf.org, "'James Lick'" <jlick@drivel.com>
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1863834042=="
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--===============1863834042==
Content-Type: MULTIPART/signed;
	BOUNDARY="-1747394880-839875784-1113315114=:15068";
	protocol="application/x-pkcs7-signature"; micalg=sha1

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

---1747394880-839875784-1113315114=:15068
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed


On Tue, 12 Apr 2005, Larry Seltzer wrote:

> I had a thought yesterday that I wish I had before I hit the publish button
> on the article: Perhaps the answer for people who need an exception case for
> port 25 blocking is port 587 or even some non-standard port. I checked and
> my own mail server supports both. Put SMTP on port 1125 or something like
> that for your external users, or use 587 and require authentication. Is
> there a reason this wouldn't work?

Several issues:
1. Some locations (specially airport wireless, etc) actually do full
    port filtering in way that only well known ports are open. Anything
    new (and that includes port 587 unfortunetly) is not on their list.
2. A non-standard port that is 100% open just like regular SMTP is bound
    to soon be known and start to be abused. It has to be some type of
    restricted profile smtp with authentication (which is what submit is,
    so why reinvent it...).

---
William Leibzon
   mailto: william@completewhois.com
Anti-Spam and Email Security Research Worksite:
   http://www.elan.net/~william/emailsecurity/
Whois & DNS Network Investigation Tools:
   http://www.completewhois.com
---1747394880-839875784-1113315114=:15068
Content-Type: APPLICATION/x-pkcs7-signature; name="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: BASE64

MIIEWgYJKoZIhvcNAQcCoIIESzCCBEcCAQExCzAJBgUrDgMCGgUAMAsGCSqG
SIb3DQEHAaCCAl8wggJbMIIBxKADAgECAgMMcrUwDQYJKoZIhvcNAQEEBQAw
YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQ
dHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJ
c3N1aW5nIENBMB4XDTA0MDYwNTA5NDI0MVoXDTA1MDYwNTA5NDI0MVowSzEf
MB0GA1UEAxMWVGhhd3RlIEZyZWVtYWlsIE1lbWJlcjEoMCYGCSqGSIb3DQEJ
ARYZd2lsbGlhbUBjb21wbGV0ZXdob2lzLmNvbTCBnzANBgkqhkiG9w0BAQEF
AAOBjQAwgYkCgYEAxU1TG0vg2fYJeZ2TZ7cFst7hHB/83aN00wQS1cmKBpDA
q3UgvHfcnltbJqmM0+Wfr35P7RDKGjCvqZTS6sDhXeEUDE1OgdwHsYv62TUr
y94CQMVu6cctH3T+ajzQ9m1NmR0AT+uYQK7hwwcz70PB6T2troUUlcxFon+H
1jB1t1ECAwEAAaM2MDQwJAYDVR0RBB0wG4EZd2lsbGlhbUBjb21wbGV0ZXdo
b2lzLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBAUAA4GBACxJJGcY
lC9YU8SQWQBr/lzwwk9coMdLKs7YsqcroT12o0UT+AKO+5Ec4VPE7OfBvz66
5w1sz41oAlZM2JggwDSJ8NeYCpLxUxk/1wx1BclPGuedYsRm7NO5CCQP4IO7
qlwgTwBkfkrLeadbUf9MMuOjURVwTKfVkT6qfX8bvbqzMYIBwzCCAb8CAQEw
aTBiMQswCQYDVQQGEwJaQTElMCMGA1UEChMcVGhhd3RlIENvbnN1bHRpbmcg
KFB0eSkgTHRkLjEsMCoGA1UEAxMjVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWls
IElzc3VpbmcgQ0ECAwxytTAJBgUrDgMCGgUAoIGxMBgGCSqGSIb3DQEJAzEL
BgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA1MDQxMjE0MTE1NFowIwYJ
KoZIhvcNAQkEMRYEFAZsR04AH4RjLpdCz8vGOoRLnND6MFIGCSqGSIb3DQEJ
DzFFMEMwCgYIKoZIhvcNAwcwDgYIKoZIhvcNAwICAgCAMA0GCCqGSIb3DQMC
AgFAMAcGBSsOAwIHMA0GCCqGSIb3DQMCAgEoMA0GCSqGSIb3DQEBAQUABIGA
Q8QJwK0Nb+lQQ+jofnj5H5tSCxmYwiH5zCNTHJeu8aiXcWP1Q8wI8Py4rEI+
QydUo/AOpkazEEyNw9R5YA342orsND5zznzg/nfCyxiZf2hM7exwwTWv37PN
MQx4qwC/PoYRz7MElXIL0DPEI0ubR7VaIORbJ/6DbSJy6OodyNY=

---1747394880-839875784-1113315114=:15068--


--===============1863834042==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--===============1863834042==--



From asrg-bounces@ietf.org  Tue Apr 12 10:15:40 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02894
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 10:15:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLMKe-0001wH-65
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 10:25:37 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLLxA-00062k-DZ; Tue, 12 Apr 2005 10:01:20 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLLx8-00061f-1A
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 10:01:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01008
	for <asrg@ietf.org>; Tue, 12 Apr 2005 10:00:59 -0400 (EDT)
Received: from dsl081-214-187.nyc2.dsl.speakeasy.net ([64.81.214.187]
	helo=3comemail.larryseltzer.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLM6R-0001WX-On
	for asrg@ietf.org; Tue, 12 Apr 2005 10:10:57 -0400
From: "Larry Seltzer" <larry@larryseltzer.com>
To: <asrg@ietf.org>
Subject: RE: [Asrg] article: port 25 blocking
Date: Tue, 12 Apr 2005 10:02:33 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <Pine.LNX.4.60.0504120706550.15068@cwhois1.completewhois.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
Thread-Index: AcU/ZwUenRNrV3y7R7OXt5sJWD2xBQAAIfvw
Message-ID: <t0zf81nxps3na3q.120420051002@shayndel>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit

>>http://www.completewhois.com

Hey, I'm a big fan. Good site.

>>1. Some locations (specially airport wireless, etc) actually do full
    port filtering in way that only well known ports are open. 

I guess this only works if 587 becomes "well-known" in this sense, but that
doesn't seem unreasonable. Blocking it by default is probably a mistake.

>>2. A non-standard port that is 100% open just like regular SMTP is bound
    to soon be known and start to be abused. 

That would be true if everyone used the same one, but if small numbers of
people are involved you just pick a number out of a hat that doesn't
conflict with an existing one. I suppose a really sophisticated worm could
sniff all traffic looking for where the mail is going, but we're nowhere
near there yet. If there are more than a few people involved then a real
authentication facility is probably advisable anyway. 

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



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


From asrg-bounces@ietf.org  Tue Apr 12 11:13:45 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07282
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 11:13:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLNEs-0003dN-Hw
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 11:23:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLMsE-00074Q-G1; Tue, 12 Apr 2005 11:00:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLMsC-000702-76
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 11:00:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06362
	for <asrg@ietf.org>; Tue, 12 Apr 2005 11:00:08 -0400 (EDT)
Received: from tcp.com ([66.92.182.248])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLN1h-0003GH-5f
	for asrg@ietf.org; Tue, 12 Apr 2005 11:10:06 -0400
Received: from [127.0.0.1] (tcp.com [66.92.182.248])
	by tcp.com (8.12.10+Sun/8.12.10) with ESMTP id j3CF06rN029848
	for <asrg@ietf.org>; Tue, 12 Apr 2005 08:00:07 -0700 (PDT)
Message-ID: <425BE272.7080803@drivel.com>
Date: Tue, 12 Apr 2005 23:00:02 +0800
From: James Lick <jlick@drivel.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking
References: <200504120901.FAA10732@ietf.org>
In-Reply-To: <200504120901.FAA10732@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by tcp.com id
	j3CF06rN029848
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: quoted-printable
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d
Content-Transfer-Encoding: quoted-printable

George Ou wrote:

>Permitting only legitimate SMTP
>servers via SenderID lookup follows the "least privileges" rule and is a
>much more effective ACL.  Anyone who blocks all non-SPF compliant messag=
es
>blocks all illegitimate SMTP servers using a database (public DNS record=
s)
>that they don't need to personally manage.  Creating or managing a massi=
ve
>database of non-SMTP servers is totally impractical.
> =20
>

Port 25 blocking is also a least privileges model.  Consumer ISPs block=20
all outgoing port 25, then punch a few holes in the firewall for their=20
own mail servers and the few customers that request an exemption. =20
Sounds quite manageable to me.

>What makes you think that it takes "ALL domains" to implement SPF?  Just=
 the
>top 50 domains in the world alone implementing it would pretty much forc=
e
>the entire world to comply unless they don't care for their messages to =
be
>delivered to the 50 largest domains.  Do you honestly believe you can ge=
t
>all ISPs and hotspots to manage a much larger non-SMTP server ACL?
> =20
>

I think you just answered your own question.  In summary you are saying=20
that if the large domains require SPF then everyone will be forced to=20
put SPF records in for any domain that sends email.  So you are in fact=20
saying that yes, everyone will be forced to implement SPF records in=20
your scheme.  I submit that no ISP is willing to risk the loss of=20
requiring SPF because doing so would lose a vast amount of legitimate=20
email.  In the current environment at best you would be able to get=20
sites to reject on SPF hard fail, but that wouldn't achieve your goal. =20
It's a chicken and egg problem that I don't think any ISP in their right=20
might would go along with.

Your blog says that port 25 blocking is controversial with users.  I=20
submit that it is controversial to a miniscule number of users.  On the=20
other hand, requiring an SPF pass on all incoming email right now would=20
cause huge amounts of legitimate mail to be blocked.  How controversial=20
do you think that will be?  Already we have a number of respected=20
anti-spammers who are quite opposed to SPF because hard fails are=20
occasionally false positives.  You're gonna have people bouncing off the=20
walls if you reject soft fail and unknown status and only allow SPF pass=20
messages.

Implementing port 25 blocking also requires significant work, but the=20
downside is limited to only a few people.  Also the number of consumer=20
ISPs is much smaller than the number of email domains out there.  If you=20
got the top 50 consumer ISPs to implement port 25 blocking, then nobody=20
else has to do anything at all and you'll probably be at least 80% of=20
the way done in terms of number of zombies no longer effective.

A number of large consumer ISPs have already implemented it with only a=20
few grumbles about it.  Consumer ISPs which implement it will see an=20
immediate reduction of complaints coming into their abuse mailbox, and=20
only have a handful of users who will need to make a change.  That=20
sounds a heck of a lot more manageable than forcing everyone to=20
implement SPF records and having tons of legitimate mail rejected until=20
everyone complies.

--=20
James Lick -- =E9=BB=8E=E5=BB=BA=E6=BA=A5 -- jlick@jameslick.com -- http:=
//jameslick.com/

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


From asrg-bounces@ietf.org  Tue Apr 12 11:46:24 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09438
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 11:46:23 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLNkS-0004Xl-Ji
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 11:56:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLNPF-0003ky-IR; Tue, 12 Apr 2005 11:34:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLNPD-0003kE-Pt; Tue, 12 Apr 2005 11:34:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08709;
	Tue, 12 Apr 2005 11:34:13 -0400 (EDT)
Received: from mail71.messagelabs.com ([193.109.255.131])
	by ietf-mx.ietf.org with smtp (Exim 4.33)
	id 1DLNYe-0004Cs-3u; Tue, 12 Apr 2005 11:44:11 -0400
X-VirusChecked: Checked
X-Env-Sender: Danny_Angus@slc.co.uk
X-Msg-Ref: server-11.tower-71.messagelabs.com!1113320036!11500767!1
X-StarScan-Version: 5.4.11; banners=slc.co.uk,-,-
X-Originating-IP: [195.99.121.125]
Received: (qmail 12115 invoked from network); 12 Apr 2005 15:33:57 -0000
Received: from mail1.slc.co.uk (HELO drsneaky.slc.co.uk) (195.99.121.125)
	by server-11.tower-71.messagelabs.com with SMTP;
	12 Apr 2005 15:33:57 -0000
Received: from emerald.slc.co.uk (emerald.slc.co.uk) by drsneaky.slc.co.uk 
	(Content Technologies SMTPRS 4.3.12) with ESMTP id 
	<T7043ab4bb3c0a864655a4@drsneaky.slc.co.uk>; Tue, 12 Apr 2005 16:33:56 
	+0100
Subject: Re: [Asrg] article: port 25 blocking
To: Daniel Feenberg <feenberg@nber.org>
X-Mailer: Lotus Notes Release 5.0.12   February 13, 2003
Message-ID: <OFCA5C8D96.F8B02FA8-ON80256FE1.0054B2D4-80256FE1.00558238@slc.co.uk>
From: Danny Angus <Danny_Angus@slc.co.uk>
Date: Tue, 12 Apr 2005 16:33:58 +0100
X-MIMETrack: Serialize by Router on Emerald/SLC (Release 6.5.2|June 01, 2004) 
	at 12/04/2005 16:33:56
MIME-Version: 1.0
Content-type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Cc: asrg@ietf.org, asrg-bounces@ietf.org, James Lick <jlick@drivel.com>
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352





> Can you suggest a DNSBL that does this?

No, I can't. All I know is that James' (http://james.apache.org) users
periodically complain that James is broken when in fact their dynamic IP is
being blocked, so I figure _someone_ has a list.

> For example, we get several hundred messages
> from east.verizon.net every day.
> Could there actually be legitimate MTAs in that block?

Well yes, if you were a small business you might reasonably be running your
own MTA
to handle mail efficiently for the half dozen people who use the 2 or 3
PC's in your home office.
The workaround would be as simple as having them route through their ISP's
SMTP gateway.

If we are careful to distinguish between blocking outgoing connections to
port 25 and listening on port 25 just anyone with an IP in an ISP's block
will, by definition, have an ISP who can provide an outgoing SMTP relay.

Letting people also directly listen on port 25 lets them host their own
SMTP mail domain and implement all the MTA functionality they could wish
for, without creating an empty playground for spam-bots.

d.


***************************************************************************
The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient (or responsible for delivery of the message to the intended recipient) please notify us immediately on 0141 306 2050 and delete the message from your computer. You may not copy or forward it or use or disclose its contents to any other person. As Internet communications are capable of data corruption Student Loans Company Limited does not accept any  responsibility for changes made to this message after it was sent. For this reason it may be inappropriate to rely on advice or opinions contained in an e-mail without obtaining written confirmation of it. Neither Student Loans Company Limited or the sender accepts any liability or responsibility for viruses as it is your responsibility to scan attachments (if any). Opinions and views expressed in this e-mail are those of the sender and may not reflect the opinions and views of The Student Loans Company Limi!
 ted.

This footnote also confirms that this email message has been swept for the presence of computer viruses.

**************************************************************************

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


From asrg-bounces@ietf.org  Tue Apr 12 12:44:49 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14216
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 12:44:49 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLOf2-0006RW-H0
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 12:54:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLODf-0001hm-Od; Tue, 12 Apr 2005 12:26:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLODd-0001fz-DP
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 12:26:29 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12149
	for <asrg@ietf.org>; Tue, 12 Apr 2005 12:26:18 -0400 (EDT)
Received: from mail1.nber.org ([66.251.72.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLON5-0005jM-Rd
	for asrg@ietf.org; Tue, 12 Apr 2005 12:36:17 -0400
Received: from mail1 (root@localhost)
	by mail1.nber.org (8.12.8/8.12.8) with SMTP id j3CGQ9Q7009472
	for <asrg@ietf.org>; Tue, 12 Apr 2005 12:26:09 -0400
Received: from nber6.nber.org (nber6.nber.org [66.251.72.76])
	by mail1.nber.org (8.12.8/8.12.8) with ESMTP id j3CGQ9vL009440;
	Tue, 12 Apr 2005 12:26:09 -0400
Date: Tue, 12 Apr 2005 12:26:09 -0400 (EDT)
From: Daniel Feenberg <feenberg@nber.org>
To: Danny Angus <Danny_Angus@slc.co.uk>
Subject: Re: [Asrg] article: port 25 blocking
In-Reply-To: <OFCA5C8D96.F8B02FA8-ON80256FE1.0054B2D4-80256FE1.00558238@slc.co.uk>
Message-ID: <Pine.GSO.4.10.10504121222160.5648-100000@nber6.nber.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Cc: asrg@ietf.org, asrg-bounces@ietf.org, James Lick <jlick@drivel.com>
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c


I have prepared a web page

http://www.nber.org/REASON-FOR-REJECTION/smarthost.html 

which I refer corespondents to when they are blocked because their IP
address looks dynamic. In fact they always claim there is nothing they can
do and insist we whitelist them. Still, I can hope that eventually they
will get a reasonable RDNS or smarthost if they have enough trouble
getting their mail through.

I phrased the page as though the person reading it were legitimate, I
don't think spammers are affected by insults, but legitimate corespondents
are likely to be (in the wrong way, of course).

Daniel Feenberg

On Tue, 12 Apr 2005, Danny Angus wrote:

> 
> 
> 
> 
> > Can you suggest a DNSBL that does this?
> 
> No, I can't. All I know is that James' (http://james.apache.org) users
> periodically complain that James is broken when in fact their dynamic IP is
> being blocked, so I figure _someone_ has a list.
> 
> > For example, we get several hundred messages
> > from east.verizon.net every day.
> > Could there actually be legitimate MTAs in that block?
> 
> Well yes, if you were a small business you might reasonably be running your
> own MTA
> to handle mail efficiently for the half dozen people who use the 2 or 3
> PC's in your home office.
> The workaround would be as simple as having them route through their ISP's
> SMTP gateway.
> 
> If we are careful to distinguish between blocking outgoing connections to
> port 25 and listening on port 25 just anyone with an IP in an ISP's block
> will, by definition, have an ISP who can provide an outgoing SMTP relay.
> 
> Letting people also directly listen on port 25 lets them host their own
> SMTP mail domain and implement all the MTA functionality they could wish
> for, without creating an empty playground for spam-bots.
> 
> d.
> 
> 
> ***************************************************************************
> The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient (or responsible for delivery of the message to the intended recipient) please notify us immediately on 0141 306 2050 and delete the message from your computer. You may not copy or forward it or use or disclose its contents to any other person. As Internet communications are capable of data corruption Student Loans Company Limited does not accept any  responsibility for changes made to this message after it was sent. For this reason it may be inappropriate to rely on advice or opinions contained in an e-mail without obtaining written confirmation of it. Neither Student Loans Company Limited or the sender accepts any liability or responsibility for viruses as it is your responsibility to scan attachments (if any). Opinions and views expressed in this e-mail are those of the sender and may not reflect the opinions and views of The Student Loans Company Li!
mited.
> 
> This footnote also confirms that this email message has been swept for the presence of computer viruses.
> 
> **************************************************************************
> 



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


From asrg-bounces@ietf.org  Tue Apr 12 13:11:35 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16865
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 13:11:35 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLP4w-0007Tu-G8
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 13:21:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLOm6-0008KX-7u; Tue, 12 Apr 2005 13:02:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLOm4-0008K4-1H
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 13:02:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA16107
	for <asrg@ietf.org>; Tue, 12 Apr 2005 13:01:52 -0400 (EDT)
Received: from mail.asarian-host.net ([194.109.160.70])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLOvW-000798-MB
	for asrg@ietf.org; Tue, 12 Apr 2005 13:11:52 -0400
Received: from anonymizer.asarian-host.net (localhost [127.0.0.1])
	(authenticated bits=0)
	by mail.asarian-host.net (8.13.4/8.13.4) with ESMTP id j3CH1iYI039141
	for <asrg@ietf.org>; Tue, 12 Apr 2005 19:01:44 +0200 (CEST)
	(envelope-from admin@asarian-host.net)
From: Mark <admin@asarian-host.net>
Received-SPF: pass (asarian-host.net: sender IP
	is authenticated by a trusted mechanism)
	receiver=asarian-host.net; client-ip=sender IP;
	envelope-from=<admin@asarian-host.net>; helo=asarian-host;
Message-Id: <200504121701.j3CH1hYA039131@asarian-host.net>
Date: Tue, 12 Apr 2005 17:01:43 GMT
X-Authenticated-Sender: admin@asarian-host.net
Subject: RE: [Asrg] article: port 25 blocking
X-Trace: KZGujmze8bJ866JAfyk9uJRcNmh3uJLntLo6F0BiJMtMePYa8S7mcHg/4KmvaGNYdZ/2uLPb41CPBNEPj+aXtQ==
X-Complaints-To: abuse@asarian-host.net
X-Abuse-Info: Please be sure to forward a copy of ALL headers,
	otherwise we are unable to process your complaint
Organization: Asarian-host
To: <asrg@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.GSO.4.10.10504121222160.5648-100000@nber6.nber.org>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Auth: Asarian-host PGP signature
	iQEVAwUAQlv++DFqW1BleBN9AQEdXwf/brly+bU8NKlXXw/5GpRlgH4O6sJdadpw
	LWRnhfmqm4jJPQipLHWEwRe4ZTOEdMd6I63FxwIDCEtgnskvKFydVHmJ2c/Jf9fJ
	Yvqc/5EuS+n/63VDMufM3FmP/fu7r7PrZ83Xb1hdCmlomX3cb5egJ8xUQ09et6v9
	GnZll1gLfbepSrN/iVaIx6JV+3vpBIkAmtOHsGCZktbDPiNqVTk34NQG2JNLcB9g
	L8E9BD8VsK3U1G/7lM4Dwz7uahsUeAtxDj56bFjanp0SwSvvmTLoH/lHPI9Q5ejP
	eVVy/XsoLNK5IOakDB6+SR5VITRpiVj1s6qrl/1eNnmwA4b86BKs0w== =9mUK
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit


> -----Original Message-----
> From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On 
> Behalf Of Daniel Feenberg
> Sent: dinsdag 12 april 2005 18:45
> To: Danny Angus
> Cc: asrg@ietf.org; asrg-bounces@ietf.org; James Lick
> Subject: Re: [Asrg] article: port 25 blocking
> 
> I have prepared a web page
> 
> http://www.nber.org/REASON-FOR-REJECTION/smarthost.html 
> 

SMTP.COM says: "Using your sending email address as an identifier,
SMTP.com's servers recognize you immediately, check your status in our
database, and deliver your email within seconds."

Since they force you to identify by "sending email address" (meaning you
can only use that one email address) they are, pardon my French,
hilariously unfit to be called a smarthost in the true sense; because a
true smarthost, like your own smtp server, is, of course, not ridiculously
tied to 1 email address! LOL :)

- Mark 
 
        System Administrator Asarian-host.org
 
---
"If you were supposed to understand it,
we wouldn't call it code." - FedEx


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


From asrg-bounces@ietf.org  Tue Apr 12 14:12:47 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21659
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 14:12:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLQ27-0000tm-EH
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 14:22:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLPoT-0005Zk-1Z; Tue, 12 Apr 2005 14:08:37 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLPoR-0005Ym-HP
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 14:08:35 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21191
	for <asrg@ietf.org>; Tue, 12 Apr 2005 14:08:33 -0400 (EDT)
Message-Id: <200504121808.OAA21191@ietf.org>
Received: from smtp817.mail.sc5.yahoo.com ([66.163.170.3])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLPy3-0000kR-6J
	for asrg@ietf.org; Tue, 12 Apr 2005 14:18:32 -0400
Received: from unknown (HELO gous6120) (gcou@sbcglobal.net@216.226.168.4 with
	login)
	by smtp817.mail.sc5.yahoo.com with SMTP; 12 Apr 2005 18:03:49 -0000
From: "George Ou" <george_ou@netzero.com>
To: "'James Lick'" <jlick@drivel.com>, <asrg@ietf.org>
Subject: RE: [Asrg] article: port 25 blocking
Date: Tue, 12 Apr 2005 11:03:48 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <425BE272.7080803@drivel.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcU/dXSbgh8q+q8uSKS5i/cHU93w4wAE1OpA
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Content-Transfer-Encoding: 7bit

-----Original Message-----
From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of
James Lick
Sent: Tuesday, April 12, 2005 8:00 AM
To: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking

>Port 25 blocking is also a least privileges model.  Consumer ISPs block all
outgoing port 25, then punch a few holes in the firewall for their own mail
servers and the few customers that request an exemption.  
Sounds quite manageable to me.

How can it be "least privileges" unless you micromanage IP ACLs?  All it
takes is a few ISPs to not participate and you have leakage.  There are also
lots of non-consumer IP blocks out there too.  Permitting only SPF compliant
servers has virtually no leakage.

>It's a chicken and egg problem that I don't think any ISP in their right
might would go along with.

At some point, we're going to have to bite the bullet and adopt some sort of
domain level authentication.  Email is a server problem that is best handled
at the DNS and SMTP servers.  Don't try to push this off to the network
administrators and router ACLs.

>Your blog says that port 25 blocking is controversial with users.  I submit
that it is controversial to a miniscule number of users.  On the other hand,
requiring an SPF pass on all incoming email right now would cause huge
amounts of legitimate mail to be blocked.  How controversial do you think
that will be?  Already we have a number of respected anti-spammers who are
quite opposed to SPF because hard fails are occasionally false positives.
You're gonna have people bouncing off the walls if you reject soft fail and
unknown status and only allow SPF pass messages.

SPF enforcement would work if the top 50 ISPs implemented it in unison.
They don't need to implement a hard fail at first, maybe a 48 delay and slap
a "non-SPF" warning on every subject header.  Then start jacking it up to 4
days, 8 days, and then hard fail.  Is this easy?  No.  But we need to stop
skirting beating around the bush and start dealing with the real problem.


George


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


From asrg-bounces@ietf.org  Tue Apr 12 14:46:07 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24374
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 14:46:07 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLQYQ-0001qg-K1
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 14:56:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLQIO-0002uZ-P8; Tue, 12 Apr 2005 14:39:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLQIM-0002uO-Qj
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 14:39:30 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23687
	for <asrg@ietf.org>; Tue, 12 Apr 2005 14:39:16 -0400 (EDT)
Received: from mail1.nber.org ([66.251.72.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLQRm-0001fA-Iw
	for asrg@ietf.org; Tue, 12 Apr 2005 14:49:15 -0400
Received: from mail1 (root@localhost)
	by mail1.nber.org (8.12.8/8.12.8) with SMTP id j3CId7Ct022646
	for <asrg@ietf.org>; Tue, 12 Apr 2005 14:39:07 -0400
Received: from nber6.nber.org (nber6.nber.org [66.251.72.76])
	by mail1.nber.org (8.12.8/8.12.8) with ESMTP id j3CId6vL022623;
	Tue, 12 Apr 2005 14:39:07 -0400
Date: Tue, 12 Apr 2005 14:39:06 -0400 (EDT)
From: Daniel Feenberg <feenberg@nber.org>
To: Mark <admin@asarian-host.net>
Subject: RE: [Asrg] article: port 25 blocking
In-Reply-To: <200504121701.j3CH1hYA039131@asarian-host.net>
Message-ID: <Pine.GSO.4.10.10504121435110.17705-100000@nber6.nber.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8



On Tue, 12 Apr 2005, Mark wrote:

> 
> > -----Original Message-----
> > From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On 
> > Behalf Of Daniel Feenberg
> > Sent: dinsdag 12 april 2005 18:45
> > To: Danny Angus
> > Cc: asrg@ietf.org; asrg-bounces@ietf.org; James Lick
> > Subject: Re: [Asrg] article: port 25 blocking
> > 
> > I have prepared a web page
> > 
> > http://www.nber.org/REASON-FOR-REJECTION/smarthost.html 
> > 
> 
> SMTP.COM says: "Using your sending email address as an identifier,
> SMTP.com's servers recognize you immediately, check your status in our
> database, and deliver your email within seconds."
> 
> Since they force you to identify by "sending email address" (meaning you
> can only use that one email address) they are, pardon my French,
> hilariously unfit to be called a smarthost in the true sense; because a
> true smarthost, like your own smtp server, is, of course, not ridiculously
> tied to 1 email address! LOL :)


Agreed, but in my experience the operators of MTAs on dynamic addresses
have only one user. So it will do fine. The point here is not identify
best practice, but to gently convince the operator of a MTA on a dynamic
address that it isn't going to work, and that he needs to do something
else. Traducing his alternatives won't help me achieve that end.

> 
> - Mark 
>  
>         System Administrator Asarian-host.org
>  
> ---
> "If you were supposed to understand it,
> we wouldn't call it code." - FedEx
> 
> 
> _______________________________________________
> 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 asrg-bounces@ietf.org  Tue Apr 12 16:36:54 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08063
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 16:36:54 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLSHf-0006Tm-9B
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 16:46:55 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLRgq-0007dW-3d; Tue, 12 Apr 2005 16:08:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLRgn-0007cx-RL
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 16:08:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03143
	for <asrg@ietf.org>; Tue, 12 Apr 2005 16:08:39 -0400 (EDT)
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLRqI-0004pL-GD
	for asrg@ietf.org; Tue, 12 Apr 2005 16:18:39 -0400
Received: (qmail 35201 invoked by uid 1013); 12 Apr 2005 20:08:34 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=testkey; d=space.net;
	b=R6j4xLKc/WO5J7M1TlUHaaqa9NkQNTJnw3O7AgvUt8FcWhlrWEYUyssox7QybKLH  ;
Date: Tue, 12 Apr 2005 22:08:34 +0200
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: George Ou <george_ou@netzero.com>
Subject: Re: [Asrg] article: port 25 blocking
Message-ID: <20050412200834.GS20465@Space.Net>
References: <425B50B2.3000305@linuxbox.org> <200504120637.CAA00488@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200504120637.CAA00488@ietf.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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034

On Mon, Apr 11, 2005 at 11:37:05PM -0700, George Ou wrote:
> *  Start banning all non-SPF compliant domains within a certain deadline
> which would effectively make port 25 blocking moot.

Sorry, this is not how SPF works.

Nothing prevents a spammer from getting throwaway domains, adding TTL 300
SPF records and using some 10000 cracked hosts on broadband access to spam.

The .DE TLD alone has currently more than 7 million domains. According to SPF
activists 700,000 domains worldwide now use SPF. This is less than 0.1% of all
domains worldwide. Happy deployment.

SPF is NOT an anti-spam method, it is a method for accreditation. It will
not stop spammers abusing cracked hosts on broadband access. Port 25 blocks will
do this. MTAMARK can help do this without port 25 blocking.

Everything that utilizes the forward domain, which is under full control of the
spammers, will be rather useless unless we have widely deployed Accreditation
Services and these will have tons of other problems associated with.. This is the
reason why even CSV (Certified Server Validation) will be of minor success.

	\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 asrg-bounces@ietf.org  Tue Apr 12 18:21:48 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA18996
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 18:21:48 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLTvC-00026C-Uz
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 18:31:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLTH1-0008ST-Mn; Tue, 12 Apr 2005 17:50:19 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLTGz-0008Rh-JX
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 17:50:17 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15674
	for <asrg@ietf.org>; Tue, 12 Apr 2005 17:50:06 -0400 (EDT)
Message-Id: <200504122150.RAA15674@ietf.org>
Received: from smtp807.mail.sc5.yahoo.com ([66.163.168.186])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLTQV-00017m-D8
	for asrg@ietf.org; Tue, 12 Apr 2005 18:00:08 -0400
Received: from unknown (HELO gous6120) (gcou@sbcglobal.net@216.226.160.13 with
	login)
	by smtp807.mail.sc5.yahoo.com with SMTP; 12 Apr 2005 21:50:03 -0000
From: "George Ou" <george_ou@netzero.com>
To: "'Markus Stumpf'" <maex-lists-spam-ietf-asrg@Space.Net>
Subject: RE: [Asrg] article: port 25 blocking
Date: Tue, 12 Apr 2005 14:50:00 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
In-Reply-To: <20050412200834.GS20465@Space.Net>
Thread-Index: AcU/qJ4hPEk+Y5l/SGGm/Do6NUDXwQAAESVw
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit

-----Original Message-----
From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of
Markus Stumpf
Sent: Tuesday, April 12, 2005 1:09 PM
To: George Ou
Cc: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking

On Mon, Apr 11, 2005 at 11:37:05PM -0700, George Ou wrote:
>> *  Start banning all non-SPF compliant domains within a certain 
>> deadline which would effectively make port 25 blocking moot.

>Sorry, this is not how SPF works.

Says who?  SPF blocks all hosts that are not registered as SMTP servers in
their domain's authoritative DNS servers.  That DOES make blocking consumer
outbound 25 moot.

>Nothing prevents a spammer from getting throwaway domains, adding TTL 300
SPF records and using some 10000 cracked hosts on broadband access to spam.

I never claimed SPF stops spammers from using stolen SMTP credentials.  This
same issue applies to port 25 blocking as well.  SPF does make it possible
to block abusive or irresponsible domains.


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


From asrg-bounces@ietf.org  Tue Apr 12 18:44:27 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20436
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 18:44:26 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLUH6-0002fR-L5
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 18:54:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLU2e-0006Pe-Rz; Tue, 12 Apr 2005 18:39:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLU2d-0006KF-KR
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 18:39:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20169
	for <asrg@ietf.org>; Tue, 12 Apr 2005 18:39:10 -0400 (EDT)
Received: from mail2.panix.com ([166.84.1.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLUC0-0002Zl-4s
	for asrg@ietf.org; Tue, 12 Apr 2005 18:49:13 -0400
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail2.panix.com (Postfix) with ESMTP id 0A9EDA6FB5
	for <asrg@ietf.org>; Tue, 12 Apr 2005 18:39:11 -0400 (EDT)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p3/8.8.8/PanixN1.1) id j3CMdBt04531;
	Tue, 12 Apr 2005 18:39:11 -0400 (EDT)
Date: Tue, 12 Apr 2005 18:39:11 -0400 (EDT)
Message-Id: <200504122239.j3CMdBt04531@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <200504122150.RAA15674@ietf.org> (george_ou@netzero.com)
Subject: Re: [Asrg] article: port 25 blocking
References: <200504122150.RAA15674@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69

"George Ou" <george_ou@netzero.com> wrote:
> From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of
> Markus Stumpf
> On Mon, Apr 11, 2005 at 11:37:05PM -0700, George Ou wrote:
>>> *  Start banning all non-SPF compliant domains within a certain 
>>> deadline which would effectively make port 25 blocking moot.
>
>>Sorry, this is not how SPF works.
>
> Says who?  SPF blocks all hosts that are not registered as SMTP servers in
> their domain's authoritative DNS servers.  That DOES make blocking consumer
> outbound 25 moot.

Markus is right.  What is "their domain"?  It's the domain the trojan
_claims_ it to be.  Who owns that domain?  The spammer.  What does the
spammer's SPF server say the authorized mail sender for that domain
is?  The machine with the trojan on it.

>>Nothing prevents a spammer from getting throwaway domains, adding
>>TTL 300 SPF records and using some 10000 cracked hosts on broadband
>>access to spam.
>
> I never claimed SPF stops spammers from using stolen SMTP
> credentials.

The smtp credentials aren't stolen, they were purchased by the spammer
with the domain.

>  This same issue applies to port 25 blocking as well.

No, it doesn't.  If the ISP blocks port 25, stuff doesn't get out.  If
I require an SPF pass, the spam passes.

>  SPF does make it possible to block abusive or irresponsible
>  domains.

Yes, it does.  Are you going to maintain that list accurately and as
quickly as spammers buy more domains?

Seth

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


From asrg-bounces@ietf.org  Tue Apr 12 18:45:15 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20558
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 18:45:15 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLUHt-0002jJ-60
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 18:55:18 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLTr2-0004o5-DL; Tue, 12 Apr 2005 18:27:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLTr1-0004n6-1Q
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 18:27:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19418
	for <asrg@ietf.org>; Tue, 12 Apr 2005 18:27:19 -0400 (EDT)
Received: from adsl-63-195-85-27.dsl.snfc21.pacbell.net ([63.195.85.27]
	helo=zardoc.esmtp.org) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLU0X-0002GX-6m
	for asrg@ietf.org; Tue, 12 Apr 2005 18:37:22 -0400
Received: from zardoc.esmtp.org (localhost.endmail.org. [127.0.0.1])
	by zardoc.esmtp.org (sendmail X.0.0.PreAlpha17) with ESMTPS
	(TLS=TLSv1/SSLv3, cipher=AES256-SHA, bits=256, verify=NO)
	id S000000000003155900; Tue, 12 Apr 2005 15:27:47 -0700
Received: (from ca@localhost)
	by zardoc.esmtp.org (8.13.0/8.12.10.Beta0/Submit) id j3CMRlPx025422
	for asrg@ietf.org; Tue, 12 Apr 2005 15:27:47 -0700 (PDT)
Date: Tue, 12 Apr 2005 15:27:46 -0700
From: Claus Assmann <ca+asrg@esmtp.org>
To: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking
Message-ID: <20050412222746.GA6026@zardoc.esmtp.org>
Mail-Followup-To: asrg@ietf.org
References: <20050412200834.GS20465@Space.Net> <200504122150.RAA15674@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200504122150.RAA15674@ietf.org>
User-Agent: Mutt/1.5.6i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

On Tue, Apr 12, 2005, George Ou wrote:

> On Mon, Apr 11, 2005 at 11:37:05PM -0700, George Ou wrote:
> >> *  Start banning all non-SPF compliant domains within a certain 
> >> deadline which would effectively make port 25 blocking moot.

> >Markus Stumpf:
> >Sorry, this is not how SPF works.

> Says who?  SPF blocks all hosts that are not registered as SMTP servers in
> their domain's authoritative DNS servers.  That DOES make blocking consumer
> outbound 25 moot.

MTAmark would be right "technology" for this. SPF is not suitable
for this purpose (as Markus explained.)


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


From asrg-bounces@ietf.org  Tue Apr 12 19:07:32 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22315
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 19:07:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLUdT-0003Qd-6k
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 19:17:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLUJt-0000u8-FV; Tue, 12 Apr 2005 18:57:21 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLUJr-0000sl-QQ
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 18:57:20 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21483
	for <asrg@ietf.org>; Tue, 12 Apr 2005 18:57:08 -0400 (EDT)
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLUTO-00035m-UJ
	for asrg@ietf.org; Tue, 12 Apr 2005 19:07:11 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1DLUG4-0002bI-74
	for asrg@ietf.org; Wed, 13 Apr 2005 00:53:24 +0200
Received: from 212.82.251.36 ([212.82.251.36])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <asrg@ietf.org>; Wed, 13 Apr 2005 00:53:24 +0200
Received: from nobody by 212.82.251.36 with local (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <asrg@ietf.org>; Wed, 13 Apr 2005 00:53:24 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: asrg@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Wed, 13 Apr 2005 00:54:15 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 36
Message-ID: <425C5197.6817@xyzzy.claranet.de>
References: <425B50B2.3000305@linuxbox.org> <200504120637.CAA00488@ietf.org>
	<20050412200834.GS20465@Space.Net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 212.82.251.36
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: article: port 25 blocking
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Content-Transfer-Encoding: 7bit

Markus Stumpf wrote:
 
> Sorry, this is not how SPF works.

A receiver could try to "enforce" it, but one of its strong
points is that it's a _voluntary_ system working without any
"worldwide deployment" FUSSP.

> less than 0.1% of all domains worldwide

If the users of these domains don't get the tons of bounces
anymore they got before it's fine for all participants.

Even the evil third in this game can simply switch to one
of the remaining 99.9% domains, all participants are happy.
It's not a trick, it's SPF.

> It will not stop spammers abusing cracked hosts on 
> broadband access.

True.

> Port 25 blocks will do this.

IBTD.  A zombie minus port 25 is still a zombie.  SpamCast
pretends that blocking port 25 is an adequate replacement
of a proper abuse desk, but that's a lie.

> MTAMARK can help do this without port 25 blocking.

Indeed, it could be used as input for DynIP BLs.  Or for
SIQ servers.  SIQ could support SPF or Sender-ID or wild
mixtures of RFCI cum MTAMARK times CSV modulo SPF.

                     Bye, Frank



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


From asrg-bounces@ietf.org  Tue Apr 12 19:33:15 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA20438
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 18:44:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLUH6-0002fS-L0
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 18:54:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLTqM-0004i0-LA; Tue, 12 Apr 2005 18:26:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLTqL-0004gr-3L
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 18:26:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA19412
	for <asrg@ietf.org>; Tue, 12 Apr 2005 18:26:37 -0400 (EDT)
Received: from toaster.scconsult.com ([66.73.230.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLTzs-0002EI-1S
	for asrg@ietf.org; Tue, 12 Apr 2005 18:36:40 -0400
Received: from toaster.scconsult.com (localhost [127.0.0.1])
	by toaster.scconsult.com (Postfix) with ESMTP id C2510537EAA
	for <asrg@ietf.org>; Tue, 12 Apr 2005 18:26:19 -0400 (EDT)
Mime-Version: 1.0
Message-Id: <p0623051bbe8150a2869e@toaster.scconsult.com>
In-Reply-To: <200504120637.CAA00488@ietf.org>
References: <200504120637.CAA00488@ietf.org>
Date: Tue, 12 Apr 2005 18:26:16 -0400
To: <asrg@ietf.org>
From: Bill Cole <asrg2@billmail.scconsult.com>
Subject: RE: [Asrg] article: port 25 blocking
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813

At 11:37 PM -0700 4/11/05, George Ou wrote:
>Blocking port 25 harms a lot of legitimate uses.  Why not do the following
>to deal with the issue as a whole.
>
>*  Start banning all non-SPF compliant domains within a certain deadline
>which would effectively make port 25 blocking moot.

SPF '-all' publishing and enforcement has not proven feasible for 
domains of any significant scale and/or user diversity. Without all 
domains publishing '-all' record along with a large fraction of 
receiving systems being willing to enforce those records, SPF use 
cannot reduce the utility of port 25 blocking.

Beyond that, any proposal that requires everyone to make changes on 
the same schedule or else the first movers will break their systems 
badly, is simply never going to happen at all on any schedule. SPF as 
the FUSSP requires behavior that is self-harming unless everyone else 
does it at the same time.

>*  Then we deal with the problem of ISPs who don't implement SMTP AUTH and
>who won't implement some reasonable rate limiting schemes.

Who is 'we' and how do you propose 'we' deal with such ISP's? Most of 
the larger ISP's  for years have been making business decisions fior 
a decade in support of continuing the growth of spam and the spread 
of the malware used to send most modern spam, and there has been no 
'we' willing and able to 'deal' with them in any serious and 
consistent way for all of that time.

>*  Then start requiring some sort of official registration or bonding of
>domains who bulk send (based on Distributed Checksum Clearinghouse
>measurements) so that we can either easily track you down for prosecution or
>we confiscate the bond for any kind of abuses from an SPF abusive domain.

The owners of the mail systems I work with are not going to pursue 
anyone's certification and are unlikely to trust any certification 
that anyone issues. Even those which send some bulk mail and those 
who are inundated by it have seen no value in certification systems 
like Habeas or Ironport's Bonded Sender. Such systems have proven in 
the marketplace to be of very limited interest and utility.

>These steps would seem to me a lot more effective and cause a lot less
>collateral damage.

You've got a very odd idea of what constitutes 'collateral damage' if 
you believe that requiring that all domain owners make mandatory 
changes, establishing a new enforcement authority, and creating a new 
certifying authority to bless domains constitutes less damage than 
inconveniencing a single-digit percentage of individual end users.

>As the owner of a few small personal domains and someone
>who uses outbound 25 for legitimate SMTP relay, I'd much rather you force me
>to put in a few SPF records than blocking my outbound port 25 access.

I see. Those steps seem less damaging to you because they cause less 
damage to you.

Have you looked at how port 25 blocking is actually being done by 
even the minimally competent ISP's? SBC is an example of one such. 8 
months ago they had a press release and sent mail to all customers 
about the coming rollout of port 25 blocking. With that they included 
a way to preemptively request exemption and they made clear that 
customers with static address accounts would be excluded by default. 
To my profound shock, SBC has actually managed to execute that 
rollout with reasonable speed and accuracy. There may well be some 
ISP's who are implementing port 25 blocking without exempting users 
with static IP assignments, but I believe they would be the minority. 
SBC's willingness to provide exceptions for anyone who asks may be 
unusual, but it is not unique.

Note that I DO NOT argue that port 25 blocking is a panacea. It is a 
generally negative thing, but as long as ISP's insist on offering 
services in ways that encourage customers to view their own computers 
and network connection as an appliance requiring no more thought than 
a toaster or a telephone, the customers of that sort of service 
should be surrounded by significant impediments to their 
exploitation, which intrinsically includes impediments to their 
misuse of the network at large where people who are competent to 
handle an unfettered link operate. It is unfortunate that no useful 
consensus is possible on what constitutes 'competent' in this 
context, so the evolving proxy for competence is willingness and 
ability to find and pay for an account that is not restricted.

>We're
>essentially talking about the same thing here only from different sides of
>the problem.  Do we create an ACL (Access Control List) that denies all
>non-SMTP servers of the world or do we create an ACL that permits all
>legitimate SMTP servers of the world?  It would seem to me that the latter
>is a much smaller database and much easier to implement than the former.

Yes, and because the two yield logically identical results, either 
ends up as a default assumption of invalidity and some system where 
the legitimate systems are blessed. This is how port 25 blocking is 
done: network owners who are the best authorities on the nature of 
their address space and its use decide where to allow port 25 
traffic. If they decide to only service people who have no desire for 
full service, they can do so. If they decide to charge a little more 
for full service, they can do that. If they decide that full service 
is available to anyone who knows that they want it, that is also 
feasible.


-- 
Bill Cole
bill@scconsult.com


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


From asrg-bounces@ietf.org  Tue Apr 12 19:40:52 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24745
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 19:40:52 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLV9i-0004BE-9W
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 19:50:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLUdU-0003n9-Jy; Tue, 12 Apr 2005 19:17:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLUdS-0003li-5N
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 19:17:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA23163
	for <asrg@ietf.org>; Tue, 12 Apr 2005 19:17:22 -0400 (EDT)
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLUmz-0003gj-OJ
	for asrg@ietf.org; Tue, 12 Apr 2005 19:27:26 -0400
Received: (qmail 70145 invoked by uid 1013); 12 Apr 2005 23:17:22 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=testkey; d=space.net;
	b=KIV+qAq5jPw6yL/maVD8rT/8IfRy3Ec53FATLWIhX2u579GqdLoT9p233zkXXvag  ;
Date: Wed, 13 Apr 2005 01:17:22 +0200
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: George Ou <george_ou@netzero.com>
Subject: Re: [Asrg] article: port 25 blocking
Message-ID: <20050412231722.GU20465@Space.Net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cd26b070c2577ac175cd3a6d878c6248
Cc: asrg@ietf.org, "'Markus Stumpf'" <maex-lists-spam-ietf-asrg@Space.Net>
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6

On Tue, Apr 12, 2005 at 02:50:00PM -0700, George Ou wrote:
> >Sorry, this is not how SPF works.
> 
> Says who?

Says me.

> SPF blocks all hosts that are not registered as SMTP servers in
> their domain's authoritative DNS servers.  That DOES make blocking consumer
> outbound 25 moot.

No. *sigh*

> >Nothing prevents a spammer from getting throwaway domains, adding TTL 300
> > SPF records and using some 10000 cracked hosts on broadband access to spam.
> 
> I never claimed SPF stops spammers from using stolen SMTP credentials.

But you claim SPF makes port 25 blocking moot. To me there is some kind of
antagonism in this.

> This
> same issue applies to port 25 blocking as well.

No, it does not apply to port 25 blocking as well.
Port 25 blocking stops dull spammers, stops dull viruses, stops dull botnets
and stops misconfigured hosts. It stops unauthenticated mail injection (usually),
besides for smarthosts.
You can't turn a host behind a port 25 block into something that pretends to be a
mailserver and makes connections to other mailservers as it were itself a mailserver.

SPF does all this NOT and it breaks widely deployed Internet Mail Infrastructure.

> SPF does make it possible
> to block abusive or irresponsible domains.

If this domain uses SPF records, yes. If it doesn't you have the same situation
as you have now. With less than 0.01% of all domains using SPF records really a
big win. Deployment is the problem. Without > 80% of all domains deploying SPF
(and SRS) I will never block based on SPF, because I have better things to do
than to talk to 500 business customers a day and explain them 100 times why the
eMail from a SPF -all didn't reach them.

Do you have customers? Do you manage domains for them? Choose 100. Call them and
ask them for information that is needed to add correct and usable SPF records.
Come back in 4 weeks and tell us your results. Call them again in 6 months and
look how much of the information is still accurate.
We're managing only about 20-40000 domains. We have direct customers, we have
resellers. Adding useful SPF records will take *ages*:
    250 working days a year. 
    8 working hours a day
    4 domains per hour (*very* optimistic)
This makes 8000 domains per one person per year. With 30000 domain this will make
3.75 years for one person or about 1 year for 4-5 persons. And: this staff has to
be skilled.  They have to understand: what is SPF, how emails work, what IP addresses
are and they have to be able to ask the correct questions and you need large databases
of mailservers, because if the customer says: "I am using provider EXAMPLE",
you have to know the IP addresses of the outgoing mailservers and you need *tight*
inter-ISP communication, because you have to change SPF records if the other
ISP changes MTA addresses. As to my knowledge there are currently NO such lists.
So before starting the "SPF-for-every-domain" project we should probably start the
"every-ISP-lists-its-mailservers" project (dooh, this would be a MTAMARK like
list).

Who will pay for this? With USD 5 or 6 for a domain how to do fund the 15-30 minutes
it takes to query the customer for SPF records and add them?

Reality bites.

*sigh* We've been through this a 100 times on this list and on MARID.
Is this Groundhog Day or what?

	\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 asrg-bounces@ietf.org  Tue Apr 12 19:48:19 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25447
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 19:48:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLVGx-0004MX-8V
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 19:58:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLUsG-0006I6-9v; Tue, 12 Apr 2005 19:32:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLUsE-0006Gs-R3
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 19:32:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24409
	for <asrg@ietf.org>; Tue, 12 Apr 2005 19:32:39 -0400 (EDT)
Received: from toaster.scconsult.com ([66.73.230.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLV1l-00042c-Ke
	for asrg@ietf.org; Tue, 12 Apr 2005 19:42:43 -0400
Received: from toaster.scconsult.com (localhost [127.0.0.1])
	by toaster.scconsult.com (Postfix) with ESMTP id 19991537EFF
	for <asrg@ietf.org>; Tue, 12 Apr 2005 19:32:25 -0400 (EDT)
Mime-Version: 1.0
Message-Id: <p0623051dbe81fbe5aa98@toaster.scconsult.com>
In-Reply-To: <6f3pjfer25drbae.120420050621@shayndel>
References: <6f3pjfer25drbae.120420050621@shayndel>
Date: Tue, 12 Apr 2005 19:32:23 -0400
To: <asrg@ietf.org>
From: Bill Cole <asrg2@billmail.scconsult.com>
Subject: RE: [Asrg] article: port 25 blocking
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a

At 6:20 AM -0400 4/12/05, Larry Seltzer wrote:
>I had a thought yesterday that I wish I had before I hit the publish button
>on the article: Perhaps the answer for people who need an exception case for
>port 25 blocking is port 587

Yes, in most cases. Port 587 is the standard port for initial mail 
submission, a protocol so closely related to SMTP that most MUA's 
don't even have to know that they are speaking it instead of SMTP.

People who are not doing initial mail submission and want port 25 for 
things they should not try to do on port 587 instead probably should 
not be doing that from a dynamically assigned address anyway, unless 
they have deep support from their ISP for that sort of use, including 
dynamically assigned reverse DNS records and other such oddities only 
witnessed in corporate networks and dreams born of jalapeno and 
anchovy pizza...

>  or even some non-standard port.

No. Please no. I beg you: do not suggest the use of 'some 
non-standard port' for anything in a published article.



>I checked and
>my own mail server supports both.

Any modern MTA worth using will support port 587 use, and most will 
allow you you put the listener on any arbitrary port. The latter 
should be reserved for carefully considered and highly unusual 
circumstances.

>  Put SMTP on port 1125 or something like
>that for your external users,

Please, no. There are standards for using non-standard ports. Using 
otherwise assigned ports is a generally bad idea.

>or use 587 and require authentication. Is
>there a reason this wouldn't work?

Sturgeon's Law always applies, but there is no other reason I've seen.

Yes, people use garbage MTA's and/or firewalls and/or configure one 
or both  poorly. At least one ISP briefly has blocked port 587 out of 
what can most charitably described as overzealousness.

>I'm also going to contact SBC and ask them how their opt-out system is
>working so far.

Based on the traffic in the private sbcglobal.help.* newsgroups, it 
seems to be working well, but of course the population of people who 
would manage to share experiences there is likely not a random 
representative sample. A somewhat differently skewed sample of 19 
people working in an IT firm with SBC DSL accounts found 2 with 
static accounts (no block) 1 who used the preemptive opt-out 
successfully, and 3 who think their machines got faster since the 
first of the year.

On the negative side, those same SBC  (user to user) help newsgroups 
have shown some reports of what looks like SBC cutting off users from 
the smtp.$SBCUNIT.yahoo.com mail servers that are part of the 
SBC-Yahoo unnatural act.


-- 
Bill Cole
bill@scconsult.com


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


From asrg-bounces@ietf.org  Tue Apr 12 19:48:30 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25562
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 19:48:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLVH7-0004NI-5K
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 19:58:34 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLUnc-0005jQ-Jh; Tue, 12 Apr 2005 19:28:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLUna-0005iQ-Cn
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 19:28:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24040
	for <asrg@ietf.org>; Tue, 12 Apr 2005 19:27:50 -0400 (EDT)
Message-Id: <200504122327.TAA24040@ietf.org>
Received: from smtp818.mail.sc5.yahoo.com ([66.163.170.4])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLUx8-0003vs-4c
	for asrg@ietf.org; Tue, 12 Apr 2005 19:37:54 -0400
Received: from unknown (HELO gous6120) (gcou@sbcglobal.net@216.226.160.13 with
	login)
	by smtp818.mail.sc5.yahoo.com with SMTP; 12 Apr 2005 23:27:52 -0000
From: "George Ou" <george_ou@netzero.com>
To: "'Bill Cole'" <asrg2@billmail.scconsult.com>, <asrg@ietf.org>
Subject: RE: [Asrg] article: port 25 blocking
Date: Tue, 12 Apr 2005 16:27:49 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-reply-to: <p0623051bbe8150a2869e@toaster.scconsult.com>
Thread-Index: AcU/tXCPoGLt8d80SdCdfBms0+IcFwAAK7Ig
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Content-Transfer-Encoding: 7bit

-----Original Message-----
From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of Bill
Cole
Sent: Tuesday, April 12, 2005 3:26 PM
To: asrg@ietf.org
Subject: RE: [Asrg] article: port 25 blocking

>SPF '-all' publishing and enforcement has not proven feasible for domains
of any significant scale and/or user diversity. Without all domains
publishing '-all' record along with a large fraction of receiving systems
being willing to enforce those records, SPF use cannot reduce the utility of
port 25 blocking.

>From the way you make it sound, it sounds like we will NEVER have any kind
of domain level authentication and the "from:" address will remain on the
honor system.  Since it appears that there is no consensus for any one's
solution be it SPF enforcement or port 25 blocking, you might be right about
that so the future remains bleak.

>Beyond that, any proposal that requires everyone to make changes on the
same schedule or else the first movers will break their systems badly, is
simply never going to happen at all on any schedule. SPF as the FUSSP
requires behavior that is self-harming unless everyone else does it at the
same time.

If we could get the top 50 domains to start "punishing" non-SPF compliant
with delays and a gradual migration to a hard fail in unison, would that not
prompt other domains to become SPF compliant?


George


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


From asrg-bounces@ietf.org  Tue Apr 12 20:03:44 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27316
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 20:03:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLVVs-0004oJ-2k
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 20:13:48 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLVKX-0003Fq-IN; Tue, 12 Apr 2005 20:02:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLVKV-00038a-7Y
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 20:02:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27079
	for <asrg@ietf.org>; Tue, 12 Apr 2005 20:01:54 -0400 (EDT)
Message-Id: <200504130001.UAA27079@ietf.org>
Received: from smtp808.mail.sc5.yahoo.com ([66.163.168.187])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLVU4-0004iC-TE
	for asrg@ietf.org; Tue, 12 Apr 2005 20:11:58 -0400
Received: from unknown (HELO gous6120) (gcou@sbcglobal.net@216.226.168.4 with
	login)
	by smtp808.mail.sc5.yahoo.com with SMTP; 13 Apr 2005 00:01:53 -0000
From: "George Ou" <george_ou@netzero.com>
To: "'Bill Cole'" <asrg2@billmail.scconsult.com>, <asrg@ietf.org>
Subject: RE: [Asrg] article: port 25 blocking
Date: Tue, 12 Apr 2005 17:01:52 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcU/tXCPoGLt8d80SdCdfBms0+IcFwABcy8g
In-Reply-To: <p0623051bbe8150a2869e@toaster.scconsult.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit

-----Original Message-----
From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of Bill
Cole
Sent: Tuesday, April 12, 2005 3:26 PM
To: asrg@ietf.org
Subject: RE: [Asrg] article: port 25 blocking


>Have you looked at how port 25 blocking is actually being done by even the
minimally competent ISP's? SBC is an example of one such. 8 months ago they
had a press release and sent mail to all customers about the coming rollout
of port 25 blocking. With that they included a way to preemptively request
exemption and they made clear that customers with static address accounts
would be excluded by default. 
To my profound shock, SBC has actually managed to execute that rollout with
reasonable speed and accuracy. There may well be some ISP's who are
implementing port 25 blocking without exempting users with static IP
assignments, but I believe they would be the minority. 
SBC's willingness to provide exceptions for anyone who asks may be unusual,
but it is not unique.


You're always free to implement port 25 blocking on your side for inbound
traffic which effectively achieves the same thing for your network.  You
just need to implement a large ACL yourself that might be synchronized with
a large shared database somewhere on the net.  Why do you want everyone else
to implement outbound port 25 blocks for you?

Bottom line is, you'll have the same problem convincing people to block
outbound 25 as you will convincing them to implement SPF.  SPF just happens
to be a better solution in my opinion.


George


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


From asrg-bounces@ietf.org  Tue Apr 12 20:08:34 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27733
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 20:08:34 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLVaY-0004wh-Ra
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 20:18:39 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLVQH-0006qX-CH; Tue, 12 Apr 2005 20:08:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLVQF-0006pv-Sf
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 20:07:59 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA27618
	for <asrg@ietf.org>; Tue, 12 Apr 2005 20:07:48 -0400 (EDT)
Message-Id: <200504130007.UAA27618@ietf.org>
Received: from smtp804.mail.sc5.yahoo.com ([66.163.168.183])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLVZl-0004uL-VB
	for asrg@ietf.org; Tue, 12 Apr 2005 20:17:52 -0400
Received: from unknown (HELO gous6120) (gcou@sbcglobal.net@216.226.168.4 with
	login)
	by smtp804.mail.sc5.yahoo.com with SMTP; 13 Apr 2005 00:07:47 -0000
From: "George Ou" <george_ou@netzero.com>
To: "'Bill Cole'" <asrg2@billmail.scconsult.com>, <asrg@ietf.org>
Subject: RE: [Asrg] article: port 25 blocking
Date: Tue, 12 Apr 2005 17:07:45 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcU/u+0lPSJkEWyhSuq08+rVDDQhsQAAFo2w
In-Reply-To: <p0623051dbe81fbe5aa98@toaster.scconsult.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit

-----Original Message-----
From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of Bill
Cole
Sent: Tuesday, April 12, 2005 4:32 PM
To: asrg@ietf.org
Subject: RE: [Asrg] article: port 25 blocking

>People who are not doing initial mail submission and want port 25 for
things they should not try to do on port 587 instead probably should not be
doing that from a dynamically assigned address anyway, unless they have deep
support from their ISP for that sort of use, including dynamically assigned
reverse DNS records and other such oddities only witnessed in corporate
networks and dreams born of jalapeno and anchovy pizza...

The standard firewall configuration is to block all traffic unless otherwise
specified.  While it's true that most SMTP servers will accept port 587,
most firewall policies only permit inbound TCP 25 to an SMTP server.  Call
this overzealousness if you will, but it's a simple reality.


George


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


From asrg-bounces@ietf.org  Tue Apr 12 20:38:17 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25453
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 19:48:19 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLVGw-0004MV-GV
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 19:58:23 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLV0p-0007be-7i; Tue, 12 Apr 2005 19:41:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLV0n-0007UU-5N
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 19:41:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA24773
	for <asrg@ietf.org>; Tue, 12 Apr 2005 19:41:29 -0400 (EDT)
Message-Id: <200504122341.TAA24773@ietf.org>
Received: from smtp812.mail.sc5.yahoo.com ([66.163.170.82])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLVAK-0004CZ-1f
	for asrg@ietf.org; Tue, 12 Apr 2005 19:51:33 -0400
Received: from unknown (HELO gous6120) (gcou@sbcglobal.net@216.226.160.13 with
	login)
	by smtp812.mail.sc5.yahoo.com with SMTP; 12 Apr 2005 23:41:30 -0000
From: "George Ou" <george_ou@netzero.com>
To: "'Markus Stumpf'" <maex-lists-spam-ietf-asrg@Space.Net>
Subject: RE: [Asrg] article: port 25 blocking
Date: Tue, 12 Apr 2005 16:41:28 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-reply-to: <20050412231722.GU20465@Space.Net>
Thread-Index: AcU/tcjGzvzYcGEBRT6w6M2e/8wEtgAAgD/A
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Content-Transfer-Encoding: 7bit

-----Original Message-----
From: Markus Stumpf [mailto:maex-lists-spam-ietf-asrg@Space.Net] 
Sent: Tuesday, April 12, 2005 4:17 PM
To: George Ou
Cc: 'Markus Stumpf'; asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking

>We're managing only about 20-40000 domains. We have direct customers, we
have resellers. Adding useful SPF records will take *ages*:
    250 working days a year. 
    8 working hours a day
    4 domains per hour (*very* optimistic) This makes 8000 
[snip]

>Who will pay for this? With USD 5 or 6 for a domain how to do fund the
15-30 minutes it takes to query the customer for SPF records and add them?

>Reality bites.

Surely you can find an automated system for managing SPF records for those
40,000 domains you're managing.  You're already managing 40,000 MX records
right?  What would be wrong with managing SPF as well?  If you were
reinventing SMTP today, would you honestly implement it with zero domain
level authentication?

Most people already manage their own DNS when they sign up with a hosting
service via web interface.  Since they're already managing their MX records
now, no reason they can't manage their own SPF records.  There are even
automated web interface wizards that help users generate SPF records for
their DNS servers.  If a user is a clueless user that uses a brain dead
script to set up their domain, simply have the brain dead script
automatically add the SPF records in addition to the MX records.  Those
people are probably using your standard relay servers anyways so it's fairly
easy to use default settings.


George


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


From asrg-bounces@ietf.org  Tue Apr 12 21:05:40 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01259
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 21:05:40 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLWTm-00063U-PX
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 21:15:43 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLWFR-0001Z9-OR; Tue, 12 Apr 2005 21:00:53 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLWFP-0001Z4-TV
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 21:00:51 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01118
	for <asrg@ietf.org>; Tue, 12 Apr 2005 21:00:49 -0400 (EDT)
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLWP5-0005xh-Cg
	for asrg@ietf.org; Tue, 12 Apr 2005 21:10:52 -0400
Received: (qmail 86158 invoked by uid 1013); 13 Apr 2005 01:00:45 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=testkey; d=space.net;
	b=GklPST51R5ig1T37booN43NpHWxLNhFXRYchrorYI6WiZR7qIeZc4sXBh+/h90YL  ;
Date: Wed, 13 Apr 2005 03:00:45 +0200
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: George Ou <george_ou@netzero.com>
Subject: Re: [Asrg] article: port 25 blocking
Message-ID: <20050413010045.GZ20465@Space.Net>
References: <20050412231722.GU20465@Space.Net> <200504122341.TAA24773@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200504122341.TAA24773@ietf.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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64
Cc: asrg@ietf.org, "'Markus Stumpf'" <maex-lists-spam-ietf-asrg@Space.Net>
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab

On Tue, Apr 12, 2005 at 04:41:28PM -0700, George Ou wrote:
> Most people already manage their own DNS when they sign up with a hosting
> service via web interface.  Since they're already managing their MX records
> now, no reason they can't manage their own SPF records.

MX != outgoing SMTP

> There are even
> automated web interface wizards that help users generate SPF records for
> their DNS servers.  If a user is a clueless user that uses a brain dead
> script to set up their domain, simply have the brain dead script
> automatically add the SPF records in addition to the MX records.

Again, MX != outgoing SMTP for large parts of the Internet.
Call your provider and request a list of outgoing SMTP IP addresses and see what
you get. And remember, the IP address you use for a smart/relay may be totally
different from that the outgoing IP of that server is.

> Those
> people are probably using your standard relay servers anyways so it's fairly
> easy to use default settings.

No, a not so small number of them aren't using any of our MTAs at all.

And again: changing IPs for MX servers is easy. The MX carries that name, change
the IP for that name, done. All you have to do is change ONE A record in ONE
zone.
SPF records carry IP addresses. Changing/adding/deleting the IP address of an
outgoing MTA of an ISP requires ALL zones that list (or don't yet) that IP
address in the SPF records to be changed. Even all the SPF records in domains
that are NOT under control by the ISP providing the outgoing mailservers.

Btw.
    Return-Path: <george_ou@netzero.com>
    DomainKey-Status: no signature
    Received: from smtp812.mail.sc5.yahoo.com (66.163.170.82)
      by moebius.space.net with SMTP; 12 Apr 2005 23:41:32 -0000

I can't find SPF records for netzero.com. Your mail routing is a very good
example. You send via Yahoo and you receive via mx.lax.untd.com and
mx.nyc.untd.com. Contact Yahoo and try to get a list of IPs and add SPF
records.

Don't just talk, act and add "-all" SPF records to netzero.com. (also note that
adding one for the domain is NOT enough, you have to add SPF records for all RRs
in that domain or they may be abused).

	\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 asrg-bounces@ietf.org  Tue Apr 12 21:05:41 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01279
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 21:05:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLWTn-00063f-UX
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 21:15:44 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLWCw-00012l-5L; Tue, 12 Apr 2005 20:58:18 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLWCu-00012g-Kz
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 20:58:16 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA00917
	for <asrg@ietf.org>; Tue, 12 Apr 2005 20:58:14 -0400 (EDT)
Received: from mail1.panix.com ([166.84.1.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLWMa-0005uC-Az
	for asrg@ietf.org; Tue, 12 Apr 2005 21:08:17 -0400
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail1.panix.com (Postfix) with ESMTP id ED0DC58AD8
	for <asrg@ietf.org>; Tue, 12 Apr 2005 20:58:09 -0400 (EDT)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p3/8.8.8/PanixN1.1) id j3D0wAP28978;
	Tue, 12 Apr 2005 20:58:10 -0400 (EDT)
Date: Tue, 12 Apr 2005 20:58:10 -0400 (EDT)
Message-Id: <200504130058.j3D0wAP28978@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <200504130001.UAA27079@ietf.org> (george_ou@netzero.com)
Subject: Re: [Asrg] article: port 25 blocking
References: <200504130001.UAA27079@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5

"George Ou" <george_ou@netzero.com> wrote:

> You're always free to implement port 25 blocking on your side for
> inbound traffic which effectively achieves the same thing for your
> network.  You just need to implement a large ACL yourself that might
> be synchronized with a large shared database somewhere on the net.

Where, precisely, is the large accurate shared database?

Every ISP knows which of its IP addresses hold machines that ought to
be allowed to send email directly outside its network.  That's local
knowledge.  Nobody has complete and accurate global knowledge.

>  Why do you want everyone else to implement outbound port 25 blocks
>  for you?

Because they're the ones with the accurate information.

> Bottom line is, you'll have the same problem convincing people to
> block outbound 25 as you will convincing them to implement SPF.

They can do both.  But blocking port 25 causes their network to send
me a lot less spam, which gets them fewer complaints and makes their
legitimate email less likely to be blocked.  Some networks like that.

>  SPF just happens to be a better solution in my opinion.

Not in the opionion of many others, some of whom are a lot more
influential.

Seth

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


From asrg-bounces@ietf.org  Tue Apr 12 21:14:32 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01930
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 21:14:32 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLWcN-0006Hx-M8
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 21:24:35 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLWSW-00049O-FS; Tue, 12 Apr 2005 21:14:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLWSV-00048P-E9
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 21:14:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01925
	for <asrg@ietf.org>; Tue, 12 Apr 2005 21:14:21 -0400 (EDT)
Received: from www.scconsult.com ([66.73.230.185] helo=toaster.scconsult.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLWc9-0006Ff-Vx
	for asrg@ietf.org; Tue, 12 Apr 2005 21:24:24 -0400
Received: from toaster.scconsult.com (localhost [127.0.0.1])
	by toaster.scconsult.com (Postfix) with ESMTP id 588C2537F91
	for <asrg@ietf.org>; Tue, 12 Apr 2005 21:12:40 -0400 (EDT)
Mime-Version: 1.0
Message-Id: <p06230521be821134a91a@toaster.scconsult.com>
Date: Tue, 12 Apr 2005 21:12:37 -0400
To: <asrg@ietf.org>
From: Bill Cole <asrg2@billmail.scconsult.com>
Subject: RE: [Asrg] article: port 25 blocking
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 057ebe9b96adec30a7efb2aeda4c26a4

[ broken quoting repaired]

At 4:27 PM -0700 4/12/05, George Ou wrote:
>-----Original Message-----
>From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of Bill
>Cole
>Sent: Tuesday, April 12, 2005 3:26 PM
>To: asrg@ietf.org
>Subject: RE: [Asrg] article: port 25 blocking
>
>>SPF '-all' publishing and enforcement has not proven feasible for domains
>>of any significant scale and/or user diversity. Without all domains
>>publishing '-all' record along with a large fraction of receiving systems
>>being willing to enforce those records, SPF use cannot reduce the utility of
>>port 25 blocking.
>
>From the way you make it sound, it sounds like we will NEVER have any kind
>of domain level authentication and the "from:" address will remain on the
>honor system.

Yes and no. There already IS domain-level authentication for those 
who want and need it and have taken the time to set it up with 
domains they want to maintain reliable authentication with.

Domain-level authentication that is really trustworthy and fully 
enforceable (i.e. both passing and failing are treated as 
definitively meaning something) with all domains is never going to 
happen. SPF has been a good demo of why it can't work. I say that as 
someone who was enthusiastic and evangelistic 5 years ago about the 
core concept that evolved into SPF. I was wrong. SPF and its kin are 
not completely worthless, but they won't ever be a full solution to 
spam.

Yahoo's DomainKeys stands a chance of being useful domain 
authentication that is not onerous to set up and has different (and 
less ugly) break points than SPF, but it also is not going to ever be 
truly global and enforceable. Even if it were, domain authentication 
is not the same thing as authorization, and it is already common for 
spammers to use 'throwaway' domains in enough volume that they've 
made blacklisting by authoritative nameserver a usable tactic.

>Since it appears that there is no consensus for any one's
>solution be it SPF enforcement or port 25 blocking, you might be right about
>that so the future remains bleak.

Not at all. The present is reasonably good and the future is fairly 
bright. The exceptions to that are for people who want a single magic 
bullet for spam control, and particularly for people who want that 
magic bullet to be their own patented idea. It is possible right now 
to achieve 95% spam rejection before DATA in SMTP and 99% rejection 
overall, with less than 0.01% false positives. The constraints in 
which that can be done are not economically feasible for large ISP's 
and might not even be possible for their sorts of very large and very 
diverse mail domains.

Looking at the problem as one addressed by SPF *or* port 25 blocking 
*or* some other approach is a hopeless approach. SPF and port 25 
blocking both can help solve certain problems related to spam, but 
neither is anywhere near a full solution. There is a huge set of 
tactics and tools out there right now that can be applied carefully, 
selectively, and *jointly* in different situations to achieve very 
good results. The 'spam problem' is not that no one knows how to 
avoid spam, but rather that too few people are willing to devote the 
needed resources to avoiding it and making sure they don't contribute 
to it. SPF helps on one side by letting some domains publish hints of 
mixed value as to the validity of mail claiming to be them. Port 25 
blocking of dynamically assigned address space aids on another front 
by reducing the population of useful spam zombies.


>>Beyond that, any proposal that requires everyone to make changes on the
>>same schedule or else the first movers will break their systems badly, is
>>simply never going to happen at all on any schedule. SPF as the FUSSP
>>requires behavior that is self-harming unless everyone else does it at the
>>same time.
>
>If we could get the top 50 domains to start "punishing" non-SPF compliant
>with delays and a gradual migration to a hard fail in unison, would that not
>prompt other domains to become SPF compliant?

Yes, and if we could get pigs to grow wings and wear saddles, we 
could have leaner pork, less traffic congestion, and a lot of free 
fertilizer from the sky for everyone.

Even global adoption of SPF with hard failure does not solve the 
problem addressed by port 25 blocking. The trick of setting up 
perfectly valid domains with records that seem to say that abused 
zombie machines on dynamically assigned addresses are perfectly valid 
mail servers for that domain is about 2 years old. A zombie can 
easily have a valid SPF record for the domain it sends as.






-- 
Bill Cole
bill@scconsult.com


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


From asrg-bounces@ietf.org  Tue Apr 12 21:15:54 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02058
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 21:15:53 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLWdf-0006JO-Vc
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 21:25:57 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLWSC-00043r-0w; Tue, 12 Apr 2005 21:14:04 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLWSA-00043L-KH
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 21:14:02 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA01900
	for <asrg@ietf.org>; Tue, 12 Apr 2005 21:13:44 -0400 (EDT)
Received: from mail3.panix.com ([166.84.1.74])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLWba-0006GL-HF
	for asrg@ietf.org; Tue, 12 Apr 2005 21:23:47 -0400
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail3.panix.com (Postfix) with ESMTP id A8CF998202
	for <asrg@ietf.org>; Tue, 12 Apr 2005 21:13:44 -0400 (EDT)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p3/8.8.8/PanixN1.1) id j3D1Di320540;
	Tue, 12 Apr 2005 21:13:44 -0400 (EDT)
Date: Tue, 12 Apr 2005 21:13:44 -0400 (EDT)
Message-Id: <200504130113.j3D1Di320540@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <200504130007.UAA27618@ietf.org> (george_ou@netzero.com)
Subject: Re: [Asrg] article: port 25 blocking
References: <200504130007.UAA27618@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32

"George Ou" <george_ou@netzero.com> wrote:

> The standard firewall configuration is to block all traffic unless
> otherwise specified.

Which RFC defines that "standard"?

>  While it's true that most SMTP servers will accept port 587,
> most firewall policies only permit inbound TCP 25 to an SMTP server.

"most" out of precisely how many you surveyed?

And the smtp server needs to know to treat 587 differently (clients
must be identified), so it should know to accept connections there.

>  Call this overzealousness if you will, but it's a simple reality.

In which universe?

Seth

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


From asrg-bounces@ietf.org  Tue Apr 12 21:26:47 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02792
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 21:26:46 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLWoE-0006a0-3y
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 21:36:50 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLWcd-0006Yd-3y; Tue, 12 Apr 2005 21:24:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLWcb-0006Y6-VC
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 21:24:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02765
	for <asrg@ietf.org>; Tue, 12 Apr 2005 21:24:47 -0400 (EDT)
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLWmH-0006Xf-Km
	for asrg@ietf.org; Tue, 12 Apr 2005 21:34:51 -0400
Received: (qmail 90152 invoked by uid 1013); 13 Apr 2005 01:24:45 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=testkey; d=space.net;
	b=RjeIZcNB/hs2WhsrDXM451I2HVAIrFVyo+JeZpi9Xf8GV4erfqAKEh5ZHH/QgUV6  ;
Date: Wed, 13 Apr 2005 03:24:45 +0200
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking
Message-ID: <20050413012445.GA20465@Space.Net>
References: <200504130001.UAA27079@ietf.org>
	<200504130058.j3D0wAP28978@panix5.panix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200504130058.j3D0wAP28978@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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b

On Tue, Apr 12, 2005 at 08:58:10PM -0400, Seth Breidbart wrote:
> Every ISP knows which of its IP addresses hold machines that ought to
> be allowed to send email directly outside its network.

I doubt that.
If we give e.g. a /28 to a (business) customer we don't know which IP the
mailserver will be on (if any). I don't think we are different with this regard to
the majority of all other ISPs.
We get a hint if the customer wants us to set up revDNS and add a RR that points
to a machine named "mail" or "exchange" but sometimes the name is "www" or even
"snoopy".

> That's local
> knowledge.  Nobody has complete and accurate global knowledge.

But that could be made public with MTAMARK ;-)))

> > Bottom line is, you'll have the same problem convincing people to
> > block outbound 25 as you will convincing them to implement SPF.
> 
> They can do both.  But blocking port 25 causes their network to send
> me a lot less spam, which gets them fewer complaints and makes their
> legitimate email less likely to be blocked.  Some networks like that.

And it is *much* easier deployed.
There is a big difference between 5 or 10 rules in 2 to 20 border routers and
SPF lines in some 10K domains and also to the RRs in those domains.

	\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 asrg-bounces@ietf.org  Tue Apr 12 22:02:18 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04669
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 22:02:18 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLXMb-0007Kg-IJ
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 22:12:22 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLX87-0004nR-BY; Tue, 12 Apr 2005 21:57:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLX85-0004mR-Pa
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 21:57:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA04393
	for <asrg@ietf.org>; Tue, 12 Apr 2005 21:56:59 -0400 (EDT)
Received: from mail1.panix.com ([166.84.1.72])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLXHS-0007Ee-3G
	for asrg@ietf.org; Tue, 12 Apr 2005 22:07:03 -0400
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail1.panix.com (Postfix) with ESMTP id C0CF858AC4
	for <asrg@ietf.org>; Tue, 12 Apr 2005 21:56:59 -0400 (EDT)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p3/8.8.8/PanixN1.1) id j3D1ux801747;
	Tue, 12 Apr 2005 21:56:59 -0400 (EDT)
Date: Tue, 12 Apr 2005 21:56:59 -0400 (EDT)
Message-Id: <200504130156.j3D1ux801747@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <20050413012445.GA20465@Space.Net> (message from Markus Stumpf on
	Wed, 13 Apr 2005 03:24:45 +0200)
Subject: Re: [Asrg] article: port 25 blocking
References: <200504130001.UAA27079@ietf.org>
	<200504130058.j3D0wAP28978@panix5.panix.com>
	<20050413012445.GA20465@Space.Net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581

Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net> wrote:
> On Tue, Apr 12, 2005 at 08:58:10PM -0400, Seth Breidbart wrote:
>> Every ISP knows which of its IP addresses hold machines that ought to
>> be allowed to send email directly outside its network.
>
> I doubt that.
> If we give e.g. a /28 to a (business) customer we don't know which
> IP the mailserver will be on (if any). I don't think we are
> different with this regard to the majority of all other ISPs.

If you're an ISP giving a subnet to a business (or a smaller ISP),
then as far as you're concerned they're welcome to put their
mailswerver on any of their IP addresses, so you don't have to block.
It's their problem.

Seth

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


From asrg-bounces@ietf.org  Tue Apr 12 22:03:45 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04733
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 22:03:45 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLXO0-0007Mu-IP
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 22:13:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLXDQ-0005Ri-Sp; Tue, 12 Apr 2005 22:02:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLXDO-0005Rd-P9
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 22:02:50 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04706
	for <asrg@ietf.org>; Tue, 12 Apr 2005 22:02:48 -0400 (EDT)
Message-Id: <200504130202.WAA04706@ietf.org>
Received: from smtp817.mail.sc5.yahoo.com ([66.163.170.3])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLXN4-0007M7-9e
	for asrg@ietf.org; Tue, 12 Apr 2005 22:12:52 -0400
Received: from unknown (HELO gous6120) (gcou@sbcglobal.net@216.226.168.4 with
	login)
	by smtp817.mail.sc5.yahoo.com with SMTP; 13 Apr 2005 02:02:45 -0000
From: "George Ou" <george_ou@netzero.com>
To: "'Markus Stumpf'" <maex-lists-spam-ietf-asrg@Space.Net>
Subject: RE: [Asrg] article: port 25 blocking
Date: Tue, 12 Apr 2005 19:02:44 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
Thread-Index: AcU/xfKHJPoD878LRkyYX3ciUh4GqgABhl0w
In-Reply-To: <20050413010045.GZ20465@Space.Net>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Content-Transfer-Encoding: 7bit

-----Original Message-----
From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of
Markus Stumpf
Sent: Tuesday, April 12, 2005 6:01 PM
To: George Ou
Cc: asrg@ietf.org; 'Markus Stumpf'
Subject: Re: [Asrg] article: port 25 blocking

On Tue, Apr 12, 2005 at 04:41:28PM -0700, George Ou wrote:
>> Most people already manage their own DNS when they sign up with a 
>> hosting service via web interface.  Since they're already managing 
>> their MX records now, no reason they can't manage their own SPF records.

>MX != outgoing SMTP

Where did I claim "=="?  I'm simply stating that if one can manage an MX
record for incoming SMTP, then it is reasonable to ask that they manage SPF
records for outgoing SMTP.

>Again, MX != outgoing SMTP for large parts of the Internet.

Again, that's your words, not mine.

>> Those
>> people are probably using your standard relay servers anyways so it's 
>> fairly easy to use default settings.

>No, a not so small number of them aren't using any of our MTAs at all.

Then they use their own IP addresses.  What's your point?

[snip]

>I can't find SPF records for netzero.com. Your mail routing is a very
>good example. You send via Yahoo and you receive via mx.lax.untd.com
>and mx.nyc.untd.com. Contact Yahoo and try to get a list of IPs and
>add SPF records.

I have no problem changing to the official netzero.com smtp relay server
there.


George


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


From asrg-bounces@ietf.org  Tue Apr 12 22:03:50 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04760
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 22:03:50 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLXO5-0007N3-Aj
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 22:13:54 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLXBK-0005Fx-WC; Tue, 12 Apr 2005 22:00:43 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLXBJ-0005E5-IL
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 22:00:41 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04595
	for <asrg@ietf.org>; Tue, 12 Apr 2005 22:00:39 -0400 (EDT)
Received: from ns1.nixcartel.com ([66.98.212.93] helo=tin.nixcartel.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLXKz-0007Jk-Nt
	for asrg@ietf.org; Tue, 12 Apr 2005 22:10:43 -0400
Received: from dvb.homelinux.org (unknown [210.18.157.242])
	by tin.nixcartel.org (Postfix) with ESMTP id 1CA4C1AC07F
	for <asrg@ietf.org>; Tue, 12 Apr 2005 21:23:32 -0500 (CDT)
Received: by dvb.homelinux.org (Postfix, from userid 500)
	id 5E70F340D0; Wed, 13 Apr 2005 07:29:53 +0530 (IST)
Date: Wed, 13 Apr 2005 07:29:53 +0530
From: Devdas Bhagat <devdas@dvb.homelinux.org>
To: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking
Message-ID: <20050413072953.A11366@evita.devdas.geek>
Mail-Followup-To: asrg@ietf.org
References: <200504130007.UAA27618@ietf.org>
	<200504130113.j3D1Di320540@panix5.panix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
In-Reply-To: <200504130113.j3D1Di320540@panix5.panix.com>;
	from sethb@panix.com on Tue, Apr 12, 2005 at 09:13:44PM -0400
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Devdas Bhagat <devdas@dvb.homelinux.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22

On 12/04/05 21:13 -0400, Seth Breidbart wrote:
> "George Ou" <george_ou@netzero.com> wrote:
> 
> > The standard firewall configuration is to block all traffic unless
> > otherwise specified.
> 
> Which RFC defines that "standard"?
> 
You don't need a RFC for that. That is canonical default policy.

> >  While it's true that most SMTP servers will accept port 587,
> > most firewall policies only permit inbound TCP 25 to an SMTP server.
> 
> "most" out of precisely how many you surveyed?
> 
Are we speaking inbound to MX servers, or about outbound SMTP servers?
Would your outbound SMTP servers not be inside your firewall? Or at
least in the DMZ? And given that adjusting firewall rules for a whole
baggage of other protocols is acceptable (voice and OWA come to mind),
why not use a proper SMTP server as an application layer gateway for
SMTP services?

Devdas Bhagat

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


From asrg-bounces@ietf.org  Tue Apr 12 22:06:41 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04882
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 22:06:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLXQr-0007Rj-9d
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 22:16:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLXFh-0005uu-G1; Tue, 12 Apr 2005 22:05:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLXFe-0005ts-PV
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 22:05:11 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA04826
	for <asrg@ietf.org>; Tue, 12 Apr 2005 22:05:00 -0400 (EDT)
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLXPD-0007Ov-Ef
	for asrg@ietf.org; Tue, 12 Apr 2005 22:15:04 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1DLXCI-00017A-Qz
	for asrg@ietf.org; Wed, 13 Apr 2005 04:01:42 +0200
Received: from 212.82.251.36 ([212.82.251.36])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <asrg@ietf.org>; Wed, 13 Apr 2005 04:01:42 +0200
Received: from nobody by 212.82.251.36 with local (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <asrg@ietf.org>; Wed, 13 Apr 2005 04:01:42 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: asrg@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Wed, 13 Apr 2005 03:59:04 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 57
Message-ID: <425C7CE8.4A56@xyzzy.claranet.de>
References: <p0623051bbe8150a2869e@toaster.scconsult.com>
	<200504122327.TAA24040@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 212.82.251.36
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: article: port 25 blocking
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit

George Ou wrote:

> If we could get the top 50 domains to start "punishing"
> non-SPF compliant with delays and a gradual migration to
> a hard fail in unison, would that not prompt other domains
> to become SPF compliant?

Something with your definition of "non-SPF compliant" is wrong.

"v=spf1 -ip4:127.0.0.1 +all" is perfectly compliant, it could
even make sense.  And if not it's easy to find cases where +all
is _very_ useful, see the recent include:not.me discussion on
the spf-discuss mailing list.

"v=spf1 a ~all" is also perfectly compliant, the latest draft
proposes to process a SOFTFAIL in a greylisting-style.

Something like "v=spf1" (implicitly the same as "v=spf1 ?all")
or many other policies ending with "?all" might be useless, but
they are still "compliant".  And there are cases where a "?"
NEUTRAL result is exactly what the sender wanted, e.g.

"v=spf1 mx ?a:sometimes.i.use.a.spamcast.mta.example -all"

But maybe you define "compliant" as "no sender policy is bad".
That's not true, because it's relatively easy for spammers to
get an SPF PASS if they want it:

"v=spf1 +exists:%{ir}.comcast.blackholes.us -all"

This policy radically PASSes for all spamcast zombies, and it
is again relatively simple to get a similar effect with a less
obvious policy.

In other words PASS is meaningless unless it's from somebody
you already know (e.g. paypal).  SOFTFAIL could be useful.  But
the full power of SPF is FAIL, because receivers can reject it.

That forces spammers to forge another domain.  No more bogus
bounces / challenges / vacation / what else mails to the owners
of SPF-FAIL protected domains.

Effect on spam:  zero, they just forge another domain.  Effect
on SMTP:  nice, SMTP only works if the whole world does _not_
stop to send bounces etc. or delete them automatically on sight.

If you really think that SPF is a FUSSP (IMNSHO it is not) you
have to add meaning to a PASS (PASS from ebay vs. PASS from an
unknown stranger), and for that you need white lists of known
senders, and the only obvious way to create them on the fly is
some kind of C/R system <shudder />

Otherwise SPF is unrelated to anti-spam, like "port 25 blocks"
are unrelated to anti-zombie, and Sender-ID is unrelated to
anti-phishing.
                              Bye, Frank



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


From asrg-bounces@ietf.org  Tue Apr 12 22:14:16 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05654
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 22:14:16 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLXYB-0007e5-JV
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 22:24:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLXMd-0007mp-0i; Tue, 12 Apr 2005 22:12:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLXMb-0007mD-FE
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 22:12:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA05541
	for <asrg@ietf.org>; Tue, 12 Apr 2005 22:12:10 -0400 (EDT)
Received: from moebius2.space.net ([195.30.1.100])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DLXW9-0007c8-I8
	for asrg@ietf.org; Tue, 12 Apr 2005 22:22:15 -0400
Received: (qmail 97714 invoked by uid 1013); 13 Apr 2005 02:12:10 -0000
Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=testkey; d=space.net;
	b=QWvC105FqTIG35FCzoHFBpaNEV5n4jyaf7VntlvnyYEzHILjAbsP/nuKdLxGRhkd  ;
Date: Wed, 13 Apr 2005 04:12:10 +0200
From: Markus Stumpf <maex-lists-spam-ietf-asrg@Space.Net>
To: George Ou <george_ou@netzero.com>
Subject: Re: [Asrg] article: port 25 blocking
Message-ID: <20050413021210.GB20465@Space.Net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
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
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: asrg@ietf.org, "'Markus Stumpf'" <maex-lists-spam-ietf-asrg@Space.Net>
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb

On Tue, Apr 12, 2005 at 07:02:44PM -0700, George Ou wrote:
> >Again, MX != outgoing SMTP for large parts of the Internet.
> Again, that's your words, not mine.

And intentionally. However you decided to "snip" the reason why this makes a big
difference.

> >No, a not so small number of them aren't using any of our MTAs at all.
> Then they use their own IP addresses.  What's your point?

No they are not.
They use the mailserver of their dialin/broadband providers or the mailservers
of their friends or the mailserver of whoever allows them to relay ...

> >I can't find SPF records for netzero.com. Your mail routing is a very
> >good example. You send via Yahoo and you receive via mx.lax.untd.com
> >and mx.nyc.untd.com. Contact Yahoo and try to get a list of IPs and
> >add SPF records.
> 
> I have no problem changing to the official netzero.com smtp relay server
> there.

According to the non existant netzero.com SPF records there is no official
netzero.com smtp outgoing server.

But this is not the challenge.
The challenge is: contact Yahoo and try to get a list of IPs of their outgoing
SMTP servers to construct a SPF record.

	\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 asrg-bounces@ietf.org  Tue Apr 12 22:41:57 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06974
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 22:41:57 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLXyz-0008EJ-Ox
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 22:52:02 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLXjB-00048M-8U; Tue, 12 Apr 2005 22:35:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLXj9-00046M-Fj
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 22:35:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06630
	for <asrg@ietf.org>; Tue, 12 Apr 2005 22:35:36 -0400 (EDT)
Received: from toaster.scconsult.com ([66.73.230.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLXsq-00086L-PV
	for asrg@ietf.org; Tue, 12 Apr 2005 22:45:41 -0400
Received: from toaster.scconsult.com (localhost [127.0.0.1])
	by toaster.scconsult.com (Postfix) with ESMTP id 35F7E537FEB
	for <asrg@ietf.org>; Tue, 12 Apr 2005 22:35:22 -0400 (EDT)
Mime-Version: 1.0
Message-Id: <p06230523be82228ab947@toaster.scconsult.com>
Date: Tue, 12 Apr 2005 22:35:19 -0400
To: <asrg@ietf.org>
From: Bill Cole <asrg2@billmail.scconsult.com>
Subject: RE: [Asrg] article: port 25 blocking
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4

At 5:01 PM -0700 4/12/05, George Ou wrote pointlessly to both me and 
the list with broken quoting
>-----Original Message-----
>From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of Bill
>Cole
>Sent: Tuesday, April 12, 2005 3:26 PM
>To: asrg@ietf.org
>Subject: RE: [Asrg] article: port 25 blocking
>
>
>>Have you looked at how port 25 blocking is actually being done by even the
>>minimally competent ISP's? SBC is an example of one such. 8 months ago they
>>had a press release and sent mail to all customers about the coming rollout
>>of port 25 blocking. With that they included a way to preemptively request
>>exemption and they made clear that customers with static address accounts
>>would be excluded by default.
>>To my profound shock, SBC has actually managed to execute that rollout with
>>reasonable speed and accuracy. There may well be some ISP's who are
>>implementing port 25 blocking without exempting users with static IP
>>assignments, but I believe they would be the minority.
>>SBC's willingness to provide exceptions for anyone who asks may be unusual,
>>but it is not unique.
>
>
>You're always free to implement port 25 blocking on your side for inbound
>traffic which effectively achieves the same thing for your network.

No, I cannot, because I cannot tell which addresses on some other 
network are dynamically assigned and which are statically assigned 
and which are dynamically assigned to people who have received 
permission from the owners of the address space (i.e. their ISP) to 
use any dynamic address assigned to them for an unknown period for 
SMTP. It is not possible for me to set that up. The owner of the 
address space can.

>You
>just need to implement a large ACL yourself that might be synchronized with
>a large shared database somewhere on the net.  Why do you want everyone else
>to implement outbound port 25 blocks for you?

I don't. I want ISP's to act responsibly. I expect any network owner 
to assure that no abusive traffic comes out of their network. Failing 
to do that is not acceptable, no matter what the business model of 
the network owner says.

If an ISP would rather sell second-class service to customers who 
can't be bothered with securing their own machines than assure that 
they only allow responsible customers to remain customers for any 
length of time, that is their choice. Most consumer-focused ISP's 
have chosen irrevocably to sell to careless customers, so they have 
to find ways to either cut off the bozos fast or to wall them in so 
that they are less of a nuisance. I'd much prefer the swift and sure 
cutoff, but few ISP's like that option.

>Bottom line is, you'll have the same problem convincing people to block
>outbound 25 as you will convincing them to implement SPF.

ISP's have been implementing port 25 blocking in gradual and 
constantly growing numbers for 6 years. SPF implementation in any way 
that can reduce acceptance of primary spam is at a dead halt, if not 
retreating, because it does harm to early adopters on both ends.I 
wish that were not so, but I have been massively outvoted by people 
who like traditional forwarding and do not see it as a harmful relic 
of a lost time.

On the other side, port 25 blocking is a net benefit to the 
implementing ISP immediately, which is why it has been spreading 
steadily since the days of throwaway dialup accounts as the preferred 
spam route. It is implemented unilaterally by the party that benefits 
from it, in contrast to SPF which cannot be correctly implemented in 
any way that actually cuts into spam without bilateral participation 
of domain owners and receiving sites to publish '-all' records and to 
actually enforce them. Until such time as both are widely done, 
traditional forwarding and other practices that break SPF will remain 
common and anyone trying to enforce hard-line SPF on either end will 
get breakage.

>SPF just happens
>to be a better solution in my opinion.

SPF addresses a very different problem set from port 25 blocking. It 
is a mystery to me why you persist in presenting SPF as an 
alternative to port 25 blocking. The only alternative to port 25 
blocking (or equivalently tight restrictions on user behavior) is 
serious policing of customer security such that compromised machines 
are not provided access to the network. That would be an expensive 
means for ISP's to assure that their networks do not emit spam and 
also don't have a bunch of zombies on them. Port 25 blocking only 
stops the spam and limits one sort of value the zombies have to their 
controllers.


-- 
Bill Cole
bill@scconsult.com


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


From asrg-bounces@ietf.org  Tue Apr 12 22:42:42 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07036
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 22:42:42 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLXzi-0008F2-QQ
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 22:52:47 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLXie-00042q-Ms; Tue, 12 Apr 2005 22:35:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLXic-000416-Ul
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 22:35:07 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06619
	for <asrg@ietf.org>; Tue, 12 Apr 2005 22:34:48 -0400 (EDT)
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLXs4-00084l-B4
	for asrg@ietf.org; Tue, 12 Apr 2005 22:44:52 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1DLXep-0003GQ-Vo
	for asrg@ietf.org; Wed, 13 Apr 2005 04:31:11 +0200
Received: from 212.82.251.36 ([212.82.251.36])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <asrg@ietf.org>; Wed, 13 Apr 2005 04:31:11 +0200
Received: from nobody by 212.82.251.36 with local (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <asrg@ietf.org>; Wed, 13 Apr 2005 04:31:11 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: asrg@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Wed, 13 Apr 2005 04:32:31 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 34
Message-ID: <425C84BF.76A8@xyzzy.claranet.de>
References: <20050412231722.GU20465@Space.Net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 212.82.251.36
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: article: port 25 blocking
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit

Markus Stumpf wrote:

> SPF does all this NOT and it breaks widely deployed Internet
> Mail Infrastructure.

That's not true (a.k.a. a lie) following the spec.  Receivers
just have to check it at the one hop from the last MTA of the
sender to the first MTA (MX) of the receiver, then it "breaks"
nothing, let alone the "Internet Mail Infrastructure".

Even if a receiver screws up badly and checks it later nothing
evil happens, the MTA in question rejects the mail, and the MTA
before it creates a bounce - that strikes me as a very complex
approximation of "551 user not local", but it's SMTP as defined
in STD 10 and later.

Second attempt to break anything, somebody wants a "bounces-to"
as in mail-arch, i.e. use a given MAIL FROM anywhere.  That's
very simple, he just does not publish a sender policy, ready.

> Without > 80% of all domains deploying SPF (and SRS) I will
> never block based on SPF

That's your decision, SPF is a voluntary system, and the most
important volunteers are the spammers, not you.

> this would be a MTAMARK like list

MTAMARK and SPF are unrelated.  The only thing they might share
is the fact, that IPs marked as MTAs can be IPs of spammers,
like MAIL FROMs or HELOs resulting in a SPF PASS can be set up
by spammers.
                         Bye, Frank



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


From asrg-bounces@ietf.org  Tue Apr 12 23:31:15 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA12025
	for <asrg-web-archive@ietf.org>; Tue, 12 Apr 2005 23:31:15 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLYkh-000148-IK
	for asrg-web-archive@ietf.org; Tue, 12 Apr 2005 23:41:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLYZF-0006yt-0u; Tue, 12 Apr 2005 23:29:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLYZC-0006xw-Uh
	for asrg@megatron.ietf.org; Tue, 12 Apr 2005 23:29:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA11925
	for <asrg@ietf.org>; Tue, 12 Apr 2005 23:29:18 -0400 (EDT)
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLYip-00010l-94
	for asrg@ietf.org; Tue, 12 Apr 2005 23:39:23 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1DLYVS-0007LV-Do
	for asrg@ietf.org; Wed, 13 Apr 2005 05:25:34 +0200
Received: from 212.82.251.36 ([212.82.251.36])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <asrg@ietf.org>; Wed, 13 Apr 2005 05:25:34 +0200
Received: from nobody by 212.82.251.36 with local (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <asrg@ietf.org>; Wed, 13 Apr 2005 05:25:34 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: asrg@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Wed, 13 Apr 2005 05:19:31 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 55
Message-ID: <425C8FC3.7F1F@xyzzy.claranet.de>
References: <20050412231722.GU20465@Space.Net> <200504122341.TAA24773@ietf.org>
	<20050413010045.GZ20465@Space.Net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: 212.82.251.36
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: article: port 25 blocking
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 3.0 (+++)
X-Scan-Signature: 02ec665d00de228c50c93ed6b5e4fc1a
Content-Transfer-Encoding: 7bit

Markus Stumpf wrote:

> MX != outgoing SMTP

Actually it's "MX is not necessarily an / the outgoing SMTP".

It would be nice to have "MX == RMX", for starters it would
make SPF (the baroque form of RMX) unnecessary.  Ignoring the
"use A if no MX" loophole in this fantasy.

Maybe it was once meant this way, "Mail eXchanger" sounds like
"those who can receive can also send, and vice versa".

> the IP address you use for a smart/relay may be totally
> different from that the outgoing IP of that server is.

mail2.hamburg.de != frontend-1.hamburg.de, guessing the RMX is
certainly not always trivial.  And the SPF wizard is a script,
like all scripts it's rather stupid.

> changing the IP address of an outgoing MTA of an ISP requires
> ALL zones that list (or don't yet) that IP address in the SPF
> records to be changed.

Depends.  First of all you can use a:frontend-1.hamburg.de and
then the IP can be changed without changing the sender policy.

And if you're a customer of an "SPF-aware" mail provider you'd
simply include:my.1st.mail.provider.example etc., it's then
their business to keep their SPF record up to date.

"All" foobar.claranet.de use a "v=spf1 redirect=claranet.de",
if something has to be changed it's only the latter.  That's
not precisely an optimal example, because that "all" is only
one wildcard for all vanity domains like foobar or xyzzy, but
let's say that the SPF "zone cut" idea changed twice (it will
be removed in the next draft, and it was never implemented).

> note that adding one for the domain is NOT enough, you have
> to add SPF records for all RRs in that domain

 From his POV only those FQDNs below netzero.com are relevant
that have an MX (or an A with a smtpd), e.g. mail.netzero.com
or pop.netzero.com

 From the POV of a receiver adding CSV and its "quasi-zone-cut"
could help as far as forged netzero-HELOs not covered by SPF
are concerned.  Claims that _one_ scheme, SPF / CSV / MTAMARK /
port-25-blocks / 2476-enforced-submission-rights / ... solves
_all_ spam related problems are just wrong.

                            Bye, Frank
-- 
http://www.cbronline.com/article_news.asp?guid=44D2955C-3C04-4BA1-AC45-AF8277B8B455



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


From asrg-bounces@ietf.org  Wed Apr 13 08:21:41 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA20718
	for <asrg-web-archive@ietf.org>; Wed, 13 Apr 2005 08:21:41 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLh24-0005YH-Mc
	for asrg-web-archive@ietf.org; Wed, 13 Apr 2005 08:31:49 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLgde-0003Ud-I2; Wed, 13 Apr 2005 08:06:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLgdc-0003Sw-6J
	for asrg@megatron.ietf.org; Wed, 13 Apr 2005 08:06:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19264
	for <asrg@ietf.org>; Wed, 13 Apr 2005 08:06:22 -0400 (EDT)
Received: from mail1.nber.org ([66.251.72.7])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLgnD-00054b-7H
	for asrg@ietf.org; Wed, 13 Apr 2005 08:16:30 -0400
Received: from mail1 (root@localhost)
	by mail1.nber.org (8.12.8/8.12.8) with SMTP id j3DC6BdR019149
	for <asrg@ietf.org>; Wed, 13 Apr 2005 08:06:11 -0400
Received: from nber5.nber.org (nber5.nber.org [66.251.72.75])
	by mail1.nber.org (8.12.8/8.12.8) with ESMTP id j3DC68vL019112;
	Wed, 13 Apr 2005 08:06:08 -0400
Date: Wed, 13 Apr 2005 08:06:08 -0400 (EDT)
From: Daniel Feenberg <feenberg@nber.org>
To: George Ou <george_ou@netzero.com>
Subject: RE: [Asrg] article: port 25 blocking
In-Reply-To: <200504130001.UAA27079@ietf.org>
Message-ID: <Pine.GSO.4.10.10504130758150.4932-100000@nber5.nber.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8



On Tue, 12 Apr 2005, George Ou wrote:

> -----Original Message-----
> From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of Bill
> Cole
> Sent: Tuesday, April 12, 2005 3:26 PM
> To: asrg@ietf.org
> Subject: RE: [Asrg] article: port 25 blocking
> 
> 
> 
> You're always free to implement port 25 blocking on your side for inbound
> traffic which effectively achieves the same thing for your network.  You
> just need to implement a large ACL yourself that might be synchronized with
> a large shared database somewhere on the net.  Why do you want everyone else
> to implement outbound port 25 blocks for you?
> 


The advantage that the source ISP has is that they have actual knowledge
of which IP addresses are dynamic and which are not. The receiving MTA can
use DNSBLs and the RDNS to guess, but it seems that a fair number of ISPs
give dynamic looking addresses to customers with legitimate mail servers.  
Not a good idea, but the customer will likely not know why there mail is
often rejected. Of course, the ISP could inform the DNSBLs of which
addresses were dynamic, which would allow the DNSBL to be just as accurate
as the outbound port 25 block.

One advantage of using DNSBLs rather than blocking port 25 is that it
enhances the value of DNSBLs. If more MTAs use a good DNSBL that helps
control spam from static addresses. Otherwise, I hardly think it makes a
difference if the packets are stopped at the outbound router or the
receiving MTA. It is just a couple of packets - not the entire spam
message.

The worst spam crime has to be mixing spam with legitimate mail from the
same address. If an address sends only spam, it is easy enough to ignore.


> 
> George
> 
> 
> _______________________________________________
> 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 asrg-bounces@ietf.org  Wed Apr 13 16:31:02 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04327
	for <asrg-web-archive@ietf.org>; Wed, 13 Apr 2005 16:31:02 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLofi-0003QY-NF
	for asrg-web-archive@ietf.org; Wed, 13 Apr 2005 16:41:14 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLoIo-0001tB-45; Wed, 13 Apr 2005 16:17:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLoIl-0001sG-Tg
	for asrg@megatron.ietf.org; Wed, 13 Apr 2005 16:17:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01394
	for <asrg@ietf.org>; Wed, 13 Apr 2005 16:17:24 -0400 (EDT)
Received: from pcls3.std.com ([192.74.137.143] helo=TheWorld.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLoSW-0002P0-KP
	for asrg@ietf.org; Wed, 13 Apr 2005 16:27:37 -0400
Received: from world.std.com (tlw@world.std.com [192.74.137.5])
	by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id j3DKHNGb010203;
	Wed, 13 Apr 2005 16:17:23 -0400
Received: (from bzs@localhost)
	by world.std.com (8.12.8p1/8.12.8) id j3DKGTiB004889;
	Wed, 13 Apr 2005 16:16:29 -0400 (EDT)
From: Barry Shein <bzs@world.std.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16989.32285.639328.868828@world.std.com>
Date: Wed, 13 Apr 2005 16:16:29 -0400
To: Seth Breidbart <sethb@panix.com>
Subject: Re: [Asrg] article: port 25 blocking
In-Reply-To: <200504130058.j3D0wAP28978@panix5.panix.com>
References: <200504130001.UAA27079@ietf.org>
	<200504130058.j3D0wAP28978@panix5.panix.com>
X-Mailer: VM 7.07 under Emacs 21.2.2
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Content-Transfer-Encoding: 7bit


OTOH, rate-limiting port 25 probably would be a reasonable compromise
if the rates were set reasonably.

Unfortunately, easier said than done.

-- 
        -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 asrg-bounces@ietf.org  Wed Apr 13 16:35:20 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA05130
	for <asrg-web-archive@ietf.org>; Wed, 13 Apr 2005 16:35:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DLojs-0003gT-65
	for asrg-web-archive@ietf.org; Wed, 13 Apr 2005 16:45:33 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DLoHp-0001lI-M6; Wed, 13 Apr 2005 16:16:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DLoHn-0001l9-UA
	for asrg@megatron.ietf.org; Wed, 13 Apr 2005 16:16:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01282
	for <asrg@ietf.org>; Wed, 13 Apr 2005 16:16:22 -0400 (EDT)
Received: from pcls3.std.com ([192.74.137.143] helo=TheWorld.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DLoRV-0002LO-MD
	for asrg@ietf.org; Wed, 13 Apr 2005 16:26:35 -0400
Received: from world.std.com (world.std.com [192.74.137.5])
	by TheWorld.com (8.12.8p1/8.12.8) with ESMTP id j3DKFNGb007500;
	Wed, 13 Apr 2005 16:15:39 -0400
Received: (from bzs@localhost)
	by world.std.com (8.12.8p1/8.12.8) id j3DKDafW014226;
	Wed, 13 Apr 2005 16:13:36 -0400 (EDT)
From: Barry Shein <bzs@world.std.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16989.32112.649125.770068@world.std.com>
Date: Wed, 13 Apr 2005 16:13:36 -0400
To: "George Ou" <george_ou@netzero.com>
Subject: RE: [Asrg] article: port 25 blocking
In-Reply-To: <200504122327.TAA24040@ietf.org>
References: <p0623051bbe8150a2869e@toaster.scconsult.com>
	<200504122327.TAA24040@ietf.org>
X-Mailer: VM 7.07 under Emacs 21.2.2
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 7bit


On April 12, 2005 at 16:27 george_ou@netzero.com (George Ou) wrote:
 > 
 > If we could get the top 50 domains to start "punishing" non-SPF compliant
 > with delays and a gradual migration to a hard fail in unison, would that not
 > prompt other domains to become SPF compliant?
 > 

I'd imagine if the top 50 domains refused e-mail unless one was
wearing a funny hat you'd see a lot more people wearing funny hats.

But what effect that would have on spam per se, like SPF, is highly
questionable.



-- 
        -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 asrg-bounces@ietf.org  Thu Apr 14 13:06:21 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02932
	for <asrg-web-archive@ietf.org>; Thu, 14 Apr 2005 13:06:21 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DM7xO-0000Dv-5e
	for asrg-web-archive@ietf.org; Thu, 14 Apr 2005 13:16:46 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DM7Up-0001xF-FL; Thu, 14 Apr 2005 12:47:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DM7Uo-0001wv-Oy
	for asrg@megatron.ietf.org; Thu, 14 Apr 2005 12:47:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01123
	for <asrg@ietf.org>; Thu, 14 Apr 2005 12:47:11 -0400 (EDT)
From: gep2@terabites.com
Message-Id: <200504141647.MAA01123@ietf.org>
Received: from sccrmhc14.comcast.net ([204.127.202.59])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM7eo-0007k3-Gl
	for asrg@ietf.org; Thu, 14 Apr 2005 12:57:36 -0400
Date: Thu, 14 Apr 2005 16:47:03 +0000 (GMT)
X-Comment: Sending client does not conform to RFC822 minimum requirements
X-Comment: Date has been added by Maillennium
Received: from WinProxy.anywhere
	(c-24-0-189-130.hsd1.tx.comcast.net[24.0.189.130])
	by comcast.net (sccrmhc14) with SMTP
	id <2005041416470301400geco9e>; Thu, 14 Apr 2005 16:47:03 +0000
Received: from 192.168.0.104 by 192.168.0.100 (WinProxy);
	Thu, 14 Apr 2005 11:46:55 -0600
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
To: asrg@ietf.org
X-Mailer: SPRY Mail Version: 04.00.06.17
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Subject: [Asrg] RE: article: port 25 blocking (Barry Shein)
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 1.1 (+)
X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69
Content-Transfer-Encoding: 7bit

>> If we could get the top 50 domains to start "punishing" non-SPF compliant
 > with delays and a gradual migration to a hard fail in unison, would that not
 > prompt other domains to become SPF compliant?
 

> I'd imagine if the top 50 domains refused e-mail unless one was
wearing a funny hat you'd see a lot more people wearing funny hats.

> But what effect that would have on spam per se, like SPF, is highly
questionable.

Right!!

SPF is one of the stupidest pieces of garbage I've seen get as far as it has... 
evidence of to what absurd lengths people will go to APPEAR to be 'doing 
something', even if it in fact doesn't solve the problem!  (In fact, it does 
VERY little to prevent spamming, and doesn't even really do anything much to 
ensure that E-mail isn't forged.)

Maybe what OUGHT to happen is that systems worldwide ought to stop supporting, 
or maybe "punish", SPF-oriented servers...!  

Let's simply STOP the stupid, blind, ill-conceived rush into half-assed 
"solutions" that AREN'T!!!

[snip]

> OTOH, rate-limiting port 25 probably would be a reasonable compromise
if the rates were set reasonably.

Blocking (or throttling) port 25 only guarantees that SMTP servers will start 
accepting mail on other, non-blocked, non-compromised ports. 

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 asrg-bounces@ietf.org  Thu Apr 14 13:38:04 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05051
	for <asrg-web-archive@ietf.org>; Thu, 14 Apr 2005 13:38:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DM8S3-0001Oe-Nn
	for asrg-web-archive@ietf.org; Thu, 14 Apr 2005 13:48:27 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DM8BW-00059K-6U; Thu, 14 Apr 2005 13:31:22 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DM8BT-00058H-FP
	for asrg@megatron.ietf.org; Thu, 14 Apr 2005 13:31:19 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA04508
	for <asrg@ietf.org>; Thu, 14 Apr 2005 13:31:00 -0400 (EDT)
Received: from mail2.panix.com ([166.84.1.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM8LE-00019X-Kh
	for asrg@ietf.org; Thu, 14 Apr 2005 13:41:25 -0400
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail2.panix.com (Postfix) with ESMTP id 1307DA6FEA
	for <asrg@ietf.org>; Thu, 14 Apr 2005 13:30:57 -0400 (EDT)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p3/8.8.8/PanixN1.1) id j3EHUvL09506;
	Thu, 14 Apr 2005 13:30:57 -0400 (EDT)
Date: Thu, 14 Apr 2005 13:30:57 -0400 (EDT)
Message-Id: <200504141730.j3EHUvL09506@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <200504141647.MAA01123@ietf.org> (gep2@terabites.com)
Subject: Re: [Asrg] RE: article: port 25 blocking (Barry Shein)
References: <200504141647.MAA01123@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8

gep2@terabites.com wrote:

> Blocking (or throttling) port 25 only guarantees that SMTP servers
> will start accepting mail on other, non-blocked, non-compromised
> ports.

Please explain why I would want my mail swerver to accept mail on
other ports, given that it's almost certainly spam (because it's only
sent on those ports because the sending machine has port 25 blocked
because its ISP doesn't think it should be sending email directly).

If you want to go out of your way to accept spam, be my guest.  I
don't think most of the rest of us will.

Seth

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


From asrg-bounces@ietf.org  Thu Apr 14 14:17:27 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08545
	for <asrg-web-archive@ietf.org>; Thu, 14 Apr 2005 14:17:27 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DM949-00034k-8W
	for asrg-web-archive@ietf.org; Thu, 14 Apr 2005 14:27:51 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DM8nv-0005m6-Kx; Thu, 14 Apr 2005 14:11:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DM8nt-0005ll-Nv
	for asrg@megatron.ietf.org; Thu, 14 Apr 2005 14:11:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07890
	for <asrg@ietf.org>; Thu, 14 Apr 2005 14:10:52 -0400 (EDT)
Received: from sparkle.rodents.montreal.qc.ca ([216.46.5.7]
	ident=Dq4ytdnCbISb0HZ1ZSPNvkCyW9xsHzqNLRpSIDnedGi)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DM8xl-0002lL-Lb
	for asrg@ietf.org; Thu, 14 Apr 2005 14:21:16 -0400
Received: (from mouse@localhost)
	by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id OAA10696;
	Thu, 14 Apr 2005 14:10:40 -0400 (EDT)
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Message-Id: <200504141810.OAA10696@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.
X-Message-Flag: Microsoft: the company who gave us the zombie armies.
Date: Thu, 14 Apr 2005 14:07:07 -0400 (EDT)
To: asrg@ietf.org
Subject: Re: [Asrg] RE: article: port 25 blocking (Barry Shein)
In-Reply-To: <200504141730.j3EHUvL09506@panix5.panix.com>
References: <200504141647.MAA01123@ietf.org>
	<200504141730.j3EHUvL09506@panix5.panix.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 8bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Content-Transfer-Encoding: 8bit

>> Blocking (or throttling) port 25 only guarantees that SMTP servers
>> will start accepting mail on other, non-blocked, non-compromised
>> ports.
> Please explain why I would want my mail swerver to accept mail on
> other ports, given that it's almost certainly spam

If you have so few roaming users wanting to send mail through you via
SMTP that mail to that port is "almost certainly spam", then you
probably don't want to do that.

But places with a lot of roaming users, especially the sort of
semi-geek often called a "power user", quite probably do, because the
resulting mail *isn't* "almost certainly spam".

Presumably such things will be using SMTP AUTH or better to secure the
connections; if they don't, yes, they will promptly become spam
conduits and get shunned in consequence.

/~\ 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 asrg-bounces@ietf.org  Thu Apr 14 21:07:28 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17888
	for <asrg-web-archive@ietf.org>; Thu, 14 Apr 2005 21:07:28 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMFT1-0004bu-If
	for asrg-web-archive@ietf.org; Thu, 14 Apr 2005 21:17:56 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMFCS-0004uZ-F1; Thu, 14 Apr 2005 21:00:48 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMFCP-0004su-SZ
	for asrg@megatron.ietf.org; Thu, 14 Apr 2005 21:00:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA17310
	for <asrg@ietf.org>; Thu, 14 Apr 2005 21:00:20 -0400 (EDT)
Received: from orb.pobox.com ([207.8.226.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMFM7-0004LY-1Y
	for asrg@ietf.org; Thu, 14 Apr 2005 21:10:48 -0400
Received: from orb (localhost [127.0.0.1])
	by orb.pobox.com (Postfix) with ESMTP id 244D2733
	for <asrg@ietf.org>; Thu, 14 Apr 2005 21:00:14 -0400 (EDT)
Received: from [192.168.0.103] (cpe-66-68-124-39.austin.res.rr.com
	[66.68.124.39])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by orb.sasl.smtp.pobox.com (Postfix) with ESMTP id F006687
	for <asrg@ietf.org>; Thu, 14 Apr 2005 21:00:13 -0400 (EDT)
Message-ID: <425F121A.9040005@pobox.com>
Date: Thu, 14 Apr 2005 20:00:10 -0500
From: mathew <meta@pobox.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking
References: <6f3pjfer25drbae.120420050621@shayndel>
	<Pine.LNX.4.60.0504120706550.15068@cwhois1.completewhois.com>
In-Reply-To: <Pine.LNX.4.60.0504120706550.15068@cwhois1.completewhois.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Content-Transfer-Encoding: 7bit

William Leibzon wrote:

> 2. A non-standard port that is 100% open just like regular SMTP is bound
>    to soon be known and start to be abused. It has to be some type of
>    restricted profile smtp with authentication (which is what submit is,
>    so why reinvent it...).


Right--there's no point in blocking port 25 if you just open up another 
port to plain unauthenticated SMTP. All you're doing then is 
inconveniencing many people by changing the standard port number for 
SMTP; you're not actually improving security at all. Botnets will just 
start probing all the common SMTP ports rather than the standard one.

On the other hand, if you implement SMTP authentication, there's no need 
to block port 25, and you make the bot-programmer's work harder, or even 
impossible if the user's mail client uses a properly-implemented 
lockable keychain.

So instead of wasting time playing move-the-port and annoying people, 
just implement SMTP authentication. I mean, even my Palm handheld and my 
mobile phone know about SMTP AUTH these days.


mathew

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


From asrg-bounces@ietf.org  Thu Apr 14 21:46:03 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20042
	for <asrg-web-archive@ietf.org>; Thu, 14 Apr 2005 21:46:03 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMG4O-0005xG-6q
	for asrg-web-archive@ietf.org; Thu, 14 Apr 2005 21:56:32 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMFoR-00084Y-F2; Thu, 14 Apr 2005 21:40:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMFoP-00083i-1D
	for asrg@megatron.ietf.org; Thu, 14 Apr 2005 21:40:01 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19668
	for <asrg@ietf.org>; Thu, 14 Apr 2005 21:39:50 -0400 (EDT)
Received: from sparkle.rodents.montreal.qc.ca ([216.46.5.7]
	ident=YHdPH2bxXvCEkRd6GMhLVCglOEHDbapdakNcCXaM5Ag)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMFyM-0005kT-7e
	for asrg@ietf.org; Thu, 14 Apr 2005 21:50:19 -0400
Received: (from mouse@localhost)
	by Sparkle.Rodents.Montreal.QC.CA (8.8.8/8.8.8) id VAA22818;
	Thu, 14 Apr 2005 21:39:49 -0400 (EDT)
From: der Mouse <mouse@Rodents.Montreal.QC.CA>
Message-Id: <200504150139.VAA22818@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.
X-Message-Flag: Microsoft: the company who gave us the zombie armies.
Date: Thu, 14 Apr 2005 21:36:56 -0400 (EDT)
To: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking
In-Reply-To: <425F121A.9040005@pobox.com>
References: <6f3pjfer25drbae.120420050621@shayndel>
	<Pine.LNX.4.60.0504120706550.15068@cwhois1.completewhois.com>
	<425F121A.9040005@pobox.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 79899194edc4f33a41f49410777972f8
Content-Transfer-Encoding: 8bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 8bit

>> [...]
> Right--there's no point in blocking port 25 if you just open up
> another port to plain unauthenticated SMTP.

Agreed.

> On the other hand, if you implement SMTP authentication, there's no
> need to block port 25, and [...]

Except for the important point that the entity (putatively)
implementing SMTP AUTH or using another port usually is not the same
entity as the one (putatively) blocking port 25.  In the classic
road-warrior scenario, the entity blocking port 25 is the dialup ISP
used when on the road and the entity whose SMTP server is being futzed
with is the organization who's "home" to the road-warrior.

/~\ 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 asrg-bounces@ietf.org  Thu Apr 14 21:54:01 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20651
	for <asrg-web-archive@ietf.org>; Thu, 14 Apr 2005 21:54:01 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMGC6-0006Gf-2Q
	for asrg-web-archive@ietf.org; Thu, 14 Apr 2005 22:04:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMFyo-0003Xf-4n; Thu, 14 Apr 2005 21:50:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMFyl-0003W9-Py
	for asrg@megatron.ietf.org; Thu, 14 Apr 2005 21:50:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20453
	for <asrg@ietf.org>; Thu, 14 Apr 2005 21:50:41 -0400 (EDT)
Received: from dsl081-214-187.nyc2.dsl.speakeasy.net ([64.81.214.187]
	helo=3comemail.larryseltzer.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMG8r-00068r-9y
	for asrg@ietf.org; Thu, 14 Apr 2005 22:01:10 -0400
From: "Larry Seltzer" <larry@larryseltzer.com>
To: <asrg@ietf.org>
Subject: RE: [Asrg] article: port 25 blocking
Date: Thu, 14 Apr 2005 21:52:28 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
In-Reply-To: <425F121A.9040005@pobox.com>
Thread-Index: AcVBWMSGNF3La7szSTubV7M9zBaQiwAA3k7A
Message-ID: <6sk63rogcv4arks.140420052152@shayndel>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Content-Transfer-Encoding: 7bit

>>> 2. A non-standard port that is 100% open just like regular SMTP is bound
>>>    to soon be known and start to be abused. It has to be some type of
>>>    restricted profile smtp with authentication (which is what submit is,
>>>    so why reinvent it...).

>>Right--there's no point in blocking port 25 if you just open up another
port to plain unauthenticated SMTP....

Don't get me wrong, this was just a crazy off-the-top-of-my-head idea and I
can certainly believe I'm wrong, but this reasoning doesn't persuade me.
There's no reason to believe that there would be a few common ports. 

Let's say I want to let my team of users access the mail server from their
ISP accounts. I set up SMTP on (pull number out of ass) TCP 48207. I have to
set this up on all their clients (and open it up on any firewalls between
us), so for practical purposes it can't be too many of them. 

Assuming the ISP hasn't blocked that port as well (ISP's don't generally
block arbitrary ports) it should solve the problem of getting through the
port 25 block. *Conventional* worms on the system will still fail because
they will be trying to use port 25. A new worm could be written to monitor
all communications looking for SMTP on non-standard ports, but this is a lot
of work when there is still low-hanging fruit out there.

So how is this not going to solve anything? I agree I'd much rather have
users run port 587 and authenticate, but if it's just your sense of
networking asthetics that's offended by this scheme then that's worth
saying.

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



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


From asrg-bounces@ietf.org  Thu Apr 14 22:40:39 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23334
	for <asrg-web-archive@ietf.org>; Thu, 14 Apr 2005 22:40:39 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMGvF-0007oi-2L
	for asrg-web-archive@ietf.org; Thu, 14 Apr 2005 22:51:09 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMGiu-0006Vs-Hl; Thu, 14 Apr 2005 22:38:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMGit-0006Vn-Mb
	for asrg@megatron.ietf.org; Thu, 14 Apr 2005 22:38:23 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23171
	for <asrg@ietf.org>; Thu, 14 Apr 2005 22:38:21 -0400 (EDT)
Message-Id: <200504150238.WAA23171@ietf.org>
Received: from smtp812.mail.sc5.yahoo.com ([66.163.170.82])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DMGsz-0007md-6T
	for asrg@ietf.org; Thu, 14 Apr 2005 22:48:50 -0400
Received: from unknown (HELO gous6120) (gcou@sbcglobal.net@216.226.160.13 with
	login)
	by smtp812.mail.sc5.yahoo.com with SMTP; 15 Apr 2005 02:38:20 -0000
From: "George Ou" <george_ou@netzero.com>
To: "'Bill Cole'" <asrg2@billmail.scconsult.com>, <asrg@ietf.org>
Subject: RE: [Asrg] article: port 25 blocking
Date: Thu, 14 Apr 2005 19:38:17 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
x-mimeole: Produced By Microsoft MimeOLE V6.00.2900.2180
Thread-Index: AcU/x2GxfjWx4GeHSNGybLL5ltiYnABnCviA
In-Reply-To: <p06230521be821134a91a@toaster.scconsult.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit


-----Original Message-----
From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of Bill
Cole
Sent: Tuesday, April 12, 2005 6:13 PM
To: asrg@ietf.org
Subject: RE: [Asrg] article: port 25 blocking

[SNIP]
>Not at all. The present is reasonably good and the future is fairly bright.
The exceptions to that are for people who want a single magic bullet for
spam control, and particularly for people who want that magic bullet to be
their own patented idea. It is possible right now to achieve 95% spam
rejection before DATA in SMTP and 99% rejection overall, with less than
0.01% false positives. The constraints in which that can be done are not
economically feasible for large ISP's and might not even be possible for
their sorts of very large and very diverse mail domains.

>Looking at the problem as one addressed by SPF *or* port 25 blocking *or*
some other approach is a hopeless approach. SPF and port 25 blocking both
can help solve certain problems related to spam, but neither is anywhere
near a full solution. There is a huge set of tactics and tools out there
right now that can be applied carefully, selectively, and *jointly* in
different situations to achieve very good results. The 'spam problem' is not
that no one knows how to avoid spam, but rather that too few people are
willing to devote the needed resources to avoiding it and making sure they
don't contribute to it. SPF helps on one side by letting some domains
publish hints of mixed value as to the validity of mail claiming to be them.
Port 25 blocking of dynamically assigned address space aids on another front
by reducing the population of useful spam zombies.


Bill, although I really hate the idea of port blocking, you make some very
persuasive arguments.  Sorry about the bad quoting, it's this stupid client
software of mine.


George


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


From asrg-bounces@ietf.org  Thu Apr 14 23:04:43 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25408
	for <asrg-web-archive@ietf.org>; Thu, 14 Apr 2005 23:04:43 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMHIX-0000EQ-JO
	for asrg-web-archive@ietf.org; Thu, 14 Apr 2005 23:15:13 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMH4g-0007uX-7N; Thu, 14 Apr 2005 23:00:54 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMH4e-0007uS-BT
	for asrg@megatron.ietf.org; Thu, 14 Apr 2005 23:00:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA24809
	for <asrg@ietf.org>; Thu, 14 Apr 2005 23:00:41 -0400 (EDT)
Received: from toaster.scconsult.com ([66.73.230.185])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMHEd-00006X-Cg
	for asrg@ietf.org; Thu, 14 Apr 2005 23:11:11 -0400
Received: from toaster.scconsult.com (localhost [127.0.0.1])
	by toaster.scconsult.com (Postfix) with ESMTP id CE5EB53C6CD
	for <asrg@ietf.org>; Thu, 14 Apr 2005 23:00:26 -0400 (EDT)
Mime-Version: 1.0
Message-Id: <p06230501be84d5b4b804@toaster.scconsult.com>
In-Reply-To: <6sk63rogcv4arks.140420052152@shayndel>
References: <6sk63rogcv4arks.140420052152@shayndel>
Date: Thu, 14 Apr 2005 23:00:22 -0400
To: <asrg@ietf.org>
From: Bill Cole <asrg2@billmail.scconsult.com>
Subject: RE: [Asrg] article: port 25 blocking
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8

At 9:52 PM -0400 4/14/05, Larry Seltzer wrote:
>>>>  2. A non-standard port that is 100% open just like regular SMTP is bound
>>>>     to soon be known and start to be abused. It has to be some type of
>>>>     restricted profile smtp with authentication (which is what submit is,
>>>>     so why reinvent it...).
>
>>>Right--there's no point in blocking port 25 if you just open up another
>port to plain unauthenticated SMTP....
>
>Don't get me wrong, this was just a crazy off-the-top-of-my-head idea and I
>can certainly believe I'm wrong, but this reasoning doesn't persuade me.
>There's no reason to believe that there would be a few common ports.
>
>Let's say I want to let my team of users access the mail server from their
>ISP accounts. I set up SMTP on (pull number out of ass) TCP 48207. I have to
>set this up on all their clients (and open it up on any firewalls between
>us), so for practical purposes it can't be too many of them.
>
>Assuming the ISP hasn't blocked that port as well (ISP's don't generally
>block arbitrary ports) it should solve the problem of getting through the
>port 25 block. *Conventional* worms on the system will still fail because
>they will be trying to use port 25. A new worm could be written to monitor
>all communications looking for SMTP on non-standard ports, but this is a lot
>of work when there is still low-hanging fruit out there.
>
>So how is this not going to solve anything? I agree I'd much rather have
>users run port 587 and authenticate, but if it's just your sense of
>networking asthetics that's offended by this scheme then that's worth
>saying.

That certainly is a workable approach, but it may well not be as 
usable as the port 587 approach, since there are probably marginally 
fewer mail clients capable of arbitrary port usage than are capable 
of using port 587 (or the non-standard but unfortunately still widely 
deployed port 465.) If you can put a  non-authenticated SMTP on an 
arbitrary high port, you can probably put it on port 587 just as 
easily.

However, there's really no excuse for anyone putting an 
unauthenticated SMTP for mail submission on any port. Requiring 
authentication makes a higher bar for malware to get over, and it 
really is the malware at this point that is the driving motivator for 
port 25 blocking by connection providers. Requiring authentication 
does not necessarily make it impossible for some trojan to sniff out 
how to send mail on a misdesigned system, but it generally easier to 
dig up basic config information than to find passwords.

Bottom line: putting unauthenticated SMTP for initial mail submission 
on some port other than 25 gets around port 25 blocking and presents 
no significant danger *today* but it has its own deployment problems 
for client systems and is likely to fall to the next generation of 
malware well before they figure out how to get around existing 
systems for password security and so crack authenticated SMTP.


-- 
Bill Cole
bill@scconsult.com


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


From asrg-bounces@ietf.org  Fri Apr 15 00:04:30 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28953
	for <asrg-web-archive@ietf.org>; Fri, 15 Apr 2005 00:04:30 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMIEO-0002ML-8f
	for asrg-web-archive@ietf.org; Fri, 15 Apr 2005 00:15:01 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMI1L-0004Do-SH; Fri, 15 Apr 2005 00:01:31 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMI18-00042q-Qg
	for asrg@megatron.ietf.org; Fri, 15 Apr 2005 00:01:18 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA28862
	for <asrg@ietf.org>; Fri, 15 Apr 2005 00:01:07 -0400 (EDT)
Received: from orb.pobox.com ([207.8.226.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMIB6-0002G2-Iv
	for asrg@ietf.org; Fri, 15 Apr 2005 00:11:38 -0400
Received: from orb (localhost [127.0.0.1])
	by orb.pobox.com (Postfix) with ESMTP id 59203821
	for <asrg@ietf.org>; Fri, 15 Apr 2005 00:01:03 -0400 (EDT)
Received: from [192.168.0.103] (cpe-66-68-124-39.austin.res.rr.com
	[66.68.124.39])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by orb.sasl.smtp.pobox.com (Postfix) with ESMTP id 12F3E8D
	for <asrg@ietf.org>; Fri, 15 Apr 2005 00:01:02 -0400 (EDT)
Message-ID: <425F3C7F.3040102@pobox.com>
Date: Thu, 14 Apr 2005 23:01:03 -0500
From: mathew <meta@pobox.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking
References: <6sk63rogcv4arks.140420052152@shayndel>
In-Reply-To: <6sk63rogcv4arks.140420052152@shayndel>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: d16ce744298aacf98517bc7c108bd198
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de
Content-Transfer-Encoding: 7bit

Larry Seltzer wrote:

>>Right--there's no point in blocking port 25 if you just open up another 
>>port to plain unauthenticated SMTP....
>
>
>Don't get me wrong, this was just a crazy off-the-top-of-my-head idea and I
>can certainly believe I'm wrong, but this reasoning doesn't persuade me.
>There's no reason to believe that there would be a few common ports. 
>
>Let's say I want to let my team of users access the mail server from their
>ISP accounts. I set up SMTP on (pull number out of ass) TCP 48207. I have to
>set this up on all their clients (and open it up on any firewalls between
>us), so for practical purposes it can't be too many of them.
>  
>

Let's start with why this proposal won't work.

Basically, it's security through obscurity. And in this case, the 
obscurity will only last until the first port scan. There are only 65535 
ports in total; there are plenty of tools out there which will scan them 
all in a couple of minutes; adding code to go back to each open port and 
check for an SMTP server is a trivial addition.

Like every cable modem user, I already get port scanned regularly by 
malware. As soon as any significant number of SMTP servers start using 
random unadvertised ports for unauthenticated SMTP, the port scanning 
0wn3d machines already out there will find out what those ports are. The 
spammers will simply add the port number to each address on the lists of 
open relays they already exchange with each other.

Remember, they don't care if the port scan sets off alarm bells and gets 
the scanning machine's owner into trouble, because they're using 
botnets. In fact, good luck even detecting a port scan when it's coming 
from 10,000 different IP addresses over the course of a month.

So all you'll have done is slowed the spammers for maybe a few weeks or 
a few months, depending on how long your scheme takes to become popular 
and how long it takes them to take their existing port scan code and use 
it to scan your server. Then you'll be back to square one, except you'll 
have the added support burden of having to explain to grandma what a 
port number is, and why it's different for her account than it is for 
the account of her friend that helped her set up the computer, and what 
she should do to use her e-mail client that doesn't allow arbitrary 
random port numbers to be entered.

>Assuming the ISP hasn't blocked that port as well (ISP's don't generally
>block arbitrary ports) it should solve the problem of getting through the
>port 25 block.
>
The *problem* is spam. Blocking port 25 was supposed to be a *solution*. 
Instead, it causes a problem, and doesn't stop or slow spam for any 
significant period of time.

>A new worm could be written to monitor all communications looking for SMTP on non-standard ports, but this is a lot
>of work when there is still low-hanging fruit out there.
>  
>
It's also a lot of work when you can just port scan the server, or use 
the list of server:port combinations you obtained from your spamware 
supplier.

So, it won't work. Now for some additional reasons why it's a bad idea.

First off, plenty of places only allow connections on known ports. The 
company I work for has a hard enough time getting clients to allow VPN 
connections, let alone SMTP on port 13281. There's a reason why IPSec is 
gradually disappearing and being replaced by SSL-based VPN.

Secondly, while it's common for software to implement SMTP 
authentication, it's uncommon for it to allow the user to set whatever 
random port number he likes. My phone won't allow that, for instance.

Third issue: one of the reasons we have ports in the first place is so 
that you don't get someone's FTP data session coming in on the port your 
SMTP server is connected to. There's a finite set of ports available, 
and if you start using random *necessarily undocumented* ports for your 
servers, the chance of a client talking protocol X hitting a server 
talking protocol Y increases. Better hope the client checks the server 
is talking the right protocol, and doesn't dumbly retry, or your mail 
server logs are going to fill up pretty quickly.

For problem four, let's imagine you're in charge of security for a big 
ISP. You have hundreds of corporate customers, so you'd like to be 
pro-active and watch out for intrusion attempts and have the system warn 
you. Well, now you have the problem of distinguishing between 1,000 
incoming legitimate SMTP connections on random ports caused by company 
employees sending mail via company servers, and a port scan from a 
botnet. The only way you'll be able to do it will be to do traffic 
analysis on every single incoming TCP/IP connection. That might make 
Cisco happy, because they'll be able to sell a ton of new routers, but 
it probably won't make anyone else happy.

Except that ironically, this exact same traffic pattern (incoming TCP 
connections on random ports eventually talking SMTP) is exactly what 
you'll be wanting to catch when it comes from botnets, because then 
it'll be spammers probing your customers for SMTP servers on random 
ports, rather than your customers connecting to their SMTP servers on 
random ports. So even traffic analysis won't help too much, because the 
new normal traffic pattern looks exactly like a botnet port scan.

Problem five is that another use for well-known ports is rate limiting, 
or to look at it from the other side, quality of service. Suppose you're 
in charge of networking for a major corporation. You'd probably like to 
be able to allocate a fixed minimum amount of bandwidth to SMTP, so that 
your employees can still send and receive e-mail no matter how many 
inconsiderate clods are downloading Linux ISOs via FTP. Except that now 
SMTP might be on any random port, so that's going to be more difficult 
than it used to be.

In fact, you don't even need to be a big company to have that issue--my 
home router has QoS features so I can make sure e-mail goes out even if 
the spouse or kids are uploading or downloading movies. Or at least, it 
does so long as the services I want to ensure have bandwidth, are on 
known ports...

Problem six is that it encourages spammers to generate more traffic and 
penetrate more systems. Even if we assume it does slow them for a few 
months, it's trivially defeatable if they do lots and lots of port 
scans, so guess what they're gonna be doing next year? I for one would 
rather not incent mass port scanning by botnets.

I'm sure the above isn't an exhaustive list of problems either. So, why 
not do the simpler thing that also happens to be more effective and less 
disruptive, and put authentication on your SMTP server?

I'm not saying that port 25 blocking is worthless; it's probably a 
reasonable idea under specific circumstances. That is, if a big ISP 
detects a suspicious number of outgoing SMTP connections from one of 
their customers to random machines on the Internet, it's probably worth 
blocking port 25 for that customer until the customer can explain what 
they're doing. It's probably better still (and simpler) to rate-limit 
SMTP, though.

Because of port scanning, blanket blocking of port 25 everywhere isn't 
*sufficient* as a solution to the spam problem. And since you can do 
authentication on SMTP on port 25, I think it's pretty clear that it 
isn't *necessary* either. So, we have something which is neither 
necessary nor sufficient to solve the spam problem, which causes all the 
headaches listed above. I think that qualifies it as a bad idea.

Since all the technical talk about ports and protocols is boring, I'll 
end with an analogy any random person should be able to appreciate: If 
you find that people are walking through your front door and stealing 
from your house, you can probably stop them for a little while, or at 
least slow them down, by bricking up the front door and leaving the back 
door open instead. But you know, it's not going to stop them for long, 
it's going to be a pain in the ass for you, and the real solution is to 
put a lock on the door.


mathew

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


From asrg-bounces@ietf.org  Fri Apr 15 21:33:04 2005
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA16880
	for <asrg-web-archive@ietf.org>; Fri, 15 Apr 2005 21:33:04 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1DMcLY-0006pA-TP
	for asrg-web-archive@ietf.org; Fri, 15 Apr 2005 21:43:45 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DMbv6-0001bW-At; Fri, 15 Apr 2005 21:16:24 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DMbv3-0001bC-LT
	for asrg@megatron.ietf.org; Fri, 15 Apr 2005 21:16:21 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15815
	for <asrg@ietf.org>; Fri, 15 Apr 2005 21:16:19 -0400 (EDT)
Received: from smtp.istop.com ([66.11.167.126])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DMc5L-0005sv-FI
	for asrg@ietf.org; Fri, 15 Apr 2005 21:27:00 -0400
Received: from m450 (ip225-179.tor.istop.com [66.11.179.225])
	by smtp.istop.com (Postfix) with SMTP id 41A7D2B3B5
	for <asrg@ietf.org>; Fri, 15 Apr 2005 21:17:54 -0400 (EDT)
Received: by m450 (sSMTP sendmail emulation); Fri, 15 Apr 2005 21:17:35 -0400
Date: Fri, 15 Apr 2005 21:17:35 -0400
From: Walter Dnes <waltdnes@waltdnes.org>
To: ASRG list <asrg@ietf.org>
Subject: Re: [Asrg] article: port 25 blocking
Message-ID: <20050416011734.GA8834@waltdnes.org>
References: <6sk63rogcv4arks.140420052152@shayndel>
	<425F3C7F.3040102@pobox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <425F3C7F.3040102@pobox.com>
User-Agent: Mutt/1.5.8i
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa

On Thu, Apr 14, 2005 at 11:01:03PM -0500, mathew wrote
> Larry Seltzer wrote:

> >Let's say I want to let my team of users access the mail server from
> >their ISP accounts. I set up SMTP on (pull number out of ass) TCP
> >48207. I have to set this up on all their clients (and open it up on
> >any firewalls between us, so for practical purposes it can't be too
> >many of them.
> > 
> >
> 
> Let's start with why this proposal won't work.
> 
> Basically, it's security through obscurity. And in this case, the
> obscurity will only last until the first port scan. There are only
> 65535 ports in total; there are plenty of tools out there which will
> scan them all in a couple of minutes; adding code to go back to each
> open port and check for an SMTP server is a trivial addition.

  Rather than accessing random open ports, the road warriors' machines
should be using ssh-tunneling or VPN or whatever.  I know from personal
experience that ssh-tunneling works over a NAT'ed connection, which can
break some VPNs.  Set up the sshd config to not accept passwords, i.e.
the client must use their key to authenticate.  Somebody with a traffic
sniffer sees encrypted traffic to port 22; like whoopee.

> Like every cable modem user, I already get port scanned regularly by
> malware. As soon as any significant number of SMTP servers start using
> random unadvertised ports for unauthenticated SMTP, the port scanning
> 0wn3d machines already out there will find out what those ports
> are. The spammers will simply add the port number to each address
> on the lists of open relays they already exchange with each other.

  So the traffic-sniffer sees a bunch of encrypted traffic going to port
22 on the corporate server; again, like whoopee.

-- 
Walter Dnes <waltdnes@waltdnes.org>
An infinite number of monkeys pounding away on keyboards will
eventually produce a report showing that Windows is more secure,
and has a lower TCO, than linux.

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


From asrg-bounces@ietf.org Mon Apr 18 22:48:07 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DNimV-00054L-KF; Mon, 18 Apr 2005 22:48:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DNimU-000547-A3
	for asrg@megatron.ietf.org; Mon, 18 Apr 2005 22:48:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA06458
	for <asrg@ietf.org>; Mon, 18 Apr 2005 22:48:04 -0400 (EDT)
Received: from orb.pobox.com ([207.8.226.5])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNixO-0007m4-Hp
	for asrg@ietf.org; Mon, 18 Apr 2005 22:59:23 -0400
Received: from orb (localhost [127.0.0.1])
	by orb.pobox.com (Postfix) with ESMTP id E65738B7
	for <asrg@ietf.org>; Mon, 18 Apr 2005 22:47:59 -0400 (EDT)
Received: from [192.168.0.103] (cpe-66-68-124-39.austin.res.rr.com
	[66.68.124.39])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by orb.sasl.smtp.pobox.com (Postfix) with ESMTP id C484987
	for <asrg@ietf.org>; Mon, 18 Apr 2005 22:47:59 -0400 (EDT)
Message-ID: <42647160.1030907@pobox.com>
Date: Mon, 18 Apr 2005 21:48:00 -0500
From: mathew <meta@pobox.com>
User-Agent: Mozilla Thunderbird 1.0 (X11/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Cc: ASRG list <asrg@ietf.org>
Subject: Re: [Asrg] article: port 25 blocking
References: <6sk63rogcv4arks.140420052152@shayndel>	<425F3C7F.3040102@pobox.com>
	<20050416011734.GA8834@waltdnes.org>
In-Reply-To: <20050416011734.GA8834@waltdnes.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

Walter Dnes wrote:

>On Thu, Apr 14, 2005 at 11:01:03PM -0500, mathew wrote
>  
>
>>Basically, it's security through obscurity. And in this case, the
>>obscurity will only last until the first port scan. There are only
>>65535 ports in total; there are plenty of tools out there which will
>>scan them all in a couple of minutes; adding code to go back to each
>>open port and check for an SMTP server is a trivial addition.
>>    
>>
>
>  Rather than accessing random open ports, the road warriors' machines
>should be using ssh-tunneling or VPN or whatever.
>

In which case there's no need for the "random ports" proposal in the 
first place.


mathew

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



From asrg-bounces@ietf.org Tue Apr 19 12:24:26 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DNvWU-0005NM-AR; Tue, 19 Apr 2005 12:24:26 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DNvWS-0005NE-4y
	for asrg@megatron.ietf.org; Tue, 19 Apr 2005 12:24:24 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24205
	for <asrg@ietf.org>; Tue, 19 Apr 2005 12:24:20 -0400 (EDT)
Received: from b1.iprcom.com ([84.234.16.216])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DNvhT-0004kg-RP
	for asrg@ietf.org; Tue, 19 Apr 2005 12:35:49 -0400
Received: from iprcom.com (localhost [127.0.0.1])
	by b1.iprcom.com (8.12.8/8.12.8) with SMTP id j3JGOFRx004733
	for <asrg@ietf.org>; Tue, 19 Apr 2005 17:24:16 +0100
Received: from 193.128.25.20 (SquirrelMail authenticated user ian)
	by iprcom.com with HTTP; Tue, 19 Apr 2005 17:24:16 +0100 (BST)
Message-ID: <26777.193.128.25.20.1113927856.squirrel@iprcom.com>
In-Reply-To: <30605.193.128.25.20.1112200575.squirrel@iprcom.com>
References: <200503280718500.SM06476@sk.cybercominc.com>     
	<424ACC70.80304@pobox.com> 
	<30605.193.128.25.20.1112200575.squirrel@iprcom.com>
Date: Tue, 19 Apr 2005 17:24:16 +0100 (BST)
From: "Ian Rogers" <ian@iprcom.com>
To: asrg@ietf.org
User-Agent: SquirrelMail/1.4.0
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
X-Priority: 3
Importance: Normal
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Subject: [Asrg] Re: Anti-spam comparison
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

> --- I wrote: ---
> Is there any kind of central resource that attempts to compare all the
> anti-spam techniques and/or algorithms in one place?
>
> I know many people have their own websites arguing for/against their
> favourite/most-hated scheme, but has there ever been an attempt to bring
> all the arguments together *dis*-passionately?


As there was no answer to my post above I've gone ahead and created an AS
comparison site - www.fussp.info

It's only just starting so comments are *extremely* welcome at this point.
For example:

Has this been done elsewhere? What are the key functions/features you'd
like to see on the site? Where should I be concentrating/prioritising my
efforts? etc.

Regards,

Ian.

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



From asrg-bounces@ietf.org Wed Apr 20 01:14:48 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DO7Xz-0006h3-Nk; Wed, 20 Apr 2005 01:14:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DO7Xv-0006gv-0q
	for asrg@megatron.ietf.org; Wed, 20 Apr 2005 01:14:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA27740
	for <asrg@ietf.org>; Wed, 20 Apr 2005 01:14:42 -0400 (EDT)
Received: from out1.smtp.messagingengine.com ([66.111.4.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DO7j1-00059u-F3
	for asrg@ietf.org; Wed, 20 Apr 2005 01:26:14 -0400
Received: from frontend2.messagingengine.com (frontend2.internal
	[10.202.2.151])
	by frontend1.messagingengine.com (Postfix) with ESMTP id 2EC91C76DD5;
	Wed, 20 Apr 2005 01:14:37 -0400 (EDT)
X-Sasl-enc: /L6JCMTv1XlBq1ESn5gyPO7ZA3S71QbrrgA+lIeIsPIu 1113974076
Received: from [192.168.2.98] (adsl-67-122-214-165.dsl.snfc21.pacbell.net
	[67.122.214.165])
	by frontend2.messagingengine.com (Postfix) with ESMTP id 8179F56F785;
	Wed, 20 Apr 2005 01:14:35 -0400 (EDT)
Message-ID: <4265E53C.4000702@elvey.com>
Date: Tue, 19 Apr 2005 22:14:36 -0700
From: Matthew Elvey <matthew@elvey.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Larry Seltzer <larry@larryseltzer.com>
Subject: Re: [Asrg] article: port 25 blocking
References: <t0zf81nxps3na3q.120420051002@shayndel>
In-Reply-To: <t0zf81nxps3na3q.120420051002@shayndel>
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
X-Spam-Score: -7.9 (-------)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

Ok, I think some clarification is in order.

On 4/12/2005 7:02 AM, Larry Seltzer sent forth electrons to convey:
 > <that random ports should be used, and that if 465/587 became common, 
spammers would adapt to using them instead of 25.>

Larry, I think you're a bit confused (assuming my paraphrasing of your 
statements is accurate).  465/587 are being suggested as alternatives 
for 25 because the ONLY way to send spam (or legitimate email) using 
SMTP is over port 25.  Let me explain.
Briefly (and with some simplification), this is how systems send mail to 
an Internet email address:
1) Look up the IP of the machine that receives mail for the domain. 
2) Open up a TCP connection to that IP ON PORT 25. 
3) Send the message. 
The machines that receive Internet email for domains via SMTP from 
systems with which there is no prior relationship do not receive that 
mail on ports other than TCP port 25.
There's no way that's going to change in the foreseeable future (ie. 
flying pigs, or 100% adoption of SPF WITH end-user roll-out, '-all' 
records AND SRS are more likely).
Let's assume that there's massive adoption of  mail submission via 
465/587, and of port 25 blocking.   It will still be the case that all 
mail sent via 465/587 will then be sent via the 3-step process above, 
via port 25.  So the port 25 blocking will remain effective.  It will 
not be possible for spammer's zombies to send mail by following the 
3-step process above. Why?  The only machines they will be able to reach 
via port 25 will be their/the zombie's ISP's mail servers.  And if they 
try to send spam via 465/587, they will be sending via machines that are 
relays, as these will be the only machines listening on those ports. 
These (closed) relays (which are not port 25-blocked) are managed by ISPs. 

Make sense?

BTW, have you looked at CSV? 


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



From asrg-bounces@ietf.org Wed Apr 20 02:43:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DO8wB-0000N6-3P; Wed, 20 Apr 2005 02:43:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DO8w9-0000N1-1p
	for asrg@megatron.ietf.org; Wed, 20 Apr 2005 02:43:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA07597
	for <asrg@ietf.org>; Wed, 20 Apr 2005 02:43:47 -0400 (EDT)
Received: from out1.smtp.messagingengine.com ([66.111.4.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DO97I-0007W0-Ck
	for asrg@ietf.org; Wed, 20 Apr 2005 02:55:21 -0400
Received: from frontend2.messagingengine.com (frontend2.internal
	[10.202.2.151])
	by frontend1.messagingengine.com (Postfix) with ESMTP id 8BE39C7728D;
	Wed, 20 Apr 2005 02:43:44 -0400 (EDT)
X-Sasl-enc: E4Abthsr0ArfyEQdrRIKsdn5U9y+Fc0U3cEwT29HLVrz 1113979424
Received: from [192.168.2.98] (adsl-67-122-214-165.dsl.snfc21.pacbell.net
	[67.122.214.165])
	by frontend2.messagingengine.com (Postfix) with ESMTP id 630CB570159;
	Wed, 20 Apr 2005 02:43:43 -0400 (EDT)
Message-ID: <4265FA21.3070909@elvey.com>
Date: Tue, 19 Apr 2005 23:43:45 -0700
From: Matthew Elvey <matthew@elvey.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ian Rogers <ian@iprcom.com>
Subject: Re: [Asrg] Re: Anti-spam comparison
References: <200503280718500.SM06476@sk.cybercominc.com>
	<424ACC70.80304@pobox.com>
	<30605.193.128.25.20.1112200575.squirrel@iprcom.com>
	<26777.193.128.25.20.1113927856.squirrel@iprcom.com>
In-Reply-To: <26777.193.128.25.20.1113927856.squirrel@iprcom.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
X-Spam-Score: -7.9 (-------)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

On 4/19/05 9:24 AM, Ian Rogers sent forth electrons to convey:

>>--- I wrote: ---
>>Is there any kind of central resource that attempts to compare all the
>>anti-spam techniques and/or algorithms in one place?
>>
>>I know many people have their own websites arguing for/against their
>>favourite/most-hated scheme, but has there ever been an attempt to bring
>>all the arguments together *dis*-passionately?
>>    
>>
>
>
>As there was no answer to my post above I've gone ahead and created an AS
>comparison site - www.fussp.info
>  
>
Hi, Ian.
I don't think it reached the list; I didn't get it and I don't filter 
list traffic.
Cute domain. :) 
Go here:
http://wiki.fastmail.fm/index.php/EvaluationsOfCSV
to find info on previous evaluation efforts - ASRG evaluation criteria 
(a must read!), plus some good stuff from Meng Wong, and from me on CSV.
Just looked at the site. The scenarios are a good idea too.  I think the 
site's content should boil down to a  2-axis chart:
schemes on one axis, evaluation criteria (e.g. scenarios) on the other. 
Oh, and is the site content open? (I.e. Creative commons licensed?  To 
be considered as IETF WG work?  Who's in control?)

>It's only just starting so comments are *extremely* welcome at this point.
>For example:
>
>Has this been done elsewhere? What are the key functions/features you'd
>like to see on the site? Where should I be concentrating/prioritising my
>efforts? etc.
>


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



From asrg-bounces@ietf.org Wed Apr 20 03:55:01 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOA32-0008RY-Q6; Wed, 20 Apr 2005 03:55:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOA2z-0008RQ-62
	for asrg@megatron.ietf.org; Wed, 20 Apr 2005 03:54:57 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13011
	for <asrg@ietf.org>; Wed, 20 Apr 2005 03:54:55 -0400 (EDT)
Received: from out1.smtp.messagingengine.com ([66.111.4.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOAE9-0001Ch-Dt
	for asrg@ietf.org; Wed, 20 Apr 2005 04:06:30 -0400
Received: from frontend3.messagingengine.com (frontend3.internal
	[10.202.2.152])
	by frontend1.messagingengine.com (Postfix) with ESMTP id DC4D6C76988
	for <asrg@ietf.org>; Wed, 20 Apr 2005 03:54:53 -0400 (EDT)
X-Sasl-enc: EMAGm1KuX1XL9phJNSKi/SRGnFmPrGXy2r6gAUgDDER5 1113983693
Received: from [192.168.2.98] (adsl-67-122-214-165.dsl.snfc21.pacbell.net
	[67.122.214.165])
	by frontend3.messagingengine.com (Postfix) with ESMTP id B56FC6C;
	Wed, 20 Apr 2005 03:54:52 -0400 (EDT)
Message-ID: <42660ACE.6060001@elvey.com>
Date: Wed, 20 Apr 2005 00:54:54 -0700
From: Matthew Elvey <matthew@elvey.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ASRG <asrg@ietf.org>
References: <F28EE5829564BA41A08E1B4F026B1709333CB8@ct-ex02.ciphertrust.com>
In-Reply-To: <F28EE5829564BA41A08E1B4F026B1709333CB8@ct-ex02.ciphertrust.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
X-Spam-Score: -7.9 (-------)
X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Ban ciphertrust?
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

Can we semi-permanently ban ciphertrust.com from the ASRG mailing list?  
This is not the first time they've used a broken auto-responder.

Re: Out of Office AutoReply: [Asrg] Re: Anti-spam comparison

On 4/19/05 11:57 PM, bradon.rogers@ciphertrust.com sent forth electrons 
to convey:

>I will be out of the country on vacation beginning Wednesday April 20 and
>will be returning Monday April 25.  I will be checking email occassionally
>and will respond as I can.  
>
>If you require technical assistance please contact CipherTrust Support at
>678-867-2999 or support@ciphertrust.com.  Otherwise I will be back in full
>gear on Monday the 25th and I will help you then.  
>
>Thank you very much,
>
>Bradon
>  
>


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



From asrg-bounces@ietf.org Wed Apr 20 06:05:41 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOC5U-0006SW-WD; Wed, 20 Apr 2005 06:05:41 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOC5T-0006SR-B9
	for asrg@megatron.ietf.org; Wed, 20 Apr 2005 06:05:39 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21657
	for <asrg@ietf.org>; Wed, 20 Apr 2005 06:05:37 -0400 (EDT)
Received: from mail28.sea5.speakeasy.net ([69.17.117.30])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOCGf-0004tx-La
	for asrg@ietf.org; Wed, 20 Apr 2005 06:17:14 -0400
Received: (qmail 5125 invoked from network); 20 Apr 2005 10:05:37 -0000
Received: from dsl081-214-187.nyc2.dsl.speakeasy.net (HELO
	3comemail.larryseltzer.com) ([64.81.214.187])
	(envelope-sender <larry@larryseltzer.com>)
	by mail28.sea5.speakeasy.net (qmail-ldap-1.03) with SMTP
	for <asrg@ietf.org>; 20 Apr 2005 10:05:36 -0000
From: "Larry Seltzer" <larry@larryseltzer.com>
To: "'Matthew Elvey'" <matthew@elvey.com>
Subject: RE: [Asrg] article: port 25 blocking
Date: Wed, 20 Apr 2005 06:07:35 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
In-Reply-To: <4265E53C.4000702@elvey.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
thread-index: AcVFaRcE+0fQbPKBTa6XT2gaMkdNxwAJo7ig
Message-ID: <oetrwxhbgaeyf1p.200420050607@shayndel>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Content-Transfer-Encoding: 7bit
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

>>....
>>These (closed) relays (which are not port 25-blocked) are managed by ISPs.

>>Make sense?

Actually, no, I can't find the message with the exact quote from me you cite
and it's over a week ago so I don't remember exactly what the context was. I
think everything you say is obvious and I don't know what you're clarifying.

>>BTW, have you looked at CSV?  

Not in a long time.

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

-----Original Message-----
From: asrg-bounces@ietf.org [mailto:asrg-bounces@ietf.org] On Behalf Of
Matthew Elvey
Sent: Wednesday, April 20, 2005 1:15 AM
To: Larry Seltzer
Cc: asrg@ietf.org
Subject: Re: [Asrg] article: port 25 blocking

Ok, I think some clarification is in order.

On 4/12/2005 7:02 AM, Larry Seltzer sent forth electrons to convey:
 > <that random ports should be used, and that if 465/587 became common,
spammers would adapt to using them instead of 25.>

Larry, I think you're a bit confused (assuming my paraphrasing of your
statements is accurate).  465/587 are being suggested as alternatives for 25
because the ONLY way to send spam (or legitimate email) using SMTP is over
port 25.  Let me explain.
Briefly (and with some simplification), this is how systems send mail to an
Internet email address:
1) Look up the IP of the machine that receives mail for the domain. 
2) Open up a TCP connection to that IP ON PORT 25. 
3) Send the message. 
The machines that receive Internet email for domains via SMTP from systems
with which there is no prior relationship do not receive that mail on ports
other than TCP port 25.
There's no way that's going to change in the foreseeable future (ie. 
flying pigs, or 100% adoption of SPF WITH end-user roll-out, '-all' 
records AND SRS are more likely).
Let's assume that there's massive adoption of  mail submission via 
465/587, and of port 25 blocking.   It will still be the case that all 
mail sent via 465/587 will then be sent via the 3-step process above, via
port 25.  So the port 25 blocking will remain effective.  It will not be
possible for spammer's zombies to send mail by following the 3-step process
above. Why?  The only machines they will be able to reach via port 25 will
be their/the zombie's ISP's mail servers.  And if they try to send spam via
465/587, they will be sending via machines that are relays, as these will be
the only machines listening on those ports. 
These (closed) relays (which are not port 25-blocked) are managed by ISPs. 

Make sense?

BTW, have you looked at CSV? 


_______________________________________________
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 asrg-bounces@ietf.org Wed Apr 20 08:33:34 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOEOc-0002hf-SN; Wed, 20 Apr 2005 08:33:34 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOEOb-0002ha-80
	for asrg@megatron.ietf.org; Wed, 20 Apr 2005 08:33:33 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03329
	for <asrg@ietf.org>; Wed, 20 Apr 2005 08:33:32 -0400 (EDT)
Received: from b1.iprcom.com ([84.234.16.216])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOEZn-0000yX-Nb
	for asrg@ietf.org; Wed, 20 Apr 2005 08:45:09 -0400
Received: from iprcom.com (localhost [127.0.0.1])
	by b1.iprcom.com (8.12.8/8.12.8) with SMTP id j3KCXVRx001952;
	Wed, 20 Apr 2005 13:33:31 +0100
Received: from 193.128.25.20 (SquirrelMail authenticated user ian)
	by iprcom.com with HTTP; Wed, 20 Apr 2005 13:33:31 +0100 (BST)
Message-ID: <59633.193.128.25.20.1114000411.squirrel@iprcom.com>
In-Reply-To: <4265FA21.3070909@elvey.com>
References: <200503280718500.SM06476@sk.cybercominc.com><424ACC70.80304@pobox.com>
	<30605.193.128.25.20.1112200575.squirrel@iprcom.com><26777.193.128.25.
	20.1113927856.squirrel@iprcom.com> <4265FA21.3070909@elvey.com>
Date: Wed, 20 Apr 2005 13:33:31 +0100 (BST)
Subject: Re: [Asrg] Re: Anti-spam comparison
From: "Ian Rogers" <ian@iprcom.com>
To: "Matthew Elvey" <matthew@elvey.com>
User-Agent: SquirrelMail/1.4.0
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
X-Priority: 3
Importance: Normal
X-Spam-Score: 0.8 (/)
X-Scan-Signature: c1c65599517f9ac32519d043c37c5336
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

Matthew Elvey wrote:
> On 4/19/05 9:24 AM, Ian Rogers sent forth electrons to convey:
>
>>I've gone ahead and created an AS comparison site - www.fussp.info
>>
>>
> Go here:
> http://wiki.fastmail.fm/index.php/EvaluationsOfCSV
> to find info on previous evaluation efforts - ASRG evaluation criteria
> (a must read!),

Thanks, I've added it to the todo list.

> Just looked at the site. The scenarios are a good idea too.  I think the
> site's content should boil down to a  2-axis chart:
> schemes on one axis, evaluation criteria (e.g. scenarios) on the other.

Yes, that's exactly what I had in mind - plus a database and description
language so that when someone says "oh but surely we can just make a
hybrid of this, this and this" we'll be able to plug a description
straight in and see if it comes up "green light" against all the scenarios
- no more long-winded arguments after that...

> Oh, and is the site content open? (I.e. Creative commons licensed?

Yes: CC, GPL, whatever. It's just a case of picking the most appropriate
one (I guess I'll have to pick one before I can accept any new authors -
is there a license comparison site??).

> To be considered as IETF WG work?

I'd love it to become a WG community site.

> Who's in control?)

Err, me :-) Benign Dictator I hope :)

Ian.

Ps.

> Cute domain. :)

:) I tried to contact to owner of fussp.net and fussp.com, as he's doing
nothing with the domains, to see how generous he'd be in return for good
karma but got no reply...


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



From asrg-bounces@ietf.org Wed Apr 20 12:26:12 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOI1j-00081d-Gb; Wed, 20 Apr 2005 12:26:12 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOI1h-00080j-Ud
	for asrg@megatron.ietf.org; Wed, 20 Apr 2005 12:26:10 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24687
	for <asrg@ietf.org>; Wed, 20 Apr 2005 12:26:07 -0400 (EDT)
Received: from out1.smtp.messagingengine.com ([66.111.4.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOICw-0008NI-GH
	for asrg@ietf.org; Wed, 20 Apr 2005 12:37:47 -0400
Received: from frontend3.messagingengine.com (frontend3.internal
	[10.202.2.152])
	by frontend1.messagingengine.com (Postfix) with ESMTP id 50D29C770FE;
	Wed, 20 Apr 2005 12:26:05 -0400 (EDT)
X-Sasl-enc: iIBxAkWPUgK4xTCmP9BUkB/JRaCrsCVapO/rTPM3KtKJ 1114014365
Received: from [192.168.2.98] (adsl-67-122-214-165.dsl.snfc21.pacbell.net
	[67.122.214.165])
	by frontend3.messagingengine.com (Postfix) with ESMTP id 95D075F;
	Wed, 20 Apr 2005 12:26:04 -0400 (EDT)
Message-ID: <42668299.3020608@elvey.com>
Date: Wed, 20 Apr 2005 09:26:01 -0700
From: Matthew Elvey <matthew@elvey.com>
User-Agent: Mozilla Thunderbird 1.0 (Macintosh/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Larry Seltzer <larry@larryseltzer.com>, ASRG <asrg@ietf.org>
Subject: Re: [Asrg] article: port 25 blocking
References: <oetrwxhbgaeyf1p.200420050607@shayndel>
In-Reply-To: <oetrwxhbgaeyf1p.200420050607@shayndel>
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
X-Spam-Score: -7.9 (-------)
X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352
Content-Transfer-Encoding: 7bit
Cc: 
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

On 4/20/05 3:07 AM, Larry Seltzer sent forth electrons to convey:

>>>....
>>>These (closed) relays (which are not port 25-blocked) are managed by ISPs.
>>>      
>>>
>
>  
>
>>>Make sense?
>>>      
>>>
>
>Actually, no, I can't find the message with the exact quote from me you cite
>  
>
I was paraphrasing, hence the <> and use of the words "that" and 
"paraphrasing".  Sorry if it wasn't clear enough for ya, or wasn't 
paraphrasing accurately, or mis-attributed - there were a lot of posts 
that were being quoted anonymously or with broken mail clients. 

PLEASE, FOLKS, IF YOUR MAIL CLIENT CAN'T QUOTE PROPERLY, USE ANOTHER 
ONE!  (USE A WEBMAIL CLIENT IF YOU CAN'T SWITCH YOUR MAIN CLIENT!)  (But 
if the quoting is already broken by someone else, removing the 
attribution is reasonable...)

>and it's over a week ago so I don't remember exactly what the context was. I
>think everything you say is obvious and I don't know what you're clarifying.
>  
>
Ok, then.  :)

>  
>
>>>BTW, have you looked at CSV?  
>>>      
>>>
>
>Not in a long time.
>  
>
If you've looked at it and understand it, that's fine.  It's not 
constantly changing and forking.  But code is being written. Thanks.
NRN.

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



From asrg-bounces@ietf.org Wed Apr 20 13:56:05 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOJQj-0004Yq-5O; Wed, 20 Apr 2005 13:56:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOJQh-0004Yl-Ai
	for asrg@megatron.ietf.org; Wed, 20 Apr 2005 13:56:03 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02277
	for <asrg@ietf.org>; Wed, 20 Apr 2005 13:56:00 -0400 (EDT)
Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOJbv-0002xZ-Jn
	for asrg@ietf.org; Wed, 20 Apr 2005 14:07:40 -0400
Received: from list by ciao.gmane.org with local (Exim 4.43)
	id 1DOJKU-0000Mv-SC
	for asrg@ietf.org; Wed, 20 Apr 2005 19:49:38 +0200
Received: from c-134-88-84.hh.dial.de.ignite.net ([62.134.88.84])
	by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
	id 1AlnuQ-0007hv-00
	for <asrg@ietf.org>; Wed, 20 Apr 2005 19:49:38 +0200
Received: from nobody by c-134-88-84.hh.dial.de.ignite.net with local (Gmexim
	0.1 (Debian)) id 1AlnuQ-0007hv-00
	for <asrg@ietf.org>; Wed, 20 Apr 2005 19:49:38 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: asrg@ietf.org
From: Frank Ellermann <nobody@xyzzy.claranet.de>
Date: Wed, 20 Apr 2005 19:50:47 +0200
Organization: <URL:http://purl.net/xyzzy>
Lines: 17
Message-ID: <42669677.3A91@xyzzy.claranet.de>
References: <oetrwxhbgaeyf1p.200420050607@shayndel>
	<42668299.3020608@elvey.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet@sea.gmane.org
X-Gmane-NNTP-Posting-Host: c-134-88-84.hh.dial.de.ignite.net
X-Mailer: Mozilla 3.0 (OS/2; U)
X-Spam-Score: 2.9 (++)
X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: article: port 25 blocking
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

Matthew Elvey wrote:

> It's not constantly changing and forking.

The MAY quasi-zone-cut stuff is rather new (Feb 20).

<rant mode="on"> Unlike SPF, where the removal of the
real zone-cut is not yet published in an I-D, and the
switch from "MAY test HELO" to SHOULD is also not yet
published. </rant>

> code is being written

Don't expect too much, even the "flying pigs" (as you
said) with an immediate obvious profit for senders and
receivers had some difficulties learning to fly.  Bye



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



From asrg-bounces@ietf.org Wed Apr 20 14:20:28 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOJoK-0000AX-39; Wed, 20 Apr 2005 14:20:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOJoI-00008d-9M
	for asrg@megatron.ietf.org; Wed, 20 Apr 2005 14:20:26 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04749
	for <asrg@ietf.org>; Wed, 20 Apr 2005 14:20:24 -0400 (EDT)
Received: from twentyseven.202.omne.uk.net ([80.255.202.27]
	helo=dolphin.chromatix.org.uk)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOJzX-0003uO-DK
	for asrg@ietf.org; Wed, 20 Apr 2005 14:32:04 -0400
Received: from arowana.chromatix.org.uk ([192.168.200.106])
	by dolphin.chromatix.org.uk with esmtp (Exim 4.43)
	id 1DOJoE-0003fw-4q; Wed, 20 Apr 2005 19:20:22 +0100
In-Reply-To: <26777.193.128.25.20.1113927856.squirrel@iprcom.com>
References: <200503280718500.SM06476@sk.cybercominc.com>
	<424ACC70.80304@pobox.com>
	<30605.193.128.25.20.1112200575.squirrel@iprcom.com>
	<26777.193.128.25.20.1113927856.squirrel@iprcom.com>
Mime-Version: 1.0 (Apple Message framework v622)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <f7682bac3b9f14a343d51cedb507a802@chromatix.demon.co.uk>
Content-Transfer-Encoding: 7bit
From: Jonathan Morton <chromi@chromatix.demon.co.uk>
Subject: Re: [Asrg] Re: Anti-spam comparison
Date: Wed, 20 Apr 2005 19:20:29 +0100
To: "Ian Rogers" <ian@iprcom.com>
X-Mailer: Apple Mail (2.622)
X-Spam-Score: 2.6 (++)
X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32
Content-Transfer-Encoding: 7bit
Cc: ASRG <asrg@ietf.org>
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org


On 19 Apr, 2005, at 5:24 pm, Ian Rogers wrote:

> As there was no answer to my post above I've gone ahead and created an 
> AS
> comparison site - www.fussp.info
>
> It's only just starting so comments are *extremely* welcome at this 
> point.

Cheers.  You now have a resident hashcash expert (me), busily making 
posts and comments.  I wonder if article/comment authors get 
notification when someone else posts something relevant?

There's a slight problem with the site layout, in that comments to a 
short article are hidden right at the bottom of a long scroll, due to 
the extremely long right-hand banner.  It'd be rather a good idea to 
fix that.

--------------------------------------------------------------
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 asrg-bounces@ietf.org Wed Apr 20 14:22:36 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOJqO-0000LF-U6; Wed, 20 Apr 2005 14:22:36 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOJqM-0000Kq-2x
	for asrg@megatron.ietf.org; Wed, 20 Apr 2005 14:22:34 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04942
	for <asrg@ietf.org>; Wed, 20 Apr 2005 14:22:32 -0400 (EDT)
Received: from chiark.greenend.org.uk ([193.201.200.170] ident=mail)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOK1a-0003wY-IA
	for asrg@ietf.org; Wed, 20 Apr 2005 14:34:13 -0400
Received: by chiark.greenend.org.uk (Debian Exim 3.35 #1) with local
	(return-path fanf@chiark.greenend.org.uk)
	id 1DOJqE-00021d-00; Wed, 20 Apr 2005 19:22:26 +0100
To: matthew@elvey.com
From: Tony Finch <dot@dotat.at>
Subject: Re: [Asrg] article: port 25 blocking
In-Reply-To: <42668299.3020608@elvey.com>
References: <oetrwxhbgaeyf1p.200420050607@shayndel>
	<oetrwxhbgaeyf1p.200420050607@shayndel>
Message-Id: <E1DOJqE-00021d-00@chiark.greenend.org.uk>
Date: Wed, 20 Apr 2005 19:22:26 +0100
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

>>>>BTW, have you looked at CSV?  
>>
>>Not in a long time.
>
>If you've looked at it and understand it, that's fine.  It's not 
>constantly changing and forking.  But code is being written.

My Exim CSA implementation works well and should be included in the
next release.

Tony.
-- 
f.a.n.finch  <dot@dotat.at>  http://dotat.at/
FAEROES SOUTHEAST ICELAND: EAST OR SOUTHEAST 4 OR 5. MAINLY FAIR. MODERATE OR
GOOD.

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



From asrg-bounces@ietf.org Wed Apr 20 20:36:44 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOPgS-0000yb-Mu; Wed, 20 Apr 2005 20:36:44 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOPgP-0000yT-JD
	for asrg@megatron.ietf.org; Wed, 20 Apr 2005 20:36:42 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14050
	for <asrg@ietf.org>; Wed, 20 Apr 2005 20:36:39 -0400 (EDT)
Received: from out1.smtp.messagingengine.com ([66.111.4.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOPri-0006SW-7s
	for asrg@ietf.org; Wed, 20 Apr 2005 20:48:23 -0400
Received: from frontend2.messagingengine.com (frontend2.internal
	[10.202.2.151])
	by frontend1.messagingengine.com (Postfix) with ESMTP id C5A3BC777AC;
	Wed, 20 Apr 2005 20:36:36 -0400 (EDT)
X-Sasl-enc: iPZCdyfzfzys+uYh2uFWoGyPQpI8iWQsj6Yy02mjamNh 1114043795
Received: from [192.168.1.4] (office.nextbus.com [64.142.39.200])
	by frontend2.messagingengine.com (Postfix) with ESMTP id 2C84256F785;
	Wed, 20 Apr 2005 20:36:34 -0400 (EDT)
Message-ID: <4266F590.9000005@elvey.com>
Date: Wed, 20 Apr 2005 17:36:32 -0700
From: Matthew Elvey <matthew@elvey.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Ian Rogers <ian@iprcom.com>, ASRG <asrg@ietf.org>
References: <200503280718500.SM06476@sk.cybercominc.com><424ACC70.80304@pobox.com>
	<30605.193.128.25.20.1112200575.squirrel@iprcom.com><26777.193.128.25.
	20.1113927856.squirrel@iprcom.com> <4265FA21.3070909@elvey.com>
	<59633.193.128.25.20.1114000411.squirrel@iprcom.com>
In-Reply-To: <59633.193.128.25.20.1114000411.squirrel@iprcom.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
X-Spam-Score: -8.0 (--------)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Content-Transfer-Encoding: 7bit
Cc: 
Subject: [Asrg] comparisons
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

As long as we're talking about comparisons: Here's an interesting take 
on spam-fighting:
http://wiki.fastmail.fm/wiki/index.php/FightSpam  Shows the upside and 
downside of wikis... (note the hit-man references).
=-=-=-=-=
Apropos fussp.info:
A few schemes and scheme tweaks I've thought of.

Universal adoption says:
"A whitelist scheme can only be used to reject spam when *every* 
legitimate mail sender is part of the scheme. "
Well, no.  Having a whitelist scheme in place means you can turn up the 
sensitivity on your spam-detection tools (i.e. lower SpamAssassin score 
thresholds and reject more spam) and maintain the same FP rate, or keep 
them at the current level and have a lower FP rate.  Also, what does 
"Universal" mean?  Every sender? user? recipient? server? domain? needs 
to adopt it?

New scheme:
"User support is expensive"
e.g. Large ISPs will not adopt schemes that require each end-user make 
changes to their setups, such as installing new software or even just 
reconfiguring current software.  They are not willing to do something 
that will precipitate a deluge of support calls.

BTW, the current TOU (Terms of Use) are unreasonable:
Too long.
Undated.
changes w/o notice???
Usage of my account by another due to a security flaw in your system is 
not my responsibility.
12. Reservation of rights - NOT compatible with open content...

Privacy policy:
too long, etc.

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



From asrg-bounces@ietf.org Thu Apr 21 06:28:06 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DOYuj-0004fC-Uj; Thu, 21 Apr 2005 06:28:05 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DOYui-0004f5-Cs
	for asrg@megatron.ietf.org; Thu, 21 Apr 2005 06:28:04 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13826
	for <asrg@ietf.org>; Thu, 21 Apr 2005 06:28:02 -0400 (EDT)
Received: from b1.iprcom.com ([84.234.16.216])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DOZ66-0001EV-H3
	for asrg@ietf.org; Thu, 21 Apr 2005 06:39:52 -0400
Received: from iprcom.com (localhost [127.0.0.1])
	by b1.iprcom.com (8.12.8/8.12.8) with SMTP id j3LAS2Rx004983;
	Thu, 21 Apr 2005 11:28:02 +0100
Received: from 193.128.25.20 (SquirrelMail authenticated user ian)
	by iprcom.com with HTTP; Thu, 21 Apr 2005 11:28:02 +0100 (BST)
Message-ID: <31473.193.128.25.20.1114079282.squirrel@iprcom.com>
In-Reply-To: <4266F590.9000005@elvey.com>
References: <200503280718500.SM06476@sk.cybercominc.com><424ACC70.80304@pobox.com>
	<30605.193.128.25.20.1112200575.squirrel@iprcom.com><26777.193.128.25.
	20.1113927856.squirrel@iprcom.com> 
	<4265FA21.3070909@elvey.com><59633.193.128.25.20.1114000411.squirrel@i
	prcom.com> <4266F590.9000005@elvey.com>
Date: Thu, 21 Apr 2005 11:28:02 +0100 (BST)
From: "Ian Rogers" <ian@iprcom.com>
To: "Matthew Elvey" <matthew@elvey.com>
User-Agent: SquirrelMail/1.4.0
MIME-Version: 1.0
Content-Type: text/plain;charset=iso-8859-1
X-Priority: 3
Importance: Normal
X-Spam-Score: 0.8 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Cc: ASRG <asrg@ietf.org>
Subject: [Asrg] Re: comparisons
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

Matthew Elvey wrote:
> http://wiki.fastmail.fm/wiki/index.php/FightSpam  Shows the upside and
> downside of wikis... (note the hit-man references).

An interesting article (and with anonymising communications and payment
escrow the "go to jail" risk could be minimised :)

> =-=-=-=-=
> Apropos fussp.info:
> A few schemes and scheme tweaks I've thought of.
>
> Universal adoption [ http://www.fussp.info/Article20.html ]  says:
> "A whitelist scheme can only be used to reject spam when *every*
> legitimate mail sender is part of the scheme. "
> Well, no.  Having a whitelist scheme in place means you can turn up the
> sensitivity on your spam-detection tools (i.e. lower SpamAssassin score
> thresholds and reject more spam) and maintain the same FP rate, or keep
> them at the current level and have a lower FP rate.

Yes that's exactly correct - a whitelist doesn't increase the positive
rate (ie. you can't use it on its own to reject spam) though it can be
used to lower the false-positive rate for next layer (though the whitelist
needs to be backed up by a working authenticated-sender scheme (which
doesn't exist yet??) to be reliable).

> Also, what does
> "Universal" mean?  Every sender? user? recipient? server? domain? needs
> to adopt it?

Yes, good comment, I am vague there (though perhaps usefully so :-) I'll
extend the article in due course.


> New scheme:
> "User support is expensive"
> e.g. Large ISPs will not adopt schemes that require each end-user make
> changes to their setups, such as installing new software or even just
> reconfiguring current software.  They are not willing to do something
> that will precipitate a deluge of support calls.

That's a scenario as opposed to a scheme, but please go ahead an submit
that as an article on the site (I'm keen not to steal authorship kudos for
myself).

> BTW, the current TOU (Terms of Use) are unreasonable:
> Too long.
> Undated.
> changes w/o notice???
> Usage of my account by another due to a security flaw in your system is
> not my responsibility.
> 12. Reservation of rights - NOT compatible with open content...
>
> Privacy policy:
> too long, etc.

I rushed up the current T&C as a guideline before people started writing
articles (I have a day-job so can't spend 8 hours a day on this :)  I'm
finding your comments very useful so please get in touch "offline" so to
speak and we'll work out an appropriate T&C.

Cheers,

Ian.

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



From asrg-bounces@ietf.org Mon Apr 25 21:57:50 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQFKg-0005Qm-UJ; Mon, 25 Apr 2005 21:57:50 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQFKf-0005Qg-K1
	for asrg@megatron.ietf.org; Mon, 25 Apr 2005 21:57:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA20827
	for <asrg@ietf.org>; Mon, 25 Apr 2005 21:57:46 -0400 (EDT)
From: gep2@terabites.com
Message-Id: <200504260157.VAA20827@ietf.org>
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQFX1-0004U9-Mp
	for asrg@ietf.org; Mon, 25 Apr 2005 22:10:36 -0400
Date: Tue, 26 Apr 2005 01:57:34 +0000 (GMT)
X-Comment: Sending client does not conform to RFC822 minimum requirements
X-Comment: Date has been added by Maillennium
Received: from WinProxy.anywhere
	(c-24-0-189-130.hsd1.tx.comcast.net[24.0.189.130])
	by comcast.net (rwcrmhc13) with SMTP
	id <2005042601573301500587kfe>; Tue, 26 Apr 2005 01:57:33 +0000
Received: from 192.168.0.104 by 192.168.0.100 (WinProxy);
	Mon, 25 Apr 2005 20:56:29 -0600
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
To: asrg@ietf.org
In-Reply-To: <auto-000059778874@fr5.webmaillogin.com>
X-Mailer: SPRY Mail Version: 04.00.06.17
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 00e94c813bef7832af255170dca19e36
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: whitelisting
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

>> "A whitelist scheme can only be used to reject spam when *every*
> legitimate mail sender is part of the scheme. "

That's ridiculous.  

The point of a whitelist (IMHO) is to toss out certain types of incoming mail 
that you aren't willing to trust or accept from people you don't recognize.

Ideally, such a whitelist is VERY finely-grained, and with a "relatively safe" 
default behavior.

I have proposed here (and I'll do so again) that a reasonable default behavior 
(for senders not on your whitelist) is to allow plain ASCII text, NO HTML, no 
attachments, and of a limited size (say 25K or 50K or something).

When you whitelist senders, you ought to be able to do so (again) in a 
fine-grained way.  For example, Aunt Gertrude might send me a JPG of her poodle 
Fifi, or might use her favorite stationery with a nice script or handwriting 
font, but there's no likelihood that she'd try to send me a 165K byte PIF file 
or an ActiveX enclosure or some kind of encrypted Javascript.  Anything 
purporting to come from her which contains that kind of unusual stuff is almost 
certainly bogus, and can be safely deleted.

Once the HTML, scripting, and attachments are zapped, there are relatively few 
tricks remaining that spammers can use to evade content filters... so the 
fine-grained whitelist discrimination should be followed up by a good content 
filter.

> Well, no.  Having a whitelist scheme in place means you can turn up the
> sensitivity on your spam-detection tools (i.e. lower SpamAssassin score
> thresholds and reject more spam) and maintain the same FP rate, or keep
> them at the current level and have a lower FP rate.

It's certainly true that a good fine-grained whitelist makes it a LOT easier for 
your content filter to do a good (in fact, probably EXCELLENT) job.

> Yes that's exactly correct - a whitelist doesn't increase the positive
rate (ie. you can't use it on its own to reject spam) 

I disagree... I think you CAN use it to reject spam, although one might argue 
that it's even more useful to reject OTHER kinds of unwanted/untrustworthy 
mail.... specifically, phishing scams with misrepresented hyperlinks, 
attachments which carry viruses or worms, and other unwanted junk.

> ...though it can be used to lower the false-positive rate for next layer 
(though the whitelist needs to be backed up by a working authenticated-sender 
scheme (which doesn't exist yet??) to be reliable).

I agree that knowing who the "real" sender is can be useful, although by itself 
it's NO guarantee of safety (or not being spam) either.  The fact that the 
"from:" address represents the actual machine of (or an alternate machine 
sometimes used by) that legitimate sender is NOT a guarantee that said machine 
hasn't been commandeered by a spambot zombie which is sending out spam or 
viruses using the victim's authorizations and certificates.  

Many "certification" schemes are worse still in that they only try to determine 
that the E-mail originated from a server authorized to send mail from the 
indicated "sender domain", and for domains containing (literally) millions of 
valid E-mail addresses, that means that ANY of those millions of machines could 
counterfeit/spoof the E-mail address of any other user within the same domain 
name and still successfully pass the "authorized mail server for that domain" 
test.

Ultimately, it's a FAR better solution to identify spam based on whether it 
"looks right" (i.e. looks like mail is EXPECTED to look, coming from that 
specific sender) and that it doesn't contain anything (executable attachments, 
encrypted ZIP files, Javascript, ActiveX modules, etc etc) that make its purpose 
or intentions suspect.

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 asrg-bounces@ietf.org Tue Apr 26 10:31:33 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQR65-00051M-Qk; Tue, 26 Apr 2005 10:31:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQR63-00051H-Q6
	for asrg@megatron.ietf.org; Tue, 26 Apr 2005 10:31:31 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13023
	for <asrg@ietf.org>; Tue, 26 Apr 2005 10:31:25 -0400 (EDT)
Received: from smtpauth04.mail.atl.earthlink.net ([209.86.89.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQRIR-0005in-Gw
	for asrg@ietf.org; Tue, 26 Apr 2005 10:44:20 -0400
Received: from [199.174.117.121] (helo=[10.30.102.232])
	by smtpauth04.mail.atl.earthlink.net with asmtp (Exim 4.34)
	id 1DQR5l-0006iu-Vx; Tue, 26 Apr 2005 10:31:14 -0400
In-Reply-To: <200504260157.VAA20827@ietf.org>
References: <200504260157.VAA20827@ietf.org>
Mime-Version: 1.0 (Apple Message framework v622)
Message-Id: <eab9ffa2b1fc6d33d6b2c7cf36bac12b@corp.earthlink.net>
From: James Baldwin <baldwin@corp.earthlink.net>
Subject: [Asrg] Re: whitelisting
Date: Tue, 26 Apr 2005 10:31:10 -0400
To: gep2@terabites.com
X-Pgp-Agent: GPGMail 1.0.2
X-Mailer: Apple Mail (2.622)
X-ELNK-Trace: de55e2125488fe2cc06e95782e8f638e7e972de0d01da940f65e31f3cb7d60fb0fc3b91a4bf080e3350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 199.174.117.121
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 93e7fb8fef2e780414389440f367c879
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1441754900=="
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org


--===============1441754900==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="Apple-Mail-4-927201049"
Content-Transfer-Encoding: 7bit


--Apple-Mail-4-927201049
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit

On 25 Apr 2005, at 21:57, gep2@terabites.com wrote:

> The point of a whitelist (IMHO) is to toss out certain types of 
> incoming mail
> that you aren't willing to trust or accept from people you don't 
> recognize.

I think we're getting into a bit of a semantical tiff here. This is 
dependent on whether or not your site is practicing a default deny or 
default accept policy with regards to mail. Many sites would rather 
trust unknown senders and reject known poor senders rather than 
increase false positive rates and associated support costs.

> Ideally, such a whitelist is VERY finely-grained, and with a 
> "relatively safe"
> default behavior.

Finely grained anything leads to scalability and complexity issues. 
That is not to say such solutions cannot work, only that the trade off 
between complexity and effectiveness often yields diminishing returns.

> When you whitelist senders, you ought to be able to do so (again) in a
> fine-grained way.

In your proposed implementation, who controls this white list? The 
"you" appears to indicate the mail service provider, however, managing 
a finely grained permission set for millions of users quickly outstrips 
available resources. Another solution is to have service 
representatives default allow behavior when a customer complains, 
however this is expensive both in representative time and in the amount 
of churn it will cause due to dissatisfied customers. The most scalable 
solution is to have the customer control their settings. This most 
likely would fail as most customers will not understand the options of 
a finely grained control system.

> Once the HTML, scripting, and attachments are zapped, there are 
> relatively few
> tricks remaining that spammers can use to evade content filters... so 
> the
> fine-grained whitelist discrimination should be followed up by a good 
> content
> filter.

Do content filters not weight based on the presence of HTML, scripting, 
and attachments? Does not automatically deleting matches to this 
blanket rule reduce, not increase, your amount of control over what 
mail you allow?

> I disagree... I think you CAN use it to reject spam, although one 
> might argue
> that it's even more useful to reject OTHER kinds of 
> unwanted/untrustworthy
> mail.... specifically, phishing scams with misrepresented hyperlinks,
> attachments which carry viruses or worms, and other unwanted junk.

Once again, this is semantics. Default deny versus default reject.

> I agree that knowing who the "real" sender is can be useful, although 
> by itself
> it's NO guarantee of safety (or not being spam) either.  The fact that 
> the
> "from:" address represents the actual machine of (or an alternate 
> machine
> sometimes used by) that legitimate sender is NOT a guarantee that said 
> machine
> hasn't been commandeered by a spambot zombie which is sending out spam 
> or
> viruses using the victim's authorizations and certificates.

This is a remote site management issue. It is up to the remote site to 
manage whether or not their senders can forge "From:" fields. The 
domain based identification allows us make policy decisions based on 
administrative boundaries, that is to say we can either block poor 
senders or return mail to the administrators for further investigation. 
You cannot guarantee that the mail was send legitimately, but you can 
guarantee that your policies are affecting the responsible parties.

> Many "certification" schemes are worse still in that they only try to 
> determine
> that the E-mail originated from a server authorized to send mail from 
> the
> indicated "sender domain", and for domains containing (literally) 
> millions of
> valid E-mail addresses, that means that ANY of those millions of 
> machines could
> counterfeit/spoof the E-mail address of any other user within the same 
> domain
> name and still successfully pass the "authorized mail server for that 
> domain"
> test.

Once again, "spoofing" is a domain based sender policy issue. If the 
remote site is only allowing "From:" fields to match the authenticated 
username this is a non issue. If the site is not authenticated mail 
sourced within their domain, then my external policies are in place to 
restrict this behavior.

> Ultimately, it's a FAR better solution to identify spam based on 
> whether it
> "looks right" (i.e. looks like mail is EXPECTED to look, coming from 
> that
> specific sender) and that it doesn't contain anything (executable 
> attachments,
> encrypted ZIP files, Javascript, ActiveX modules, etc etc) that make 
> its purpose
> or intentions suspect.

I disagree. Keeping state on specific senders will not scale to the 
whole internet. If you're discussing keeping state on specific senders 
in an edge model, this might be appropriate as the number of legitimate 
senders to a single receiver is small, however on an enterprise level I 
cannot fathom a manner to efficiently manage state for every sender 
destined to my customers. It is less complex to create stateless 
policies based on message contents and keep state on high traffic 
authenticated sender domains.

--Apple-Mail-4-927201049
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFCblCuILGER88VYe0RAnhJAJ0TzBl+qxZACzJl0TtFw1dzZPq1KwCgxCGH
fQly91YgXoYUzaaZjgt1LzQ=
=+OBV
-----END PGP SIGNATURE-----

--Apple-Mail-4-927201049--



--===============1441754900==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1441754900==--





From asrg-bounces@ietf.org Tue Apr 26 20:22:15 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQaJj-0008Mf-D4; Tue, 26 Apr 2005 20:22:15 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQaJh-0008Ma-UY
	for asrg@megatron.ietf.org; Tue, 26 Apr 2005 20:22:14 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06871
	for <asrg@ietf.org>; Tue, 26 Apr 2005 20:22:12 -0400 (EDT)
From: gep2@terabites.com
Message-Id: <200504270022.UAA06871@ietf.org>
Received: from rwcrmhc13.comcast.net ([204.127.198.39])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQaWD-00048m-BX
	for asrg@ietf.org; Tue, 26 Apr 2005 20:35:12 -0400
Date: Wed, 27 Apr 2005 00:22:01 +0000 (GMT)
X-Comment: Sending client does not conform to RFC822 minimum requirements
X-Comment: Date has been added by Maillennium
Received: from WinProxy.anywhere
	(c-24-0-189-130.hsd1.tx.comcast.net[24.0.189.130])
	by comcast.net (rwcrmhc13) with SMTP
	id <20050427002200015005496oe>; Wed, 27 Apr 2005 00:22:00 +0000
Received: from 192.168.0.104 by 192.168.0.100 (WinProxy);
	Tue, 26 Apr 2005 19:20:01 -0600
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Subject: [Asrg] Re: whitelisting
To: asrg@ietf.org
X-Mailer: SPRY Mail Version: 04.00.06.17
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 71f780ffdd80c541d3e75aa5f2710d3d
Content-Transfer-Encoding: 7bit
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

>> The point of a whitelist (IMHO) is to toss out certain types of 
> incoming mail
> that you aren't willing to trust or accept from people you don't 
> recognize.

> I think we're getting into a bit of a semantical tiff here. 

No, not really.

> This is dependent on whether or not your site is practicing a default deny or 
default accept policy with regards to mail. 

No.

The default behavior (for unlisted senders) under my approach would depend upon 
the characteristics of the E-mail message.

A plain text E-mail, with no attachments, no HTML, and less than some specified 
size (probably 25K or 50K or something) would probably be set to default to 
"accept".  This would provide for "ordinary" unsolicited E-mails (say for a 
customer relations department of a consumer products company) to be delivered.  

People without an established contact history who send "large" E-mails, or 
attachments, or HTML, or scripting, etc etc, would find their mail either 
blocked or at least rerouted to quarantine for exceptional handling.

> Many sites would rather trust unknown senders and reject known poor senders 
rather than increase false positive rates and associated support costs.

That approach has led to the widespread conclusion that whitelisting approaches 
are not tolerable... especially in situations where users might ANTICIPATE 
receiving "unsolicited" E-mails (e.g. hearing from someone you gave a business 
card to, once upon a time).  Now, on my approach you could theoretically set it 
as you're suggesting (if you REALLY want to) by setting the defaults 
appropriately.

But my feeling is that someone you don't know who sends you an unsolicited 
E-mail containing encrypting Javascript or a 160K-byte PIF executable file or a 
125Kbyte encrypted ZIP file (or even just an 80K .COM file attachment) is 
probably someone that you didn't really want to receive that mail from anyhow.  
:-)

>> Ideally, such a whitelist is VERY finely-grained, and with a 
> "relatively safe" default behavior.

> Finely grained anything leads to scalability and complexity issues. 

"Scalability" is not a serious issue if the screening is (at least initially) 
conducted at the recipient end, where there are as a rule plenty of resources 
available.

Complexity issues depend entirely on how the software is implemented.  I claim 
that it's possible to implement the software such that it's easy to manage these 
sorts of finely-grained permissions list (for example, by offering the user the 
option to "allow this sender to send this type of E-mail message in the future" 
without them having to worry about what specific permissions are involved in 
achieving that).

> That is not to say such solutions cannot work, only that the trade off 
between complexity and effectiveness often yields diminishing returns.

Certainly there ARE diminishing returns in many anti-spam approaches, but I feel 
(strongly) that a good implementation of my approach does not end up there.

>> When you whitelist senders, you ought to be able to do so (again) in a
> fine-grained way.

> In your proposed implementation, who controls this white list? 

The whitelist would be controlled by the recipient.

> The "you" appears to indicate the mail service provider, however, managing 
a finely grained permission set for millions of users quickly outstrips 
available resources. 

No, my plan is for the recipient (the person directly affected by its operation, 
and most directly benfitting from its proper tuning) will be the person managing 
the filters.

> Another solution is to have service 
representatives default allow behavior when a customer complains, 
however this is expensive both in representative time and in the amount 
of churn it will cause due to dissatisfied customers. 

The problem with ISP-provided solutions is precisely that they are too crude and 
too un-nuanced to enable them to do a good job.

> The most scalable 
solution is to have the customer control their settings. 

Exactly.

> This most likely would fail as most customers will not understand the options 
of a finely grained control system.

That's an implementation issue, and a good software implementation will shield 
users from those specific details.

>> Once the HTML, scripting, and attachments are zapped, there are 
> relatively few
> tricks remaining that spammers can use to evade content filters... so 
> the
> fine-grained whitelist discrimination should be followed up by a good 
> content filter.

> Do content filters not weight based on the presence of HTML, scripting, 
and attachments? 

The problem is that HTML, scripting, attachments and the like are typically used 
by spammers to evade content filters... things like "text as image", encrypted 
attachments, scripting, misrepresented links, and so forth.  Content filters can 
do a FAR better job once the input data going into them is cleansed from such 
things.

Meanwhile, ESTABLISHED senders that you TRUST (if any) can be set to allow their 
use of such more dangerous/risky stuff.  But you could set your E-mail to ONLY 
allow THOSE (few, probably) specific users to send you that type of content...

> Does not automatically deleting matches to this blanket rule reduce, not 
increase, your amount of control over what mail you allow?

No, because you can set the defaults to whatever you want.  The important 
concept is that INITIAL contacts (to establish a relationship, whether personal 
or commercial) can be done in a general and 'safe' way that works for everyone. 
 Any more advanced content can be sent ONLY after being negotiated between the 
users.

>> I disagree... I think you CAN use it to reject spam, although one 
> might argue
> that it's even more useful to reject OTHER kinds of 
> unwanted/untrustworthy
> mail.... specifically, phishing scams with misrepresented hyperlinks,
> attachments which carry viruses or worms, and other unwanted junk.

> Once again, this is semantics. Default deny versus default reject.

No.  It's more nuanced than that.  Its default behavior depends on the TYPE of 
content in the mail (and its size).  

>> I agree that knowing who the "real" sender is can be useful, although 
> by itself
> it's NO guarantee of safety (or not being spam) either.  The fact that 
> the
> "from:" address represents the actual machine of (or an alternate 
> machine
> sometimes used by) that legitimate sender is NOT a guarantee that said 
> machine
> hasn't been commandeered by a spambot zombie which is sending out spam 
> or viruses using the victim's authorizations and certificates.

> This is a remote site management issue. 

It doesn't matter.

The point is that even (usually) well-managed systems CAN be infected, and other 
users at the same ISP can often forge addresses for other users at the same ISP 
domain name.  

The approach I propose has the very nice property that it would effortlessly 
discriminate between the mail from Aunt Gertrude that LOOKS like her mail, while 
still quarantining stuff CLAIMING to be from her that doesn't "look" right.

> It is up to the remote site to 
manage whether or not their senders can forge "From:" fields. 

It's fine to tell others what they "should" do but my proposal can be 
implemented on a single-ended basis and provide IMMEDIATE benefit to the person 
responsible for installing and tuning it, whether any sending-end changes are 
made or not.  Therefore it allows eliminating the ugliness of "someday" and 
allows besieged recipients to get relief RIGHT AWAY.

> The domain based identification allows us make policy decisions based on 
administrative boundaries, that is to say we can either block poor 
senders or return mail to the administrators for further investigation. 

Again, my approach offers MUCH greater nuance than that.  A trusted friend who 
happens to be using a somewhat-flakey or sloppy ISP doesn't have to be 
penalized.  Your suggestion results in painting folks with too wide a brush, 
which prevents effective filtering.

> You cannot guarantee that the mail was send legitimately, but you can 
guarantee that your policies are affecting the responsible parties.

It leaves innocent victims who are punished by association.

>> Many "certification" schemes are worse still in that they only try to 
> determine
> that the E-mail originated from a server authorized to send mail from 
> the
> indicated "sender domain", and for domains containing (literally) 
> millions of
> valid E-mail addresses, that means that ANY of those millions of 
> machines could
> counterfeit/spoof the E-mail address of any other user within the same 
> domain
> name and still successfully pass the "authorized mail server for that 
> domain"
> test.

> Once again, "spoofing" is a domain based sender policy issue. 

Fine.  Again, my approach allows a recipient to control what THEY receive, and 
without leaving them in the frustrating position of "I wish someone else would 
do <whatever>."

> If the remote site is only allowing "From:" fields to match the authenticated 
username this is a non issue. 

No, because the mail could be FULLY authenticated, if the victim's machine has 
been infected by a spambot zombie.  That spambot could send E-mail spams and 
worms using the REAL user's AUTHENTICATED permissions.

> If the site is not authenticated mail sourced within their domain, then my 
external policies are in place to restrict this behavior.

Even if they are, authenticated mail can still be fraudulent.

>> Ultimately, it's a FAR better solution to identify spam based on 
> whether it
> "looks right" (i.e. looks like mail is EXPECTED to look, coming from 
> that
> specific sender) and that it doesn't contain anything (executable 
> attachments,
> encrypted ZIP files, Javascript, ActiveX modules, etc etc) that make 
> its purpose or intentions suspect.

> I disagree. Keeping state on specific senders will not scale to the 
whole internet. 

It doesn't have to.  You only need to have individual recipients each have a 
finite number of TRUSTED recipients (and the GREAT majority of senders a given 
recipient receives mail from will NOT need to be whitelisted).

> If you're discussing keeping state on specific senders 
in an edge model, this might be appropriate as the number of legitimate 
senders to a single receiver is small, 

Exactly.

> ...however on an enterprise level I cannot fathom a manner to efficiently 
manage state for every sender destined to my customers. 

It's really a very simple problem, and not a particularly difficult or 
complicated one to resolve (probably easier, in fact, than IP routing and 
such...)

> It is less complex to create stateless policies based on message contents and 
keep state on high traffic authenticated sender domains.

Less complex approaches (and my approach is NOT particularly complicated, at 
that) are demonstrably inadequate, again because they paint people and mail with 
such a wide brush that inevitably a lot of unwanted mail slips through.


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 asrg-bounces@ietf.org Wed Apr 27 16:21:29 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQt2H-0005c5-BT; Wed, 27 Apr 2005 16:21:29 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQt2F-0005az-9q
	for asrg@megatron.ietf.org; Wed, 27 Apr 2005 16:21:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29234
	for <asrg@ietf.org>; Wed, 27 Apr 2005 16:21:23 -0400 (EDT)
Received: from xuxa.iecc.com ([208.31.42.42])
	by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DQtEr-0008D0-H2
	for asrg@ietf.org; Wed, 27 Apr 2005 16:34:34 -0400
Received: (qmail 27083 invoked by uid 100); 27 Apr 2005 20:21:01 -0000
Date: 27 Apr 2005 20:21:01 -0000
Message-ID: <20050427202101.27082.qmail@xuxa.iecc.com>
From: John Levine <asrg@johnlevine.com>
To: asrg@ietf.org
Subject: Re: [Asrg] Ban ciphertrust?
In-Reply-To: <42660ACE.6060001@elvey.com>
Organization: I.E.C.C., Trumansburg NY USA
Mime-Version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Content-Transfer-Encoding: 7bit
Cc: matthew@elvey.com
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

>Can we semi-permanently ban ciphertrust.com from the ASRG mailing list?  
>This is not the first time they've used a broken auto-responder.

I do it one address at a time.

>On 4/19/05 11:57 PM, bradon.rogers@ciphertrust.com sent forth electrons 
>to convey:

Hmmn, that address isn't subscribed nor is anything like it.  Any idea
who it came from?

>
>>I will be out of the country on vacation beginning Wednesday April 20 and
>>will be returning Monday April 25.  I will be checking email occassionally
>>and will respond as I can.  
>>
>>If you require technical assistance please contact CipherTrust Support at
>>678-867-2999 or support@ciphertrust.com.  Otherwise I will be back in full
>>gear on Monday the 25th and I will help you then.  
>>
>>Thank you very much,
>>
>>Bradon

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



From asrg-bounces@ietf.org Wed Apr 27 19:36:51 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DQw5L-0001Gr-0J; Wed, 27 Apr 2005 19:36:51 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DQw5J-0001Gm-FX
	for asrg@megatron.ietf.org; Wed, 27 Apr 2005 19:36:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19789
	for <asrg@ietf.org>; Wed, 27 Apr 2005 19:36:46 -0400 (EDT)
Received: from out1.smtp.messagingengine.com ([66.111.4.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DQwI2-0006RM-Tv
	for asrg@ietf.org; Wed, 27 Apr 2005 19:50:00 -0400
Received: from frontend2.messagingengine.com (frontend2.internal
	[10.202.2.151])
	by frontend1.messagingengine.com (Postfix) with ESMTP id CA1BEC7E56B;
	Wed, 27 Apr 2005 19:36:41 -0400 (EDT)
X-Sasl-enc: OpQGu7TofIyvunOW3YvL86IK5YrGByf3NBM5H+7Qdy5/ 1114645000
Received: from [192.168.1.250] (pix.nextbus.com [64.142.39.201])
	by frontend2.messagingengine.com (Postfix) with ESMTP id CF88456D31D;
	Wed, 27 Apr 2005 19:36:35 -0400 (EDT)
Message-ID: <42702203.9010801@elvey.com>
Date: Wed, 27 Apr 2005 16:36:35 -0700
From: Matthew Elvey <matthew@elvey.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: John Levine <asrg@johnlevine.com>, bradon.rogers@ciphertrust.com,
	ASRG <asrg@ietf.org>
Subject: Re: [Asrg] Ban ciphertrust?
References: <20050427202101.27082.qmail@xuxa.iecc.com>
In-Reply-To: <20050427202101.27082.qmail@xuxa.iecc.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
X-Spam-Score: -8.0 (--------)
X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d
Content-Transfer-Encoding: 7bit
Cc: 
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

Bradon tells me he's unsubscribed, and asked what was broken.
FYI, I did email him the last time this happened, *as well as* the folks 
the broken autoresponder said to email*.
But the same, still-broken auto-responder was used again. It's broken 
because it violates several suggestions in  RFC 3834. 3834 has several 
suggestions that will keep autoresponders from sending mail to mailing 
lists. IN ADDITION, spamcop.net clearly explains what's wrong with 
Bradon's auto-responder via a prominent link on their home page to 
http://www.spamcop.net/fom-serve/cache/329.html
Still, yeah, I overrreacted a bit.  We don't want to ban Paul Judge...  
Case closed.


*To: bradon.rogers@ciphertrust.com, mark@ciphertrust.com, 
akuehn@ciphertrust.com

Subject: Re:  [Asrg] Collaborative real time spam blocking
References: <DAB35AC199E7D14BAF265C1D188583687A434A@ct-ex01.ciphertrust.com>
In-Reply-To: <DAB35AC199E7D14BAF265C1D188583687A434A@ct-ex01.ciphertrust.com>

Your autoresponder is fubarred.
 
On 10/22/2004 3:30 PM, bradon.rogers@ciphertrust.com sent forth 
electrons to convey:
>...
>
>If you require sales assistance please contact Mark Caldwell at 678-570-1571
>or mark@ciphertrust.com.
>
>If you require sales engineering assistance please contact Aaron Kuehn at
>678-904-9250 or akuehn@ciphertrust.com.
>
>Lastly if you require technical assistance please contact CipherTrust
>Support at 678-867-2999 or support@ciphertrust.com.
>
>Thank you very much,
>
>Bradon


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



From asrg-bounces@ietf.org Thu Apr 28 11:59:16 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRBQ4-00051Y-FZ; Thu, 28 Apr 2005 11:59:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRBQ3-00051T-8I
	for asrg@megatron.ietf.org; Thu, 28 Apr 2005 11:59:15 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA29180
	for <asrg@ietf.org>; Thu, 28 Apr 2005 11:59:10 -0400 (EDT)
Received: from smtpauth04.mail.atl.earthlink.net ([209.86.89.64])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRBct-0000Xz-SJ
	for asrg@ietf.org; Thu, 28 Apr 2005 12:12:32 -0400
Received: from [199.174.117.121] (helo=[10.30.102.232])
	by smtpauth04.mail.atl.earthlink.net with asmtp (Exim 4.34)
	id 1DRBPr-0003Jr-2t; Thu, 28 Apr 2005 11:59:03 -0400
In-Reply-To: <200504270022.UAA06871@ietf.org>
References: <200504270022.UAA06871@ietf.org>
Mime-Version: 1.0 (Apple Message framework v622)
Message-Id: <927ad5adc003cc0d4f0983ddbeeecf2b@corp.earthlink.net>
From: James Baldwin <baldwin@corp.earthlink.net>
Subject: Re: [Asrg] Re: whitelisting
Date: Thu, 28 Apr 2005 11:59:02 -0400
To: gep2@terabites.com
X-Pgp-Agent: GPGMail 1.0.2
X-Mailer: Apple Mail (2.622)
X-ELNK-Trace: de55e2125488fe2cc06e95782e8f638e7e972de0d01da940208a7bb7ab4e65c2d42c4e73b78de910350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 199.174.117.121
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Cc: asrg@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1541322970=="
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org


--===============1541322970==
Content-Type: multipart/signed; protocol="application/pgp-signature";
	micalg=pgp-sha1; boundary="Apple-Mail-2--1042211041"
Content-Transfer-Encoding: 7bit


--Apple-Mail-2--1042211041
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit

On 26 Apr 2005, at 20:22, gep2@terabites.com wrote:

> That's an implementation issue, and a good software implementation 
> will shield
> users from those specific details.

I agree that an implementation which provide ease of use and 
accessibility for users to have this level of finely grained control is 
a good thing. I do not think it will solve our problem any more than 
current solutions in edge filtering already provide. The problem I am 
referring to is not, necessarily, that of the customer being delivered 
unsolicited mail but rather the support and operating costs it 
generates. I do not think the adoption rate of any application which 
requires consistent user interaction to derive effectiveness will be 
high enough to offset the costs necessary to reduce filtering in the 
core.

If you find anything which meets your requirements, I would love to see 
it if for nothing else than personal use.

> The point is that even (usually) well-managed systems CAN be infected, 
> and other
> users at the same ISP can often forge addresses for other users at the 
> same ISP
> domain name.

Unless you are referring to the risk of an ISPs mail server itself 
becoming infected, you can mitigate this risk by ensuring that only 
authenticated users can send mail and that authenticated users can only 
send mail with "from:" addresses matching their specific allowed 
addresses.

> Therefore it allows eliminating the ugliness of "someday" and
> allows besieged recipients to get relief RIGHT AWAY.

Your definition of "right away" and mine differ. Your solution still 
requires development and cost incurred by promoting its adoption within 
our user base. It would be significantly sooner than waiting for 
adoption of all players in Internet mail to secure their mail servers 
and I look forward to seeing a mail client with this functionality.

> Again, my approach offers MUCH greater nuance than that.  A trusted 
> friend who
> happens to be using a somewhat-flakey or sloppy ISP doesn't have to be
> penalized.  Your suggestion results in painting folks with too wide a 
> brush,
> which prevents effective filtering.

I do not encourage sloppy or somewhat-flakey players in any space. 
Inconsistent mail service is a good reason to switch to a better 
network provider. I believe a more appropriate point would be that you 
do not wish to penalize your own subscribers by blocking legitimate 
mail received from friends on sloppy providers. Unfortunately, not 
penalizing a subset of customers who receive mail from legitimate 
sources on sloppy providers often times penalizes are larger subset of 
customers who receive unsolicited mail from this same provider. And 
thus begins the magic juggling dance of blocking unsolicited mail while 
reducing false positives.

> It leaves innocent victims who are punished by association.

Encourage innocent victims to make better choices.

> Fine.  Again, my approach allows a recipient to control what THEY 
> receive, and
> without leaving them in the frustrating position of "I wish someone 
> else would
> do <whatever>."

This is akin to a thread I am currently participating in on NANOG. In 
cases where customers want to be in complete control of the traffic 
they receive, they should be willing and understand that this will be 
awarded at a higher price point and include maintaining their own mail 
infrastructure.

> No, because the mail could be FULLY authenticated, if the victim's 
> machine has
> been infected by a spambot zombie.  That spambot could send E-mail 
> spams and
> worms using the REAL user's AUTHENTICATED permissions.

Yes. Regardless of the content recognition you place on the receiving 
end, in this case you will receive some spam or have a higher rate of 
false positives.

> Even if they are, authenticated mail can still be fraudulent.

Authenticated mail which does not match the finely grained controls, 
which could place undue burden on the sender to know those controls in 
advance, is going to be passed along in either case. When that happens, 
it is important to have authenticated sender schemes in place in order 
to respond to the appropriate party.

> It doesn't have to.  You only need to have individual recipients each 
> have a
> finite number of TRUSTED recipients (and the GREAT majority of senders 
> a given
> recipient receives mail from will NOT need to be whitelisted).

Agreed. When you find a system like this which provides the finely 
grained control you want, pass it along. Mail clients have provided 
this for a long time in the form of accepting messages only from known 
senders. It doesn't have the finely grained control you desire, but it 
is an effective example. As in that case, I do not think it will prove 
effective in the long run as it requires too much interaction from the 
participant in spite of its high effectiveness rate.
---
James Baldwin
hkp://pgp.mit.edu/jbaldwin@antinode.net
"Syntatic sugar causes cancer of the semicolon."

--Apple-Mail-2--1042211041
content-type: application/pgp-signature; x-mac-type=70674453;
	name=PGP.sig
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)

iD8DBQFCcQhGILGER88VYe0RAgOsAJ4pH3ayaVwp0/TCE9daFI9rmw3RaQCgk2Gw
jJdiQRXm3UdUWAQr6iOtmfM=
=mmGC
-----END PGP SIGNATURE-----

--Apple-Mail-2--1042211041--



--===============1541322970==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1541322970==--





From asrg-bounces@ietf.org Fri Apr 29 23:24:08 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRiaO-0006ib-0O; Fri, 29 Apr 2005 23:24:08 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRiaJ-0006gS-9C
	for asrg@megatron.ietf.org; Fri, 29 Apr 2005 23:24:06 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14185
	for <asrg@ietf.org>; Fri, 29 Apr 2005 23:24:00 -0400 (EDT)
From: gep2@terabites.com
Message-Id: <200504300324.XAA14185@ietf.org>
Received: from rwcrmhc12.comcast.net ([216.148.227.85])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRinU-00061v-K2
	for asrg@ietf.org; Fri, 29 Apr 2005 23:37:41 -0400
Date: Sat, 30 Apr 2005 03:23:52 +0000 (GMT)
X-Comment: Sending client does not conform to RFC822 minimum requirements
X-Comment: Date has been added by Maillennium
Received: from WinProxy.anywhere
	(c-24-0-189-130.hsd1.tx.comcast.net[24.0.189.130])
	by comcast.net (rwcrmhc12) with SMTP
	id <2005043003235201400kt2hfe>; Sat, 30 Apr 2005 03:23:52 +0000
Received: from 192.168.0.104 by 192.168.0.100 (WinProxy);
	Fri, 29 Apr 2005 22:21:58 -0600
MIME-Version: 1.0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Subject: Re: [Asrg] Re: whitelisting
To: asrg@ietf.org
X-Mailer: SPRY Mail Version: 04.00.06.17
X-Spam-Score: 0.4 (/)
X-Scan-Signature: 913ee11e7c554f7d4da75d500826397e
Content-Transfer-Encoding: 7bit
Cc: 
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

>> That's an implementation issue, and a good software implementation 
> will shield users from those specific details.

> I agree that an implementation which provide ease of use and 
accessibility for users to have this level of finely grained control is 
a good thing. I do not think it will solve our problem any more than 
current solutions in edge filtering already provide. 

I think it WILL, because:

  1)  it will virtually eliminate E-mail as a successful vector for the 
transmission of worms and viruses (thus GREATLY reducing the ability to create 
spambot zombies);

  2)  it will make it harder to spoof URLs in phishing exploits;

  3)  it will GREATLY increase the efficacy of antispam content filters.

> The problem I am referring to is not, necessarily, that of the customer being 
delivered unsolicited mail 

"Unsolicited mail" is NOT automatically a bad thing... for example, if you're in 
the "customer relations" department for a consumer product manufacturer, the 
GREAT majority of what you're going to receive is from people you've never 
gotten E-mail from before.  (Likewise for people who hand out a lot of business 
cards and network vigorously!).  This is, in fact, the reason why "don't deliver 
mail from anyone that's not whitelisted" is not a reasonable solution.

But I don't *EVER* need to receive 160K PIF attachments, or decrypting 
Javascript E-mails, or unsolicited 5Mb .BMP files attachments, or most other 
kinds of HTML-burdened E-mails.

> ...but rather the support and operating costs it generates. I do not think the 
adoption rate of any application which requires consistent user interaction to 
derive effectiveness will be high enough to offset the costs necessary to reduce 
filtering in the core.

I don't think user interaction, if they SEE SIGNIFICANT PROGRESS, and feel like 
THEY ARE IN CONTROL, is a problem.

> If you find anything which meets your requirements, I would love to see 
it if for nothing else than personal use.

Well, one thought would be for me to simply write one (and I'm currently running 
here a somewhat different self-written incoming E-mail processing filter, 
written in protected-mode SPITBOL) but ultimately where my proposed filter WANTS 
to be is incorporated into Outlook Express and Outlook (and following which, in 
competing E-mail client software).  Nowadays, the problem isn't so much WRITING 
good software, but managing to get it distributed widely enough to be helpful.

That said, I'd be glad to write the software to run independently (i.e. to work 
with existing E-mail clients), if you know someone who would be interested in 
funding the effort... if you do, send 'em my way.

>> The point is that even (usually) well-managed systems CAN be infected, 
> and other
> users at the same ISP can often forge addresses for other users at the 
> same ISP domain name.

> Unless you are referring to the risk of an ISPs mail server itself 
becoming infected, 

It doesn't (not at all!) have to happen that way.

> ...you can mitigate this risk by ensuring that only authenticated users can 
send mail... 

No, because once their system becomes infected their machine can send spam using 
the user's valid "authentication".

That's a big reason why the whole SPF and "user authentication" approach simply 
is ill-conceived.  It doesn't solve the problem.

> ...and that authenticated users can only send mail with "from:" addresses 
matching their specific allowed addresses.

Likewise, that's completely ill-conceived.

First off, many users send "business" mail (or other mail using their 
personalized "vanity" domain names) through a differently-named (e.g. home) ISP.

Second, people travelling need to be able to deal with their E-mail (from their 
cruise ship Internet cafe, the business center in the hotel where they're 
staying, etc etc.) and it's stupid and a nonstarter to try to force them to not 
use their own E-mail address as the "From:" address.

Third, people sending mail from (for example) airport E-mail access kiosks have 
NO choice over which SMTP server will be used to send the mail messages.

Fourth, just making sure that the From: address domain corresponds to a mail 
server "authorized" to send mail for that domain name is hopelessly inadequate 
because major ISPs (swbell.net or whatever) could have literally MILLIONS of 
users and hundreds or thousands of "corresponding" mail servers... so ANYBODY 
sending through ANY of those could conceivably forge mails from ANY other 
customer connecting through that same ISP.

>> Therefore it allows eliminating the ugliness of "someday" and
> allows besieged recipients to get relief RIGHT AWAY.

> Your definition of "right away" and mine differ. 

Installing the software would result in an IMMEDIATE and SIGNIFICANT elimination 
(as seen by the installing recipient) of large classes of junk mails, including 
virtually all viruses and worms.  It would HUGELY improve the performance of 
their (perhaps existing) antispam content filter.

> Your solution still requires development...! 

Sure, I don't know of any solution that will write itself.

At least my solution CAN be written, doesn't break existing standards, and 
doesn't require worldwide consensus to be useful and effective.

> ...and cost incurred by promoting its adoption within 
our user base. 

That's the distribution issue I mentioned earlier.  Sure.  Software doesn't 
install itself (at least it SHOULD NOT, as a rule) and typically you WANT users 
to be (very) aware of the change to their incoming mail rules.

(If nothing else, you want them to KNOW what they've added so they'll RECOGNIZE 
AND APPRECIATE the difference once it's installed).

> It would be significantly sooner than waiting for 
adoption of all players in Internet mail to secure their mail servers 
and I look forward to seeing a mail client with this functionality.

I hope so.  I keep hounding my contacts in Microsoft... hopefully someday the 
message will get to someone in a position to do something about it.  But it's a 
big company, sigh.

>> Again, my approach offers MUCH greater nuance than that.  A trusted 
> friend who
> happens to be using a somewhat-flakey or sloppy ISP doesn't have to be
> penalized.  Your suggestion results in painting folks with too wide a 
> brush, which prevents effective filtering.

> I do not encourage sloppy or somewhat-flakey players in any space. 

Sure, but you may not have a lot of choice.  For example, in my area there are 
basically two 'reasonable' ways to get high-speed Internet connections to my 
home... DSL (invariably involving SBC... and I'm presently too far from their 
wiring center for DSL), or Comcast via cable connection.  The others are merely 
marketing subcontractors for those two, or else higher-priced 'commercial"-type 
suppliers.  In case you hadn't noticed, there's been a lot of consolidation in 
the field.  :-(

> Inconsistent mail service is a good reason to switch to a better 
network provider. I believe a more appropriate point would be that you 
do not wish to penalize your own subscribers by blocking legitimate 
mail received from friends on sloppy providers. 

The filtering needs to be COMPLETELY transparent to recipients so they can 
quickly go and see what has been quarantined.  The spam filters that one of my 
service providers used turned out to have SO many false positives (and thus 
quarantining a LOT of legitimate mail) that I finally (after fighting them for a 
while) just decided to turn theirs off completely and deal with the stuff here 
using my own tools and approaches.

[At least I *was* able to do that!]

> Unfortunately, not 
penalizing a subset of customers who receive mail from legitimate 
sources on sloppy providers often times penalizes are larger subset of 
customers who receive unsolicited mail from this same provider. 

That's why it's simply STUPID and ILL-CONCEIVED to make the decision based on 
where the mail (apparently) came from.  It's smarter to decide based on what the 
mail CONTAINS.

> And thus begins the magic juggling dance of blocking unsolicited mail while 
reducing false positives.

Again, there's nothing wrong with unsolicited mail.  I **want** unsolicited 
mail, as long as it's responsible... and even better if it's an inquiry from a 
potential new consulting client.  :-)

Meanwhile, there are a lot of types of incoming E-mails which contain content so 
clearly unwanted or egregious that I don't care if I *never* see it.

One example is any incoming E-mail message which contains (for example) a PIF 
attachment bigger than (say) 16K bytes.  I also don't need or want E-mails which 
contain obscured URLs in HTML links... those which (for example) store the 
entire server domain reference as a single huge integer, or which obscure the 
domain name by converting it to gratuitous hex references or some such.  
(Actually, I don't much care to EVER receive HTML-burdened E-mails, especially 
not on an unsolicited basis, but I realize that others are less upset about that 
wasteful stupidity than some of us folks are).

>> It leaves innocent victims who are punished by association.

> Encourage innocent victims to make better choices.

They may not have a lot of choices.

For another example, when you're traveling on business, how do you know what ISP 
is operating those airport Internet access kiosks?  Do you get to control who 
provides the service to your hotel's business center?

Sorry, but this "better choices" crap is simply unrealistic.

>> Fine.  Again, my approach allows a recipient to control what THEY 
> receive, and
> without leaving them in the frustrating position of "I wish someone 
> else would do <whatever>."

> This is akin to a thread I am currently participating in on NANOG. In 
cases where customers want to be in complete control of the traffic 
they receive, they should be willing and understand that this will be 
awarded at a higher price point and include maintaining their own mail 
infrastructure.

When the customer is accepting MORE of the burden of the processing, it's 
obnoxious for the ISP to try to charge them MORE for the privilege.

It's kind of like the cheap-ass ISPs who assign stupid miniscule 10Mb E-mail 
boxes and then bounce their customer's mail if their mailbox overflows, maybe 
just because they're off on a cruise or because their retrieval process bombed 
(power glitch at their home, maybe).  With disk space costing thirty to fifty 
cents a gigabyte, purchase price, and high-speed ISP service costing sixty to 
eighty dollars a month, it's ludicrous to force customers to undergo painful 
contortions because their ISP won't allow them to use (even on an exception 
basis) more than a penny's worth of hard disk space for mail storage.

I'd gladly set up my own mail infrastructure here (and in fact, I have it, 
except I can only use my own servers locally), other than that my cable 
connectivity provider won't let me set up my own servers and hook them to their 
service.

>> No, because the mail could be FULLY authenticated, if the victim's 
> machine has
> been infected by a spambot zombie.  That spambot could send E-mail 
> spams and worms using the REAL user's AUTHENTICATED permissions.

> Yes. Regardless of the content recognition you place on the receiving 
end, in this case you will receive some spam or have a higher rate of 
false positives.

No.

If a recipient has the (default) rule to not accept executable attachments from 
anybody (unless they're whitelisted, and most users simply in practice wouldn't 
whitelist anybody to send them executable content), then that should be 
basically 100% effective at blocking the E-mail transmission of viruses and 
worms.

I don't believe that it's NECESSARY to eliminate absolutely 100% of all spam 
messages.  I think it's probably enough to reduce the number of undetected 
incoming spam messages to a "very tolerable" level.

>> Even if they are, authenticated mail can still be fraudulent.

> Authenticated mail which does not match the finely grained controls, 
which could place undue burden on the sender to know those controls in 
advance, 

Oh, give me a break.

It's no big "burden" to expect a (especially first-time) sender to send plain 
ASCII text, and to not (abusively!) send HTML, attachments, or large E-mails to 
people unless they've previously contacted that recipient to confirm with that 
recipient that they consent to receive that kind of content, and from THAT 
sender.

It's simple courtesy.

> ...is going to be passed along in either case. When that happens, 
it is important to have authenticated sender schemes in place in order 
to respond to the appropriate party.

I don't think that "authenticated sender" schemes work for many folks, and in 
any case they CERTAINLY do not do much to eliminate or reduce spamming, or 
worms, or viruses.  Any spambot zombie can send "authenticated" spam.

"Authenticated sender" schemes are braindead, ill-conceived approaches which 
simply don't solve the problem.  Any time spent on promoting or installing them 
is probably time wasted that could better be spent on more productive 
directions.

>> It doesn't have to.  You only need to have individual recipients each 
> have a
> finite number of TRUSTED recipients (and the GREAT majority of senders 
> a given recipient receives mail from will NOT need to be whitelisted).

> Agreed. 

Finally.  :-)

> When you find a system like this which provides the finely 
grained control you want, pass it along. 

Again, I'd gladly write it if someone wants to fund the development, and help 
set up distribution for the finished product.  :-)  Send 'em my way.  (Drop by 
my Web site to see what other kinds of stuff I've already done... so this isn't 
a meaningless offer.)

> Mail clients have provided 
this for a long time in the form of accepting messages only from known 
senders. It doesn't have the finely grained control you desire, but it 
is an effective example. 

Bogus!!!  As you no doubt realize, the crude "accept messages only from known 
senders" simply isn't acceptable, so it gets disabled.  Please don't even try to 
equate a braindead and unusable approach which doesn't work, with a more nuanced 
and practical approach which WOULD.

> ...As in that case, I do not think it will prove effective in the long run as 
it requires too much interaction from the participant in spite of its high 
effectiveness rate.

How much interaction is required on the part of the recipient is a software 
design issue.  Good human-engineering can result in this being reduced to a VERY 
reasonable level.

Especially since the GREAT majority of legitimate E-mail, under my approach, 
would not require whitelisting (or other exceptional handling) at all.

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 asrg-bounces@ietf.org Fri Apr 29 23:53:46 2005
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1DRj34-00055j-D2; Fri, 29 Apr 2005 23:53:46 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1DRj33-00055e-Fs
	for asrg@megatron.ietf.org; Fri, 29 Apr 2005 23:53:45 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15983
	for <asrg@ietf.org>; Fri, 29 Apr 2005 23:53:42 -0400 (EDT)
Received: from mail2.panix.com ([166.84.1.73])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DRjGE-0007WG-Jr
	for asrg@ietf.org; Sat, 30 Apr 2005 00:07:23 -0400
Received: from panix5.panix.com (panix5.panix.com [166.84.1.5])
	by mail2.panix.com (Postfix) with ESMTP id D93A3A6FC1
	for <asrg@ietf.org>; Fri, 29 Apr 2005 23:53:38 -0400 (EDT)
Received: (from sethb@localhost)
	by panix5.panix.com (8.11.6p3/8.8.8/PanixN1.1) id j3U3qNQ05348;
	Fri, 29 Apr 2005 23:52:24 -0400 (EDT)
Date: Fri, 29 Apr 2005 23:52:24 -0400 (EDT)
Message-Id: <200504300352.j3U3qNQ05348@panix5.panix.com>
From: Seth Breidbart <sethb@panix.com>
To: asrg@ietf.org
In-reply-to: <200504300324.XAA14185@ietf.org> (gep2@terabites.com)
Subject: Re: [Asrg] Re: whitelisting
References: <200504300324.XAA14185@ietf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/asrg>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>,
	<mailto:asrg-request@ietf.org?subject=subscribe>
Sender: asrg-bounces@ietf.org
Errors-To: asrg-bounces@ietf.org

gep2@terabites.com wrote:

> "Unsolicited mail" is NOT automatically a bad thing... for example,
> if you're in the "customer relations" department for a consumer
> product manufacturer, the GREAT majority of what you're going to
> receive is from people you've never gotten E-mail from before.

That doesn't make it unsolicited.  If you asked for it (for instance,
you put on your web site "If you want to comment about our products,
send email to . . .") then it's solicited by definition.

Seth

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



