菜单
  
    Primitive language analysis Primitive language analysis is the process of matching specific phrases of text to an email. The very first spam filters were quite primitive and were not really filters at all. Before real spam filters emerged, these primitive tools used a very simple approach to language analysis by simply scanning email for known senders in the message headers, multiple Usenet cross-postings (messages sent to a large number of different forums), or for phrases that were indicative of spam such as “Call Now!” and “Free Trial!” Between 1994 and 1997, there wasn’t much else the world could do about spam. The technology to fight it was too limited.39908
    In the early days of spam, before spammers learned many of the nasty tricks they use today , filters that cross-checked against lists of junk mail sender lists were somewhat effective only because it was possible to filter based on a known list of words and phrases which most of the world believed only existed in spam. Filtering based on a single word alone had a potential success rate of around 80 percent, with very little chance of catching legitimate messages.
    Most of these early spam-catching tools were home-brewed solutions. Some tools, such as procmail (a utility for mail processing), were used to create recipes to filter for certain basic words and phrases in incoming email. As new spams were being distributed on a daily basis, the word and phrase lists required continued maintenance. Many inpiduals found themselves with better things to do with their time, and so a few commercial solutions became popular during this period. These commercial solutions were sold in conjunction with a subscription nightly-update service to automatically download and apply new filtering phrases.
    This primitive approach to spam filtering became mainstream for a while. Early versions of some email clients such as Microsoft Outlook implemented simple junk mail sender lists that would check for known sender addresses in message headers. Although this approach had some weaknesses, it worked well enough up until it didn’t.
    One major weakness of primitive language filtering is that a single guilty phrase, such as the words “toll free,” could condemn an entire legitimate message to a user’s junk mailbox. The simplicity of these spam filters eventually led to a high false-positive rate. Although some of these guilty phrases applied to a majority of spam, they also began to apply to a small collection of legitimate mail. As a result, a user had to check their bit-bucket frequently to make sure that no legitimate messages were caught. It also became clear that there were some gray areas to spam filtering: As the phrase “one man’s spam is another man’s ham” (which grew out of this period) suggests, some messages (like a bulk invitation to a conference) might be considered wanted mail by some users and spam by others.
    One of the advantages of primitive filtering was that it was so simple to implement that users generally custom-tailored these filters to match their own email behavior. But this was also one of the biggest problems; it required a lot of maintenance in order to work properly. As spam began to grow, the lists of guilty words and phrases became longer and less manageable. The complexity of filtering spiked around 1997, when struggling spammers began to look for new ways to trick users into reading their emails. The new ways they found to change and obfuscate messages left most filters ineffective. Updating them took too much work, and primitive filters were effectively extinguished.
    A blacklisted network may appeal its blacklisting after taking care of the problem (namely tossing the spammer off their network), at which point it may be removed from the list at the maintainer’s discretion (and sometimes the maintainer’s mood). Blacklists allowed people to filter spam based on its origin rather than its contents. Subscribers no longer needed to maintain their own content-based filtering lists (although many did) and could instead rely on the blackhole to tell them what mail to filter.
  1. 上一篇:MongoDB数据库安全性英文文献和中文翻译
  2. 下一篇:路由信息协议Rip英文文献和中文翻译
  1. 利用BIM来分析施工安全风...

  2. 柴油机缸内润滑油消耗分...

  3. 干涉配合轴的应力分析英文文献和中文翻译

  4. 加压蛋壳分析英文文献和中文翻译

  5. 基卡气体管道PLEM结构的原...

  6. 极端波浪载荷实验船模的...

  7. 船舶设计中的消防安全性...

  8. g-C3N4光催化剂的制备和光催化性能研究

  9. NFC协议物理层的软件实现+文献综述

  10. 现代简约美式风格在室内家装中的运用

  11. 江苏省某高中学生体质现状的调查研究

  12. 中国传统元素在游戏角色...

  13. 浅析中国古代宗法制度

  14. 巴金《激流三部曲》高觉新的悲剧命运

  15. C++最短路径算法研究和程序设计

  16. 上市公司股权结构对经营绩效的影响研究

  17. 高警觉工作人群的元情绪...

  

About

优尔论文网手机版...

主页:http://www.youerw.com

关闭返回