From Randall's link:
Quote:
|
Among the other protections that spam blocking software employs, one method to block spam is by blocking messages that appear to be sent from non-existent domain names. This feature magically stopped working tonight, as there is no way for a domain name lookup to fail.
|
Verisign's white paper is kind of technical, but doesn't it say that it will take 15 minutes before they do their wild card processing? I don't know how anti-spam software is usually written, but I know that there is a Perl module used to get web pages and it times out by default after something like 3 minutes, and that default time is typically shortened. Is it really necessary for spam blockers to try to resolve an address for over 15 minutes per try?
Quote:
|
This response is dramatically different from what is called for in VeriSign's own Implementation documentation. Instead of returning a 550 error code for our example domain, the mail server continues with a positive, 250 OK response.
|
Sounds like VeriSign would be willing to fix that problem if it was brought to their attention (emphasis on
Sounds).
Quote:
"We assure you that the information we gather from you about your visit is in aggregate form and solely for the purposes of operating and improving the performance of our Site Finder."
To the contrary, there is no doubt in my mind that individually identifying information will be collected as part of an active monitoring and archival system, once again, as disclosed by VeriSign themselves in the Implementation document.
|
This refers to personal information passed through URL's, which doesn't happen when you're dealing with a reliable website/business. The danger of passing information through a URL deals with hackers and, if you're breaking the law, law enforcement, not Verisign.
Hybrid Mode
