Re: [Asrg] Some data on the validity of MAIL FROM addresses

Michael Rubel <asrg@mikerubel.org> Tue, 20 May 2003 19:14 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26545 for <asrg-archive@odin.ietf.org>; Tue, 20 May 2003 15:14:24 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KIeoq26399 for asrg-archive@odin.ietf.org; Tue, 20 May 2003 14:40:50 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIeoB26396 for <asrg-web-archive@optimus.ietf.org>; Tue, 20 May 2003 14:40:50 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26495; Tue, 20 May 2003 15:13:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ICXK-0007m9-00; Tue, 20 May 2003 15:12:34 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ICXJ-0007m6-00; Tue, 20 May 2003 15:12:33 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIY2B25202; Tue, 20 May 2003 14:34:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KIXAB25160 for <asrg@optimus.ietf.org>; Tue, 20 May 2003 14:33:10 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA25626 for <asrg@ietf.org>; Tue, 20 May 2003 15:06:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ICPt-0007jA-00 for asrg@ietf.org; Tue, 20 May 2003 15:04:53 -0400
Received: from entropy.galcit.caltech.edu ([131.215.119.61]) by ietf-mx with esmtp (Exim 4.12) id 19ICPt-0007j7-00 for asrg@ietf.org; Tue, 20 May 2003 15:04:53 -0400
Received: from localhost (localhost [127.0.0.1]) by entropy.galcit.caltech.edu (Postfix) with ESMTP id DF32F5D7; Tue, 20 May 2003 15:05:55 -0400 (EDT)
From: Michael Rubel <asrg@mikerubel.org>
X-X-Sender: mrubel@entropy.galcit.caltech.edu
To: Yakov Shafranovich <research@solidmatrix.com>
Cc: asrg@ietf.org
Subject: Re: [Asrg] Some data on the validity of MAIL FROM addresses
In-Reply-To: <5.2.0.9.2.20030520134501.00b99fa0@std5.imagineis.com>
Message-ID: <Pine.LNX.4.44.0305201142590.1499-100000@entropy.galcit.caltech.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Tue, 20 May 2003 12:05:55 -0700

Yakov Shafranovich wrote:
> See RFC 2821, section 3.1.:
> 
> ---snip----
>     However, in practice, some servers do not perform recipient
>     verification until after the message text is received.  These servers
>     SHOULD treat a failure for one or more recipients as a "subsequent
>     failure" and return a mail message as discussed in section 6.
> ---snip----
> 
> Even thought it might be recommended to do processing in real-time, in 
> practice many systems do not and will not. We must be take that into account. 

I agree with Yakov, and would even go further.  I think smtp-session
reject is falling out of favor and will eventually disappear.

There are strong reasons to prefer accept-then-bounce or even filter to 
reject.

(1) Reject gives feedback about your system to would-be bad
    guys--including dictionary spammers--in a much faster and more 
    reliable way.  Sysadmins rightly want to give out as little 
    information as possible, because that's standard practice anywhere
    security is involved.

(2) Reject is a less flexible mechanism.  Accept-then-bounce or filter 
    allows recipients to work around certain obselete or overzealous
    systems.

(3) Senders have come to understand that messages get incorrectly
    filtered as spam sometimes; they no longer expect to recieve an
    immediate rejection if there is a problem delivering a message.

Like ident, smtp-reject has some usefulness inside private networks, but
one shouldn't expect to see it widely used on the public Internet.

Mike


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