IETF Logo Mail Archive

Re: Last Call: draft-klensin-rfc2821bis

SM <sm@resistor.net> Sat, 29 March 2008 16:42 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6B7B828C472; Sat, 29 Mar 2008 09:42:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.562
X-Spam-Level:
X-Spam-Status: No, score=-100.562 tagged_above=-999 required=5 tests=[AWL=-0.125, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WQEVzGhilLjW; Sat, 29 Mar 2008 09:42:18 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 811BB28C2DA; Sat, 29 Mar 2008 09:42:16 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D0F63A6F11 for <ietf@core3.amsl.com>; Sat, 29 Mar 2008 09:42:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 59vKM9FccdeS for <ietf@core3.amsl.com>; Sat, 29 Mar 2008 09:42:13 -0700 (PDT)
Received: from ns1.qubic.net (ns1.qubic.net [208.69.177.116]) by core3.amsl.com (Postfix) with ESMTP id 2674428C41A for <ietf@ietf.org>; Sat, 29 Mar 2008 09:41:46 -0700 (PDT)
Received: from subman.resistor.net ([10.0.0.1]) (authenticated bits=0) by ns1.qubic.net (8.14.3.Beta0/8.14.3.Beta0) with ESMTP id m2TGfCC0022233 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 29 Mar 2008 09:41:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1206808888; x=1206895288; bh=NFBjoAJAb+8aAfF0E4fRfYflFKXezEDRsX+O 4hVJ0aU=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To: References:Mime-Version:Content-Type; b=UzFAERYvi3ttIWvOjPhMfhw+RJ RUYDP/v4u42jgNKtsuB2uJRUB0/+ovfLAcPE9efep/HwQuzhHPIfSexO+bkSKyJ42FA rRRxUliJWZBO+DJOwo97Sl+Vu2ZheBNcr4KhWJfS0isBV375R8SL9ixMl5TxxNKxCTM uwM7o74fMZI=
DomainKey-Signature: a=rsa-sha1; s=mail; d=resistor.net; c=simple; q=dns; b=Wl63FtHUNy7fjtkDKa/d2Vr+jG2f0fiJeNAmV8QF2Q0ENJAlHhNIS5LsRlweH69Fi OTa2x1M1MyZad86hlkiDU/RObN9kvfBqE8D6vXGfZl9b8bhzxebx9vChjSWKHwbbS5Z FM/Sr29iMGhxfzv9pDymDbIplwycViclxI4b9iA=
Message-Id: <6.2.5.6.2.20080329090200.02c30030@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Sat, 29 Mar 2008 09:40:44 -0700
To: Henning Schulzrinne <hgs@cs.columbia.edu>
From: SM <sm@resistor.net>
Subject: Re: Last Call: draft-klensin-rfc2821bis
In-Reply-To: <53378CB3-DA0D-4421-9426-C3CB342360AF@cs.columbia.edu>
References: <47EA8CD8.3010500@network-heretics.com> <alpine.BSF.1.00.0803261436260.36932@simone.iecc.com> <11a101c88f75$96b63bd0$c422b370$@net> <47EAB7E3.4060308@dcrocker.net> <47EACFB4.5010100@cisco.com> <alpine.LRH.1.10.0803290926060.7344@netcore.fi> <9D58802557DBD059763C0316@p3.JCK.COM> <01MSZFLDOT0U000078@mauve.mrochek.com> <47EE499E.5090602@dcrocker.net> <47EE4F2A.8040801@network-heretics.com> <20080329143401.GB32033@mit.edu> <53378CB3-DA0D-4421-9426-C3CB342360AF@cs.columbia.edu>
Mime-Version: 1.0
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

At 08:10 29-03-2008, Henning Schulzrinne wrote:
>One of the problems I have seen first-hand is "disappearing" mail.
>Example: A webserver sends outbound email directly, but doesn't want
>to receive inbound email. The hostname leaks and mail gets sent to
>that address, based  on the A(AAA) record. The mail is "received", but
>disappears into some never-seen /var file. In that case, the sender
>never suspects that anything is amiss; it would be much better if the
>sender got an immediate "sorry, that domain name doesn't support email
>service" error.

I came across a few (IPv4) cases where mail and web services are 
hosted by different organizations.  The MX query failed and the SMTP 
client did a fallback to the A RR.  The mail was accepted by the host 
running the web service and it "disappeared".

The above can happen when sendmail is running on the web server and 
it automatically adds the domain to the list of domains for local 
delivery and there's a catchall address.

Regards,
-sm


_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email