MCP Actions -> custom()

[duesen]

Hi all!
I just registered so I can be part of future dicussions.

First of all I want to thank for all the great work that E.F.A has made towards a great anti-spam solution.
I evalutated some solutions (commercial and free available) but I think E.F.A is built on a good set of modules and the detection rate is up to commercial solutions and so I began to dig into the depths of E.F.A and its unerlying modules.

An installation for production use was set up and now it is time to finetune some settings to fit our personal needs.

In the meanwhile I am familiar with most of the settings that can be done via EFA-Configure, tweaking the configfiles, custom reports, ...

Now I have one problem that I did not figure out how to solve it.

Using the syntax of the MailScanner.conf file the "Spam Action" has a nice feature. It is possible to append "custom(spam)" to the config and if a message is spam the user can self-release the corresponding message (self-release means the link in the e-mail which is filled up with the correct token to "click and release" the message from the email-client!)

I set up MCP with custom filters and all this is working fine now. But it looks that internally MCP messages are handled through a different actions set because if I test it with e.g.:
"MCP Actions = store custom(spam)"
this will not work as expected.

What am I missing?

-
duesen

[shawniverson]

MCP Actions are different from Spam Actions, so I would need to take a look a this. Chances are that the custom action does not understand MCP.