[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: "Hallam-Baker, Phillip" <pbaker@xxxxxxxxxxxx>
Subject: Re: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic
From: Koen Martens <gmc@xxxxxxxx>
Date: Sat, 4 Sep 2004 10:12:27 +0200
Cc: IETF MARID WG <ietf-mxcomp@xxxxxxx>
In-reply-to: <>
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>
References: <>
Sender: owner-ietf-mxcomp@xxxxxxxxxxxx
User-agent: Mutt/1.4.1i

On Fri, Sep 03, 2004 at 09:08:13PM -0700, Hallam-Baker, Phillip wrote:
> There is a reason why NNTP has been replaced by the blogosphere.

And that reason is spam. Not bad protocol design.

-- 
K.F.J. Martens, Sonologic, http://www.sonologic.nl/
Networking, embedded systems, unix expertise, artificial intelligence.
Public PGP key: http://www.metro.cx/pubkey-gmc.asc
Wondering about the funny attachment your mail program
can't read? Visit http://www.openpgp.org/

References:
- RE: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic
  - From: Hallam-Baker, Phillip

Prev by Date: Re: Issues raised in comments by Steve Belovin from January 2004
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
Index(es):
- Date
- Thread