<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Bohack &#187; Spam</title>
	<atom:link href="http://www.bohack.com/category/spam/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bohack.com</link>
	<description>Check In and Tune Out!</description>
	<lastBuildDate>Sun, 08 Jan 2012 20:59:56 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Best Email Address Practices For Combating SPAM</title>
		<link>http://www.bohack.com/2009/01/best-email-address-practices-for-combating-spam/</link>
		<comments>http://www.bohack.com/2009/01/best-email-address-practices-for-combating-spam/#comments</comments>
		<pubDate>Fri, 02 Jan 2009 19:41:57 +0000</pubDate>
		<dc:creator>Bohack</dc:creator>
				<category><![CDATA[Spam]]></category>
		<category><![CDATA[email]]></category>

		<guid isPermaLink="false">http://www.bohack.com/?p=230</guid>
		<description><![CDATA[To kick the new year off right I am sharing a strategy to fight SPAM and email annoyances; it is a common sense approach to SPAM. This concept I can not take full credit from, although I can no longer find the original source to cite; so I will take credit for it now. If [...]<div class="addthis_toolbox addthis_default_style addthis_32x32_style" addthis:url='http://www.bohack.com/2009/01/best-email-address-practices-for-combating-spam/' addthis:title='Best Email Address Practices For Combating SPAM ' ><a class="addthis_button_preferred_1"></a><a class="addthis_button_preferred_2"></a><a class="addthis_button_preferred_3"></a><a class="addthis_button_preferred_4"></a><a class="addthis_button_compact"></a></div>]]></description>
			<content:encoded><![CDATA[<p>To kick the new year off right I am sharing a strategy to fight SPAM and email annoyances; it is a common sense approach to SPAM. This concept I can not take full credit from, although I can no longer find the original source to cite; so I will take credit for it now. If you can find the original cite, please post it in the comments; I only remember it was a security consortium and it was in their best practices (circa 1990).</p>
<p><span id="more-230"></span>So the secret is to take a tiered approach to email addresses. The three tiers of email are Personal, Semi-Private and Public. I have used this strategy for years and it works! Basically you need to create three email accounts and I will explain how to use them below. I recommend using Gmail; because you can have the other two accounts forward mail to the one you login to daily, so no need to check three separate accounts. You are creating a level of trust with each of the email addresses from most trusted to least trusted. You should choose passwords for the accounts the same way; hardest to easy. I will use fictitious name for the example below of John Doe.</p>
<p>First step is sign up for your uber secret &#8216;Personal&#8217; account. This account should be used for your banking, bills, blockbuster account and personal information; that you would never want to intermingle with relatives or friend&#8217;s conversations. The naming of the account should probably be something that a normal person (friend) would never figure out. Like John Doe would be best to sign up for an account like jedidoe@gmail.com. Make it personal by attaching a nickname you would like to have appended to your real name, but do not use something that is common knowledge about yourself. This account should also have a very hard password with letters, numbers, symbols and have a length of 14 characters or better.</p>
<p>Second email is your semi-personal account. This account will become your main account, it will be used for email directed to friends, family, etc&#8230; The name for this account for John Doe should be JohnDoe@gmail.com or Doe.John@gmail.com, but something that can be given out in normal conversation. Even nicknames are great&#8230; As long as it is not something inappropriate like DoeKiller@gmail.com or you probably won&#8217;t get an email from the girl you just met in passing. This account should have a somewhat secure password that you can type in quickly.</p>
<p>The last email is your SPAM account&#8230; The account you use for forums, signups, and anything that you know you&#8217;ll get SPAM from. This account will become the untrusted email account so anything sent to this email takes lowest priority and should be considered a scam. For this account you can create a pretty simple password, but do not use one from the other accounts.</p>
<p>The last step is to login to Gmail account the will be Personal and create a filter to forward mail to your semi-private acount. Since this account holds emails from banks you should probably forward and keep a copy. Next login to your public account and forward to your semi-private account all mail and select delete after forward. This account will basically create alot of mail and you don&#8217;t want it to pile up forever. Last step is login to your main semi-private account and create labels and filters by using the &#8216;To box&#8217; to sort by.</p>
<div class="addthis_toolbox addthis_default_style addthis_32x32_style" addthis:url='http://www.bohack.com/2009/01/best-email-address-practices-for-combating-spam/' addthis:title='Best Email Address Practices For Combating SPAM ' ><a class="addthis_button_preferred_1"></a><a class="addthis_button_preferred_2"></a><a class="addthis_button_preferred_3"></a><a class="addthis_button_preferred_4"></a><a class="addthis_button_compact"></a></div>]]></content:encoded>
			<wfw:commentRss>http://www.bohack.com/2009/01/best-email-address-practices-for-combating-spam/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

