Fetures in stable Relase and Installer Bug

[ThomasH.]

Hello,

Will the stable version also include the option to block, review, and then approve file attachments? Will administrators be able to view the entire email before approving it? Can emails be stored for a certain period (1-2 months) to potentially re-approve them later (like a small backup) or to find and approve emails that were incorrectly identified as spam? The "other" EfA version had all these features, and we found them fantastic and don't want to do without them.


The current installer does not work if you change the database names and/or the database user to your own names. You must use the predefined values, otherwise the Spacy server will not start!

[adrastosefa]

The stable version should be completed this weekend. Maybe tomorrow night pacific time. Also, currently things are set to maintain the emails for 30 days. In the version finalizing right now, there is a disk management and screen presentation process in place. The emails are soft deleted from the Gui interface, but still retrievable by the Superadmin.

Also, the learning and scoring algorithm has been greatly improved. As well, we are currently running machine learning along side the current dynamic rules and learning functions. The ML is literally building a continuous learning pattern and making the decsion as to mark it as spam or not spam, quarantine or not quarantine. Currently that process is just an accumulation of numbers and credits from the different modules.

I am thinking the ML might be released sometime after the new year. This will all lead to a EFACollective that we all contribute to will replace outdate RBL, blacklists, and other legacy type information. The Collective is a ways out, maybe second quarter, but is in the architecture.

I will double check that the database issue has been completely fixed. There was a lot of hard coded type information in previous releases and I think all of that has been fixed.

[adrastosefa]

Found the issue where if you changed the default database option, it broke the functionality. It has been corrected in the upcoming release. You will be prompted to use the default, but also able to change to custom.