efa-project.org

This is good and bad: GOOD: no need to user relay_recipient map and thus the need to create a script to populate it THE BAD: if someone tries to ddos your postfix gateway you have two side effects: a) down of the postfix gateway b) down of your internal ldap server flooded by the ldap query MITIGATI...

Show the evidences of the problem from your logs please.

I would suggest to enable a sasl service to let postfix do smtp-auth against a pop3/imap service of corporate internal mail server.
After all all mails coming tru efa are delivered to a final smtp server.
And even exchange has imap/pop services.

Michael just to be sure:

1) Have you tried MailScanner --lint from shell and see if avg is detected ?
2) Have you tried to send test virus (fake or true) and see if mailscanner detects it ?

Thx

Michael very informative post. thank you !

Shawn is there an available workaround ?

Nevermind .. find the clue. I'm focused on Spam Actions while problem was on High Spam btw rule should be (in mailscanner.conf): Spam Actions = store custom(spam) Ad NOT: Spam Actions = store notify custom(spam) Otherwise you will receive notifications twice: one from notify (without link) and one f...

I've the same problems.

Note that:

1) efa 3.0.4
2) the incoming sig rules are not bounded on domain
3) Spam Actions = store notify custom(spam)

The {Spam not delivered} subjected mail is correctly sended but the line showing the link is not showed.

Could u help me ?

Hi Darky. The web gui is all coded in php , just like mailwatch and msre. I've started from msre, so the css are based on it. You will find the layout similar to mailwatch (yes ... not a big thing but is a start ..). Some script are written in perl (mainly script launched from the webgui to commit t...

Reading mailscanner lists appear .eu domain stops working too.
Now seems to work but cdn is actually down.

Ryan this thread is for future works on EFA.

Note that:

1) phishing update is related to mailscanner not with efa: plz check mailscanner lists: they already suggested a fix
2) i already post on efa forums a solution (same fix as 1)

So plz don't hijack threads and read ALL threads.

Hi all

Before re-write from scratch a webgui for EFA you could take a look to mine in progress.
Darky&Shawn: If you get me your static ip address i will open an access on my dev box so you will see my work.

After your comments we could decide if it could be the right road for official EFA.

Thx

The old mailscanner site is down and so the script basically grab nothing.

To fix edit /usr/sbin/update_bad_phishing_sites, find the $urlbase variable and replace it with:

my $urlbase = "http://www.mailscanner.eu/";

Note to dev: Is SASL really used in EFA ? i don't think.

Seems that your rant in mainly related to mailwatch.
I'm almost agree with u, but one of the advantage of mailwatch his it's simplicity: you could easily adapt to suit your needs.

Why not trying to improve efa rather than criticize it ?

Tokens are user by mailscanner custom action to mark email and permit later from your mail client to learn it from gci script.
Said that, your perfectly right: sql syntax in EFA-Tokens-Cron is wrong.

Thx

me too...

I working as i already told you on something very similar (in features) to the one outlined in this topic.

well ...i think it's a standard efa installation plus their own web gui additions.
More or less the same as my wip.

Good but actually it depends from how you update the sign. Seems to be 2 method that runs in parallel: 1) freshclam 2) mailscanner scripts In my opinion is better to use the "standard" mailscanner way. In this case if the mailscanner script is simply a wrapper around freshclam so customdbu...

And most important.. Switch to innodb engine.

Nothing special, just upgraded the package.
If i rember correctly the only thing to change was the clamav daemon user in the conf.

I haven't actually any vm to retry the installation.
If you have one i cant try on it if u want.

Thx

Is it opensource ? i can't find any evidence on this.

Ok then you are facing the same problem of mine. I suggest to simply remove /etc/cron.daily/freshclam . In this way you let the clamav defs update to carry on by the mailscanner script. To see if updates are performed fine plz mainly check: 1) /tmp/ClamAV.update.log 2) on web gui: http|https://you_e...

1) block subject: yes, using mcp
2) yes, see messages operations on webgui

I think all tmp file issues could be fixed by the following: https://github.com/MailScanner/MailScanner/pull/4