<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://www.easyweb.co.uk">
<channel>
 <title>easyweb.co.uk - emkay</title>
 <link>http://www.easyweb.co.uk/taxonomy/term/58/0</link>
 <description></description>
 <language>en</language>
<item>
 <title>New Webmail System</title>
 <link>http://www.easyweb.co.uk/new-webmail-system</link>
 <description>&lt;p&gt;Because I&#039;m working away from home at client site much of the time, and un-snooped access to my home email is A Good Thing&amp;trade; to have, setting up secure webmail was a priority for me when I moved to hosting my own email setup. &lt;/p&gt;
&lt;p&gt;I&#039;ve been using &lt;a href=&quot;http://www.squirrelmail.org/&quot;&gt;SquirrelMail&lt;/a&gt; for pretty much all that time - having a system that I can keep up to date using Debian&#039;s &lt;code&gt;apt-get&lt;/code&gt; management tools is a strong incentive. &lt;/p&gt;
&lt;p&gt;But I never really liked it - the interface is extremely clunky, and uses &lt;a href=&quot;http://evolt.org/node/293&quot;&gt;frames&lt;/a&gt;, which is a &lt;em&gt;particular&lt;/em&gt; hate of mine. Recently though, improved Open Source webmail interfaces have been coming along like buses, no doubt inspired by the success of &lt;a title=&quot;...which I&#039;m still the only geek on the planet not to use&quot; href=&quot;gmail.google.com/&quot;&gt;Gmail&lt;/a&gt;. &lt;/p&gt;
&lt;p&gt;One&#039;s so good, I installed it for a test, and liked it &lt;em&gt;so&lt;/em&gt; much, I repointed my webmail domain at it within 5 minutes. &lt;/p&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://www.easyweb.co.uk/new-webmail-system&quot; dc:identifier=&quot;http://www.easyweb.co.uk/new-webmail-system&quot; dc:title=&quot;New Webmail System&quot; trackback:ping=&quot;http://www.easyweb.co.uk/trackback/104&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://www.easyweb.co.uk/folksonomy/things/a-good-thing-tm">A Good Thing (tm)</category>
 <category domain="http://www.easyweb.co.uk/taxonomy/term/56">email</category>
 <category domain="http://www.easyweb.co.uk/taxonomy/term/58">emkay</category>
 <category domain="http://www.easyweb.co.uk/taxonomy/term/55">hosting</category>
 <pubDate>Fri, 24 Feb 2006 20:36:08 +0000</pubDate>
</item>
<item>
 <title>Greylisting - Another Spam Barrier</title>
 <link>http://www.easyweb.co.uk/Members/martin/blog/blog_post.2005-05-09.6875214849</link>
 <description>&lt;p&gt;Having had previous success with the Great Wall of Spam and DSPAM, I was still a bit annoyed by the amount of spam making it to the DSPAM quarantine, and so to be periodically scanned and a small number of false positives permitted through.&lt;/p&gt;
&lt;p&gt;
I&#039;d been hearing a bit about Greylisting, and &lt;a href=&quot;http://new.netend.org/&quot;&gt;Mike&lt;/a&gt; had had some good results with it, so thought I&#039;d give it a go. A wee mail SNAFU last week was the trigger, and I installed &lt;a href=&quot;http://www.jonatkins.com/qgreylist/&quot;&gt;qgreylist&lt;/a&gt; as a layer between IP blocking and DSPAM.&lt;/p&gt;
&lt;p&gt;
The way it works is like this: &lt;acronym title=&quot;Simple Mail Transport Protocol - the standard protocol for transferring mail between hosts&quot;&gt;SMTP&lt;/acronym&gt; is designed to be tolerant of downtime of the recipient mailhost. So if a sending hosts discovers a problem, it&#039;ll wait a bit, then try again (and if it still has a problem, will wait for a longer time and try again - repeat for a few days until finally giving up). However, spam-sending software is designed for maximum volume throughput, not maximum %age reaching destination, both for not sweating the small stuff reasons, and because spam-senders tend to get blackholed within a few hours. So generally, it doesn&#039;t follow this part of the SMTP protocol.&lt;/p&gt;

&lt;p&gt;
So what happens when you deliberately cause a temporary problem to &lt;em&gt;every&lt;/em&gt; piece of mail? Spam generally doesn&#039;t get repeated - it disappears before reaching your &lt;acronym title=&quot;Mail Transfer Agent&quot;&gt;MTA&lt;/acronym&gt;. As long as you keep a track of mailservers that have tried to send you mail, and accept mail the second time around, real mail still gets through.
&lt;/p&gt;
&lt;p&gt;
The results are impressive: my average 60-80 spams a day has been cut to around 10. Checking the DSPAM quarantine is no longer a nightmare if you leave it a few days. And as far as I know, no real mail has been lost.
&lt;/p&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://www.easyweb.co.uk/Members/martin/blog/blog_post.2005-05-09.6875214849&quot; dc:identifier=&quot;http://www.easyweb.co.uk/Members/martin/blog/blog_post.2005-05-09.6875214849&quot; dc:title=&quot;Greylisting - Another Spam Barrier&quot; trackback:ping=&quot;http://www.easyweb.co.uk/trackback/26&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://www.easyweb.co.uk/taxonomy/term/58">emkay</category>
 <category domain="http://www.easyweb.co.uk/taxonomy/term/10">mates</category>
 <category domain="http://www.easyweb.co.uk/taxonomy/term/57">spam</category>
 <pubDate>Mon, 09 May 2005 21:30:48 +0000</pubDate>
</item>
</channel>
</rss>
