Another viewpoint
---------- Forwarded Message ---------- Date: Monday, September 15, 2003 11:50:23 PM -0700 From: xxxxx To: [EMAIL PROTECTED], [EMAIL PROTECTED] Cc: Subject: RE: Verisign's wildcard in .com and .net
One of the side-effects is that any attempt to block email by checking that the sender's domain exists, will now fail.
Rather, all such checks will succeed (which renders the checks useless). Of course, such code could be modified to ignore responses that point at the nasty Verisign A record.
Another side-effect concerns mis-configured mail servers or DNS entries: if you are configuring a mail relay and/or put a typo in the MX record, you may get unexpected results since the IP address indicated by Verisign happens to be running an SMTP server.
I'll refrain from repeating the outraged comments on various discussion groups. It will be interesting to see how this situation evolves.
Mail authorization via DNS is going to accelerate, and with good reason.
---------- End Forwarded Message ----------
-- Daniel Monjar IS Manager, Technical Services bioM�rieux, Inc. Durham, NC US
pgp00000.pgp
Description: PGP signature
-- TriLUG mailing list : http://www.trilug.org/mailman/listinfo/trilug TriLUG Organizational FAQ : http://trilug.org/faq/ TriLUG Member Services FAQ : http://members.trilug.org/services_faq/ TriLUG PGP Keyring : http://trilug.org/~chrish/trilug.asc
