s and Anti-spam

Similar documents
Instructions Microsoft Outlook 2010 Page 1

Instructions Microsoft Outlook 2007 Page 1

Instructions Microsoft Outlook 2013 Page 1

Instructions Eudora OSE Page 1

Instructions Microsoft Outlook 2003 Page 1

Office 365: Secure configuration

SMTP Settings for Magento 2

Setting Up in Daycare Works Help. Version: 06/25/2013

Symantec Security. Setup and Configuration Guide

Best Practices. Kevin Chege

Trustwave SEG Cloud BEC Fraud Detection Basics

Choic Anti-Spam Quick Start Guide

Marketing 201. March, Craig Stouffer, Pinpointe Marketing (408) x125

Mail Assure. Quick Start Guide

SPF classic. Przemek Jaroszewski CERT Polska / NASK The 17th TF-CSIRT and FIRST joint Event, Amsterdam, January 2006

Mail Assure Quick Start Guide

SMTP Relay set up. Technical team

Important Information

Installation guide for Choic . Enterprise Edition. When Installing On The Same Server As: Microsoft s Exchange 2000 & 2003 Mail Servers

Franzes Francisco Manila IBM Domino Server Crash and Messaging

Installation Guide For Choic . Enterprise Edition. When Installing On The Same Server As: Microsoft s Exchange 5.5 Mail Server

WITH INTEGRITY

TrendMicro Hosted Security. Best Practice Guide

Getting Started 2 Logging into the system 2 Your Home Page 2. Manage your Account 3 Account Settings 3 Change your password 3

SPF (Sender Policy Framework)

Accessing Encrypted s Guide for Non-NHSmail users

Communicator. Branded Sending Domain July Branded Sending Domain

Frequently Asked Questions (FAQ)

to Stay Out of the Spam Folder

IBM Managed Security Services for Security

Step 2 - Deploy Advanced Security for Exchange Server

Appliance Installation Guide

WHITEPAPER BlueHornet. bluehornet.com

Ethical Hacking and. Version 6. Spamming

Canadian Anti-Spam Legislation (CASL)

Using Trustwave SEG Cloud with Exchange Online

Introduction to Antispam Practices

Canada s Anti-Spam Legislation (CASL) What it means for Advisors. Distributor Learning & Development

Office 365 Inbound and Outbound SMX configuration. 4 th January 2018

Account Customer Portal Manual

Beam Suntory Privacy Policy WEBSITE PRIVACY NOTICE

NSDA ANTI-SPAM POLICY

A Federal Agency Guide to Complying with Binding Operational Directive (BOD) 18-01

Handling unwanted . What are the main sources of junk ?

Error Codes have 3 Digits

How to Configure Esva for Office365

Canadian Anti-Spam Legislation (CASL)

Deliverability Terms

Setting up Microsoft Office 365

Privacy and Spam Policy Ten Tigers Grain Marketing Pty Ltd

ISOCNET Quarantine. User s Guide

Hallmark Solutions Limited PRIVACY NOTICE

Entering the China Market

1.1. Agreement means this document together with the Ignite General Terms and Conditions.

Forward set up. Technical team

Configuring Gmail (G Suite) with Cisco Cloud Security

DONE FOR YOU SAMPLE INTERNET ACCEPTABLE USE POLICY

WASPA Member (SP) Complaint Number #4674. Code of Conduct Version 5.7. Date of Adjudication 09/10/2008. Complaint

Mail Services SPAM Filtering

SSAC Public Meeting Paris. 24 June 2008

Untitled Page. Help Documentation

Guide To Navigating POPI

ADMA Briefing Summary March

S E R V E R C E N T R E

Glenwood Telecommunications, Inc. Acceptable Use Policy (AUP)

Version SurfControl RiskFilter - Administrator's Guide

Distributed-Application Security

It s still very important that you take some steps to help keep up security when you re online:

NWQ Capital Management Pty Ltd. Privacy Policy. March 2017 v2

Security Protection

Comendo mail- & spamfence

Bulletproof Strategies

Anti-Spoofing. Inbound SPF Settings

Office 365 Standalone Security

Using Trustwave SEG Cloud with Cloud-Based Solutions

