I decided to go with a retro 80s theme. The subject fell into place when I was browsing for kitsch: the Rubik’s Cube. Even better was the fact that nine squares (3×3) exactly fits the spelling of DRE-AMH-OST. To finish the design I needed something to indicate, beyond any question of doubt, that this shirt was sent back to the future from the 1980s. A word often used to describe a nerd was “dweeb” which seems to have lost its vogue. All the elements of a radical t-shirt came into place.

What Works?

If the company was named “Dreamshost” I would either wrap the text to another side or move on. The nine-letter coincidence worked in my favor. There’s very little that can’t be identified with the 80s here. The light gray boundary around the design allows for black or white t-shirts to be used without diminishing the impact of the design.

What Failed?

It’s not immediately clear this is a retro design. The individual elements are there but there’s nothing in your face to remind you it’s a retro t-shirt. It also doesn’t tie-in the 62nd birthday or anniversary or whatever Dreamhost is celebrating. But being ironic isn’t representative of the 1980s – that’s something the 00s can claim.

Although DH currently supports SA, it is applied to your entire domain. To further complicate matters, DH upgraded to Debian Linux “Sarge” and it caused compatibility issues with the Bayesian database files; these are read/write files created using a Perl library. The next best alternative is to store those Bayes tokens in a MySQL database. By using SA’s Bayesian filtering you stand a much greater chance of eliminating your junk mail, and MySQL seems to circumvent the problem mentioned earlier.

Update: changes to Dreamhost’s network architecture require amendments to this procedure. Please reference my updated tutorial for more information.

A few assumptions before we get started…

• You have a basic understanding of Linux.
• You have an active DH account.
• You have access to the DH Panel.
• The %> notation indicates what you should type at the command prompt.
• The <Valid URL for: FileXYZ> notation indicates you need to insert a URL that points to the file in question.

1. Disable all keyword and junk mail filtering via the Dreamhost Panel. The Panel modifies your .procmailrc file and later we will be making changes to it and other files in your root directory.




2. Log in to the account that will be using SpamAssassin. You will be doing most of the work from the shell. Having a browser window open to the DH Panel would also be a good idea.
3. Download SpamAssassin 3.1.0. The 3.1.0 distribution can be obtained from the SA home page. Be sure to get the tar.gz format. Using this command will download it to your home directory. Type the following:

   %> cd ~
   %> wget <Valid URL for: Mail-SpamAssassin-3.1.0.tar.gz>
   

4. Extract the SpamAssassin archive. You must now extract the files to prepare for installation. Be sure the tar.gz file is in your root directory. Type the following:

   %> tar xvfz Mail-SpamAssassin-3.1.0.tar.gz
   %> cd Mail-SpamAssassin-3.1.0
   

5. Make the SpamAssassin files. This step is found in the INSTALL file under the heading “Installing SpamAssassin for Personal Use (Not System-Wide).” Each step takes some processing time, so please be patient. It will place your configuration files in ~/saetc and binaries in ~/sausr. Type the following at the command prompt:

   %> perl Makefile.PL PREFIX=~/sausr SYSCONFDIR=~/saetc
   %> make
   %> make install
   

6. Create a directory for spam rules. This directory provides a location for all of your procmail-related rules. Type the following at the command prompt:

   %> cd ~
   %> mkdir procmail
   %> cd procmail
   

7. Create the spam.rc file in your procmail folder. The spam.rc file will tell SA where to place junk mail and where to find associated rules for filtering. I have set up a rule to sort all spam into SquirrelMail’s Spam folder. Thus, it is not downloaded by my POP3 client. Type the following at the command prompt and insert the text shown:

   %> pico spam.rc
   
   #=================================================
   # spam.rc should be located in ~/procmail
   
   # Send e-mail to SpamAssassin if less than 500kB in size
   :0fw
   * < 500000
   | $HOME/sausr/bin/spamassassin
   
   # Delete all spam with a score of 8 or higher
   :0
   * ^X-Spam-Level: ********
   /dev/null
   
   # Move suspected spam into a separate folder
   :0:
   * ^X-Spam-Status: Yes
   .Spam/
   #=================================================
   

8. Create the .forward.postfix file in your root directory. Type the following at the command prompt and insert the text shown:

   %> cd ~
   %> pico .forward.postfix
   
   
   #==========================================
   #.forward.postfix should be located in ~
   "| /usr/bin/procmail -t"
   #==========================================
   

9. Modify the .procmailrc file in your root directory. This step edits the file that specifies which rules are applied to your e-mail. You want to reference the spam.rc file you already created. Type the following at the command prompt and modify the file as shown:

   %> mv .procmailrc .procmailrc.bak
   %> pico .procmailrc
   
   
   #=======================================
   # .procmailrc should be located in ~
   
   # Directory for procmail-related files
   PMDIR=$HOME/procmail
   
   # This is the message directory
   MAILDIR=$HOME/Maildir
   
   # procmail will use spam.rc for rules
   INCLUDERC=$PMDIR/spam.rc
   
   # Send everything else to Maildir
   :0
   $HOME/Maildir/
   #=======================================
   

