efa-project.org

That's odd. Also, I noticed you can't sudo these. You need to be root.

As root: Is the output what you expect?

There should be an update log file in the following location: /var/log/EFA Please attach a copy of this log or use a pastebin to share so we can see what went wrong. As for your immediate issue, it sounds like clamd.conf wasn't modified properly. 1) Drop in your old clamd.conf just like you did. 2) ...

Something is wrong with your greylisting. When you restart sqlgrey, you should see the following: May 29 17:27:26 efa sqlgrey: 2015/05/29-17:27:26 sqlgrey (type Net::Server::Multiplex) starting! pid(26275) May 29 17:27:26 efa sqlgrey: Using default listen value of 128 May 29 17:27:26 efa sqlgrey: Bi...

I agree, I don't see anything there per se...

Just out of curiosity, was it the incoming or outgoing queues that were stalled?

What about your employer's domain....

Are you seeing any errors in your httpd logs in /var/log/httpd?

Are your users trying to submit from a cell phone (external network)?

Definitely an issue in mysql hostname field... To fix...change "mynewfqdn" to the fully qualified domain name of your host as root: echo "UPDATE maillog SET hostname='mynewfqdn';" | mysql -u mailwatch --password=`grep "^MAILWATCHSQLPWD:" /etc/EFA-Config | sed 's/.*://'`...

I am seeing a problem after changing the name of my test server:

In detail.php:

XML-RPC Error: Didn't receive 200 OK from remote server. (HTTP/1.0 301 Moved Permanently)

I am troubleshooting further...

That looks fine. Now, are you able to see anything happening in /var/log/maillog or /var/log/messages at the time when the failure occurred that could offer some clues?

You could add an entry into /etc/hosts to get around this, I believe.

I have setup a brand new Exchange and everything seems to be working if I take EFA out of the picture. i have the SMTP port in FW configured to go to EFA. I have tried sending email from Gmail and my work address but no luck. >> #554 5.7.1 Service unavailable; Client host [xx.xx.xxx.] blocked using...

drewmorris wrote:One other question about ram disk... does Clamd use it to unpack as well? Using a ramdisk for Clamd seems like a good idea as well.

Yes

When you look at free space, are you looking at just the VM or in greater detail?

Run this from a console in EFA:

Patch fix for Transport editor in EFA-Configure: 56a57 > [[ $(((y/2 + 1) % 25)) -eq 0 ]] && pause 68c69 < if [[ $choice > "0" && $choice < $((tLen/2+1)) ]]; then --- > if [[ $choice -gt 0 && $choice -lt $((tLen/2+1)) ]]; then Copy this into a file called func_mailse...

We would also like to thank everyone for their support and contributions to this project. :clap: The following issues have been fixed in 3.0.0.8: Issue #40 Enhancement - Extend MailWatch to hide high spam from regular users Issue #45 Enhancement - Add ScamNailer ClamAV ruleset (superceded by issue #...

Apache already has DH 2048bit and export ciphers disabled. No action needed here. Apache is not vulnerable in EFA to logjam Postfix is vulnerable. To fix weak DH key: Generate a 2048bit Diffie-Hellman key sudo openssl dhparam -out /etc/postfix/ssl/dhparam.pem 2048 Add the DH key to postfix: sudo pos...

Known issue, but you would see the problem in the following log: /var/log/maillog You would see MailScanner attempting to submit to clamd for scanning, failing, and requeing the same batch over and over. We found that 2GB is not sufficient, so all new builds start with 4GB of memory. I encourage eve...

Strange thing. When I try to edit a domain using EFA-Configure (Mail Settings->Transport Settings), I might get an error saying 'Error.... "n" is not an option..." I have a list of 116 domains. If I type '116', it lets me edit the last domain in the list. If I type '46' it complains ...

Likely clamd has crashed on your system. Reboot to stabilize your system temporarily.

How much memory do you have?

How many mailscanner threads are you running?

Starting a thread on the Logjam Vulnerability.

I am currently researching and will post results and how-to here.

www.emailsecuritycheck.net has some silly tests. For example... "attached.()bat" "()bat" is not a .bat file. It is a ".()bat" file. There's no rule in MailScanner by default to block a ".()bat" file. Besides, it would need to be .bat before it could do any harm.

The 3.0.0.8-beta update is now available for BETA TESTING ONLY. DO NOT USE IN PRODUCTION. We would also like to thank everyone for their support and contributions to this project. :clap: The following issues have been fixed (hopefully) in 3.0.0.8-beta: Issue #40 Enhancement - Extend MailWatch to hid...