Abort data transfer?

David MacQuigg <macquigg@ece.arizona.edu> Sat, 17 October 2009 21:29 UTC

Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n9HLTsJf041922 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 17 Oct 2009 14:29:54 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n9HLTsQs041921; Sat, 17 Oct 2009 14:29:54 -0700 (MST) (envelope-from owner-ietf-smtp@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-smtp@mail.imc.org using -f
Received: from smtp103.prem.mail.sp1.yahoo.com (smtp103.prem.mail.sp1.yahoo.com [98.136.44.58]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n9HLTlN9041909 for <ietf-smtp@imc.org>; Sat, 17 Oct 2009 14:29:53 -0700 (MST) (envelope-from macquigg@ece.arizona.edu)
Received: (qmail 61514 invoked from network); 17 Oct 2009 21:29:46 -0000
Received: from (macquigg@69.9.25.232 with plain) by smtp103.prem.mail.sp1.yahoo.com with SMTP; 17 Oct 2009 14:29:46 -0700 PDT
X-Yahoo-SMTP: w0y7P.WswBDZ0jJGN667TA9o5a6IoN_2gYtT
X-YMail-OSG: .Nn1nX8VM1lhDw1.CvLSb.447f1H9kfmoSoV.QiervuqgeDAJttuX7fXKWNy6Uw9Gzwtbx1kUQkFZ0qRX9QZBOPbQenXANEMfngYU9_cA6_qpA7JCkdTww2KyBsfPmR8ZI_aF40s6sji2e33hCwM5xUlvS.FhU0T9w0NrI0j97nH9WM5zmcsAsdg4vEeJHh8LpYyOX0hYFjeSQOjzShzo7ShKa8CB3eYRGOUDGOnWODa_Y13yRtu7Mh7tsg0Il2K.48BhpD1qukTcVySii3LKsyDx.IM8uEQKgxWyiuiQtY1Hcxl4lKvM0.dr6CFuCvu05tyEHia
X-Yahoo-Newman-Property: ymail-3
Message-ID: <4ADA374A.90706@ece.arizona.edu>
Date: Sat, 17 Oct 2009 14:29:46 -0700
From: David MacQuigg <macquigg@ece.arizona.edu>
User-Agent: Thunderbird 2.0.0.23 (Macintosh/20090812)
MIME-Version: 1.0
To: IETF SMTP list <ietf-smtp@imc.org>
Subject: Abort data transfer?
References: <01N97HCA0JFM000078@mauve.mrochek.com> <20090522000539.11392.qmail@simone.iecc.com> <01N982F3TXPS00007A@mauve.mrochek.com> <alpine.BSF.2.00.0905221121360.13905@simone.home>
In-Reply-To: <alpine.BSF.2.00.0905221121360.13905@simone.home>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-smtp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-smtp/mail-archive/>
List-ID: <ietf-smtp.imc.org>
List-Unsubscribe: <mailto:ietf-smtp-request@imc.org?body=unsubscribe>

Is it permissible to abort data transfer before the end of data, say 
after you have received all headers, and you know the DKIM sig is bad?

RFC-5321 section 3.3 says:

   If the verb is initially accepted and the 354 reply issued, the DATA
   command should fail only if the mail transaction was incomplete (for
   example, no recipients), if resources were unavailable (including, of
   course, the server unexpectedly becoming unavailable), or if the
   server determines that the message should be rejected for policy or
   other reasons.

Failed DKIM would be a policy reason.

-- Dave

************************************************************     *
* David MacQuigg, PhD    email: macquigg at ece.arizona.edu   *  *
* Research Associate                phone: USA 520-721-4583   *  *  *
* ECE Department, University of Arizona                       *  *  *
*                                 9320 East Mikelyn Lane       * * *
* http://purl.net/macquigg        Tucson, Arizona 85710          *
************************************************************     *