10. Install modules necessary to enable DNS tests. Although DNS-based tests are not necessary for SA to work, it’s another great feature that helps to reduce spam. You’ll need the Net::IP dependency before installing Net::DNS. DH currently has this installed but the version is insufficient for SA to run correctly. Type the following at the command prompt:

    %> cd ~
    %> wget <Valid URL for: Net-IP-1.24.tar.gz>
    %> wget <Valid URL for: Net-DNS-0.53.tar.gz>
    %> tar xvfz Net-IP-1.24.tar.gz
    %> tar xvfz Net-DNS-0.53.tar.gz
    %> export PERL5LIB=/home/your_username/sausr/share/perl/5.8.4
    %> cd Net-IP-1.24
    %> perl Makefile.PL PREFIX=~/sausr
    %> make
    %> make install
    %> cd ~/Net-DNS-0.53
    %> perl Makefile.PL PREFIX=~/sausr
    %> make
    %> make install
    %> ln -s ~/sausr/lib/perl/5.8.4/Net/* ~/sausr/share/perl/5.8.4/Net
    

11. Send yourself an e-mail to check the installation. Your installation should be working properly. Be sure to check the e-mail headers for “X-Spam-Checker-Version: SpamAssassin 3.1.0″ This means your local copy of SA is working.
12. Create a MySQL database for SA. Go to the Goodies, MySQL link on the DH Panel. The username/password are examples. For security reasons, do not use the following. I used these only to complete the guide. Remember these settings because you’ll be using them later. After DH has set-up your database you will see it added to your list. Proceed to the next step.
13. Create the database tables necessary for SA. Doing this step will create all the necessary tables used by SA for user preferences and the Bayes tokens. I’m not currently using the database for my preferences but doing this step now would make it easier later. Type the following at the command prompt and enter your database password as prompted:

    %> cd ~/Mail-SpamAssassin-3.1.0/sql
    %> mysql -h spam.sa.com -u spam_user -p MySpamDB < userpref_mysql.sql
    %> mysql -h spam.sa.com -u spam_user -p MySpamDB < bayes_mysql.sql
    %> mysql -h spam.sa.com -u spam_user -p MySpamDB < awl_mysql.sql
    

14. Modify the local.cf file. Everything is set-up to use Bayesian filtering but it’s not enabled by default. Type the following at the command prompt and add the lines indicated:

    %> cd ~/saetc/mail/spamassassin
    %> pico local.cf
    
    
    #===================================================
    # These lines must be in your local.cf file
    
    # Tell SA to use Bayesian filtering
    use_bayes 1
    
    # Tell SA to use a MySQL database for tokens
    bayes_store_module  Mail::SpamAssassin::BayesStore::MySQL
    bayes_sql_dsn       DBI:mysql:MySpamDB:spam.sa.com
    bayes_sql_username  spam_user
    bayes_sql_password  itsasecret
    
    user_scores_dsn           DBI:mysql:MySpamDB:spam.sa.com
    user_scores_sql_username  spam_user
    user_scores_sql_password  itsasecret
    
    #===================================================
    

15. Modify the user_prefs file. The user_prefs file is where you should add any white or black listed e-mail addresses. The MySQL database can store this information but I haven’t integrated it with SquirrelMail…yet. These preferences are optional but I believe they lead to greater reliability when SA assigns a score to an e-mail. Type the following at the command prompt and add the lines indicated:

    %> pico ~/.spamassassin/user_prefs
    
    
    #===================================================
    # These lines should be in your user_prefs file
    
    # Do not autolearn from Bayes
    bayes_auto_learn 0
    
    # Do not autowhitelist e-mail addresses
    use_auto_whitelist 0
    
    # Bayes will ignore these headers
    bayes_ignore_header X-Virus-Scanned
    bayes_ignore_header X-Spam-Status
    bayes_ignore_header X-Spam-Level
    bayes_ignore_header X-Spam-Flag
    
    #===================================================
    

16. Create a script for training SA. This will vastly simply your life so training SA becomes almost automatic. The script is capable of training for spam or ham, depending upon the command line argument. If training on spam, it will delete all the messages when it’s done. Type the following at the command prompt and insert the text shown:

    %> echo > ~/salearn.bat
    %> chmod 744 ~/salearn.bat<br>
    %> pico ~/salearn.bat
    
    
    echo '========================================='
    TESTED=false
    if [ "$1" ]
    then
      if [ $1 = "spam" ]
      then
        TESTED=true
        ~/sausr/bin/sa-learn -V
        echo '-----------------------------------------'
        echo Learning what is SPAM...
        ~/sausr/bin/sa-learn --spam ~/Maildir/.Spam/cur
        rm -f ~/Maildir/.Spam/cur/*
        echo All messages from your Spam folder were deleted.
      elif [ $1 = "ham" ]
      then
        TESTED=true
        ~/sausr/bin/sa-learn -V
        echo '-----------------------------------------'
        echo Learning what is HAM...
        ~/sausr/bin/sa-learn --ham ~/Maildir/cur
      fi
    
      if [ $TESTED = true ]
      then
        echo '-----------------------------------------'
        echo Summary statistics of Bayes database...
        ~/sausr/bin/sa-learn --dump magic
        echo '-----------------------------------------'
      fi
    else
      echo Enter one argument:  [ham | spam]
    fi
    echo '========================================='
    

17. Allow spam to accumulate in your Spam folder and train SA. SpamAssassin gets even better after training it with several thousand spam messages. It assigns a statistical probability to certain words and characteristics of mail you have designated as junk. When your Spam folder is getting full type the following at the command prompt:

    %> ~/salearn.bat spam
    %> ~/salearn.bat ham
    

18. Create a crontab job to run your script. You have a script but you need to execute it with regularity. That’s what crontab is used to do. You could have it doing lots of other chores like emptying the Trash folder, but I will leave the extras to you. After the script executes you are sent an e-mail with a summary of what happened. The script will execute 10 minutes after midnight every Sunday. Type the following at the command prompt and add the text listed:

    %> crontab -e
    
    10 0 * * 7 $HOME/salearn.bat spam
    

19. Delete the temporary SpamAssassin folder. To free up a little disk space, go back and delete the temporary folder created when we decompressed the archive. Type the following at the command prompt:

    %> cd ~
    %> rm -R -f Mail-SpamAssassin-3.1.0