Beat Spam Using the E-Mail Security Appliance Nicole Wajer, Consulting Systems Engineer Nicole

Total Page:16

File Type:pdf, Size:1020Kb

Beat Spam Using the E-Mail Security Appliance Nicole Wajer, Consulting Systems Engineer Nicole Beat Spam Using The E-mail Security Appliance Nicole Wajer, Consulting Systems Engineer Nicole Nicole Wajer Consulting Systems Engineer @vlinder_nl EMEAR Agenda • SMTP Review • Email Threats - Protecting against SPAM, Viruses, Malware, Phishing • Spam vs Graymail • Email Security Appliance (ESA) • SPF,DKIM and DMARC • Conclusion We will cover: • SMTP Review • Email Spam Trends and Threats SMTP Review Email Review: Definitions Mail Protocols SMTP Sender SMTP Receiver Sending: Simple Mail Transfer 1. Establish TCP 2. Establish TCP Protocol (SMTP) Connection to Connection Send Receiving MTA 220 “Ready” reply • Connection oriented, text based protocol that communicates over TCP port 25 3. Receive “Ready” send “HELO” 4. Receive “HELO” • Client-Server architecture defined originally send 250 OK with in RFC821 in 1982 with the latest revision Extensions 5. Receive “OK” , in 2008, RFC5321 connection open and send from / to and • Uses a series of command and reply extensions sequences to define headers and data to Receive DATA be transmitted Send DATA • Relies on DNS to determine routing of 6. Send Quit 7. Receive “QUIT”, send goodbye messages from sender to recipient 8. Receive goodbye, close connection One or more Received headers Mail Anatomy showing the servers that are It’s impressive… sending the message Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com. [173.37.142.92]) by mx.google.com with ESMTPS (version=TLSv1 cipher=RC4-SHA bits=128/128); The FROM Header From: “Nicole Wajer(niwajer)" <[email protected]> The TO, CC and BCC Headers To: “[email protected]" <[email protected]> Subject: Print this Subject Headers Custom Headers Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: yes X-MS-TNEF-Correlator: MIME Headers specifying x-originating-ip: [10.24.192.221] boundaries for the different parts of the message Content-Type: multipart/mixed; boundary="_002_440E600602613146ABEF4739925CE56C2291B80Dxmbalnx04ciscoc_" MIME-Version: 1.0 --_002_440E600602613146ABEF4739925CE56C2291B80Dxmbalnx04ciscoc_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Can you please print this? First part of the message, in _002_440E600602613146ABEF4739925CE56C2291B80Dxmbalnx04ciscoc_ this case, plain text Mail Anatomy Start of the next part There’s more! --_002_440E600602613146ABEF4739925CE56C2291B80Dxmbalnx04ciscoc_ Content-Type: text/plain; name=list.txt" Attachment details Content-Description: list.txt Content-Disposition: attachment; filename=list.txt"; size=53814; creation-date="Sun, 19 Jan 2014 03:58:56 GMT"; modification-date="Mon, 20 Jan 2014 19:51:37 GMT" Content-Transfer-Encoding: base64 BASE64 Data attached MS4gV2hpY2ggb2YgdGhlIGZvbGxvd2luZyBzdGF0ZW1lbnRzIGlzIE5PVCB0cnVlIHJlZ2FyZGlu ZyB0aGUgR2VvbG9jYXRpb24gZmVhdHVyZT8gDQpCLiAgVGhlIEdlb2xvY2F0aW9uIGRhdGFiYXNl IG11c3QgYmUgbWFudWFsbHkgaW5zdGFsbGVkIGluaXRpYWxseSANCiAgICAgIA0KMi4gR2VvbG9j YXRpb24gYmxvY2tpbmcgaXMgc3VwcG9ydGVkIG9uIGFsbCBTb3VyY2VmaXJlIGFwcGxpYW5jZSBw bGF0Zm9ybXMuIA0KQi4gIEZhbHNlIA0KICAgICAgDQozLiBXaGljaCBvZiB0aGUgZm9sbG93aW5n IHN0YXRlbWVudHMgaXMgdHJ1ZSByZWdhcmRpbmcgQWNjZXNzIENvbnRyb2wgcG9saWN5IHJ1bGVz ... --_002_440E600602613146ABEF4739925CE56C2291B80Dxmbalnx04ciscoc_-- End of the MIME attachment Did you get my message? Bounces and Delays • NDR: Non-Delivery Report • Generated by the sending MTA if the there is a lookup error (i.e domain does not exist) • Generated by the receiving MTA (or mailbox server) if the user does not exist or mailbox is full • Errors shown in the NDR is a 500 level error or a permanent failure, no retry Server that sent the bounce message Reason it was bounced back • DSN: Delivery Status Notifications • Generated by sending MTA when destination is down (i.e server unresponsive) • Messages are re-queued and will try to re-deliver after a specified period • DSN is a soft failure, 400 level error message • After a specified amount of time, if it can not deliver, it will fail with a NDR Email Spam Trends and Threats The Nemesis: SPAM SPAM stands for: A) Stupid, Pointless Annoying Message B) Sending Pornography and Abusive Marketing C) Slang name for Unsolicited Commercial Email D) All of the above Types of SPAM • Spamvertising • 419 scams • Phishing • Harvest spam • Image spam • Backscatter spam • Snowshoe spam Types of SPAM • Spamvertising • 419 scams • Phishing • Harvest spam • Image spam • Backscatter spam • Snowshoe spam Types of SPAM • Spamvertising • 419 scams • Phishing • Harvest spam • Image spam • Backscatter spam • Snowshoe spam Gone Phishing • Phish – The impersonation of a party to gain trust of the target and obtain confidential information • Spear Phishing – Attacks against a specific person or companies, with the intent to gain personal information • Whaling (Big Phish) – Targeted to Senior Executives or high profile personnel, with a sophisticated and researched attack • Defence: User education and URL detection on the Cisco Email Security Appliance Types of SPAM • Spamvertising • 419 scams • Phishing • Harvest spam • Image spam • Backscatter spam • Snowshoe spam Types of SPAM • Spamvertising • 419 scams • Phishing • Harvest spam • Image spam • Backscatter spam • Snowshoe spam Types of SPAM • Spamvertising • 419 scams • Phishing • Harvest spam • Image spam • Backscatter spam • Snowshoe spam Backscatter Spam • Backscatter attack – the most profitable Email DDoS • Hire a botnet • Spoof millions of messages to non-existent recipients claiming to come from DDoS target • Watch their Email systems go down under the flood of bounce messages from all over the Internet Effective countermeasures from all bounce-based danger SPF, DMARC and BATV (all supported by Cisco Email Security Appliance and Cloud Email Security!) Protecting Against BackScatter • Settings on your ESA can define which keys to use • Use a varying set of keys to sign messages • Assign them to different destinations “Snowshoe” Spam – better evasion techniques • Spam campaigns that use unique text from unique IPs • Short campaigns – morphs fast – constantly changing • Reputation and Content analysis resistant • Offer spam (Micro-category) = Sell goods or services. • Majority of Offer spam uses Snowshoe techniques • Pure content analysis can lead to high false positives – need to have a balance YourUPSorder.exe • 0-Day attacks usually consist of files such as EXE, PDF, ZIP, OFFICE, etc. • Combination of Phishing and Malware payload • Multi-Vector threats hide malware in URL • Advanced techniques uses droppers where a two-stage installer is used Defence in depth using signature AV, 0-day filtering and Advanced Malware Protection. Why Targeted Phishing Works Targeted Phishing • Attacks require criminals to efficiently build appropriate resources and trick victims into revealing valuable private information. • https://www.scamwatch.gov.au/types-of-scams/attempts-to-gain-your-personal-information/phishing Social Engineering Example of Social Engineering • Phishing scams might be the most common types of social engineering attacks used today. Most phishing scams demonstrate the following characteristics: • Seek to obtain personal information, such as names, addresses and social security numbers. • Use link shorteners or embed links that redirect users to suspicious websites in URLs that appear legitimate. • Incorporates threats, fear and a sense of urgency in an attempt to manipulate the user into acting promptly. We covered: • SMTP Review • Email Spam Trends and Threats We will cover: • Spam vs Graymail • How does the Email Security Appliance Pipeline looks like? • Protecting your users with Email Security Appliance Spam vs Graymail Spam vs Graymail - 1 • Spam is an email that the recipient didn’t opt to choose (unsolicited) and generally has embedded links, pictures and other documents that may be disguised to look legit, but are actually malicious in nature. Spam emails are intended to fool the recipient and cause harm to the end users environment. For more information on Spam, please refer to the CAN-SPAM Act of 2003. Spam vs Graymail - 2 • In short: Graymail is an email that the recipient “opted” to receive, but don’t really want them in their inbox. A good example is when you go shopping and provide your email address to receive coupons/discounts and other notifications from that vendor. These emails are known as graymail, you opted to receive them, but after a while you grow tired of how much of the annoying emails the vendor sends and thus ends up being reported as spam, which it isn’t at all. Mail Flow ESA Email Pipeline and Definitions SMTP SERVER WORKQUEUE SMTP CLIENT Host Access Table (HAT) LDAP RCPT Accept (WQ) Encryption Received Header Masquerading (Table / LDAP) Virtual Gateways Default Domain LDAP Routing Delivery Limits Domain Map Message Filters Received: Header Recipient Access Table (RAT) Anti-Spam Domain-Based Limits Alias Table Anti-Virus Domain-Based Routing LDAP RCPT Accept Advanced Malware (AMP) Global Unsubscribe SMTP Call-Ahead Graymail, Safe Unsubscribe S/MIME Encryption Policy Policy Scanning DKIM / SPF Verification Content Filtering - DKIM Signing Per DMARC Verification Outbreak Filtering Bounce Profiles S/MIME Verification DLP Filtering (Outbound) Message Delivery Protect Your Users with ESA Email Security Appliance HAT – Host Access Table • Systems are added to the various Sender Groups manually by adding the sender’s IP address, host name, or partial host name, or they fall into a particular sender group due to their reputation score. MFP – Mail Flow Policy • Check the Mail Flow Policies carefully
Recommended publications
  • DMARC — Defeating E-Mail Abuse
    CERT-EU Security Whitepaper 17-001 DMARC — Defeating E-Mail Abuse Christos Koutroumpas ver. 1.3 February 9, 2017 TLP: WHITE 1 Preface E-mail is one of the most valuable and broadly used means of communication and most orga- nizations strongly depend on it. The Simple Mail Transport Protocol (SMTP) – the Internet’s underlying email protocol – was adopted in the eighties and is still in use after 35 years. When it was designed, the need for security was not so obvious, and therefore security was not incor- porated in the design of this protocol. As a result, the protocol is susceptible to a wide range of attacks. Spear-phishing campaigns in particular can be more successful by spoofing (altering) the originator e-mail address to imper- sonate a trusted or trustworthy organization or person. This can lead to luring the recipient into giving away credentials or infecting his/her computer by executing malware delivered through the e-mail. While raising user awareness on how to avoid e-mail fraud is recommended, the Verizon Data Breach Investigations Report indicates that more needs to be done. The DBIR report reveals that 30% of all phishing e-mail messages were opened by the recipients and with 12% clicked on the content and executed malicious code. The median time for the first user of a phishing campaign to open the malicious email is 1 minute, 40 seconds. The median time to the first click on the attachment was 3 minutes, 45 seconds. These statistics highlight the risk for an organization on the receiving end of spear-phishing e-mails.
    [Show full text]
  • Delivering Results to the Inbox Sailthru’S 2020 Playbook on Deliverability, Why It’S Imperative and How It Drives Business Results Introduction to Deliverability
    Delivering Results to the Inbox Sailthru’s 2020 Playbook on Deliverability, Why It’s Imperative and How It Drives Business Results Introduction to Deliverability Every day, people receive more than 293 billion Deliverability is the unsung hero of email marketing, emails, a staggering number that only represents ultimately ensuring a company’s emails reach their the tip of the iceberg. Why? The actual number intended recipients. It’s determined by a host of of emails sent is closer to 5.9 quadrillion, with the factors, including the engagement of your subscribers overwhelming majority blocked outright or delivered and the quality of your lists. All together, these factors to the spam folder. result in your sender reputation score, which is used to determine how the ISPs treat your email stream. Something many people don’t realize is that to the Deliverability is also a background player, so far in the major Internet Service Providers (ISPs) — Gmail, shadows that many people don’t think about it, until Yahoo!, Hotmail, Comcast and AOL — “spam” there’s a major issue. doesn’t refer to marketing messages people may find annoying, but rather malicious email filled with That’s why Sailthru’s deliverability team created this scams and viruses. In order to protect their networks guide. Read on to learn more about how deliverability and their customers, the ISPs cast a wide net. If a works on the back-end and how it impacts revenue, message is deemed to be spam by the ISP’s filters, it’s your sender reputation and how to maintain a good dead on arrival, never to see the light of the inbox, as one, and best practices for list management, email protecting users’ inboxes is the top priority of any ISP.
    [Show full text]
  • Presentations Made by Senders
    SES ���� ��� � �� � � � � � � � ������������� DomainKeys ��������� SPF ��������������������� ���������� ����������������� ������������������������������������������������ Contents Introduction 3 Deployment: For Email Receivers 6 Audience 3 Two Sides of the Coin 6 How to Read this White Paper 3 Recording Trusted Senders Who Passed Authentication 6 A Vision for Spam-Free Email 4 Whitelisting Incoming Forwarders 6 The Problem of Abuse 4 What To Do About Forgeries 6 The Underlying Concept 4 Deployment: For ISPs and Enterprises 7 Drivers; or, Who’s Buying It 4 Complementary considerations for ISPs 7 Vision Walkthrough 5 Deployment: For MTA vendors 8 About Sender Authentication 8 Which specification? 8 An Example 8 Conformance testing 8 History 8 Perform SRS and prepend headers when forwarding 8 How IP-based Authentication Works 9 Add ESMTP support for Submitter 8 The SPF record 9 Record authentication and policy results in the headers 8 How SPF Classic Works 9 Join the developers mailing list 8 How Sender ID works 9 Deployment: For MUA vendors 9 How Cryptographic Techniques Work 0 Displaying Authentication-Results 9 Using Multiple Approaches Automatic switching to port 587 9 Reputation Systems Deployment: For ESPs 20 Deployment: For Email Senders 2 Don’t look like a phisher! 20 First, prepare. 2 Delegation 20 Audit Your Outbound Mailstreams 2 Publish Appropriately 20 Construct the record 2 Deployment: For Spammers 2 Think briefly about PRA and Mail-From contexts. 3 Two Types of Spammers 2 Test the record, part 3 Publish SPF and sign with DomainKeys. 2 Put the record in DNS 3 Stop forging random domains. 2 Test the record, part 2 4 Buy your own domains. 2 Keep Track of Violations 4 Reuse an expired domain.
    [Show full text]
  • Webfaction User Guide
    WebFaction User Guide WebFaction is a service of Paragon Internet Group Limited CONTENTS 1 Introduction 3 1.1 Services..................................................3 1.2 The Complete System..........................................4 2 The Control Panel 5 2.1 Log in to the Control Panel.......................................5 2.2 Change Your Control Panel Password..................................5 2.3 What to Do About a Lost Password...................................6 2.4 Two-Step Login.............................................6 3 Finding Details About Your Server9 3.1 Finding Your Server’s Name.......................................9 3.2 Finding Your Server’s Operating System................................9 3.3 Finding Your Server’s IP Address.................................... 10 4 Accessing Your Data 11 4.1 Connecting with SSH.......................................... 11 4.2 Connecting with FTP........................................... 14 4.3 Changing Your FTP or SSH Password.................................. 14 4.4 Additional Users............................................. 15 4.5 Backups................................................. 16 5 Accounts 17 5.1 Plans and Services............................................ 17 5.2 Communicating with WebFaction.................................... 18 5.3 Payments................................................. 19 5.4 Affiliate Program............................................. 23 5.5 Canceling Your Account......................................... 24 6 Domains 25 6.1 Getting
    [Show full text]
  • Combatting Spam Using Mimedefang, Spamassassin and Perl
    Combating Spam Using SpamAssassin, MIMEDefang and Perl Copyright 2003 David F. Skoll Roaring Penguin Software Inc. (Booth #23) Administrivia Please turn off or silence cell phones, pagers, Blackberry devices, etc... After the tutorial, please be sure to fill out an evaluation form and return it to the USENIX folks. 2 Overview After this tutorial, you will: Understand how central mail filtering works. Know how to use MIMEDefang to filter mail. Be able to integrate SpamAssassin into your mail filter. Know how to implement mail filtering policies with MIMEDefang and Perl. Know how to fight common spammer tactics. 3 Outline Introduction to Mail Filtering Sendmail's Milter API MIMEDefang Introduction, Architecture Writing MIMEDefang Filters SpamAssassin Integration Advanced Filter Writing Fighting Common Spammer Tactics Advanced Topics Policy Suggestions 4 Assumptions I assume that you: Are familiar with Sendmail configuration. You don't need to be a sendmail.cf guru, but should know the basics. Are familiar with Perl. Again, you don't need to be able to write an AI program in a Perl one- liner, but should be able to read simple Perl scripts. Are running the latest version of Sendmail 8.12 on a modern UNIX or UNIX-like system. 5 Why Filter Mail? The old reason: to stop viruses. The new reason: to stop spam and inappropriate content. Blocking viruses is easy. Block .exe and similar files, and test against signature databases. Blocking spam is hard, but becoming increasingly important. Organizations can even face lawsuits over inappropriate content. 6 Mail filtering is required for many reasons. In addition to the reasons given on the slide, you might need to filter outgoing mail as well to prevent virus propagation, dissemination of sensitive information, etc.
    [Show full text]
  • Account Administrator's Guide
    ePrism Email Security Account Administrator’s Guide - V10.4 4225 Executive Sq, Ste 1600 Give us a call: Send us an email: For more info, visit us at: La Jolla, CA 92037-1487 1-800-782-3762 [email protected] www.edgewave.com © 2001—2016 EdgeWave. All rights reserved. The EdgeWave logo is a trademark of EdgeWave Inc. All other trademarks and registered trademarks are hereby acknowledged. Microsoft and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Other product and company names mentioned herein may be the trademarks of their respective owners. The Email Security software and its documentation are copyrighted materials. Law prohibits making unauthorized copies. No part of this software or documentation may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into another language without prior permission of EdgeWave. 10.4 Contents Chapter 1 Overview 1 Overview of Services 1 Email Filtering (EMF) 2 Archive 3 Continuity 3 Encryption 4 Data Loss Protection (DLP) 4 Personal Health Information 4 Personal Financial Information 5 Document Conventions 6 Other Conventions 6 Supported Browsers 7 Reporting Spam to EdgeWave 7 Contacting Us 7 Additional Resources 7 Chapter 2 Portal Overview 8 Navigation Tree 9 Work Area 10 Navigation Icons 10 Getting Started 11 Logging into the portal for the first time 11 Logging into the portal after registration 12 Changing Your Personal Information 12 Configuring Accounts 12 Chapter 3 EdgeWave Administrator
    [Show full text]
  • Set up Mail Server Documentation 1.0
    Set Up Mail Server Documentation 1.0 Nosy 2014 01 23 Contents 1 1 1.1......................................................1 1.2......................................................2 2 11 3 13 3.1...................................................... 13 3.2...................................................... 13 3.3...................................................... 13 4 15 5 17 5.1...................................................... 17 5.2...................................................... 17 5.3...................................................... 17 5.4...................................................... 18 6 19 6.1...................................................... 19 6.2...................................................... 28 6.3...................................................... 32 6.4 Webmail................................................. 36 6.5...................................................... 37 6.6...................................................... 38 7 39 7.1...................................................... 39 7.2 SQL.................................................... 41 8 43 8.1...................................................... 43 8.2 strategy.................................................. 43 8.3...................................................... 44 8.4...................................................... 45 8.5...................................................... 45 8.6 Telnet................................................... 46 8.7 Can postfix receive?..........................................
    [Show full text]
  • Macsysadmin 2009 Presentatio
    Slide 1 SpamAssassin Way more than the Mac OS X Server GUI shows Presented by: Kevin A. McGrail Project Management Committee Member of the Apache Software Foundation SpamAssassin Project & President, PCCC September 16, 2009 Good Afternoon, My name is Kevin A. McGrail. If you read my biographyi for this conference, you’ll know already that I hate Spam and enjoy greatly fighting spammers. You’ll also know that I love all types of computers and use a wide variety of machines & operating systems. But I’m definitely old-school in my love for the command line interface. This doesn’t mean I don’t think that Apple’s OS X is the most beautiful pairing of a rock-solid CLI with a beautifully polished GUI. But it does mean that while we are here to talk about Mac system administration, the configuration of SpamAssassin is largely not server specific and most of the heavy- handed configuration changes will be done behind the scenes using the CLI. So let’s get started by talking about the definition of Spam. Page 1 of 67 Slide 2 What is Spam? •Spam is NOT about content, its about CONSENT. – Consent: to give assent or approval : agree <consent to being tested> Merriam‐Webster Dictionary •What is SPAM vs. spam? September 16, 2009 Chris Santerre gave the best definition of Spam I’ve ever seen. He based the definition of Spam on CONSENT not content because consent is when you give approval to someone to send you e-mails. Many people try and use various legal definitions such as CAN-SPAM in the US.
    [Show full text]
  • Email Sender Authentication Development and Deployment
    EMAIL SENDER AUTHENTICATION DEVELOPMENT AND DEPLOYMENT (PROJECT CHEESEPLATE) Volume I Technical and Management Proposal pobox.com IC Group, Inc. [email protected] v1.01 20041217 Full Proposal Control Number EB8A Email Sender Authentication OFFICIAL TRANSMITTAL LETTER IC Group, Inc., a New York State corporation, doing business as pobox.com, respectfully submits a proposal in response to solicitation BAA04-17 for Cyber Security Research and Development. It is submitted under Category 3, Technical Topic Area 7, Technologies to Defend Against Identity Theft, for consideration as a Type II Prototype Technology. Solicitation Title: BAA 04-17 Topic Title: Technologies to Defend Against Identity Theft Type Title: Type II (Prototype Technologies) Full Proposal Control Number: EB8A Proposal Title: Email Sender Authentication A companion proposal, Reputation System Clearinghouse (1RGT), is also being submitted under the same category and type. We request that these two proposals be read together. This proposal should be read first. This proposal was authored by Meng Weng Wong, Founder and Chief Technology Officer for Special Projects. He can be contacted at [email protected]. Meng Weng Wong IC Group, Inc. 1100 Vine St Ste C8 Philadelphia, PA 19107 December 15th 2004 EIN: 113236046 Central Contractor Registration: 3EKUCT Email Sender Authentication 2 EXECUTIVE SUMMARY Pobox.com aims to fight phishing by adding sender authentication “Phishing” is a class of high-tech scam that functionality to the Internet email system. First we will build a library uses fraudulent e-mail to deceive consum- ers into visiting fake replicas of familiar to implement a useful set of recently devised anti-forgery specifica- Web sites and disclosing their credit card tions, including ip-based approaches such as SPF and crypto-based numbers, bank account information, Social approaches such as DomainKeys.
    [Show full text]
  • Canit-PRO User's Guide
    CanIt-PRO User’s Guide for Version 10.2.5 AppRiver, LLC 13 September 2018 2 CanIt-PRO — AppRiver, LLC Contents 1 Introduction 13 1.1 Organization of this Manual.............................. 13 1.2 Definitions........................................ 14 2 The Simplified Interface 19 3 The My Filter Page 21 3.1 Sender Rules...................................... 21 3.2 The Quarantine..................................... 22 3.3 Online Documentation................................. 22 4 The CanIt-PRO Quarantine 23 4.1 Viewing the Quarantine................................. 23 4.1.1 Message Summary Display........................... 23 4.1.2 Sort Order.................................... 24 4.1.3 Message Body Display............................. 25 4.1.4 Summary of Links............................... 25 4.2 Message Disposition.................................. 25 4.2.1 Quick Spam Disposal.............................. 26 4.3 Reporting Phishing URLs................................ 27 4.4 Viewing Incident Details................................ 27 4.4.1 Basic Details.................................. 28 4.4.2 Address Information.............................. 29 4.4.3 History..................................... 29 4.4.4 Spam Analysis Report............................. 29 4.5 Viewing Other Messages................................ 30 4.6 Viewing Specific Incidents............................... 30 CanIt-PRO — AppRiver, LLC 3 4 CONTENTS 4.7 Searching the Quarantine................................ 30 4.8 Closed Incidents....................................
    [Show full text]
  • How to Make Sure Your Emails Land in Your Prospects' Inboxes
    How to Make Sure Your Emails Land in Your Prospects’ Inboxes How to Make Sure Your Emails Land in Your Prospects’ Inboxes | 1 Table of Contents Why Aren’t My Emails Getting Through? 3 Authentication 5 Permissions 7 Reputation 9 Sender Reputation 9 Cleanliness & Monitoring 10 List Source 10 New Domain Address Warming 11 Review Bounces 14 Monitoring Blacklists 15 Follow the Rules - CAN-SPAM, CASL, GDPR & CCPA 16 Engagement 17 Know Your Audience - Relevance, Frequency & Content Review 17 Unsubscribe Links 18 Conclusion 19 How to Make Sure Your Emails Land in Your Prospects’ Inboxes | 2 Why would my emails never make it to their destination? As we move further into the era of technology, email has become the primary source of professional communication. As a result, bad actors are doing whatever it takes to get you to view their emails. How many members of the Nigerian royal family have contacted you to transfer their fortune to your bank account? In response to more frequent attempts to phish, hack, and send spam, Internet Service Providers (ISPs) are doing everything they can to protect their customers from potentially unsolicited email, ! including blocking bulk email sends from new domains and internet protocol (IP) addresses. It’s important to remember that ISPs are always looking to protect their users (and investors). Because you’re sending emails to reach out to your prospects, these new measures have a direct impact on your ability to have your legitimate emails delivered to the inbox. How to Make Sure Your Emails Land in Your Prospects’ Inboxes | 3 Ultimately it is the practices of your company, and your engagement strategy, that determines whether or not your messages get through.
    [Show full text]
  • 2554 Netscape Communications Category: Standards Track March 1999
    Network Working Group J. Myers Request for Comments: 2554 Netscape Communications Category: Standards Track March 1999 SMTP Service Extension for Authentication Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (1999). All Rights Reserved. 1. Introduction This document defines an SMTP service extension [ESMTP] whereby an SMTP client may indicate an authentication mechanism to the server, perform an authentication protocol exchange, and optionally negotiate a security layer for subsequent protocol interactions. This extension is a profile of the Simple Authentication and Security Layer [SASL]. 2. Conventions Used in this Document In examples, "C:" and "S:" indicate lines sent by the client and server respectively. The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", and "MAY" in this document are to be interpreted as defined in "Key words for use in RFCs to Indicate Requirement Levels" [KEYWORDS]. 3. The Authentication service extension (1) the name of the SMTP service extension is "Authentication" (2) the EHLO keyword value associated with this extension is "AUTH" Myers Standards Track [Page 1] RFC 2554 SMTP Authentication March 1999 (3) The AUTH EHLO keyword contains as a parameter a space separated list of the names of supported SASL mechanisms. (4) a new SMTP verb "AUTH" is defined (5) an optional parameter using the keyword "AUTH" is added to the MAIL FROM command, and extends the maximum line length of the MAIL FROM command by 500 characters.
    [Show full text]