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

"Jon Kyme" <jrk@merseymail.com> Tue, 20 May 2003 12:42 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 IAA10395 for <asrg-archive@odin.ietf.org>; Tue, 20 May 2003 08:42:12 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KCBcL28776 for asrg-archive@odin.ietf.org; Tue, 20 May 2003 08:11:38 -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 h4KCBcB28773 for <asrg-web-archive@optimus.ietf.org>; Tue, 20 May 2003 08:11:38 -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 IAA10362; Tue, 20 May 2003 08:41:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19I6So-0004dP-00; Tue, 20 May 2003 08:43:30 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19I6Sn-0004dM-00; Tue, 20 May 2003 08:43:29 -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 h4KC2PB27528; Tue, 20 May 2003 08:02:25 -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 h4KC1cB27489 for <asrg@optimus.ietf.org>; Tue, 20 May 2003 08:01:38 -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 IAA09716 for <asrg@ietf.org>; Tue, 20 May 2003 08:31:42 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19I6J8-0004Qh-00 for asrg@ietf.org; Tue, 20 May 2003 08:33:30 -0400
Received: from argon.connect.org.uk ([193.110.243.33]) by ietf-mx with esmtp (Exim 4.12) id 19I6J7-0004Qa-00 for asrg@ietf.org; Tue, 20 May 2003 08:33:29 -0400
Received: from mmail by argon.connect.org.uk with local (connectmail/exim) id 19I6KM-0004Ck-00; Tue, 20 May 2003 13:34:46 +0100
Subject: Re: [Asrg] Some data on the validity of MAIL FROM addresses
To: Dave Crocker <dcrocker@brandenburg.com>
From: Jon Kyme <jrk@merseymail.com>
Cc: ASRG <asrg@ietf.org>
X-Mailer: [ConnectMail 3.5.5]
X-connectmail-Originating-IP: 172.25.243.3
Message-Id: <E19I6KM-0004Ck-00@argon.connect.org.uk>
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Tue, 20 May 2003 13:34:46 +0100

>Folks, the email operations world has increasingly moved away from
>real-time processing of SMTP data.
>

A colleague has just drawn my attention to the relevant part of rfc2505
(BCP 30) - for completeness here it is:

<quote>
1.5. Where to block spam, in SMTP, in RFC822 or in the UA

   Our basic assumption is that refuse/accept is handled at the SMTP
   layer and that an MTA that decides to refuse a message should do so
   while still in the SMTP dialogue. First, this means that we do not
   have to store a copy of a message we later decide to refuse and
   second, our responsibility for that message is low or none - since we
   have not yet read it in, we leave it to the sender to handle the
   error.

</quote>

I apologise for not thinking to reference this in my initial reply to the
point you raised.










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