IBM Managed Security Services (Cloud Computing) hosted and Web security - express managed security

Features & Highlights

, Rules & Regulations

Improving Newsletter Delivery with Certified Opt-In An Executive White Paper

Managing Spam. To access the spam settings in admin panel: 1. Login to the admin panel by entering valid login credentials.

Anti-Spam Processing at UofH

Installation & Configuration Guide Version 1.4

3 SECRETS OF UNSTOPPABLE DELIVERABILITY

Defining Which Hosts Are Allowed to Connect Using the Host Access Table

Delivery to the Big Four: AOL, Google, Microsoft, and Yahoo

Security and Privacy. Xin Liu Computer Science University of California, Davis. Introduction 1-1

Midstate Telephone & Midstate Communications. Acceptable Use Policy

MX Control Console. Administrative User Manual

Privacy Policy May 2018

Connecting to Mimecast

UCL Policy on Electronic Mail ( )

IGNITE HOSTED PREMIUM MAIL TERMS AND CONDITIONS OF SERVICE. 1. Definitions. 2. Services

Important Information

Comodo Comodo Dome Antispam MSP Software Version 2.12

Comodo Antispam Gateway Software Version 2.12

CASL Notice. About Allegis Group. Effective Date: January 1, 2017

Synology MailPlus Server Administrator's Guide. Based on MailPlus Server 1.4.0

Keystone Acceptable Use Policy

Sarri Gilman Privacy Policy

Update: 19 Dec One typical example of a scam

Transcription:

E-mails and Anti-spam Standard authentication AUTH method As the spammers become increasing aggressive more and more legit emails get banned as spam. When you send e-mails from your webcrm system, we use the webcrm servers to send e-mails with your own e-mail address inserted as the sender of the e-mail. Many anti-spam engines mark such e- mails as a potential spam risk because the server sending the e-mail is not the server normally used for sending your e-mails. 1. You send an e-mail from your webcrm system 2. The e-mail arrives at the receivers e-mail server 3. The receiver s e-mail server asks your e-mail server if webcrm may send e-mails on your behalf 4. If this is not the case, then the e-mail may be considered as spam Receiver s e-mail server? Your e-mail server Receiver Page 1 / 6

In your own interest webcrm enforce a policy to reduce the risk of your e-mails being considered as spam. It is important that your own e-mail server will permit webcrm servers to send e-mails on your behalf. To do this you need to define a so-called SPF record. This normally requires that you have your own e- mail domain. If your e-mail is for example an @hotmail e-mail address you should not send e-mails from webcrm. To publish that you permit sending your e-mails from the webcrm e-mail domain you need to have your Internet Service Provide create or modify the SPF record to include records from: spf.webcrm.com. Please refer to page 4 for technical details. As an alternative to SPF records you may be able to permit your own e-mail server to relay the e-mail messages sent from webcrm. If your security policies will permit relay then the webcrm servers can send the e-mails to your own e- mail server, and then your own e-mail server will send the emails on to the final receivers. It is recommended that you still create a SPF record for your own email server. To enable this, please provide us with the following information: E-mail domain or IP address to relay by The port to relay by If you want to apply encryption (TLS) To apply the standard authentication AUTH method, please also supply us with an account name (username) and password for your SMTP server. Page 2 / 6

Alternative method As an alternative to the AUTH method you can instead have an IT professional capable of configuring/enabling the relay in your firewall / e-mail server. We cannot assist you directly with this task. You must enable/permit webcrm to SMTP relay from the IP range: 194.150.113.1-194.150.113.99. Receiver s e-mail server? Your e-mail server Receiver Page 3 / 6

SPF records a technical note Sender Policy Framework (SPF) is an email validation system designed to prevent e-mail spam by detecting e-mail spoofing, a common vulnerability, by verifying sender IP addresses. SPF allows administrators to specify which hosts are allowed to send mail from a given domain by creating a specific SPF record (or TXT record) in the Domain Name System (DNS). Mail exchangers use the DNS to check that mail from a given domain is being sent by a host sanctioned by that domain's administrators. Sender Policy Framework is defined in IETF publication RFC 4408. To publish that you permit sending your e-mails from the webcrm e-mail domain you need to have your Internet Service Provide create or modify the SPF record to include records from: spf.webcrm.com SPF record formats do vary and you should consult your IT staff or Internet Service Provider for the exact format to use. Example text for SPF record permitting webcrm SMTP server as well as your own e-mail server: "v=spf1 ip4: 111.222.333.444 a mx include:spf.yourdomain.com include:spf.webcrm.com?all" "v=spf1 include:spf.webcrm.com ip4:111.222.333.444 -all" Where 111.222.333.444 is the IP for your own smtp server and your domain is yourdomain.com. Page 4 / 6

