spf-discuss
[Top] [All Lists]

RE: SenderID and v=spf1 - Please say NO

2004-10-16 09:14:28
The email address I use with this list is only for this list.
My email address now gets spam, so yes there are spammers on this list.
At least monitoring for email addresses.
If you post here, you will be added to someone's spam list.

Guy

-----Original Message-----
From: owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
[mailto:owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com] On Behalf Of 
jpinkerton
Sent: Saturday, October 16, 2004 2:54 AM
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: Re: [spf-discuss] SenderID and v=spf1 - Please say NO

LOL - Phillip - you never cease to amaze me :-)

I said *ages* ago that there were probably spammers on this mail-list - it
is public after all.  As to whether they contribute and try to manipulate
things - well they don't have to, do they?  M$ has been doing that through
Meng for some months now.

I see John Glube took you comments on the nose, whereas your mail was
actually in response to one I had posted, so I presume I was your target?  I
really don't mind you flaming me -  that's not what's mportant.  What *is*
important is that this mail-list is used for constructive critique of spf
and as a means to continue it's development and deployment.

Having said that - it is becoming obvious that a lot of people on this list
are forgetting one major thing.

SPF is all about designing the SPF records for use in authenticating mail
against domains.  Obviously spf people will be designing the receivers
software/milter/authentication as well, but that is *not* the exclusive
rights of SPF.  *Anyone* can use *any* record in a domain zonefile for any
purpose they like.  That is open source -- simple :-)

So perhaps we should forget M$, and their requests relayed through Meng to
accomodate one scope or another, and focus hard on the main job of producing
a SPF protocol which will do more than one hop.

I am told that this can be done by using Macros.

Are we developing that concept?

Are macros compatible with spfv=1?

Forget M$ guys, please just do the work.  There's been far too much time
spent blowing hot air about the politics and arguing with Meng/M$.  Just
stop doing it and it'll go away.  :-)

When there's a protocol available using macros on a RR type "SPF" - then we
can go to the world and they can decide what they want to use.  If Meng/M$
decide to use macros (or anything else) for PRA - that's their right. It's a
free world :-)


Slainte,

JohnP.
johnp(_at_)idimo(_dot_)com
ICQ 313355492


( Top posted for consistency with the original :-p  )



----- Original Message -----
From: "Hallam-Baker, Phillip" <pbaker(_at_)verisign(_dot_)com>
To: <spf-discuss(_at_)v2(_dot_)listbox(_dot_)com>
Sent: Friday, October 15, 2004 9:51 PM
Subject: RE: [spf-discuss] SenderID and v=spf1 - Please say NO


I think you all misunderstand Mengs motives here.

Microsoft could not have cared one way or the other. it was
Meng who convinced them to go this route.

Basically the SPF syntax simply specified the set of IP
addresses of the outgoing mail servers. Once that information
is out there anyone can make use of that information in any
way they please.

The spf=2 faction was a group of IETF blowhards who just
have to feel that they have done something important in
order to save the group from making a really serious error
they would regret - even when their proposal has absolutely
zero impact apart from making a lot of stuff that works
today stop working for no reason at all.


Your biggest problem here is not Microsoft, it is the spammers
and the people they pay to read these lists and stir up
trouble.

Before making kneejerk posts to the list take a few moments
to think about whether someone has been deliberately pushing
your buttons to make an issue out of something unimportant.
You won't see the people responsible on the lists, but I
have seen enough evidence that convinces me that they have
been at work making sure that every disagreement obtains the
widest possible readership.

This is one of the reasons I would never have choosen the IETF
as a venue voluntarily. A consensus process is always vulnerable
to a denial of service attack.



-----Original Message-----
From: owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
[mailto:owner-spf-discuss(_at_)v2(_dot_)listbox(_dot_)com]On Behalf Of 
jpinkerton
Sent: Friday, October 15, 2004 2:50 AM
To: spf-discuss(_at_)v2(_dot_)listbox(_dot_)com
Subject: Re: [spf-discuss] SenderID and v=spf1 - Please say NO


Meng,

There was an overwhelming oppposition shown on this list to idea
of allowing Microsoft to reuse v=spf1 records for Sender ID
checking.
Because there is a number of events upcoming in which
you're sceduled
to speak regarding SPF and where SenderID would also be mentioned,
I request that you give SPF community your word that you will not
be supporting reusing v=spf1 records for purposes other then what
is specified in the just published draft.


Here here !!

I've been trying to get Meng to state his position for some time now.




If you can not do this and will be speaking in support of reusing
v=spf1 records and in support of Sender ID, please let the
SPF community
know about it so we could decide on possibility of another spokesman
for the community to answer interviews and to provide SPF position
on different events in a way that would better represents consensus
or majority view seen on this list.


Exactly - and we will need to come up with a community policy
and press
release to hit the media with on the day of each meeting.



Slainte,


JohnP.
johnp(_at_)idimo(_dot_)com
ICQ 313355492

-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
http://www.InboxEvent.com/?s=d --- Inbox Event Nov 17-19 in
Atlanta features SPF and Sender ID.
To unsubscribe, change your address, or temporarily
deactivate your subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com


-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
http://www.InboxEvent.com/?s=d --- Inbox Event Nov 17-19 in Atlanta
features SPF and Sender ID.
To unsubscribe, change your address, or temporarily deactivate your
subscription,
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com

-------
Sender Policy Framework: http://spf.pobox.com/
Archives at http://archives.listbox.com/spf-discuss/current/
http://www.InboxEvent.com/?s=d --- Inbox Event Nov 17-19 in Atlanta features
SPF and Sender ID.
To unsubscribe, change your address, or temporarily deactivate your
subscription, 
please go to
http://v2.listbox.com/member/?listname=spf-discuss(_at_)v2(_dot_)listbox(_dot_)com