[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic

To: IETF MARID WG <ietf-mxcomp@xxxxxxx>
Subject: Re: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic
From: "Anne P. Mitchell, Esq." <amitchell@xxxxxxxxx>
Date: Sat, 4 Sep 2004 02:26:06 -0700
List-archive: <http://www.imc.org/ietf-mxcomp/mail-archive/>
List-id: <ietf-mxcomp.imc.org>
List-unsubscribe: <mailto:ietf-mxcomp-request@imc.org?body=unsubscribe>
Sender: owner-ietf-mxcomp@xxxxxxxxxxxx

> There is a reason why NNTP has been replaced by the blogosphere.

And that reason is spam. Not bad protocol design.

And the the relative lack of a proficiency barrier to entry.

Anne

Follow-Ups:
- Re: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic
  - From: Dean Anderson

Prev by Date: RE: DEPLOY: Sender-ID provides little or no defence against adapt ive threats
Next by Date: Re: Unencumbered Checking (was Re: DEPLOY: SPF/Sender ID support in Courier)
Previous by thread: RE: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic
Next by thread: Re: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic
Index(es):
- Date
- Thread