<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.3.3" -->
<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/"
	>

<channel>
	<title>Email Network Security Blog</title>
	<link>http://www.emailnetworksecurityblog.com</link>
	<description>Blog About Email Network Security.</description>
	<pubDate>Sat, 15 Mar 2008 20:11:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
	<language>en</language>
			<item>
		<title>Message Recall: Not the Best Feature</title>
		<link>http://www.emailnetworksecurityblog.com/email-tips/message-recall-not-the-best-feature/03/15/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-tips/message-recall-not-the-best-feature/03/15/2008/#comments</comments>
		<pubDate>Sat, 15 Mar 2008 20:11:24 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Tips]]></category>

		<category><![CDATA[message recall]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/email-tips/message-recall-not-the-best-feature/03/15/2008/</guid>
		<description><![CDATA[Both Microsoft Exchange and IBM Lotus Notes (Domino) have a feature called &#8220;Message Recall&#8221;. They both have serious limitations and it is only under rare exceptions do they work. They ONLY work within the local mail system (not with messages to the internet, for example) and ONLY if the recipient has not read the original [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-tips/message-recall-not-the-best-feature/03/15/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Why Go Paperless? (For Your Business and Your Grandchildren)</title>
		<link>http://www.emailnetworksecurityblog.com/email-tips/why-go-paperless-for-your-business-and-your-grandchildren/03/04/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-tips/why-go-paperless-for-your-business-and-your-grandchildren/03/04/2008/#comments</comments>
		<pubDate>Tue, 04 Mar 2008 17:58:37 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Tips]]></category>

		<category><![CDATA[paperless office]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/uncategorized/why-go-paperless-for-your-business-and-your-grandchildren/03/04/2008/</guid>
		<description><![CDATA[Your office should go paperless. Why? Because you can save money and help make the planet cleaner. You care about your grandchildren don&#8217;t you? You want them to have trees to climb and shade to relax under and clean air to breath, right?
You can use modern technology (specifically email) to replace paper. Not only will [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-tips/why-go-paperless-for-your-business-and-your-grandchildren/03/04/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Blocking Port 25 to Reduce Spam and Protect Your Network</title>
		<link>http://www.emailnetworksecurityblog.com/email-security/blocking-port-25-to-reduce-spam-and-protect-your-network/02/28/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-security/blocking-port-25-to-reduce-spam-and-protect-your-network/02/28/2008/#comments</comments>
		<pubDate>Thu, 28 Feb 2008 19:06:54 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Security]]></category>

		<category><![CDATA[Network Security]]></category>

		<category><![CDATA[Spam Protection]]></category>

		<category><![CDATA[spam block port 25]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/email-security/blocking-port-25-to-reduce-spam-and-protect-your-network/02/28/2008/</guid>
		<description><![CDATA[If you have an email filtering service provider like Sentinare Messaging Solutions, Inc., then all your SMTP traffic should be coming from only the filtering provider and the filtering provider only. Therefore, you don&#8217;t have to allow direct port 25 (SMTP traffic) to your email server any more and you shouldn&#8217;t allow port 25 (SMTP) [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-security/blocking-port-25-to-reduce-spam-and-protect-your-network/02/28/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Why Not Use &#8220;mail.yourdomain.com&#8221; as the Name for Your Mail Server</title>
		<link>http://www.emailnetworksecurityblog.com/email-security/why-not-use-mailyourdomaincom-as-the-name-for-your-mail-server/02/26/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-security/why-not-use-mailyourdomaincom-as-the-name-for-your-mail-server/02/26/2008/#comments</comments>
		<pubDate>Tue, 26 Feb 2008 14:09:16 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Security]]></category>

		<category><![CDATA[Email Tips]]></category>

		<category><![CDATA[Network Security]]></category>

		<category><![CDATA[relay destination name]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/email-security/why-not-use-mailyourdomaincom-as-the-name-for-your-mail-server/02/26/2008/</guid>
		<description><![CDATA[Spammers will ignore MX records sometimes and use &#8220;mail.somedomainname.com&#8221; to relay spam to. If you have an off-site email filtering service provider and you set all your MX records to their server, all your mail should go to the off-site email filtering provider&#8217;s servers, according to the MX records, but this is not always the [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-security/why-not-use-mailyourdomaincom-as-the-name-for-your-mail-server/02/26/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Email Filtering Service: Using FQDN Versus an IP Address as Destination Relay</title>
		<link>http://www.emailnetworksecurityblog.com/email-security/email-filtering-service-using-fqdn-versus-an-ip-address-as-relay-destination/02/21/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-security/email-filtering-service-using-fqdn-versus-an-ip-address-as-relay-destination/02/21/2008/#comments</comments>
		<pubDate>Thu, 21 Feb 2008 21:38:51 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Security]]></category>

		<category><![CDATA[Spam Protection]]></category>

		<category><![CDATA[destination relay email filter]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/email-security/email-filtering-service-using-fqdn-versus-an-ip-address-as-relay-destination/02/21/2008/</guid>
		<description><![CDATA[Email filtering service providers like Sentinare Messaging Solutions accept mail via MX records, filter out spam and viruses, and then, using SMTP, relay the email to the &#8220;destination relay&#8221;, which is your mail server at your customer site. Typically you can configure the filtering service provider to relay to either a FQDN (Fully Qualified Domain [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-security/email-filtering-service-using-fqdn-versus-an-ip-address-as-relay-destination/02/21/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Auditing Data Systems and Why Your ISP/ASP Must Do This</title>
		<link>http://www.emailnetworksecurityblog.com/email-hosting/auditing-data-systems-and-why-your-ispasp-must-do-this/02/15/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-hosting/auditing-data-systems-and-why-your-ispasp-must-do-this/02/15/2008/#comments</comments>
		<pubDate>Fri, 15 Feb 2008 15:22:35 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Hosting]]></category>

		<category><![CDATA[system audit security]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/email-hosting/auditing-data-systems-and-why-your-ispasp-must-do-this/02/15/2008/</guid>
		<description><![CDATA[Many ISPs and ASPs have servers that are years old, with outdated and unmaintained software. This is a big problem for security because out of date software most certainly has security bugs that aren&#8217;t patched, rendering the server vulnerable to attack. Frequent system audits increase the reliability and security of any data system. They also [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-hosting/auditing-data-systems-and-why-your-ispasp-must-do-this/02/15/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>How to Display Email Headers in Popular Email Clients</title>
		<link>http://www.emailnetworksecurityblog.com/email-tips/how-to-display-email-headers-in-popular-email-clients/02/11/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-tips/how-to-display-email-headers-in-popular-email-clients/02/11/2008/#comments</comments>
		<pubDate>Mon, 11 Feb 2008 19:09:54 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Tips]]></category>

		<category><![CDATA[interent headers thunderbird outlook]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/email-tips/how-to-display-email-headers-in-popular-email-clients/02/11/2008/</guid>
		<description><![CDATA[We&#8217;ve covered email headers in the past two posts. Today we&#8217;ll cover how to display them in two popular email clients, Microsoft Outlook and Mozilla Thunderbird.
Here is how to display the internet header in Microsoft Outlook:

Right-mouse click on the email item for which you want to view the header.
Click &#8220;Message Options&#8221;.
At the bottom of the [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-tips/how-to-display-email-headers-in-popular-email-clients/02/11/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>How to Read Received Headers</title>
		<link>http://www.emailnetworksecurityblog.com/email-tips/how-to-read-received-headers/02/07/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-tips/how-to-read-received-headers/02/07/2008/#comments</comments>
		<pubDate>Thu, 07 Feb 2008 16:15:24 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Tips]]></category>

		<category><![CDATA[email header Received]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/email-tips/how-to-read-received-headers/02/07/2008/</guid>
		<description><![CDATA[Yesterday I wrote about Email Headers. Today I will zoom in on the Received headers. We will take an example header and break it down line by line. Consider the following set of received lines from an email header:

Received: from mx1.sentinare.net (lausanne [10.2.28.23])
  by mailbox01.sentinare.net (Postfix) with ESMTP id 051AE1DDA79C
  for &#60;chris.paul@rexconsulting.net&#62;; Thu, [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-tips/how-to-read-received-headers/02/07/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>How to Read Email Headers</title>
		<link>http://www.emailnetworksecurityblog.com/email-hosting/how-to-read-email-headers/02/06/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-hosting/how-to-read-email-headers/02/06/2008/#comments</comments>
		<pubDate>Wed, 06 Feb 2008 16:21:27 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Hosting]]></category>

		<category><![CDATA[Email Tips]]></category>

		<category><![CDATA[email header]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/email-hosting/how-to-read-email-headers/02/06/2008/</guid>
		<description><![CDATA[An email header can tell you a lot about an email. It tells you the date it was composed and the sender of course, but it also can tell you the path it took to get to your mailbox. According to the internet standard which describes email body format, RFC-2822:
Header fields are lines composed of [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-hosting/how-to-read-email-headers/02/06/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Multiple Layers of Defense for Email</title>
		<link>http://www.emailnetworksecurityblog.com/email-security/multiple-layers-of-defense-for-email/01/14/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-security/multiple-layers-of-defense-for-email/01/14/2008/#comments</comments>
		<pubDate>Mon, 14 Jan 2008 18:32:02 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Security]]></category>

		<category><![CDATA[Network Security]]></category>

		<category><![CDATA[Virus Email Protection]]></category>

		<category><![CDATA[multiple layers of defense]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/email-security/multiple-layers-of-defense-for-email/01/14/2008/</guid>
		<description><![CDATA[Relying on just one form of protection (one layer of defense) for a given service is less safe than having more than one layer of defense protecting that service. For example, there is an often repeated analogy for security plans that rely only on firewalls: This is the cookie that is hard on the outside [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-security/multiple-layers-of-defense-for-email/01/14/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>What Is an MX Record?</title>
		<link>http://www.emailnetworksecurityblog.com/email-hosting/what-is-an-mx-record/01/11/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-hosting/what-is-an-mx-record/01/11/2008/#comments</comments>
		<pubDate>Fri, 11 Jan 2008 18:18:35 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Hosting]]></category>

		<category><![CDATA[Email Tips]]></category>

		<category><![CDATA[MX records DNS]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/uncategorized/what-is-an-mx-record/01/11/2008/</guid>
		<description><![CDATA[An MX record is a public record in the global DNS (Domain Name System) that specifies which servers handle mail for a given domain name. MX records also specify the priority mail servers should be given in delivery attempts. Consider the following MX records:

yourdomain.com. IN   MX 10 mx1.sentinare.net.
yourdomain.com. IN   MX 20 [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-hosting/what-is-an-mx-record/01/11/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>The Non-Tangible Benefits of Email Filtering</title>
		<link>http://www.emailnetworksecurityblog.com/email-security/the-non-tangible-benefits-of-email-filtering/01/09/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-security/the-non-tangible-benefits-of-email-filtering/01/09/2008/#comments</comments>
		<pubDate>Wed, 09 Jan 2008 08:35:44 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Security]]></category>

		<category><![CDATA[Network Security]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/email-security/the-non-tangible-benefits-of-email-filtering/01/09/2008/</guid>
		<description><![CDATA[ The most tangible benefit to an off-site email filtering proxy service like Sentinare PostGuard is that users stop getting spam and viruses in their inbox&#8211; and your users will be very happy about that&#8211; but that is only 50% of the true benefit to using filtering service. By using an off-site email filtering service, [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-security/the-non-tangible-benefits-of-email-filtering/01/09/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Authenticated Outbound Email (SMTP-AUTH), &#8220;Port 25&#8243; and &#8220;Port 587&#8243;</title>
		<link>http://www.emailnetworksecurityblog.com/email-security/authenticated-outbound-email-smtp-auth-port-25-and-port-587/01/04/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-security/authenticated-outbound-email-smtp-auth-port-25-and-port-587/01/04/2008/#comments</comments>
		<pubDate>Fri, 04 Jan 2008 18:59:19 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Security]]></category>

		<category><![CDATA[Outbound Email]]></category>

		<category><![CDATA[14]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/uncategorized/authenticated-outbound-email-smtp-auth-port-25-and-port-587/01/04/2008/</guid>
		<description><![CDATA[ISP&#8217;s today are blocking port 25 from their users. This is a good thing. Originally mail servers didn&#8217;t distinguish between (SMTP) mail traffic from servers and SMTP mail traffic from users. With the rising use of public networks by spammers, a method was developed to segregate server mail traffic from client mail traffic.
First a brief [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-security/authenticated-outbound-email-smtp-auth-port-25-and-port-587/01/04/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Using Effective and Meaningful Subject Lines in Your Emails</title>
		<link>http://www.emailnetworksecurityblog.com/email-tips/using-effective-and-meaningful-subject-lines-in-your-emails/01/02/2008/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-tips/using-effective-and-meaningful-subject-lines-in-your-emails/01/02/2008/#comments</comments>
		<pubDate>Wed, 02 Jan 2008 15:52:07 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Tips]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/uncategorized/using-effective-and-meaningful-subject-lines-in-your-emails/01/02/2008/</guid>
		<description><![CDATA[The first two pieces of information a reader sees for each new email item is the sender and the subject. A good subject informs the reader as to the content of the message and helps in managing the inbox.
Here are some thoughts and tips for creating effective subjects:

Courtesy: A meaningful subject line clues the recipient [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-tips/using-effective-and-meaningful-subject-lines-in-your-emails/01/02/2008/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Security Experts List Email Filtering in 7 Security Tips</title>
		<link>http://www.emailnetworksecurityblog.com/email-security/security-experts-list-email-filtering-in-7-security-tips/12/27/2007/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-security/security-experts-list-email-filtering-in-7-security-tips/12/27/2007/#comments</comments>
		<pubDate>Fri, 28 Dec 2007 02:22:22 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Security]]></category>

		<category><![CDATA[Network Security]]></category>

		<category><![CDATA[11]]></category>

		<category><![CDATA[12]]></category>

		<category><![CDATA[13]]></category>

		<category><![CDATA[7]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/uncategorized/security-experts-list-email-filtering-in-7-security-tips/12/27/2007/</guid>
		<description><![CDATA[In an article titled &#8220;Seven surefire strategies to block network attacks&#8221;, Canadian security experts list email filtering as one of the most important security practices.
There are two benefits to using a provider like Sentinare Messaging Solutions.

Blocking spam and viruses: This is the most obvious benefit. Your users immediately will notice the difference in their mailbox [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-security/security-experts-list-email-filtering-in-7-security-tips/12/27/2007/feed/</wfw:commentRss>
		</item>
		<item>
		<title>IMAP and the Mobile Device</title>
		<link>http://www.emailnetworksecurityblog.com/email-hosting/imap-and-the-mobile-device/12/15/2007/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-hosting/imap-and-the-mobile-device/12/15/2007/#comments</comments>
		<pubDate>Sat, 15 Dec 2007 19:18:52 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Hosting]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/uncategorized/imap-and-the-mobile-device/12/15/2007/</guid>
		<description><![CDATA[All the smart phones out there today like the Apple Iphone and Nokia N-series have the ability to access email services. For receiving mail, there are two methods (or protocols): IMAP and POP3. It is important to know that IMAP is the newer and more capable protocol and the one you definitely want to use [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-hosting/imap-and-the-mobile-device/12/15/2007/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Password Security Strategy</title>
		<link>http://www.emailnetworksecurityblog.com/email-hosting/password-security-strategy/12/13/2007/</link>
		<comments>http://www.emailnetworksecurityblog.com/email-hosting/password-security-strategy/12/13/2007/#comments</comments>
		<pubDate>Thu, 13 Dec 2007 20:24:10 +0000</pubDate>
		<dc:creator>Sentinare Messaging Solutions</dc:creator>
		
		<category><![CDATA[Email Hosting]]></category>

		<category><![CDATA[Email Tips]]></category>

		<guid isPermaLink="false">http://www.emailnetworksecurityblog.com/uncategorized/password-security-strategy/12/13/2007/</guid>
		<description><![CDATA[Good email security means nothing without a good password security strategy. Too many people have simple passwords and use the same passwords in multiple places. With the rise of identity theft, there is grave danger in using the same easy password for every online login you use. Here is a simple and easy strategy to [...]]]></description>
		<wfw:commentRss>http://www.emailnetworksecurityblog.com/email-hosting/password-security-strategy/12/13/2007/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
