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

ietf-mxcomp

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

2004-09-04 01:12:32


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/

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
RE: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic, Hallam-Baker, Phillip Re: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic, Arnt Gulbrandsen Re: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic, Koen Martens <= Re: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic, Sam Varshavchik Re: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic, Dean Anderson OT: Forgery on moderated lists, Alan DeKok

Previous by Date:	Re: Issues raised in comments by Steve Belovin from January 2004, Chris Haynes
Next by Date:	RE: Motion to abandon Sender ID, Dean Anderson
Previous by Thread:	Re: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic, Arnt Gulbrandsen
Next by Thread:	Re: DEPLOY: Rejection of Sender ID does not result in standardiza tion of SPF Classic, Sam Varshavchik
Indexes:	[Date] [Thread] [Top] [All Lists]