534:– Several SMTP commands are allowed to be placed in one network packet and "pipelined". For example, if an email is sent with a CC: header, several SMTP "RCPT TO" commands might be placed in a single packet instead of one packet per "RCPT TO" command. The SMTP protocol, however, requires that errors be checked and everything is synchronized at certain points. Many spammers will send everything in a single packet since they do not care about errors and it is more efficient. Some MTAs will detect this invalid pipelining and reject email sent this way.
43:
858:
facility. Depending on the server and internet speed, a tarpit can slow an attack by a factor of around 500. Many systems will simply disconnect if the server doesn't respond quickly, which will eliminate the spam. However, a few legitimate email systems will also not deal correctly with these delays. The fundamental idea is to slow the attack so that the perpetrator has to waste time without any significant success.
585:, Policyd-weight and others use some or all of the various tests for spam, and assign a numerical score to each test. Each message is scanned for these patterns, and the applicable scores tallied up. If the total is above a fixed value, the message is rejected or flagged as spam. By ensuring that no single spam test by itself can flag a message as spam, the false positive rate can be greatly reduced.
966:'s ezmlm) support "confirmed opt-in" by default. Whenever an email address is presented for subscription to the list, the software will send a confirmation message to that address. The confirmation message contains no advertising content, so it is not construed to be spam itself, and the address is not added to the live mail list unless the recipient responds to the confirmation message.
555:– An SMTP connection should always be closed with a QUIT command. Many spammers skip this step because their spam has already been sent and taking the time to properly close the connection takes time and bandwidth. Some MTAs are capable of detecting whether or not the connection is closed correctly and use this as a measure of how trustworthy the other system is.
1101:
an email address. The SMTP server must check if the email address in the FROM field of an outgoing message is the same address that belongs to the user's credentials, supplied for SMTP authentication. If the FROM field is forged, an SMTP error will be returned to the email client (e.g. "You do not own the email address you are trying to send from").
1100:
Both malicious software and human spam senders often use forged FROM addresses when sending spam messages. Control may be enforced on SMTP servers to ensure senders can only use their correct email address in the FROM field of outgoing messages. In an email users database each user has a record with
497:
protocol allows for temporary rejection of incoming messages. Greylisting temporarily rejects all messages from unknown senders or mail servers – using the standard 4xx error codes. All compliant MTAs will proceed to retry delivery later, but many spammers and spambots will not. The downside is that
1371:
We do not tolerate the transmission of spam. We monitor all traffic to and from our web servers for indications of spamming and maintain a spam abuse complaint center to register allegations of spam abuse. Customers suspected to be using our products and services for the purpose of sending spam are
310:
There are now a large number of applications, appliances, services, and software systems that email administrators can use to reduce the load of spam on their systems and mailboxes. In general these attempt to reject (or "block"), the majority of spam email outright at the SMTP connection stage. If
270:
Systems that use "ham passwords" ask unrecognised senders to include in their email a password that demonstrates that the email message is a "ham" (not spam) message. Typically the email address and ham password would be described on a web page, and the ham password would be included in the subject
257:
email address — an address which the user can disable or abandon which forwards email to a real account. A number of services provide disposable address forwarding. Addresses can be manually disabled, can expire after a given time interval, or can expire after a certain number of messages have been
178:
to prevent it from being automatically collected in this way, but still allow a human reader to reconstruct the original: an email address such as, "no-one@example.com", might be written as "no-one at example dot com", for instance. A related technique is to display all or part of the email address
191:
A common piece of advice is to not to reply to spam messages as spammers may simply regard responses as confirmation that an email address is valid. Similarly, many spam messages contain web links or addresses which the user is directed to follow to be removed from the spammer's mailing list – and
861:
An organization can successfully deploy a tarpit if it is able to define the range of addresses, protocols, and ports for deception. The process involves a router passing the supported traffic to the appropriate server while those sent by other contacts are sent to the tarpit. Examples of tarpits
654:
To check the domain names in the rDNS to see if they are likely from dial-up users, dynamically assigned addresses, or home-based broadband customers. Since the vast majority of email that originates from these computers is spam, many mail servers also refuse email with missing or "generic" rDNS
393:
which collects the checksums of messages that email recipients consider to be spam (some people have a button on their email client which they can click to nominate a message as being spam); if the checksum is in the database, the message is likely to be spam. To avoid being detected in this way,
772:
As an example, if the email address "spamtrap@example.org" is placed in the source HTML of a web site in a way that it isn't displayed on the web page, human visitors to the website would not see it. Spammers, on the other hand, use web page scrapers and bots to harvest email addresses from HTML
200:
Businesses and individuals sometimes avoid publicising an email address by asking for contact to come via a "contact form" on a webpage – which then typically forwards the information via email. Such forms, however, are sometimes inconvenient to users, as they are not able to use their preferred
1200:
Artificial intelligence techniques can be deployed for filtering spam emails, such as artificial neural networks algorithms and
Bayesian filters. These methods use probabilistic methods to train the networks, such as examination of the concentration or frequency of words seen in the spam versus
740:
as his sender's address. If the receiving MTA tries to make the callback using the trap address in a MAIL FROM command, the receiving MTA's IP address will be blacklisted; (3) Finally, the standard VRFY and EXPN commands used to verify an address have been so exploited by spammers that few mail
569:
Another approach is simply creating an imitation MTA that gives the appearance of being an open mail relay, or an imitation TCP/IP proxy server that gives the appearance of being an open proxy. Spammers who probe systems for open relays and proxies will find such a host and attempt to send mail
408:
Some email servers expect to never communicate with particular countries from which they receive a great deal of spam. Therefore, they use country-based filtering – a technique that blocks email from certain countries. This technique is based on country of origin determined by the sender's IP
728:
Since a large percentage of spam has forged and invalid sender ("from") addresses, some spam can be detected by checking that this "from" address is valid. A mail server can try to verify the sender address by making an SMTP connection back to the mail exchanger for the address, as if it were
658:
A Forward
Confirmed reverse DNS verification can create a form of authentication that there is a valid relationship between the owner of a domain name and the owner of the network that has been given an IP address. While reliant on the DNS infrastructure, which has known vulnerabilities, this
548:
technique is simply the adding of an MX record pointing to a non-existent server as the "primary" (i.e. that with the lowest preference value) – which means that an initial mail contact will always fail. Many spam sources do not retry on failure, so the spammer will move on to the next victim;
857:
is any server software which intentionally responds extremely slowly to client commands. By running a tarpit which treats acceptable mail normally and known spam slowly or which appears to be an open mail relay, a site can slow down the rate at which spammers can inject messages into the mail
139:
Sharing an email address only among a limited group of correspondents is one way to limit the chance that the address will be "harvested" and targeted by spam. Similarly, when forwarding messages to a number of recipients who don't know one another, recipient addresses can be put in the
980:
Email senders typically now do the same type of anti-spam checks on email coming from their users and customers as for inward email coming from the rest of the
Internet. This protects their reputation, which could otherwise be harmed in the case of infection by spam-sending malware.
512:
says that an SMTP server "MAY verify that the domain name argument in the EHLO command actually corresponds to the IP address of the client. However, if the verification fails, the server MUST NOT refuse to accept a message on that basis." Systems can, however, be configured to
483:– A sending server is required to wait until it has received the SMTP greeting banner before it sends any data. A deliberate pause can be introduced by receiving servers to allow them to detect and deny any spam-sending applications that do not wait to receive this banner.
204:
In some cases contact forms also send the message to the email address given by the user. This allows the contact form to be used for sending spam, which may incur email deliverability problems from the site once the spam is reported and the sending IP is blacklisted.
122:
Anti-spam techniques can be broken into four broad categories: those that require actions by individuals, those that can be automated by email administrators, those that can be automated by email senders and those employed by researchers and law enforcement officials.
799:
needs, and as long as users consistently mark/tag the emails, can respond quickly to changes in spam content. Statistical filters typically also look at message headers, considering not just the content but also peculiarities of the transport mechanism of the email.
909:
There are a variety of techniques that email senders use to try to make sure that they do not send spam. Failure to control the amount of spam sent, as judged by email receivers, can often cause even legitimate email to be blocked and for the sender to be put on
1187:
Since spamming is facilitated by the fact that large volumes of email are very inexpensive to send, one proposed set of solutions would require that senders pay some cost in order to send email, making it prohibitively expensive for spammers. Anti-spam activist
427:
which allow a mail server to quickly look up the IP of an incoming mail connection - and reject it if it is listed there. Administrators can choose from scores of DNSBLs, each of which reflects different policies: some list sites known to emit spam; others list
372:
A method which may be used by internet service providers, by specialized services or enterprises to combat spam is to require unknown senders to pass various tests before their messages are delivered. These strategies are termed "challenge/response systems".
570:
through it, wasting their time and resources, and potentially, revealing information about themselves and the origin of the spam they are sending to the entity that operates the honeypot. Such a system may simply discard the spam attempts, submit them to
294:
and
Network Abuse Clearinghouse to assist, they are not always accurate. Historically, reporting spam in this way has not played a large part in abating spam, since the spammers simply move their operation to another URL, ISP or network of IP addresses.
922:
Since spammer's accounts are frequently disabled due to violations of abuse policies, they are constantly trying to create new accounts. Due to the damage done to an ISP's reputation when it is the source of spam, many ISPs and web email providers use
289:
Tracking down a spammer's ISP and reporting the offense can lead to the spammer's service being terminated and criminal prosecution. Unfortunately, it can be difficult to track down the spammer, and while there are some online tools such as
238:
or attacks upon security vulnerabilities in the HTML renderer. Mail clients which do not automatically download and display HTML, images or attachments have fewer risks, as do clients who have been configured to not display these by default.
593:
Outbound spam protection involves scanning email traffic as it exits a network, identifying spam messages and then taking an action such as blocking the message or shutting off the source of the traffic. While the primary impact of
694:
disallowed in mail messages. Thus, if a site receives spam advertising "herbal Viagra", the administrator might place this phrase in the filter configuration. The mail server would then reject any message containing the phrase.
601:
Outbound spam protection not only stops spam, but also lets system administrators track down spam sources on their network and remediate them – for example, clearing malware from machines which have become infected with a
1030:
or send email. This practice is somewhat controversial when ISPs block home users, especially if the ISPs do not allow the blocking to be turned off upon request. Email can still be sent from these computers to designated
337:
A number of systems have been developed that allow domain name owners to identify email as authorized. Many of these systems use the DNS to list sites authorized to send email on their behalf. After many other proposals,
446:
Most spam/phishing messages contain an URL that they entice victims into clicking on. Thus, a popular technique since the early 2000s consists of extracting URLs from messages and looking them up in databases such as
1003:. For this reason it is generally preferable for most rejection of incoming email to happen during the SMTP connection stage, with a 5xx error code, while the sending server is still connected. In this case then the
384:
exploits the fact that the messages are sent in bulk, that is that they will be identical with small variations. Checksum-based filters strip out everything that might vary between messages, reduce what remains to a
1070:. By limiting the rate that email can be sent around what is typical for the computer in question, legitimate email can still be sent, but large spam runs can be slowed down until manual investigation can be done.
192:
these should be treated as dangerous. In any case, sender addresses are often forged in spam messages, so that responding to spam may result in failed deliveries – or may reach completely innocent third parties.
1092:'s feedback loop, and Network Abuse Clearinghouse, the domain's abuse@ mailbox, etc., ISPs can often learn of problems before they seriously damage the ISP's reputation and have their mail servers blacklisted.
201:
email client, risk entering a faulty reply address, and are typically not notified about delivery problems. Further, contact forms have the drawback that they require a website with the appropriate technology.
927:
on new accounts to verify that it is a real human registering the account, and not an automated spamming system. They can also verify that credit cards are not stolen before accepting new customers, check
230:
Avoiding or disabling this feature does not help avoid spam. It may, however, be useful to avoid some problems if a user opens a spam message: offensive images, obfuscated hyperlinks, being tracked by
999:
back to the supposed sender. However, if (as is often the case with spam), the sender information on the incoming email was forged to be that of an unrelated third party then this bounce message is
769:
Spamtrapping is the seeding of an email address so that spammers can find it, but normal users can not. If the email address is used then the sender must be a spammer and they are black listed.
702:
fields in the header in order to hide their identity, or to try to make the email look more legitimate than it is, many of these spoofing methods can be detected, and any violation of, e.g.,
1046:
can be used to intercept all port 25 (SMTP) traffic and direct it to a mail server that enforces rate limiting and egress spam filtering. This is commonly done in hotels, but it can cause
253:
An email user may sometimes need to give an address to a site without complete assurance that the site owner will not use it for sending spam. One way to mitigate the risk is to provide a
1143:
can have a significant impact on spamming activity. Where legislation provides specific text that bulk emailers must include, this also makes "legitimate" bulk email easier to identify.
773:
source code - so they would find this address. When the spammer later sends to the address the spamtrap knows this is highly likely to be a spammer and can take appropriate action.
469:
Many spammers use poorly written software or are unable to comply with the standards because they do not have legitimate control of the computer they are using to send spam (
1812:
598:
is on spam recipients, sending networks also experience financial costs, such as wasted bandwidth, and the risk of having their IP addresses blocked by receiving networks.
1631:
131:
There are a number of techniques that individuals can use to restrict the availability of their email addresses, with the goal of reducing their chance of receiving spam.
755:
SMTP proxies allow combating spam in real time, combining sender's behavior controls, providing legitimate users immediate feedback, eliminating a need for quarantine.
698:
Header filtering looks at the header of the email which contains information about the origin, destination and content of the message. Although spammers will often
477:
will accept, a mail administrator can reduce spam significantly - but this also runs the risk of rejecting mail from older or poorly written or configured servers.
995:
If a receiving server initially fully accepts an email, and only later determines that the message is spam or to a non-existent recipient, it will generate a
1459:
895:
If a recipient periodically checks his spam folder, that will cost him time and if there is a lot of spam it is easy to overlook the few legitimate messages.
1587:
1051:
2004:
950:— to harass them, or to make the company or organisation appear to be spamming. To prevent this, all modern mailing list management programs (such as
275:" technique). Ham passwords are often combined with filtering systems which let through only those messages that have identified themselves as "ham".
1146:
Increasingly, anti-spam efforts have led to co-ordination between law enforcement, researchers, major consumer financial service companies and
116:
1773:
1499:
1209:
Channel email is a new proposal for sending email that attempts to distribute anti-spam activities by forcing verification (probably using
464:
17:
311:
they do accept a message, they will typically then analyze the content further – and may decide to "quarantine" any categorised as spam.
1358:
1876:
1332:
1275:
1601:
1802:
1121:(TOS) agreement that discourages spammers from using their system and allows the spammer to be terminated quickly for violations.
643:
Some email mail transfer agents will perform FCrDNS verification on the domain name given in the SMTP HELO and EHLO commands. See
808:
1623:
1372:
fully investigated. If we determine there is a problem with spam, we will take the appropriate action to resolve the situation.
787:
Statistical, or
Bayesian, filtering once set up requires no administrative maintenance per se: instead, users mark messages as
549:
legitimate email servers should retry the next higher numbered MX, and normal email will be delivered with only a brief delay.
2022:
1420:
1393:
574:, or store them for analysis by the entity operating the honeypot that may enable identification of the spammer for blocking.
298:
In many countries consumers may also report unwanted and deceptive commercial email to the authorities, e.g. in the US to the
2222:
1979:
1921:
1439:
736:, nearly all callbacks are to innocent third party mail servers that are unrelated to the spam; (2) When the spammer uses a
350:
are all now widely supported with growing adoption. While not directly attacking spam, these systems make it much harder to
258:
forwarded. Disposable email addresses can be used by users to track whether a site owner has disclosed an address, or had a
53:
2262:
1973:
900:
Measures that imposes costs on a third party server may be considered to be abuse and result in deliverability problems.
2237:
2050:
1939:
1473:
741:
administrators enable them, leaving the receiving SMTP server no effective way to validate the sender's email address.
390:
1734:
1709:
1681:
1654:
1313:
1130:
367:
1828:
1294:
1750:
1536:
1560:
1136:
1855:
1456:
637:
623:
1989:
Historical
Development of Spam Fighting in Relation to Threat of Computer-Aware Criminals, and Public Safety
1577:
2217:
2099:
1671:
1182:
640:(FCrDNS) verification and if there is a valid domain name, put it into the "Received:" trace header field.
1043:
885:
When a mail server rejects legitimate messages, the sender needs to contact the recipient out of channel.
1135:
From 2000 onwards, many countries enacted specific legislation to criminalize spamming, and appropriate
2257:
1964:
1225:
1147:
171:
1244:
2232:
2129:
2094:
1958:
1948:
1530:
714:, standards on how the header is to be formed can also serve as a basis for rejecting the message.
299:
248:
31:
1770:
782:
339:
324:
1988:
1905:
1897:
2067:
2043:
1350:
60:
1114:
1079:
1015:
723:
517:
Refuse connections from hosts that give an invalid HELO – for example, a HELO that is not an
271:
line of an email message (or appended to the "username" part of the email address using the "
1165:
by a given piece of spam can often be followed up with domain registrars with good results.
890:
When legitimate messages are relegated to a spam folder, the sender is not notified of this.
119:) – and the associated costs in time, effort, and cost of wrongfully obstructing good mail.
2272:
2242:
2019:, and other countries' laws and pending legislation regarding unsolicited commercial email.
1582:
1272:
959:
929:
816:
564:
448:
320:
1880:
1329:
272:
8:
2247:
2089:
1027:
1000:
990:
848:
828:
633:
490:
474:
400:
into the middle of each of their messages, to make each message have a unique checksum.
2418:
1019:
871:
691:
619:
144:" so that each recipient does not get a list of the other recipients' email addresses.
1789:
628:
The PTR DNS records in the reverse DNS can be used for a number of things, including:
540:– The email servers for any given domain are specified in a prioritized list, via the
64:
2413:
2227:
2170:
2036:
1917:
1730:
1705:
1677:
1650:
664:
595:
498:
all legitimate messages from first-time senders will experience a delay in delivery.
141:
2028:
1417:
795:
and the filtering software learns from these judgements. Thus, it is matched to the
2368:
2315:
1992:
1909:
1884:
1436:
1385:
1118:
975:
820:
732:
Callback verification has various drawbacks: (1) Since nearly all spam has forged
703:
505:
2380:
2350:
2084:
1940:
AOL's postmaster page describing the Anti-Spam
Technical Alliance (ASTA) Proposal
1913:
1832:
1777:
1564:
1443:
1424:
1336:
1317:
1298:
1279:
1192:
attempts to make spamming less profitable by bringing lawsuits against spammers.
1067:
699:
685:
672:
470:
429:
153:
1026:
traffic (TCP port 25) from machines on the network that are not supposed to run
711:
707:
509:
2390:
2360:
2310:
2252:
2175:
2165:
2109:
2016:
1213:
so back-scatter does not occur) when the first email is sent for new contacts.
1210:
1151:
996:
733:
603:
351:
284:
175:
112:
1976:– what to send, how to send it, where to send it – and what not to send or do.
2407:
2325:
2290:
2190:
2124:
2012:
1807:
1645:
Leonard, Clifton; Svidergol, Brian; Wright, Byron; Meloski, Vladimir (2016).
1189:
1162:
1047:
876:
Measures to protect against spam can cause collateral damage. This includes:
259:
30:"Spam blacklist" redirects here. For Knowledge's spam control mechanism, see
1982:
E-Mail
Spamming countermeasures: Detection and prevention of E-Mail spamming
1500:"Australian government lags UK in deploying DMARC email spoofing prevention"
1140:
690:
Content filtering techniques rely on the specification of lists of words or
179:
as an image, or as jumbled text with the order of characters restored using
2373:
2330:
2300:
2150:
947:
941:
836:
582:
473:). By setting tighter limits on the deviation from RFC standards that the
1310:
880:
The measures may consume resources, both in the server and on the network.
2335:
2145:
1898:"Spam Mail Detection Using Artificial Neural Network and Bayesian Filter"
1521:
951:
527:
Refusing to accept email whose HELO/EHLO argument does not resolve in DNS
396:
220:
1825:
1291:
1066:
Machines that suddenly start sending lots of email may well have become
1035:
via port 25 and to other smart hosts via the email submission port 587.
441:
2305:
2282:
2155:
2114:
2076:
1525:
1032:
862:
include the Labrea tarpit, Honeyd, SMTP tarpits, and IP-level tarpits.
832:
804:
750:
423:
There are large number of free and commercial DNS-based
Blacklists, or
235:
214:
167:
101:
1998:
1519:
1406:
Canada's anti-spam legislation (CASL) is in place to protect
Canadians
524:
Refusing connections from hosts that give an obviously fraudulent HELO
107:
No technique is a complete solution to the spam problem, and each has
2340:
2320:
2195:
1557:
1055:
946:
A malicious person can easily attempt to subscribe another user to a
812:
660:
545:
541:
108:
2005:
Mail DDoS Attacks through Mail Non Delivery Messages and Backscatter
1845:
2385:
2295:
2180:
2160:
2059:
1944:
1173:
Several approaches have been proposed to improve the email system.
1155:
955:
764:
668:
394:
spammers will sometimes insert unique invisible gibberish known as
386:
355:
2267:
2185:
2119:
1110:
1085:
924:
824:
291:
231:
159:
1902:
Intelligent Data Engineering and Automated Learning – IDEAL 2004
1702:
Introduction to Information Security: A Strategic-Based Approach
1602:"VRFY command—Verify whether a mailbox exists on the local host"
1245:"10 Tips to Avoid Spam | Digital Security Guide | Safeonline.ng"
1221:
Spam is the subject of several research conferences, including:
305:
1850:
917:
803:
Software programs that implement statistical filtering include
729:
creating a bounce, but stopping just before any email is sent.
607:
163:
1904:. Lecture Notes in Computer Science. Vol. 3177. pp.
1673:
Virtual Honeypots: From Botnet Tracking to Intrusion Detection
2345:
2104:
1644:
1252:
963:
911:
737:
571:
452:
424:
418:
347:
332:
1954:
2009:
1023:
1007:
server will report the problem to the real sender cleanly.
518:
494:
343:
328:
224:
76:
1282:, Federal Trade Commission. URL accessed on 24 April 2006.
68:
1089:
904:
180:
1474:"DMARC Email Security Adoption Grows in U.S. Government"
1330:
Countering Spam by Using Ham Passwords (Email Passwords)
1273:
Email Address Harvesting: How Spammers Reap What You Sow
659:
authentication is strong enough that it can be used for
644:
72:
389:, and look that checksum up in a database such as the
2001:, How to identify and protect yourself from spam email
1624:"On the dubious merits of email verification services"
1158:
activities and gathering evidence for criminal cases.
671:
cannot usually bypass this verification when they use
521:
or is an IP address not surrounded by square brackets.
458:
2058:
1984:(Shawn Hernan, with James R. Cutler and David Harris)
1896:Özgür, Levent; Güngör, Tunga; Gürgen, Fikret (2004).
1348:
1168:
935:
1980:
Computer Incident Advisory Committee's suggestions:
432:
or proxies; others list ISPs known to support spam.
354:, a common technique of spammers - but also used in
1969:
Coalition Against Unsolicited Bulk Email, Australia
1649:. Hoboken, NJ: John Wiley & Sons. p. 630.
1386:"Canada's Law on Spam and Other Electronic Threats"
174:. Address munging is the practice of disguising an
1895:
1877:Man quits job, makes living suing e-mail spammers
1846:"Results: 54,357 site shutdowns (67,095 pending)"
1727:Honeypots: A New Paradigm to Information Security
1311:Customers: TD Ameritrade failed to warn of breach
1195:
2405:
1803:"Two companies fined for breaching the Spam Act"
1462:2017-06-26 at Wikiwix. Tech Crunch. Jan 30, 2012
1347:This depends on provider's policy; for example:
1104:
776:
111:between incorrectly rejecting legitimate email (
1084:By monitoring spam reports from places such as
302:(FTC), or similar agencies in other countries.
1699:
1383:The latter depends on local law; for example:
1050:problems, as well making it impossible to use
115:) as opposed to not rejecting all spam email (
2044:
1073:
717:
409:address rather than any trait of the sender.
361:
306:Automated techniques for email administrators
242:
2025:An article about spam in Scientific American
1751:"Shutting Down the Highway to Internet Hell"
1724:
1700:Shimeall, Timothy; Spring, Jonathan (2013).
1670:Provos, Niels; Holz, Thorsten (2007-07-16).
1497:
1058:if the port 587 submission port isn't used.
932:ROKSO list, and do other background checks.
918:Background checks on new users and customers
588:
376:
186:
2051:
2037:
1729:. Boca Raton, FL: CRC Press. p. 252.
1669:
984:
403:
1771:Why can't I send mail from my hotel room?
613:
1647:Mastering Microsoft Exchange Server 2016
1558:"4.XXX.XXX Persistent Transient Failure"
969:
493:technique is built on the fact that the
208:
1472:Kerner, Sean Michael (2 January 2018).
1457:DMARC Promises A World Of Less Phishing
1216:
1150:in monitoring and tracking email spam,
1038:
679:
412:
54:instructions, advice, or how-to content
14:
2406:
1725:Joshi, R. C.; Sardana, Anjali (2011).
1471:
1396:from the original on 10 September 2014
1351:"Universal Terms of Service Agreement"
1249:Digital Security Guide | Safeonline.ng
905:Automated techniques for email senders
358:, and other types of fraud via email.
223:functionality, such as the display of
219:Many modern mail programs incorporate
126:
2032:
1704:. Waltham, MA: Syngress. p. 74.
1695:
1693:
1176:
1095:
1815:from the original on March 16, 2012.
1539:from the original on 8 December 2015
865:
645:#Strict enforcement of RFC standards
36:
1446:, NZ Department of Internal Affairs
1204:
1010:
577:
459:Strict enforcement of RFC standards
63:so that it is more encyclopedic or
24:
2238:Distributed Checksum Clearinghouse
1965:CAUBE.AU – Fight Spam in Australia
1955:Anti spam info & resource page
1869:
1826:Alleged Spam King Soloway Arrested
1790:Rate Limiting as an Anti-Spam Tool
1690:
1322:
1169:New solutions and ongoing research
936:Confirmed opt-in for mailing lists
391:Distributed Checksum Clearinghouse
147:
25:
2430:
2223:Challenge–response spam filtering
2060:Unsolicited digital communication
1933:
1875:Paul Elias, (December 26, 2010).
1498:Stilgherrian (18 December 2018).
1328:David A. Wheeler, (May 11, 2011)
1292:"Information Technology: Threats"
1131:Email spam legislation by country
1124:
368:Challenge-response spam filtering
314:
278:
1858:from the original on 17 May 2008
1634:from the original on 2015-09-08.
1590:from the original on 2007-01-06.
1361:from the original on 4 July 2014
1061:
435:
265:
195:
41:
1889:
1838:
1819:
1795:
1783:
1764:
1743:
1718:
1663:
1638:
1616:
1594:
1570:
1551:
1513:
1491:
1465:
1449:
1022:can be programmed to not allow
758:
1430:
1411:
1377:
1341:
1304:
1285:
1266:
1237:
1196:Machine-learning-based systems
13:
1:
1945:Anti-Spam Research Group wiki
1520:Jose Marcio Martins Da Cruz;
1231:
1105:Strong AUP and TOS agreements
777:Statistical content filtering
744:
638:forward-confirmed reverse DNS
624:Forward-confirmed reverse DNS
134:
27:Methods to prevent email spam
1914:10.1007/978-3-540-28651-6_74
1578:"Frequently Asked Questions"
1251:. 2016-09-07. Archived from
1183:Cost-based anti-spam systems
1161:Analysis of the sites being
558:
18:Anti-spam techniques (users)
7:
1349:Go Daddy Legal Department.
1201:legitimate email contents.
1044:Network address translation
451:' Domain Block List (DBL),
300:US Federal Trade Commission
10:
2435:
2258:Naive Bayes spam filtering
1180:
1148:Internet service providers
1128:
1077:
1074:Spam report feedback loops
988:
973:
939:
869:
846:
842:
780:
762:
748:
721:
718:SMTP callback verification
683:
617:
606:or are participating in a
562:
462:
439:
416:
365:
362:Challenge/response systems
318:
282:
246:
243:Disposable email addresses
212:
158:Email addresses posted on
151:
104:(unsolicited bulk email).
29:
2359:
2281:
2208:
2138:
2075:
2066:
1113:providers have either an
835:, and later revisions of
172:e-mail address harvesting
2233:Disposable email address
2095:Directory harvest attack
1959:Federal Trade Commission
1531:Anti-Spam Research Group
589:Outbound spam protection
377:Checksum-based filtering
249:Disposable email address
187:Avoid responding to spam
32:Knowledge:Spam blacklist
2023:Secret to Stopping Spam
1974:Composing abuse reports
1947:, which was created by
1831:March 17, 2009, at the
1278:April 24, 2006, at the
985:Limit email backscatter
783:Bayesian spam filtering
442:DNSBL § URI DNSBLs
404:Country-based filtering
325:Sender Policy Framework
1883:on December 27, 2010.
1780:AskLeo!, December 2005
614:PTR/reverse DNS checks
1676:. Pearson Education.
1115:Acceptable Use Policy
1080:Feedback Loop (email)
970:Egress spam filtering
823:, the email programs
724:callback verification
684:Further information:
675:to forge the domains.
636:(mail servers) use a
618:Further information:
463:Further information:
382:Checksum-based filter
319:Further information:
234:, being targeted by
209:Disable HTML in email
2243:Email authentication
1999:Email Security Guide
1583:The Spamhaus Project
1217:Research conferences
1039:Port 25 interception
1028:Mail Transfer Agents
930:the Spamhaus Project
680:Rule-based filtering
634:mail transfer agents
565:Honeypot (computing)
413:DNS-based blacklists
321:Email authentication
227:, URLs, and images.
100:are used to prevent
98:anti-spam techniques
2090:Bulk email software
1753:. eWeek. 2005-04-08
1604:. IBM. 16 June 2017
1427:, OnGuardOnline.gov
991:Backscatter (email)
849:Tarpit (networking)
829:Mozilla Thunderbird
692:regular expressions
487:Temporary rejection
127:End-user techniques
61:rewrite the content
1951:and is still alive
1776:2006-01-10 at the
1563:2016-03-03 at the
1442:2016-02-24 at the
1423:2013-12-17 at the
1335:2012-02-04 at the
1316:2012-03-05 at the
1297:2016-03-07 at the
1177:Cost-based systems
1096:FROM field control
872:Scunthorpe problem
620:Reverse DNS lookup
532:Invalid pipelining
502:HELO/EHLO checking
465:SMTP RFC standards
170:are vulnerable to
2401:
2400:
2228:Context filtering
2204:
2203:
1923:978-3-540-22881-3
1811:. June 22, 2007.
866:Collateral damage
663:purposes because
94:
93:
16:(Redirected from
2426:
2369:Advance-fee scam
2316:Keyword stuffing
2073:
2072:
2053:
2046:
2039:
2030:
2029:
1993:Neil Schwartzman
1928:
1927:
1893:
1887:
1885:Associated Press
1879:, archived from
1873:
1867:
1866:
1864:
1863:
1842:
1836:
1823:
1817:
1816:
1799:
1793:
1792:eWeek, June 2004
1787:
1781:
1768:
1762:
1761:
1759:
1758:
1747:
1741:
1740:
1722:
1716:
1715:
1697:
1688:
1687:
1667:
1661:
1660:
1642:
1636:
1635:
1628:www.spamhaus.org
1620:
1614:
1613:
1611:
1609:
1598:
1592:
1591:
1574:
1568:
1555:
1549:
1548:
1546:
1544:
1517:
1511:
1510:
1508:
1506:
1495:
1489:
1488:
1486:
1484:
1469:
1463:
1453:
1447:
1434:
1428:
1415:
1409:
1408:
1403:
1401:
1381:
1375:
1374:
1368:
1366:
1345:
1339:
1326:
1320:
1308:
1302:
1289:
1283:
1270:
1264:
1263:
1261:
1260:
1241:
1205:Other techniques
1119:Terms of Service
1068:zombie computers
1011:Port 25 blocking
1001:backscatter spam
976:Egress filtering
734:return addresses
673:zombie computers
650:
578:Hybrid filtering
430:open mail relays
89:
86:
80:
45:
44:
37:
21:
2434:
2433:
2429:
2428:
2427:
2425:
2424:
2423:
2404:
2403:
2402:
2397:
2381:Make Money Fast
2355:
2351:URL redirection
2277:
2200:
2134:
2085:Address munging
2062:
2057:
1936:
1931:
1924:
1894:
1890:
1874:
1870:
1861:
1859:
1844:
1843:
1839:
1833:Wayback Machine
1824:
1820:
1801:
1800:
1796:
1788:
1784:
1778:Wayback Machine
1769:
1765:
1756:
1754:
1749:
1748:
1744:
1737:
1723:
1719:
1712:
1698:
1691:
1684:
1668:
1664:
1657:
1643:
1639:
1622:
1621:
1617:
1607:
1605:
1600:
1599:
1595:
1576:
1575:
1571:
1565:Wayback Machine
1556:
1552:
1542:
1540:
1526:"URL filtering"
1518:
1514:
1504:
1502:
1496:
1492:
1482:
1480:
1470:
1466:
1455:Butcher, Mike.
1454:
1450:
1444:Wayback Machine
1435:
1431:
1425:Wayback Machine
1416:
1412:
1399:
1397:
1390:fightspam.gc.ca
1384:
1382:
1378:
1364:
1362:
1346:
1342:
1337:Wayback Machine
1327:
1323:
1318:Wayback Machine
1309:
1305:
1299:Wayback Machine
1290:
1286:
1280:Wayback Machine
1271:
1267:
1258:
1256:
1243:
1242:
1238:
1234:
1219:
1211:bounce messages
1207:
1198:
1185:
1179:
1171:
1133:
1127:
1107:
1098:
1082:
1076:
1064:
1041:
1013:
993:
987:
978:
972:
944:
938:
920:
907:
874:
868:
851:
845:
785:
779:
767:
761:
753:
747:
726:
720:
688:
686:Email filtering
682:
648:
626:
616:
591:
580:
567:
561:
471:zombie computer
467:
461:
444:
438:
421:
415:
406:
379:
370:
364:
352:spoof addresses
335:
317:
308:
287:
281:
273:plus addressing
268:
260:security breach
251:
245:
217:
211:
198:
189:
156:
154:Address munging
150:
148:Address munging
137:
129:
117:false negatives
113:false positives
90:
84:
81:
58:
46:
42:
35:
28:
23:
22:
15:
12:
11:
5:
2432:
2422:
2421:
2416:
2399:
2398:
2396:
2395:
2394:
2393:
2383:
2378:
2377:
2376:
2365:
2363:
2361:Internet fraud
2357:
2356:
2354:
2353:
2348:
2343:
2338:
2333:
2328:
2323:
2318:
2313:
2311:Google bombing
2308:
2303:
2298:
2293:
2287:
2285:
2279:
2278:
2276:
2275:
2270:
2265:
2260:
2255:
2253:List poisoning
2250:
2245:
2240:
2235:
2230:
2225:
2220:
2214:
2212:
2206:
2205:
2202:
2201:
2199:
2198:
2193:
2188:
2183:
2178:
2173:
2168:
2163:
2158:
2153:
2148:
2142:
2140:
2136:
2135:
2133:
2132:
2127:
2122:
2117:
2112:
2110:Email spoofing
2107:
2102:
2097:
2092:
2087:
2081:
2079:
2070:
2064:
2063:
2056:
2055:
2048:
2041:
2033:
2027:
2026:
2020:
2017:European Union
2007:
2002:
1996:
1986:
1977:
1971:
1962:
1952:
1942:
1935:
1934:External links
1932:
1930:
1929:
1922:
1888:
1868:
1837:
1818:
1794:
1782:
1763:
1742:
1735:
1717:
1710:
1689:
1682:
1662:
1655:
1637:
1615:
1593:
1569:
1550:
1512:
1490:
1464:
1448:
1429:
1410:
1376:
1340:
1321:
1303:
1284:
1265:
1235:
1233:
1230:
1229:
1228:
1218:
1215:
1206:
1203:
1197:
1194:
1181:Main article:
1178:
1175:
1170:
1167:
1152:identity theft
1126:
1125:Legal measures
1123:
1109:Most ISPs and
1106:
1103:
1097:
1094:
1078:Main article:
1075:
1072:
1063:
1060:
1040:
1037:
1012:
1009:
997:bounce message
989:Main article:
986:
983:
974:Main article:
971:
968:
940:Main article:
937:
934:
919:
916:
906:
903:
902:
901:
897:
896:
892:
891:
887:
886:
882:
881:
867:
864:
847:Main article:
844:
841:
781:Main article:
778:
775:
763:Main article:
760:
757:
749:Main article:
746:
743:
722:Main article:
719:
716:
681:
678:
677:
676:
656:
652:
641:
615:
612:
590:
587:
579:
576:
563:Main article:
560:
557:
553:Quit detection
529:
528:
525:
522:
481:Greeting delay
460:
457:
440:Main article:
437:
434:
417:Main article:
414:
411:
405:
402:
378:
375:
366:Main article:
363:
360:
316:
315:Authentication
313:
307:
304:
285:Spam reporting
283:Main article:
280:
279:Reporting spam
277:
267:
264:
247:Main article:
244:
241:
213:Main article:
210:
207:
197:
194:
188:
185:
176:e-mail address
152:Main article:
149:
146:
136:
133:
128:
125:
92:
91:
49:
47:
40:
26:
9:
6:
4:
3:
2:
2431:
2420:
2417:
2415:
2412:
2411:
2409:
2392:
2389:
2388:
2387:
2384:
2382:
2379:
2375:
2372:
2371:
2370:
2367:
2366:
2364:
2362:
2358:
2352:
2349:
2347:
2344:
2342:
2339:
2337:
2334:
2332:
2329:
2327:
2326:Referrer spam
2324:
2322:
2319:
2317:
2314:
2312:
2309:
2307:
2304:
2302:
2299:
2297:
2294:
2292:
2289:
2288:
2286:
2284:
2280:
2274:
2271:
2269:
2266:
2264:
2261:
2259:
2256:
2254:
2251:
2249:
2246:
2244:
2241:
2239:
2236:
2234:
2231:
2229:
2226:
2224:
2221:
2219:
2216:
2215:
2213:
2211:
2207:
2197:
2194:
2192:
2191:Telemarketing
2189:
2187:
2184:
2182:
2179:
2177:
2174:
2172:
2169:
2167:
2164:
2162:
2159:
2157:
2154:
2152:
2149:
2147:
2144:
2143:
2141:
2137:
2131:
2128:
2126:
2125:Pink contract
2123:
2121:
2118:
2116:
2113:
2111:
2108:
2106:
2103:
2101:
2098:
2096:
2093:
2091:
2088:
2086:
2083:
2082:
2080:
2078:
2074:
2071:
2069:
2065:
2061:
2054:
2049:
2047:
2042:
2040:
2035:
2034:
2031:
2024:
2021:
2018:
2014:
2013:United States
2011:
2008:
2006:
2003:
2000:
1997:
1994:
1990:
1987:
1985:
1983:
1978:
1975:
1972:
1970:
1966:
1963:
1960:
1956:
1953:
1950:
1946:
1943:
1941:
1938:
1937:
1925:
1919:
1915:
1911:
1907:
1903:
1899:
1892:
1886:
1882:
1878:
1872:
1857:
1853:
1852:
1847:
1841:
1834:
1830:
1827:
1822:
1814:
1810:
1809:
1808:Computerworld
1804:
1798:
1791:
1786:
1779:
1775:
1772:
1767:
1752:
1746:
1738:
1736:9781439869994
1732:
1728:
1721:
1713:
1711:9781597499699
1707:
1703:
1696:
1694:
1685:
1683:9780132702058
1679:
1675:
1674:
1666:
1658:
1656:9781119232056
1652:
1648:
1641:
1633:
1629:
1625:
1619:
1603:
1597:
1589:
1585:
1584:
1579:
1573:
1566:
1562:
1559:
1554:
1538:
1534:
1532:
1527:
1523:
1516:
1501:
1494:
1479:
1475:
1468:
1461:
1458:
1452:
1445:
1441:
1438:
1433:
1426:
1422:
1419:
1414:
1407:
1395:
1391:
1387:
1380:
1373:
1360:
1356:
1352:
1344:
1338:
1334:
1331:
1325:
1319:
1315:
1312:
1307:
1301:, vermont.gov
1300:
1296:
1293:
1288:
1281:
1277:
1274:
1269:
1255:on 2022-05-18
1254:
1250:
1246:
1240:
1236:
1227:
1224:
1223:
1222:
1214:
1212:
1202:
1193:
1191:
1190:Daniel Balsam
1184:
1174:
1166:
1164:
1159:
1157:
1153:
1149:
1144:
1142:
1138:
1132:
1122:
1120:
1116:
1112:
1102:
1093:
1091:
1087:
1081:
1071:
1069:
1062:Rate limiting
1059:
1057:
1053:
1049:
1048:email privacy
1045:
1036:
1034:
1029:
1025:
1021:
1017:
1008:
1006:
1002:
998:
992:
982:
977:
967:
965:
961:
957:
953:
949:
943:
933:
931:
926:
915:
913:
899:
898:
894:
893:
889:
888:
884:
883:
879:
878:
877:
873:
863:
859:
856:
850:
840:
838:
834:
830:
826:
822:
818:
814:
810:
806:
801:
798:
794:
790:
784:
774:
770:
766:
756:
752:
742:
739:
735:
730:
725:
715:
713:
709:
705:
701:
696:
693:
687:
674:
670:
666:
662:
657:
653:
646:
642:
639:
635:
631:
630:
629:
625:
621:
611:
609:
605:
599:
597:
586:
584:
575:
573:
566:
556:
554:
550:
547:
543:
539:
535:
533:
526:
523:
520:
516:
515:
514:
511:
507:
503:
499:
496:
492:
488:
484:
482:
478:
476:
472:
466:
456:
455:, and URIBL.
454:
450:
443:
436:URL filtering
433:
431:
426:
420:
410:
401:
399:
398:
392:
388:
383:
374:
369:
359:
357:
353:
349:
345:
341:
334:
330:
326:
322:
312:
303:
301:
296:
293:
286:
276:
274:
266:Ham passwords
263:
261:
256:
250:
240:
237:
233:
228:
226:
222:
216:
206:
202:
196:Contact forms
193:
184:
182:
177:
173:
169:
165:
161:
155:
145:
143:
132:
124:
120:
118:
114:
110:
105:
103:
99:
88:
78:
74:
70:
66:
62:
56:
55:
50:This article
48:
39:
38:
33:
19:
2374:Lottery scam
2331:Scraper site
2301:Doorway page
2209:
2171:Mobile phone
2151:Cold calling
1981:
1968:
1901:
1891:
1881:the original
1871:
1860:. Retrieved
1849:
1840:
1835:May 31, 2007
1821:
1806:
1797:
1785:
1766:
1755:. Retrieved
1745:
1726:
1720:
1701:
1672:
1665:
1646:
1640:
1627:
1618:
1606:. Retrieved
1596:
1581:
1572:
1553:
1541:. Retrieved
1529:
1524:(May 2009).
1515:
1503:. Retrieved
1493:
1481:. Retrieved
1477:
1467:
1451:
1432:
1413:
1405:
1398:. Retrieved
1389:
1379:
1370:
1363:. Retrieved
1354:
1343:
1324:
1306:
1287:
1268:
1257:. Retrieved
1253:the original
1248:
1239:
1220:
1208:
1199:
1186:
1172:
1163:spamvertised
1160:
1145:
1134:
1108:
1099:
1083:
1065:
1042:
1014:
1004:
994:
979:
948:mailing list
945:
942:Opt-in email
921:
908:
875:
860:
854:
852:
837:SpamAssassin
802:
796:
792:
788:
786:
771:
768:
759:Spamtrapping
754:
738:trap address
731:
727:
697:
689:
661:whitelisting
627:
600:
592:
583:SpamAssassin
581:
568:
552:
551:
537:
536:
531:
530:
501:
500:
486:
485:
480:
479:
468:
445:
422:
407:
395:
381:
380:
371:
336:
309:
297:
288:
269:
254:
252:
229:
218:
203:
199:
190:
157:
138:
130:
121:
106:
97:
95:
82:
59:Please help
51:
2336:Social spam
2248:Greylisting
2218:Client-side
2146:Auto dialer
1608:19 December
1522:John Levine
1505:20 December
1483:20 December
1437:"Anti-spam"
1400:5 September
1365:5 September
1355:GoDaddy.com
1141:enforcement
1137:legislation
1117:(AUP) or a
1033:smart hosts
952:GNU Mailman
651:HELO/EHLO .
632:Most email
491:greylisting
397:hashbusters
221:web browser
69:Wikiversity
2408:Categories
2341:Spam blogs
2306:Forum spam
2283:Spamdexing
2156:Flyposting
2115:Image spam
2077:Email spam
1957:of the US
1862:2008-05-23
1757:2008-05-31
1567:, IETF.org
1543:2 December
1259:2021-12-21
1232:References
1129:See also:
870:See also:
833:Mailwasher
805:Bogofilter
797:end user's
751:SMTP proxy
745:SMTP proxy
542:MX records
255:disposable
236:JavaScript
215:HTML email
168:chat rooms
142:bcc: field
135:Discretion
109:trade-offs
102:email spam
85:April 2024
77:Wikivoyage
2419:Anti-spam
2321:Link farm
2291:Blog spam
2210:Anti-spam
2176:Newsgroup
2166:Messaging
2068:Protocols
2010:Spam Laws
1056:SMTP-AUTH
1016:Firewalls
960:Majordomo
813:SpamBayes
559:Honeypots
546:nolisting
538:Nolisting
73:Wikibooks
52:contains
2414:Spamming
2386:Phishing
2296:Cloaking
2273:Spamhaus
2181:Robocall
2161:Junk fax
1856:Archived
1829:Archived
1813:Archived
1774:Archived
1632:Archived
1588:Archived
1561:Archived
1537:Archived
1460:Archived
1440:Archived
1421:Archived
1394:Archived
1359:Archived
1333:Archived
1314:Archived
1295:Archived
1276:Archived
1156:phishing
1052:STARTTLS
956:LISTSERV
925:CAPTCHAs
765:Spamtrap
669:phishers
665:spammers
449:Spamhaus
387:checksum
356:phishing
232:web bugs
160:webpages
96:Various
2268:SpamCop
2186:Spambot
2130:Spambot
2120:Joe job
1906:505–510
1111:webmail
1086:spamcop
1020:routers
1005:sending
843:Tarpits
825:Mozilla
793:nonspam
292:SpamCop
1967:, The
1920:
1851:KnujOn
1733:
1708:
1680:
1653:
1478:e-Week
1418:"Spam"
962:, and
912:DNSBLs
855:tarpit
821:CRM114
706:
655:names.
649:
608:botnet
572:DNSBLs
544:. The
508:
489:– The
425:DNSBLs
331:, and
164:Usenet
67:it to
2391:Voice
2346:Sping
2263:SORBS
2139:Other
2105:DNSWL
2100:DNSBL
1961:(FTC)
964:qmail
809:DSPAM
700:spoof
604:virus
453:SURBL
419:DNSBL
348:DMARC
333:DMARC
75:, or
2196:VoIP
1949:ASRG
1918:ISBN
1731:ISBN
1706:ISBN
1678:ISBN
1651:ISBN
1610:2018
1545:2015
1533:wiki
1507:2018
1485:2018
1402:2014
1367:2014
1226:TREC
1154:and
1139:and
1054:and
1024:SMTP
1018:and
827:and
817:ASSP
789:spam
712:7208
708:5322
667:and
622:and
596:spam
519:FQDN
510:5321
495:SMTP
346:and
344:DKIM
329:DKIM
225:HTML
65:move
1991:by
1910:doi
1090:AOL
791:or
704:RFC
506:RFC
475:MTA
340:SPF
181:CSS
166:or
2410::
2015:,
1916:.
1908:.
1900:.
1854:.
1848:.
1805:.
1692:^
1630:.
1626:.
1586:.
1580:.
1535:.
1528:.
1476:.
1404:.
1392:.
1388:.
1369:.
1357:.
1353:.
1247:.
1088:,
958:,
954:,
914:.
853:A
839:.
831:,
819:,
815:,
811:,
807:,
710:,
610:.
504:–
342:,
327:,
323:,
262:.
183:.
162:,
71:,
2052:e
2045:t
2038:v
1995:.
1926:.
1912::
1865:.
1760:.
1739:.
1714:.
1686:.
1659:.
1612:.
1547:.
1509:.
1487:.
1262:.
647:§
140:"
87:)
83:(
79:.
57:.
34:.
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.