E.F.A. Project
E.F.A (Which stands for Email Filter Appliance) is an (virtual) appliance for spam fighting using opensource tools.
The project combines existing open-source projects into a single virtual machine and attemtps to provide a free community-supported spam filter which aims to be effective against spam filtering and easy to use for its admins. The E.F.A. virtual machine is based on CentOS and is available for Hyper-V or VMware.
| Developer(s) | E.F.A Project |
|---|---|
| Stable release | 3.0.0.8
|
| Written in | Bash (Unix shell) |
| Engine | |
| Operating system | CentOS |
| Type | Email spam filter |
| License | GNU GPLv3[1] |
| Website | efa-project.org |
Search E.F.A. Project on Amazon.
History[edit]
In 2010 the free to use ESVA spam filter appliance project died,[2] the websites went offline and the community had no central place for communication anymore. The authors of the E.F.A. project started the esvacommunity website[3] as an attempt to bring the project back to live.
As there was no contact between the community and the original author of the ESVA project, and it was unknown if the ESVA name could be used any longer the E.F.A. project was created in 2012 after the previous ESVA project seemed to contain security issues.[4][5] The esvacommunity websites and forums were dropped in favor for E.F.A. Project in 2014.
The initial idea was to use a completely different setup than ESVA, this resulted in E.F.A. 0.2 as the first public release. E.F.A. 0.2 was based on Debian for the Operating system, Exim for the Mail Transport Agent and Baruwa as the web interface, some additional features were added in E.F.A. 0.3 which was released in January 2013.[6]
Baruwa stopped with the 1.x branch and moved over to Baruwa 2.x, an attempt was made to rebuild E.F.A. based on Baruwa 2.x but after testing and a few beta releases the decision was made to move over to a more ‘ESVA’ way, as most users got comfortable with MailWatch and preferred the MailWatch interface over Baruwa.
In January 2014 the first release of E.F.A. 3.x was released based on CentOS for the Operating system, Postfix for the Mail Transport Agent and MailWatch as the web interface.[7]
Software Used[edit]
The E.F.A. appliance use the following software:
| Function | Package |
|---|---|
| System OS | CentOS |
| MTA | Postfix |
| Core Spam Filter | MailScanner |
| Spam Filter | SpamAssassin |
| Virusscanner | ClamAV |
| Webinterface | Mailwatch |
| Content Filter | DCC |
| Spam detection network | Pyzor |
| Spam detection network | Razor |
| Grey listing | SQL grey |
| Image Recognition | ImageCeberus |
| System Management | Webmin |
Versions[edit]
There is no official release or support cycle, E.F.A. is build based on an rolling upgrade, meaning that only the latest version is supported and maintained. Upgrades are always installed 'in order'.
| E.F.A. version | Release date | Notes | |
|---|---|---|---|
| 3.0.0.8 | 26 May 2015 | Latest release based on CentOS and MailWatch | |
| 3.0.0.0 | 24 January 2014 | First release based on CentOS and MailWatch | |
| 0.3 | 3 February 2013 | minor update to 0.2, the last version based on Debian and Baruwa | |
| 0.2 | 17 October 2012 | first public release based on Debian and Baruwa | |
Old version Older version, still supported Latest version | |||
All content and scripts are located on GitHub allowing all users to contribute to the project.[8]
See also[edit]
References[edit]
- ↑ E.F.A. project. "License - GPL Documentation". E.F.A. Project.
- ↑ ESVA. "ESVA Website". global-domination.org.
- ↑ Fencepost.net. "the new home for ESVA". Fencepost.net.
- ↑ osvdb.org. "ESVA Security issue". osvdb.org.
- ↑ Tenable. "ESVA Security issue". Tenable (nessus).
- ↑ Baruwa. "E.F.A. Project chooses Baruwa for its web interface". Baruwa.
- ↑ Luca Dell'Oca. "E.F.A. Review". virtualtothecore.
- ↑ GitHub. "E.F.A. GitHub Page". E.F.A. Project.
External links[edit]
 | This software article is a stub. You can help EverybodyWiki by expanding it. |
This article "E.F.A. Project" is from Wikipedia. The list of its authors can be seen in its historical. Articles copied from Draft Namespace on Wikipedia could be seen on the Draft Namespace of Wikipedia and not main one.
