![]() Pendant: I seem to recall another RFC saying that domain names should make sense, like no-one would ever register unless it actually got populated with a web server ) FYI though, I don’t actually bounce the “regular” addresses, they just go directly into the spam folder (which I do manually skim). I have now added a non-obfuscated email address (well, some days ago) - interestingly neither of the two addresses has yet received any spam. I want to disprove that entity-encoding prevents spam, but if I get no spam, it can of course be for other reasons. I am not sure what the point of it is, though likely because the result looks more chaotic, it was believed that a script would have a harder time targeting the result of this specific encoding function.ĭouglas: Yes, you’re right. It has a 10% chance of leaving the character as raw. Jacob: The encoding to entities is automatically done by Markdown. from resellers or purchase agents, which are contacting me on behalf of someone else, and clearly not sending the email from a Mac ) ) ![]() Ole: Extending a little on the above, some of the subjects people use are also fooling a human, for example looking in my inbox I have one with a subject of just Next Round and another one showing Possible **VERY** devastating… If these were intermixed with spam emails, I am not sure I would open them, nor those which have an empty subject, or those which I open and they show a 7 pt Helvetica font (these are rare, but they come e.g. When you get 20+ emails/day, some of them using bad or empty subjects, some even in HTML, then filtering will result in false positives. which currently do not get any spam at all.Ĭhris Ryland: My problem with spam filters is false positives. I personally use tm-sales, tm-feedback, tm-support, etc. These will get spam, no matter how well you obfuscate them. Let me end this post with a general advice: when you start your business do not pick logical addresses such as sales, feedback, support, and similar. Add your suggestion as a comment to this entry, remember that formatting is Markdown, so indent your code by one tab or four spaces. The goal is to keep it as short as possible (since it will be inline). ![]() So any suggestions as to how the code should be would be appreciated. ![]() Though regardless of whether this address gets spam or not, I think the TextMate command to obfuscate an email address should (when called in an HTML context) insert a small JavaScript which use document.write or similar. This was from a Nigerian scammer, so perhaps it was manual, although none of my contact addresses have received such email. : And in response to this comment here is a non-obfuscated email address: The results are in: 286 emails received to the plain text address and just 1 received to the entity-encoded address. People occasionally ask how to modify the “Convert Selection to Entities” command to also convert ASCII so that they can use it as a simple email address obfuscation technique.īecause of that, we want to add an actual “Obfuscate Email Address” command, but how should it be done?Ī study from 2002 says that entity-encoding the email address is enough (conclusion 5) which I find rather hard to believe, which is actually the sole purpose of this post, I hereby give you one piece of entity-encoded email address: I will update this in a month or so, saying if it got any spam. ![]() Next post: Book About TextMate Announced Obfuscating Email Addresses ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |