Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym

2005-01-13 Thread Stephane Bortzmeyer
On Wed, Jan 12, 2005 at 10:59:43AM -0500, Steven Champeon <[EMAIL PROTECTED]> wrote a message of 98 lines which said: > 0) for the love of God, Montresor, just block port 25 outbound > already. If there is no escape / exemption (as proposed by William Leibzon), then, as a consumer, I scream "

Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym

2005-01-13 Thread Stephane Bortzmeyer
On Wed, Jan 12, 2005 at 10:59:43AM -0500, Steven Champeon <[EMAIL PROTECTED]> wrote a message of 98 lines which said: > 1) any legitimate mail source MUST have valid, functioning, > non-generic rDNS indicating that it is a mail server or > source. (Most do, many do not. There is NO reason why

Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym

2005-01-13 Thread Stephane Bortzmeyer
On Wed, Jan 12, 2005 at 10:59:43AM -0500, Steven Champeon <[EMAIL PROTECTED]> wrote a message of 98 lines which said: > 4) all domains with invalid whois data MUST be deactivated (not > confiscated, just temporarily removed from the root dbs) immediately > and their owners contacted. Because

Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym

2005-01-13 Thread Rich Kulawiec
On Thu, Jan 13, 2005 at 12:26:47PM +0100, Stephane Bortzmeyer wrote: > > 4) all domains with invalid whois data MUST be deactivated (not > > confiscated, just temporarily removed from the root dbs) immediately > > and their owners contacted. > > Because there is no data protection on many databas

Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym

2005-01-13 Thread Valdis . Kletnieks
On Thu, 13 Jan 2005 12:21:04 +0100, Stephane Bortzmeyer said: > American bias but remember the Internet is worldwide. I do not know > how it is in the USA but there are many parts of the world where ISP > do not have a delegation of in-addr.arpa and therefore cannot pass it > to their customers. (

Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym

2005-01-13 Thread Steven Champeon
on Thu, Jan 13, 2005 at 12:21:04PM +0100, Stephane Bortzmeyer wrote: > > On Wed, Jan 12, 2005 at 10:59:43AM -0500, > Steven Champeon <[EMAIL PROTECTED]> wrote > a message of 98 lines which said: > > > 1) any legitimate mail source MUST have valid, functioning, > > non-generic rDNS indicating

Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym

2005-01-13 Thread Owen DeLong
Requesting rDNS means "I don't want to receive email from Africa". Having an rDNS entry for a host doesn't mean you know if it is/isn't in Africa, to any higher degree of certainty than when you just had the IP address. What he was pointing out her is that a majority of African ISPs do not even hav

Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym

2005-01-13 Thread Valdis . Kletnieks
On Thu, 13 Jan 2005 11:35:23 PST, Owen DeLong said: > >> Requesting rDNS means "I don't want to receive email from Africa". > > > > Having an rDNS entry for a host doesn't mean you know if it is/isn't in > > Africa, to any higher degree of certainty than when you just had the IP > > address. > >

Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym

2005-01-14 Thread Eric Brunner-Williams in Portland Maine
> Because there is no data protection on many databases (such as ".com" > registrars who are forced to sell the data if requested), people lie > when registering, because it is the only tool they have to protect > their privacy. Yup. Our ICANN contracts both require us to sell bulk registrant dat

Re: fixing insecure email infrastructure (was: Re: [eweek article] Window of "anonym

2005-01-14 Thread Eric Brunner-Williams in Portland Maine
> The current pretense of "privacy" is nothing more than a convenient > mechanism for registrars to pad their wallets and evade responsible > for facilitating abuse. As an aside, I used a (wicked big) competitor's "privacy" service to regsiter a domain for a political worker who wanted to whistle