<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Writing and reading E-mails</title>
	<atom:link href="http://alex.mamchenkov.net/2005/06/24/writing-and-reading-e-mails/feed/" rel="self" type="application/rss+xml" />
	<link>http://alex.mamchenkov.net/2005/06/24/writing-and-reading-e-mails/</link>
	<description>... mammoth cave ...</description>
	<lastBuildDate>Mon, 16 Jan 2012 21:30:07 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: educate</title>
		<link>http://alex.mamchenkov.net/2005/06/24/writing-and-reading-e-mails/comment-page-1/#comment-2402</link>
		<dc:creator>educate</dc:creator>
		<pubDate>Wed, 10 May 2006 22:05:15 +0000</pubDate>
		<guid isPermaLink="false">http://alex.mamtchenkov.net/2005/06/24/writing-and-reading-e-mails/#comment-2402</guid>
		<description>Thanks for the information, it was very helpful.</description>
		<content:encoded><![CDATA[<p>Thanks for the information, it was very helpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leonid</title>
		<link>http://alex.mamchenkov.net/2005/06/24/writing-and-reading-e-mails/comment-page-1/#comment-66</link>
		<dc:creator>leonid</dc:creator>
		<pubDate>Sun, 26 Jun 2005 18:53:23 +0000</pubDate>
		<guid isPermaLink="false">http://alex.mamtchenkov.net/2005/06/24/writing-and-reading-e-mails/#comment-66</guid>
		<description>Alex,

Fighting viruses and trojans is pretty simple these days.  Here is the algorithm:

1. Block incoming attachments based on file type on the SMTP level.  This is good for about 80% of all incoming nasty things - scr, exe, com, bat, vbs, doc, etc.  Configure your mail server to reject the emails containing these (and similar types).  The extreme case of this would be configuring the mail server to accept only specified attachment types - Zip files, PDFs, Jpeg, Gif, Tiff, Png, Txt, HTML.

2. Install two or more anti-virus scanners on the mail server from different vendors.  In this case, you will improve your chances a lot.  If some virus won&#039;t be in the database of one anti-virus scanner, it will probably be in the database of another.

3. Install anti-spam software on the mail server.  Sometimes it also denies viruses.

4. Install anti-virus scanner on each workstation.  Preferrable use a different vendor fro those used on the mail server.

5. Migrate all users to a proper email client.  For example, I&#039;ve heard that The Bat does not show HTML messages by default.  Also disable autopreview of attachments and autoopening of emails.

6. Write a company police that would forbid users from opening attachments unless they have personally requested them.  Educate your users about dangerous viruses and trojans.  This is good to be done on a regular basis.  For example, a &quot;Virus of the week&quot; article on the Intranet every Monday (start of the week is preferrable).

Our company has been following most of these steps and we haven&#039;t had a virus for a long time now.  And we do have A LOT OF EMAIL coming in.

NOw on to your other problem of properly formatted emails.

1. Migrate everyone to a proper email client.  For example, Thunderbird complains when one tries to send an email without a subject line, or when the signature is more than 4 lines.  Many other email clients can be configured to behave properly.

2. Educate your users on the subject of netiquette.  Regularly.  With example emails.

3. Configure your mail server to notify you of badly formatted outgoing emails.  You can then talk to each user with examples of his own messages and how to properly reformat them.</description>
		<content:encoded><![CDATA[<p>Alex,</p>
<p>Fighting viruses and trojans is pretty simple these days.  Here is the algorithm:</p>
<p>1. Block incoming attachments based on file type on the SMTP level.  This is good for about 80% of all incoming nasty things &#8211; scr, exe, com, bat, <acronym title="Visual Basic Script">VBS</acronym>, doc, etc.  Configure your mail server to reject the emails containing these (and similar types).  The extreme case of this would be configuring the mail server to accept only specified attachment types &#8211; Zip files, PDFs, Jpeg, Gif, Tiff, <acronym title="Portable Network Graphics">PNG</acronym>, Txt, <acronym title="HyperText Markup Language">HTML</acronym>.</p>
<p>2. Install two or more anti-virus scanners on the mail server from different vendors.  In this case, you will improve your chances a lot.  If some virus won&#8217;t be in the database of one anti-virus scanner, it will probably be in the database of another.</p>
<p>3. Install anti-spam software on the mail server.  Sometimes it also denies viruses.</p>
<p>4. Install anti-virus scanner on each workstation.  Preferrable use a different vendor fro those used on the mail server.</p>
<p>5. Migrate all users to a proper email client.  For example, I&#8217;ve heard that The Bat does not show <acronym title="HyperText Markup Language">HTML</acronym> messages by default.  Also disable autopreview of attachments and autoopening of emails.</p>
<p>6. Write a company police that would forbid users from opening attachments unless they have personally requested them.  Educate your users about dangerous viruses and trojans.  This is good to be done on a regular basis.  For example, a &#8220;Virus of the week&#8221; article on the Intranet every Monday (start of the week is preferrable).</p>
<p>Our company has been following most of these steps and we haven&#8217;t had a virus for a long time now.  And we do have A LOT OF EMAIL coming in.</p>
<p>NOw on to your other problem of properly formatted emails.</p>
<p>1. Migrate everyone to a proper email client.  For example, Thunderbird complains when one tries to send an email without a subject line, or when the signature is more than 4 lines.  Many other email clients can be configured to behave properly.</p>
<p>2. Educate your users on the subject of netiquette.  Regularly.  With example emails.</p>
<p>3. Configure your mail server to notify you of badly formatted outgoing emails.  You can then talk to each user with examples of his own messages and how to properly reformat them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alexander Mamtchenkov</title>
		<link>http://alex.mamchenkov.net/2005/06/24/writing-and-reading-e-mails/comment-page-1/#comment-63</link>
		<dc:creator>Alexander Mamtchenkov</dc:creator>
		<pubDate>Fri, 24 Jun 2005 15:19:39 +0000</pubDate>
		<guid isPermaLink="false">http://alex.mamtchenkov.net/2005/06/24/writing-and-reading-e-mails/#comment-63</guid>
		<description>I was more talking about recommendations to users in order to save them from being infected with viruses and other stuff. It is not something strict but more a king of an advice to them.

For example the rule &quot;do not open attachements from unknown senders&quot; would match my needs. I just wanted to have more than that [if possible and there is a use of it]

On the other hand I would like to give em an advice on how to compose emails in order to make people on the other side read it [for instance: &quot;always give a meaningfull subject to email&quot; since many times I see mails comming even without any subject].

So, once again, this is not to restrict users, but to help them avoid doing stupid things and reduce the amount of headaich of IT :)</description>
		<content:encoded><![CDATA[<p>I was more talking about recommendations to users in order to save them from being infected with viruses and other stuff. It is not something strict but more a king of an advice to them.</p>
<p>For example the rule &#8220;do not open attachements from unknown senders&#8221; would match my needs. I just wanted to have more than that [if possible and there is a use of it]</p>
<p>On the other hand I would like to give em an advice on how to compose emails in order to make people on the other side read it [for instance: "always give a meaningfull subject to email" since many times I see mails comming even without any subject].</p>
<p>So, once again, this is not to restrict users, but to help them avoid doing stupid things and reduce the amount of headaich of IT :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lev</title>
		<link>http://alex.mamchenkov.net/2005/06/24/writing-and-reading-e-mails/comment-page-1/#comment-62</link>
		<dc:creator>lev</dc:creator>
		<pubDate>Fri, 24 Jun 2005 11:17:27 +0000</pubDate>
		<guid isPermaLink="false">http://alex.mamtchenkov.net/2005/06/24/writing-and-reading-e-mails/#comment-62</guid>
		<description>I most like &quot;Never open the emails that came from unknown sources.&quot;  Except tech support,  receptionists etc. 

Your &quot;Never open attachments that were sent to you without your own request.&quot; good for every one :)</description>
		<content:encoded><![CDATA[<p>I most like &#8220;Never open the emails that came from unknown sources.&#8221;  Except tech support,  receptionists etc. </p>
<p>Your &#8220;Never open attachments that were sent to you without your own request.&#8221; good for every one :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leonid</title>
		<link>http://alex.mamchenkov.net/2005/06/24/writing-and-reading-e-mails/comment-page-1/#comment-61</link>
		<dc:creator>leonid</dc:creator>
		<pubDate>Fri, 24 Jun 2005 09:05:58 +0000</pubDate>
		<guid isPermaLink="false">http://alex.mamtchenkov.net/2005/06/24/writing-and-reading-e-mails/#comment-61</guid>
		<description>Lev,

Regarding your filtering techniques - it is a very personal thing.  Often it also depends a lot on the kind and quantity of messages that you are getting.

Two examples:

1. Technical support personnel.  These guys mostly get emails from unknown senders. A question from this user, and a request from that user.  They usually don&#039;t have long discussions either.  Sender-based folders would be a nightmare.  You&#039;ll get hundreds of new folders per day.

2. CEO or other management.  These people might be getting emails from the one source only - their personall assistants.  No need to move it to sender-based folders again, since all mail will end up in the single folder.

The best approach for the company is to provide employees with enough tools to process their email according to their likings.  If someone wants a billion folders - let him have them.  If someone wants all his mail in the Inbox - amen to that.  As long as employees are productive and can keep up with their correspondence - stay out of it.

:)</description>
		<content:encoded><![CDATA[<p>Lev,</p>
<p>Regarding your filtering techniques &#8211; it is a very personal thing.  Often it also depends a lot on the kind and quantity of messages that you are getting.</p>
<p>Two examples:</p>
<p>1. Technical support personnel.  These guys mostly get emails from unknown senders. A question from this user, and a request from that user.  They usually don&#8217;t have long discussions either.  Sender-based folders would be a nightmare.  You&#8217;ll get hundreds of new folders per day.</p>
<p>2. CEO or other management.  These people might be getting emails from the one source only &#8211; their personall assistants.  No need to move it to sender-based folders again, since all mail will end up in the single folder.</p>
<p>The best approach for the company is to provide employees with enough tools to process their email according to their likings.  If someone wants a billion folders &#8211; let him have them.  If someone wants all his mail in the Inbox &#8211; amen to that.  As long as employees are productive and can keep up with their correspondence &#8211; stay out of it.</p>
<p>:)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leonid</title>
		<link>http://alex.mamchenkov.net/2005/06/24/writing-and-reading-e-mails/comment-page-1/#comment-60</link>
		<dc:creator>leonid</dc:creator>
		<pubDate>Fri, 24 Jun 2005 09:00:09 +0000</pubDate>
		<guid isPermaLink="false">http://alex.mamtchenkov.net/2005/06/24/writing-and-reading-e-mails/#comment-60</guid>
		<description>Lev,

lots of companies have policies regarding computer usage in general and email communications in particular.  Enforcing the policy is another issue altogether.  Of course, there are ways to bypass certain rules set by the policy.  But the purpose of the policy is to guide users to do the right thing.

For example, the company policy might say something like: &quot;Never open attachments in the emails that came from unknown sources.&quot; And: &quot;Never open attachments that were sent to you without your own request.&quot;  In this situation, you can&#039;t actually enforce the policy.  The decision of opening or not opening of the attachment is up to the user.  But if the opens some stupid attachment which passed through the antivirus software and infects half of the internal network - he will be held responsible.

Other examples of company policies might include:
- disclaimers in the signatures (this can actually be done automatically)
- disclosing of confidential information (can&#039;t be enforced effectively)
- mass mailings (can be controlled automatically to a certain degree)
- &quot;politeness&quot; level and stuff like that to the outside world (can&#039;t be enforced)
- different attachment rules, like outgoing file formats, sizes, language encodings, etc...</description>
		<content:encoded><![CDATA[<p>Lev,</p>
<p>lots of companies have policies regarding computer usage in general and email communications in particular.  Enforcing the policy is another issue altogether.  Of course, there are ways to bypass certain rules set by the policy.  But the purpose of the policy is to guide users to do the right thing.</p>
<p>For example, the company policy might say something like: &#8220;Never open attachments in the emails that came from unknown sources.&#8221; And: &#8220;Never open attachments that were sent to you without your own request.&#8221;  In this situation, you can&#8217;t actually enforce the policy.  The decision of opening or not opening of the attachment is up to the user.  But if the opens some stupid attachment which passed through the antivirus software and infects half of the internal network &#8211; he will be held responsible.</p>
<p>Other examples of company policies might include:<br />
- disclaimers in the signatures (this can actually be done automatically)<br />
- disclosing of confidential information (can&#8217;t be enforced effectively)<br />
- mass mailings (can be controlled automatically to a certain degree)<br />
- &#8220;politeness&#8221; level and stuff like that to the outside world (can&#8217;t be enforced)<br />
- different attachment rules, like outgoing file formats, sizes, language encodings, etc&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: leonid</title>
		<link>http://alex.mamchenkov.net/2005/06/24/writing-and-reading-e-mails/comment-page-1/#comment-59</link>
		<dc:creator>leonid</dc:creator>
		<pubDate>Fri, 24 Jun 2005 08:52:48 +0000</pubDate>
		<guid isPermaLink="false">http://alex.mamtchenkov.net/2005/06/24/writing-and-reading-e-mails/#comment-59</guid>
		<description>Alex,

company policies are usually set for different reasons.  Antivirus protection is usually done on the server.  &quot;Nice messages&quot; are not at all a concern in the modern business world.

Company policies are set to minimize the support.  Imagine having 40,000 users on the internal network with every one of them having his own email client with custom settings.  In case something breaks it will be a nightmare to troubleshoot.  It is also difficult to teach employees to use the system when there are no guidelines.

It is not very clear what kind of rules you are looking for.  If you need guidelines for writing nice emails, than Google for &quot;netiquette&quot;.  It covers things like quoting, signatures, proper subjects, attribution, and the like.</description>
		<content:encoded><![CDATA[<p>Alex,</p>
<p>company policies are usually set for different reasons.  Antivirus protection is usually done on the server.  &#8220;Nice messages&#8221; are not at all a concern in the modern business world.</p>
<p>Company policies are set to minimize the support.  Imagine having 40,000 users on the internal network with every one of them having his own email client with custom settings.  In case something breaks it will be a nightmare to troubleshoot.  It is also difficult to teach employees to use the system when there are no guidelines.</p>
<p>It is not very clear what kind of rules you are looking for.  If you need guidelines for writing nice emails, than Google for &#8220;netiquette&#8221;.  It covers things like quoting, signatures, proper subjects, attribution, and the like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lev</title>
		<link>http://alex.mamchenkov.net/2005/06/24/writing-and-reading-e-mails/comment-page-1/#comment-58</link>
		<dc:creator>lev</dc:creator>
		<pubDate>Fri, 24 Jun 2005 08:22:10 +0000</pubDate>
		<guid isPermaLink="false">http://alex.mamtchenkov.net/2005/06/24/writing-and-reading-e-mails/#comment-58</guid>
		<description>I don&#039;t know the rules and never heard about some rules like that. And I cannot imagine how to make some. Do not read mails with subject XXX, enlarge you penis, girl, Hi! ... etc?

But I can recommend my rules (it works). Move every known sender to separate folder and one folder for recent connections. Others mails have to be annihilated. 

On company level needs redirect common email to receptionist (poor thing)</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know the rules and never heard about some rules like that. And I cannot imagine how to make some. Do not read mails with subject XXX, enlarge you penis, girl, Hi! &#8230; etc?</p>
<p>But I can recommend my rules (it works). Move every known sender to separate folder and one folder for recent connections. Others mails have to be annihilated. </p>
<p>On company level needs redirect common email to receptionist (poor thing)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 1/11 queries in 0.009 seconds using disk: basic
Object Caching 476/477 objects using disk: basic

Served from: alex.mamchenkov.net @ 2012-02-08 14:57:31 -->
