efa-project.org

Ok, it appears this is an exe inside a zip.

Testing further...

Hehe...don't think we want a virus floating around in the forums

I'll suspend my scans and download. I'll have to remove the above link from the post or the post itself.

/etc/MailScanner/MailScanner.conf

Interesting. How does everything look otherwise? The next command in the update is the following: mysql --user=mailwatch --password=$(grep MAILWATCHSQLPWD /etc/EFA-Config | sed 's/MAILWATCHSQLPWD://') \ --database=mailscanner < /usr/local/bin/mailwatch/tools/UTF8_Database/upgrade_mysql_db_to_utf8.sq...

I don't recognize that at all.

Md5 must match to continue upgrade. This is a download integrity measure. 8fc17bb08a236bdf34b85dca72aea661 EFA-Update-3.0.0.7-3.0.0.8.tar.gz If it does not, your update file is getting altered in transit or is only a partial download. Make sure there are no proxies or filters between you and the dow...

Confirmed...still researching... multiple to recipients do not show in spam reports.

Looks like a potential bug in the SQL query for the report generation....still studying....

Nope, the atomic repo kazman is using. Not sure what repos you have. EPEL should remain enabled.

First off.. Don't use the atomic repo on EFA. I won't support this configuration. CentOS warns against using this repo anyway and has it listed as a Known Problem Repository. http://wiki.centos.org/AdditionalResources/Repositories EFA is a virtual appliance. You modify it at your own risk. Adding ot...

Working on this...

Good point, yes, cloning may wreck havoc on the interaface in udev.

What does your whitelisting rule look like?

Also, did you restart MailScanner after whitelisting, just in case?

I am around. Best way to do this is on irc. Hop into #efa-project on freenode.

I should be available after 5pm EDT today to assist.

Changing root should have no effect on the functioning of the appliance.

What specific issue(s) are you having?

Changing root password should have no effect on the function of the EFA appliance.

You can boot in single user mode at the console and reset root from there.

You will need to turn on full recursive DNS on your EFA appliance.

EFA-Configure --> 4) IP Settings -->4) DNS Recursion

Make sure your EFA can query DNS outbound on port 53.

Thanks!

The cause of your problem is the atomic repo. It is in conflict with the epel repo. The clam packages that installed came from atomic instead of epel.

I will need to spin up a VM and diagnose this for a fix.

The previous clamd was from repoforge and used clamav as the user.

We are transitioning to epel which uses clam as the user.

Sorry, I don't see your update.log, can you reattach it?

Also, you may try to update to 3.0.0.8 on one of your boxes and see if any updates clear your issues...

For some reason, release-msg.cgi is not matching your host address range.... Let's do a test.... #!/usr/bin/perl use CGI::Carp qw(fatalsToBrowser); use CGI qw(:standard); use Net::Netmask; print "Content-type: text/html \n\n"; open(FILE, '/etc/sysconfig/EFA_trusted_networks') or die ("...

I wonder if the problem is evident somewhere else in the logs? Would you be able to share your /var/log/messages and /var/log/maillog for analysis? If so, you can email them to me at shawniverson@ovenvsa-project.org Also, next time this problem happens, before you restart, could you run the followin...

Okay, that sounds like a mailscanner problem.

Mailscanner logs to /var/log/maillog. Were you able to see anything wrong in there?