efa-project.org

I got the alert at 3:30am EST. Since then all mail has stopped coming in.

running 'service MailScanner status' returns 'FAILED'

The web interface shows MailScanner status "NO" with 0 procs running.
The inbound queue has been steadily growing since this alert message came in and nothing's been ...

I see 3.0.0.7 is out but this issue isn't mentioned in the release notes.

Is this issue addressed in 3.0.0.7? I think users need to know if this is still an important process to perform.

Thanks for all the hard work you guys do - efa rocks!

https://www.qualys.com/research/security-advisories/GHOST-CVE-2015-0235.txt

From what I can tell, EFA is vulnerable to this exploit. Is there a recommended course of action to address this?

*Edit*

I did 'sudo yum update glibc' from the shell and it seems to have closed the vulnerability according ...

Woohoo!

That worked. Thanks!

For some reason, lists doesn't seem to like it when I use wildcards on both sides.

This works:
from: *@domain.com to: userxyz@mydomain.com (whitelist)

but this doesn't:
from: *@domain.com to: *@mydomain.com (whitelist)

Is there a better way to do this or is this a bug? There is a particular mail ...

While not as elegant as an auto-download, I'm thinking this would be more future proof:

Can the users be told where to download the files then prompted with an upload dialog from EFA?

Even if you move the files to the efa-project domain and re-point the auto update to the new location it would be ...

I think I found a workaround until this is fixed:

viewtopic.php?f=13&t=863

*testing posting privileges - hopefully this goes through*

I think this is all tied in with the GEOIP piece being broken in 3.0.0.6 - should be fixed in 3.0.0.7 though if I'm reading correctly.

Temp workaround that solved my problem:

go into /var/www/html/mailscanner/temp and delete geoip ...

Awesome appliance. No bots here.

Looking forward to eventually participating on these forums.