Email server on Raspberry PI: a seven steps guide
With this first post I start documenting, step by step, the process of setting up an email server based on a Raspberry Pi card, using open source email programs like Postfix, MailScanner, ClamAV , and SpamAssassin.
The aim is to have a low power consumption email server that can run continuosly at home. This task is currently performed by my PC, with a Linux SuSe 12.1 operating system, and with an avarege power consumption of about 70W.
Another advantage is to leave the Raspberry Email Server functioning all the time when on holiday for longer periods of time.
This proces starts today with my purchase of the Raspberry PI card.
This is a list of the items purchased:
- Raspberry Pi Type B Single Board Computer 512MB, £21.60
- Micro USB UK power supply for Raspberry Pi, £ 5.19
- 4GB Class 6 SDHC Flash memory card for Raspberry Pi , £6.49
- HDMI cable for Raspberry Pi, £ 3.39
- Raspberry Pi Type B Case - Clear, £ 3.99
Full cost, VAT include is £ 53.74
Clearly you also need a registered domain, a static IP, and a local nwtework that this email is servicing
As a navigation aid, here are all the seps required:
- Received the Raspberry Pi
- Firing it up
- Essential configuration
- Tips & utilities
- Postfix & POP3 servers
- Secure POP3 with Stunnel
- Protecting with Amavis/Clamav/SpamAssassin
NFS for linux
Setting up a network file system
I found this link for a coprhenesive NFS howto.
Assuming that we want to share some directories on server PC in a local area network with LAN address of 192.168.1.0/255.255.255.0
- On the PC providing the remote file system (server) find and install the nfs server daeomon (on my system, I install nfs-kernel-server)
- Start the system service (Runlevel editor), for service nfsserver and levels 3 and 5
- After starting the service and/or rebooting the server check that there is a process running with name nfsd (for user root)
- Edit /etc/exports and add the line(s) with the directories to export. In my case it is:
/jupiter 192.168.1.0/255.255.255.0(rw)
- Increase the security by adding the following to hosts.deny (check link NFS how to)
- And this to hosts.allow (check link NFS howto_
Now mount the file system on the client machine
Mission Statement
This blog is set-up by its authour (Gualtiero Chiaia) as a collection point for solution to be applied to a Linux machine, spanning different knowledge domains, like network, system admin, programming languages, programs and functionality.
My actual systems runs:
- Linux distro: Open-Suse 12.1, 64 bit
- Linux kernel: 3.1.10-1.16
- Gui: KDE: 4.7.2, release 5
- CPU: AMD Athlon(tm) II X2 215 Processor, 2 cores
- Monitor: NVidia GT200 [GeForce 210]