<?xml version="1.0" encoding="UTF-8"?>
<posts type="array">
  <post>
    <body>&lt;p&gt;What&amp;#8217;s the best way of extending Mail.app with &lt;a href=&quot;http://www.gnupg.org/&quot;&gt;GPG&lt;/a&gt; functionalities?&lt;/p&gt;


	&lt;p&gt;Google gave me too many answers..&lt;/p&gt;</body>
    <excerpt nil="true"></excerpt>
    <id type="integer">77</id>
    <permalink>gpg-for-mail-app</permalink>
    <published-at type="datetime">2007-12-17T04:39:02-08:00</published-at>
    <title>GPG for Mail.app ?</title>
  </post>
  <post>
    <body>&lt;p&gt;After several years using the &lt;a href=&quot;http://en.wikipedia.org/wiki/Mbox&quot;&gt;mbox&lt;/a&gt; format on my personal email server, I decided that it was more than time to move to a better format: &lt;a href=&quot;http://en.wikipedia.org/wiki/Maildir&quot;&gt;Maildir&lt;/a&gt;.&lt;/p&gt;


	&lt;p&gt;The move was triggered when I started to have real problems consulting the boxes remotely over &lt;span class=&quot;caps&quot;&gt;IMAP&lt;/span&gt; (I use &lt;a href=&quot;http://www.dovecot.org/&quot;&gt;dovecot&lt;/a&gt;). The folders started to get messed up and the system was slow.&lt;/p&gt;


	&lt;p&gt;I always knew that maildir have clear advantages for my scenario, but I thought that I would have a hard time migrating my services and scripts. I was surprised how easy it was when I really got my hands dirty!&lt;/p&gt;


	&lt;p&gt;First, used a great Perl script &lt;a href=&quot;http://packages.debian.org/etch/mb2md&quot;&gt;mb2md&lt;/a&gt; to convert my existing mailboxes. Then changed some lines on my &lt;a href=&quot;http://www.postfix.org/&quot;&gt;Postfix&lt;/a&gt; configuration. Since I do my mail processing with the Perl module &lt;a href=&quot;http://search.cpan.org/perldoc?Email::Filter&quot;&gt;Email::Filter&lt;/a&gt;, it was just a mater of changing the paths, and it worked magically!&lt;/p&gt;


	&lt;p&gt;Never thought it was so easy&amp;#8230;. Oh, and dovecot now behaves correctly :-)&lt;/p&gt;


	&lt;p&gt;Goodbye mbox, you served me well&amp;#8230;&lt;/p&gt;</body>
    <excerpt nil="true"></excerpt>
    <id type="integer">71</id>
    <permalink>from-mbox-to-maildir</permalink>
    <published-at type="datetime">2007-11-27T06:40:49-08:00</published-at>
    <title>From mbox to maildir</title>
  </post>
  <post>
    <body>&lt;p&gt;Two days ago, I was playing with DNSStuff (&lt;a href=&quot;http://dnsstuff.com&quot;&gt;http://dnsstuff.com&lt;/a&gt;), doing some checks on my domain &amp;#8220;0x82&amp;#8221;. One of the tests was about some &lt;span class=&quot;caps&quot;&gt;SPF&lt;/span&gt; thing that I never heard about.&lt;/p&gt;


	&lt;p&gt;It told me someone could send an email from anywhere, and make it appear that it was send from my domain, making it legitimate (ok, I know that this doesn&amp;#8217;t make my email secure by himself). It told me that the solution was a &lt;a href=&quot;http://www.openspf.org/&quot;&gt;SPF thing&lt;/a&gt;.&lt;/p&gt;


	&lt;p&gt;I&amp;#8217;ve started reading about it, and realized that, although it seems a big hack (what? using the &lt;span class=&quot;caps&quot;&gt;TXT&lt;/span&gt; field of a domain to store data??), it could help and protect your email. For that I needed to change the &lt;span class=&quot;caps&quot;&gt;TXT&lt;/span&gt; record of my domain (try &lt;code&gt;dig TXT 0x82.com&lt;/code&gt; on your console).&lt;/p&gt;


	&lt;p&gt;Then, to make sure that the email I receive is tested against this specification, I had to configure my &lt;a href=&quot;http://postfix.org&quot;&gt;postfix&lt;/a&gt; SMTP server. If you search on google for &amp;#8220;postfix spf debian&amp;#8221; you will find nice tutorials on how to implement that. It was really simple!&lt;/p&gt;</body>
    <excerpt nil="true"></excerpt>
    <id type="integer">52</id>
    <permalink>protecting-your-domains-email-with-spf</permalink>
    <published-at type="datetime">2007-09-15T17:09:46-07:00</published-at>
    <title>Protecting your domains' email with SPF</title>
  </post>
</posts>
