From: "Keith Ivey" <[EMAIL PROTECTED]> > Note also that the fact that wildcards allow more than one additional > level is useful too. You can't stop people from adding "www." to > everything (hell, too many of them want to add it to their e-mail > addresses), so it's good to have www.atrios.blogspot.com work as well as > atrios.blogspot.com.
But do you NEED to do this in a way that would also allow such as spoo.lazy.simpleton.atrios.blogspot.com, as well? However, I suspect this is a shortcoming for DNS tools rather than pure operator laziness. In the specific case cited if blogspot.com does not declare a wildcard at the *.blogspot.com level then the declaration for atrios should also have the specific declaration for www.atrios..... Anything else seems to be a copout to laziness. That rant notwithstanding "it happens". I am curious to know if there is a GOOD reason for doing it other than laziness on somebody's part. Is there a security benefit? (Certainly any box using the DNS that was declared as "*." will not be able to send spam. This might be a "good" thing in some cases. Is there a material difference in the DNS server's CPU time for each lookup? This might be a good reason.) These will mitigate the score for any engine (organic or digital) that uses this as a BL basis. Such an engine could grow a specific cases whitelist as well. But absent the specific cases it's score would be pretty low. But there are some spams that come in skating really close to the 5 point barrier. For example 0.25 points would have guaranteed a spam tag on another multiple Subject line spam I received today from airmx.com. I don't know if they are wildcarded or not. I strongly suspect they are based on the message format. {^_^}