If you have an existing MailCleaner appliance and have noticed that the ClamAV service is no longer starting, please see this discussion thread. Please follow this repository for additional discussions related to ongoing support of MailCleaner®.
The SpamTagger project is being led by the former head of development for the MailCleaner® antispam gateway.
The official MailCleaner® GitHub organization is still controlled by Alinto and all repositories are archived with no intention to be revived. SpamTagger Plus is a fork to revive MailCleaner® as an entirely free and open source project.
An initial release will be made available after significant upgrades are complete while maintaining compatibility with MailCleaner® configurations (so that migrations should remain possible).
SpamTagger Plus is currently quite far from being usable for production mail filtering. The first release will be changing to a bootable container system based on CentOS Stream 10 for the reasons discussed here. Aside from this, additional work is still necessary to bring the application code up to date.
The pace of development for SpamTagger Plus is expected to be quite slow after the first release, as compatibility with MailCleaner® and stability are the main goals. Some features may be ported from the core SpamTagger project where it is easy and makes sense. Additional contributions from the community will certainly be considered.
The reason that the MailCleaner® fork is called "SpamTagger Plus" is because the eventual goal is to develop a lighter-weight antispam gateway software simply called "SpamTagger". The "Plus" references additional non-essential features offered by MailCleaner® and SpamTagger Plus which will be dropped from SpamTagger.
SpamTagger will draw significantly from SpamTagger Plus, but will provide the ability to have more active development on features focused on increasing spam filtering quality with fewer overall development resources.
A spam filter is nothing without good rules and training data. Aside from providing support, the primary value proposition of MailCleaner® Enterprise Edition was that it provided premium data feeds. SpamTagger will seek to find new ways to provide similar data feeds and other tools which can be integrated into any filtering environment.
This will include community sourced SpamC rules, tools for hybrid local and shared bayes training, and other projects.
Your ideas, concerns and assistance are welcome!
If you have immediate concerns about a bug in any project, you are encouraged to use the Issues tab for that project's GitHub repository.
If you have questions or ideas that you would like to discuss with other users, you are encouraged to use the Discussion tab for that project.
SpamTagger will seek to maintain currated lists of SpamC rules which can be individually opted in to. These will be sourced from users globally and we would encourage you to share any rules that you find success with. Documentation to come...
The Wiki tab for each projects will serve as the official documentation for each project. These allow for community contributions and we would welcome improvements. If you ever encounter something that you wish was spelled out a little bit better, it is very likely that others feel the same way. Feel free to discuss it with others to make sure you understand, then add that knowledge to the Wiki.
If you have intermediate knowledge of programming (and generally a passing knowledge of Perl), you can take a look at Issues across our various repositories to find something you feel capable of fixing. Just go for it! We'll be happy to provide help!
If there is a new feature that you would like to see in any project, you are encouraged to first discuss with the community to ensure that you work in the right direction before wasting any time. When you have a good idea of what you want to contribute, please open an Issue with a [Feature] tag in the subject to state your goals and track your progress. You can then open a Pull Request and mention the Issue number when your work is ready for review.