What else can you do? Even if you have a correct SPF record your emails may still be considered as spam depending on the content of the email. General Guidelines To Avoid Emails To Be Mistaken For Spam If you run a mailing list, or email newsletter that sends out numerous similar or identical messages, you may risk being accused of sending spam. If you are accused of spamming, your ISP may cancel your account, you may lose the hosting of your website. If possible, limit each email shot to 1000 emails. If your emails are being sent to people who did not sign up to receive them, or to people who may have signed up and forgotten, you may begin receiving spam complaints. If these complaints make it to your Internet Service Provider, some of the consequences mentioned above may result. If unwilling receivers of your email report it to an internet blacklist, you may have your site may blacklisted by thousands of other internet servers. If you add people to your list without their consent, you will often be labelled as a spammer. Spam doesn't necessarily have to be for bogus products and services. Your legitimate email newsletter may be considered spam simply because it was unsolicited. If your emails are all identical, with no personalized information whatsoever, these may be considered spam as well. Since spam is mass-emailed to tens of thousands of individuals, its content is usually completely general. If your correspondence contains no personalized or unique information, or appears to be "canned" it may be mistaken for spam. If you send emails to people on your mailing list that contain topics or information that are irrelevant to the original description of your mailing list, you may be considered a spammer. People who signed up for your list did so in order to receive pertinent information, if you wish to send them email on unrelated topics, you should ask their permission first. Also, if you send correspondence to people at a more frequent rate than you had specified when they signed up, this may be considered spamming as well. Page 5 / 6

What not to do: E-mail text with more than 76 characters per line. E-mails with text lines exceeding 76 characters in one line are likely to be considered as spam. Do not purchase email lists or so-called opt-in lists from companies claiming to have "thousands of legitimate email addresses". Most of these companies do not bother to check whether the addresses on their lists are valid and hardly ever ask for consent from their recipients. You will end up sending your mail to unwilling recipients and will be accused of spamming. Do not send unsolicited e-mails with an "opt-out" option and expect this to legitimize your e- mail. Users should not have to go through the trouble of opting out of a mailing list that they did not sign up for in the first place. Many internet users will also ignore the "opt-out" instructions because spammers use these to validate the e-mail addresses in their lists. Do not request a receipt of delivery for your mailing list. Many users consider this an invasion of privacy, and spammers also use this ploy for email verification. Do not use any spamming or harvesting software. This includes automated email programs, e- mail address guessing and verification programs, webpage spiders, Usenet harvesters, or any other unsolicited e-mail software. The use of these devices is universally attributed to spammers. Do not send numerous identical messages. If you are sending out multiple e-mails, attempt to personalize the subject and body of the messages so they are not completely general. Messages that appear "canned" are often considered spam. What you should do: Always DOUBLE VERIFY every e-mail address in your list. This means that upon receiving an e- mail address from an online form, or by any other means, you should send a brief confirmation e- mail stating that their email address was submitted, and asking them to confirm their registration in your mailing list. Keep track of where you receive every e-mail address on your list. This way, if there is ever a dispute or complaint, you can provide your members with a complete history of their subscription. When you keep track of where each e-mail address came from, you can identify where the "dirty" source was, and cease to use it. Keep your mailing list up to date. Make requested contact changes promptly, and do requested removals immediately. Personalize the subject and body of your e-mails. Although this may take more time, it adds a level of credibility and professionalism that will set you apart from spammers. State your terms clearly and stick to them. If you are going to send out an e-mail every week, make sure that your recipients are aware of this, and do not send out any more than that. If you are going to be sending e-mail about one specific topic, stick to this topic and do not send out unrelated material without prior permission. Page 6 / 6