ICANN ICANN Email List Archives

[whois-comments]


<<< Chronological Index >>>    <<< Thread Index >>>

Who is or who is responsible

  • To: <whois-comments@xxxxxxxxx>
  • Subject: Who is or who is responsible
  • From: "David Wilson" <david_wilson@xxxxxxxxxxxx>
  • Date: Fri, 12 Jan 2007 13:08:13 -0600

The best place to eliminate spam is at the source. ISPs SEE the
thousands of spams coming from their SPAMing subscribers.  They have
always known who they are.  They know which subscribers are regular
folks who send a few dozen emails a day.  With knowledge of spammers at
the ISP, then go there to constrain it.

 

90% of people send 10% of the SMTP mail so look at their characteristics
and ALLOW those subscribers what they require.  Normal subscribers
woiuld never send more than 100 or a few hundred emails a day.
(doubtful)  Spammers send tens of thousands.

            In order to be allowed to send hundreds of emails one should
need to register as a business SMTP with a verified return address at
the same ISP.  (with monthly costs from the ISP).  Every ISP subscriber
would be limited to say 50 or 100 or 500 SMTP sends per day unless they
were a business SMTP.  This alone would cripple spam.

- ISPs collect more money to police their subscribers.

- Every SPAM sender is as easy to find as a geek at a tanning salon.

- Any ISP that does not comply should be listed so other ISPs can
discard thema t the firewall.

 

I hate regulation but the current thought on security is to design the
system around ALLOWING normal use characteristics rather than denying
MALuse.   Regular use behavior patterns would reguire no change.  If you
want to send thousands of EMAILS, then prove to us who you, have a
verified return address and pay extra for it.  If you do anything bad,
who did it is in black and white on the ISPs database.  It can all be
done on the ISP and they can charge for that privilege.

 

 

David Wilson

Business Critical Account Manager

CISSP

 

Office: 908.236.6554

Mobile: 908.310.1345

david_wilson@xxxxxxxxxxxx

 

JPEG image



<<< Chronological Index >>>    <<< Thread Index >>>

Privacy Policy | Terms of Service | Cookies Policy