IETF Logo Mail Archive

Re: [domainrep] rDNS identifiers

Steve Allam <steve.allam@trustsphere.com> Thu, 19 July 2012 10:33 UTC

Return-Path: <steve.allam@trustsphere.com>
X-Original-To: domainrep@ietfa.amsl.com
Delivered-To: domainrep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B1B8021F867B for <domainrep@ietfa.amsl.com>; Thu, 19 Jul 2012 03:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.246
X-Spam-Level:
X-Spam-Status: No, score=-2.246 tagged_above=-999 required=5 tests=[AWL=0.353, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z9Neuv5p-D1C for <domainrep@ietfa.amsl.com>; Thu, 19 Jul 2012 03:33:42 -0700 (PDT)
Received: from OB2-RMV3.realmail-asp.co.uk (obgw2.realmail-asp.co.uk [80.249.107.83]) by ietfa.amsl.com (Postfix) with ESMTP id ACCD321F8539 for <domainrep@ietf.org>; Thu, 19 Jul 2012 03:33:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=trustsphere.com; s=rmdkim; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:References:Subject:To:MIME-Version:From:Date:Message-ID; bh=P8rJf1zPKVPhUPozrrzCUYAWYsQTndiz32GRgBgQ/9E=; b=HGTEmNykf88Giy4LNV7VP1a3beOEd7k9tceeOoks7fwGW8NzXJG5hAosBbciWJETb1cmKTRU6TD4NgpzvevIhVhh464I8V7p2Tr6sAgHqxAL4+XG9LzrXVlx1nHB+pE9sPV7q6sPyJWS1QivTdbIzhtVdjqVWkPn5BQm+LrJoM4=;
Received: from [116.12.149.130] (helo=cgpro.boxsentry.com) by OB2-RMV3.realmail-asp.co.uk with esmtp id 1Sro41-0002gj-IJ for domainrep@ietf.org; Thu, 19 Jul 2012 11:34:34 +0100
Received: by cgpro.boxsentry.com (CommuniGate Pro PIPE 5.4.0) with PIPE id 2042038; Thu, 19 Jul 2012 18:31:53 +0800
Received: from [88.97.130.81] (account steve.allam@trustsphere.com HELO [10.1.1.35]) by cgpro.boxsentry.com (CommuniGate Pro SMTP 5.4.0) with ESMTPSA id 2042034 for domainrep@ietf.org; Thu, 19 Jul 2012 18:31:45 +0800
Message-ID: <5007E299.9070503@trustsphere.com>
Date: Thu, 19 Jul 2012 11:34:01 +0100
From: Steve Allam <steve.allam@trustsphere.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: domainrep@ietf.org
References: <CAK+pC_-tOXvq1OSqiT6=vn+0UYGWpNogB9TQoy7vGbaQR-a+ag@mail.gmail.com> <20120718184236.GA18918@solar.andreasschulze.de>
In-Reply-To: <20120718184236.GA18918@solar.andreasschulze.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-LogiQ-query: 116.12.149.130/steve.allam@trustsphere.com/domainrep@ietf.org (error socket failure)
X-RealMail-Category: UNKNOWN/UNKNOWN/
X-RealMail-Ref: UNKNOWN/str=0001.0A0B020B.5007E2BA.0082,ss=1,re=0.000,fgs=0
X-RealMail-IWF: NO
X-CTCH-SenderID: steve.allam@trustsphere.com
X-CTCH-SenderID-Flags: 0
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-Total-Spam: 0
X-CTCH-SenderID-Total-Suspected: 0
Subject: Re: [domainrep] rDNS identifiers
X-BeenThere: domainrep@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Domain Reputation discussion list <domainrep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/domainrep>, <mailto:domainrep-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/domainrep>
List-Post: <mailto:domainrep@ietf.org>
List-Help: <mailto:domainrep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/domainrep>, <mailto:domainrep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 10:33:42 -0000

Are there any numbers on the take-up of MTX?

Regards,

Steve

On 18/07/2012 19:42, Andreas Schulze wrote:
> Am 29.06.2012 12:37 schrieb Jacob R Rideout:
>> Has anyone on the list considered the use of the IPv4 (or v6) PTR rDNS
>> value as an identifier? Or more strictly, a fully qualified domain name, that also
>> resolves to the queried IP address.
> Hi,
>
> MTX is (not very common) but much stricter.
> see http://www.chaosreigns.com/mtx/
>
> It's like a distributed selfmade whitelisting/reputation.
>
> Consider I have an IP-Address 192.0.2.1 assigned to my mailserver. I like to send mail.
> The receiver usually will reverse lookup that IP.
> 1.2.0.192.in-addr.arpa. PTR -> outbound-mailer.example.org.
> That's all.
>
> Next the receiver *may* doublecheck the name resolv too.
> I personaly don't expect that the name resolv to 192.0.2.1.
> If I would force that on my MX I would lose too much legit mail.
> So the doublecheck is not practical for most people. So normal "dnscheck" ends with "sender has any rDNS".
>
> But I as a sender could do more. I could state that I *do* have control over the dns zone
> my PTR points to. That's usual if I own ip space. It's unusual for a dialup.
>
> I can provide an A record 1.2.0.192.mtx.outbound-mailer.example.org. = 127.0.0.1
> If the receiver ask for that record he knows that
>   - I control the rdns zone
>   - I control the forward zone
>   - I really spend my time to setup such records.
> The receiver may notice my much greater interest that my mails are delivered.
>
> In fact that is a nice scheme to intoduce someone as a mailsender.
> without having reputation history.
> It definitly drops sender how do not control rDNS.
>
> It does not pervent abusers to setup such records. But that ips could be blocked.
> That's a decision every receiver could meet for himself. (or use a central blacklist)
>
> Andreas
> _______________________________________________
> domainrep mailing list
> domainrep@ietf.org
> https://www.ietf.org/mailman/listinfo/domainrep

v2.23.0 | Report a Bug | By Email