Skip to main content

How to Avoid Sending Spam email?

Methods to Reduce Chances From Being Flagged As A Spammer

As spam filter settings become more strict due to the increase of spam emails, you need to make sure your email messages are not classified as being spammy. In some cases that's easier said than not.

To help out, below is a guide line of the common features of email messages that are blocked by most spam filters. Taking pre-cautions when composing messaging will increase the chances of getting your message delivered.

Avoid these common mistakes:

  • Using spammy phrases, like "Click here!" or "Once in a lifetime opportunity!"
  • Going crazy with exclamation points!!!!!!
  • USING ALL CAPS, WHICH IS LIKE YELLING IN EMAIL.
  • Excessive font coloring such as bright red, or green.
  • Subject starts with Free, GUARANTEED, Buy, dollar sign ($) or (money) amount, etc.
  • Sending nothing but one big image (with little or no text) in the message.
  • Designing HTML email in Microsoft Word, and exporting the code to HTML (that code is sloppy, and spam filters hate it).
  • If the email has three or more CAPITALIZED words in the Subject line or has no text within the subject line.
  • The email contains blank lines that make up a percentage of more than 70%.
  • Repeated, unnecessary double-quotation marks.
  • The body of the email message mentions Viagra, no prescription, online Pharmacy etc.
  • There are attempts to disguise words within the email.
  • From field and reply to are empty.
  • Subject (or other fields) contains G.a.p.p.y-T.e.x.t with lots of spaces or underscores.
  • Address contains "free".
  • Email contains an attached in the following formats: EXE BAT PIF etc (or DAT file Email sent from Apple Mac to PC issue).
  • Message is a saved web page.
  • Font colour is the same as the background (invisible text).

Sending Using HTML Format :


Here is a list of guidelines you should always follow when creating your email messages.

· If you’re using HTML emails, include a text part in the email as well, for recipients (and anti-spam checkers), and keep that text as close to the HTML copy as possible. The closer they’re related, the less likely your email will be seen as spam.

· Keep your message’s layout as simple as possible. Avoid complex formatting (yes, it will make it look better, but less people will receive it).

· Pay particular attention to your mailing’s subject: never use exclamation point (!), CAPITALIZATION, and words as “free”, “guaranteed”, and gappy text (t h i s i s g a p p y t e x t)

· Avoid generic salutation formulas as “Dear User”; it is even better to avoid salutation at all.

· If you’re using HTML emails, use high quality HTML emails. Don’t use tools which generate horrendous HTML (example: MS Word). They often leave signs behind (like empty tags, eg: ) which are generally found in spam. Unbalanced tags and invalid tags will also flag an email as spam. If you use a title, make sure the title is meaningful — the default titles generated by HTML tools are often used as spamsign.

· Don’t insert active components (javascript, ActiveX, plug-ins) in your message. If you need rich media content, just link to a media-rich page on your web site.

· Don’t insert too much graphic in your message. The less images you use the better you’ll message will get through.

· Avoid attaching files; use links to files hosted on a web server instead.

· Use email composition and mailing tools that work correctly. Well constructed emails (technically correct) can be readily identified as not-spam. Emails with missing MIME sections, invalid or missing message-ids, invalid or missing date headers, subject or other headers with unescaped unicode, etc., are frequently signs of spam.

· Avoid useless or needless encodings. Don’t use base-64 encoded text unless you need to.

· Don’t include a disclaimer that your email isn’t spam. Don’t claim compliance with some legal criteria, especially one which is not actually law in your country. Only spam needs to claim compliance: non-spam is supposed to already be in compliance.

· Use normal conversational language, be sure not to use excessive spacing and or capitalization on your subject.

· Do not use “cute” spellings, Don’t S.P.A.C.E out your words, don’t put str@nge |etters 0r characters into your emails.

· If you’re using HTML emails, do not use invisible web-bugs to track your emails. If you must track your emails and whether they’re read, use visible graphics as part of your email, not invisible graphics.

· Don’t include gratuitous references to spam subjects. Don’t talk about rolex watches, sexually oriented activities or drugs, or debt treatment, unless those topics directly relate to your email. And if they do, limit your email to one topic at a time. An email which mentions rolex watches, Viagra, porn, and debt all in one email will very possibly hit several rules that flag it as spam, even if everything else is clear.

· Don’t use tools used by spammers (i.e., advertised in spam).

· Use a well performing, well administered and trusted SMTP server. Most undeliverable mails come from poor SMTP services, which often lead to being blacklisted: make sure your SMTP service’s staff is ready to help if you are blacklisted by mistake.

· Make sure your privacy policy, including enforcement, and including query contact information, is easily found and clearly stated on your web site. It’s good to include this information (where to find this policy, contact information), in your emails. Again, people who need to find out whether you’re spammer will often look for that information: this will help you in staying out of blacklists.

· Be careful where you advertise, and be careful which advertisements you carry. If you advertise with companies that send out spam, your domains will be flagged as being related to spam. If you carry advertisements for those who spam, your domains will be flagged as being related to spam.

· Be careful which domains/companies you allow to advertise in your emails (if any). Allowing spammers to advertise will get your emails flagged by the URI blacklists. On the other hand, don’t advertise your domains with spammers — having your domain name listed in their spams can also get you flagged by some URI blacklists.

Comments

Popular posts from this blog

Connected and disconnected architecture in ADO.Net with Example

Connected Architecture of ADO.NET The architecture of ADO.net, in which connection must be opened to access the data retrieved from database is called as connected architecture. Connected architecture was built on the classes connection, command, datareader and transaction.  Connected architecture is when you constantly make trips to the database for any CRUD (Create, Read, Update and Delete) operation you wish to do. This creates more traffic to the database but is normally much faster as you should be doing smaller transactions. Disconnected Architecture in ADO.NET The architecture of ADO.net in which data retrieved from database can be accessed even when connection to database was closed is called as disconnected architecture. Disconnected architecture of ADO.net was built on classes connection, dataadapter, commandbuilder and dataset and dataview. Disconnected architecture is a method of retrieving a recor

HTTPHandler and HTTPModule in ASP.NET

If you want to implement pre-processing logic before a request hits the IIS resources. For instance you would like to apply security mechanism, URL rewriting, filter something in the request, etc. ASP.NET has provided two types of interception HttpModule and HttpHandler .   The web server examines the file name extension of the requested file, and determines which ISAPI extension should handle the request. Then the request is passed to the appropriate ISAPI extension.  For Example When an .aspx page is requested it is passed to ASP.Net page handler. Then Application domain is created and after that different ASP.Net objects like Httpcontext, HttpRequest, HttpResponse. HTTPModule: -    It's just like a filter. The Modules are called before and after the handler executes . -    HTTP Modules are objects which also participate the pipeline but they work before and after the HTTP Handler does its job, and produce additional services within the pipeline -  

ASP.NET Page Life Cycle with example

In this article, we are going to discuss the different methods and order they are executed during the load of an .aspx web page. Methods Description Page_PreInit Before page Initialization Page_Init Page Initialization LoadViewState View State Loading LoadPostData Postback Data Processing Page_Load Page Loading RaisePostDataChangedEvent PostBack Change Notification RaisePostBackEvent PostBack Event Handling Page_PreRender Page Pre Rendering Phase SaveViewState View State Saving Page_Render Page Rendering Page_Unload Page Unloading PreInit : The entry point of the page life cycle is the pre-initialization phase called “PreInit”. You can dynamically set the values of master pages and themes in this event. You can also dynamically create controls in this event.  Init : This event fires after each control h