Re: Fwd: [marf] I-D Action: draft-ietf-marf-spf-reporting-00.txt

Philip Gladstone <[email protected]>
Newsgroups gmane.mail.spam.spf.discuss
Message-ID <[email protected]>
You can do most of this today by careful choice of the elements in your 
SPF record.

My SPF record contains a logging entry that allows me to see who is 
sending mail for my domain. This, coupled with a 'stunt' DNS server 
allows me to create logs showing what is going on.

Yes, this proposal is more versatile, but I have to question the premise:

> There exist cases in which a domain name owner employing [SPF] for
>    announcing sending practises may want to know when messages are
>    received via unauthorized routing.  Currently there is no such
>    mechanism defined.

The last sentence isn't true -- I'm doing it today. However, I will 
admit that there are buggy implementations of SPF that don't get all the 
macro expansions correct! Adding a new mechanism is unlikely to help this.

My record is (currently):

v=spf1
ip4:140.177.205.131
a:mail.employees.org
ip6:2001:1868:4001:3a00:21:9bff:fefc:5ac9
-exists:%{i}.%{l1r-}.user.%{d}
ptr:zen.co.uk
a:charon.gladstonefamily.net
-exists:%{ir}.mrbl.%{d}
-exists:%{i}.3/86400.rate.%{d}
~all

Philip

p.s. Would people be interested in a web interface to look at their SPF 
drop statistics?


On 6/28/2011 9:46 AM, Scott Kitterman wrote:
> In the course of some other work I've been doing, I've started work on an
> extension to both SPF and the Messaging Abuse Reporting Format.  If you don't
> care about feedback reports you can mostly ignore this, but it does affect SPF
> in one more general way, it creates an IANA registry of known modifiers.
>
> This is part of the work of an established IETF working group, so I hope it
> can serve to solidify the status of SPF within the IETF (and yes, I still plan
> to work on a 4408bis to get it out of experimental).
>
> Please review and comment (either here or on the MARF list).
>
> Scott K
>
>
> ----------  Forwarded Message  ----------
>
> Subject: [marf] I-D Action: draft-ietf-marf-spf-reporting-00.txt
> Date: Tuesday, June 28, 2011, 09:35:07 AM
> From: [email protected]
> To: [email protected]
> CC: [email protected]
>
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Messaging Abuse Reporting Format
> Working Group of the IETF.
>
> 	Title           : SPF Authentication Failure Reporting using the Abuse
> Report Format
> 	Author(s)       : Scott Kitterman
> 	Filename        : draft-ietf-marf-spf-reporting-00.txt
> 	Pages           : 16
> 	Date            : 2011-06-28
>
>     This memo presents extensions to the Abuse Reporting Format (ARF),
>     and Sender Policy Framework (SPF) specifications to allow for
>     detailed reporting of message authentication failures in an on-demand
>     fashion.
>
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-marf-spf-reporting-00.txt
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
> This Internet-Draft can be retrieved at:
> ftp://ftp.ietf.org/internet-drafts/draft-ietf-marf-spf-reporting-00.txt
> _______________________________________________
> marf mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/marf
>
>
> -----------------------------------------
>
>
> -------------------------------------------
> Sender Policy Framework: http://www.openspf.org [http://www.openspf.org]
> Modify Your Subscription: http://www.listbox.com/member/ [http://www.listbox.com/member/]
>
> Archives: https://www.listbox.com/member/archive/735/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/735/835710-69e7d341
> Modify Your Subscription: https://www.listbox.com/member/?&
> Unsubscribe Now: https://www.listbox.com/unsubscribe/?&&post_id=20110628094640:0B9782BA-A18D-11E0-A020-B2A0DEACEFF0
> Powered by Listbox: http://www.listbox.com
>
>

-- 
Philip Gladstone
Ham: N1DQ
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.