Slashdot Mirror
.mail Domain To Eliminate Spam?
steve.m writes "The BBC are reporting on a new batch of top level domain names being submitted to ICANN for approval. By far the most interesting proposal is for a .mail TLD to register legitimate mail servers. Could this eventually be the end of spam ?" *yawn* The same old discussion, with no implementation in sight.
well, if you use it to receive mail, your mail server is already identified by an MX record...
#!/usr/bin/english
Ok, so average user has his outlook express configured to a .mail service. His computer his hijacked by spyware and it's sending tons of spam using the .mail account settings found in outlook express. I don't see a solution, or am I pisssing the point?
Junk snail mail is not spam. Spam exists, precisely because the marginal cost of one more recipient is zero (or indistinguishable from zero). Whilst it is true that junk mail still exists it is considerably less of an issue than spam, not the least of which is because (a) the centralised server [insert your postal service of choice] will respect a "no junk mail" sign and (b) the services offered in the junk have to have legit contact details within jurisdiction for the cost to be even remotely effective, hence they can be drawn to account for unethical action.
"The first thing to do when you find yourself in a hole is stop digging."
This usually bites people on the rear when they're entering names into one of BIND's configuration files, you'll do something like:
and then find that www.example.com resolves to... www1.virtualhosting.example.net.example.com.So what you actually want is for a new TLD "/" to be created...
You are not alone. This is not normal. None of this is normal.
um, we have this cool tool called reverse DNS that allows us to confirm that the machine we are talking to does indeed have a legitimate entry under the DNS name they are purporting to send mail from.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
i don't like this form of validation. I have many business customers running mail servers using business DSL from various ISP's. These IPS's do not allow for custom reverse entries on their DNS servers.
This form of validation would cripple thousands of businesses.
Nope.
Here's the goddamned standard... Make it ultra-easy so it's simple to hit critical mass where everyone uses it.
Take a look at this: Sender Policy Framework.
There is even a wizard that walks you through the creation of the appropriate TXT records for your DNS zone file.
It appeared in a slashdot comment here
and its also at Cory Doctorow's site here.
My guess is that Cory wrote it.