At 05:42 PM 1/9/2004, Valdis.Kletnieks@xxxxxx wrote... >On Fri, 09 Jan 2004 15:13:50 EST, ietf@xxxxxxxxxxxxxxx (Mike S) said: >Note that MAPS is *NOT* blocking a single piece of e-mail itself. None. Zip. Zero. Of course not. MAPS is simply a database. As I quite clearly said, *USE* of MAPS impairs email. >Meanwhile, the site that's actually rejecting your mail has made that decision *itself*, >that it doesn't want to receive mail from you, possibly with MAPS as one component >of the information used to make said decision. > >To have a chance of winning this argument, you'll have to prove that the receiving >system is legally *obligated* to accept every piece of mail that you might happen to >want to send. MX <> recipient. If I send email foobar@xxxxxxx to the published MX for aol.com and aol.com blocks the ultimate recipient from receiving that email, they are in violation of the law, having interfered with the availability of email for both the sending and receiving systems. By publishing an MX, they have agreed to accept email for any valid address within their domain. That's what an MX is. They are likely in breach of their civil contract with the recipient, also. Of course, anyone who publishes an MX record but refuses mail is simply an idiot incapable of understanding why the Internet exists in the first place. The Balkanization has begun. The Internet is dead.
Any user of such services agree to a user agreement of use of the service, which includes the right for the service to filter e-mail, monitor content, and terminate the user account.
It is interesting to see that with the new US law, some people are trying to find justification within the IETF on why SPAM should be authorised. I would not be surprised if a few IETF members here be summoned to one of these new multi-million dollar case base on their comments...
Cheers
|
---- Franck Martin franck@xxxxxxxxx SOPAC, Fiji GPG Key fingerprint = 44A4 8AE4 392A 3B92 FDF9 D9C6 BE79 9E60 81D9 1320 "Toute connaissance est une reponse a une question" G.Bachelard |
Attachment:
signature.asc
Description: This is a digitally signed message part