efa-project.org

*laugh*

Glad to have been able to help.

spf records are checked by spamassassin as part of the spamassassin checks.

given your rudeness, I'll let you work out the rest for yourself.

SPF checking requires a valid SPF _TXT entry in your DNS.

Do you have that configured properly? Have you tested your spf records for the related domains?
http://mxtoolbox.com/SuperTool.aspx

Of course I am being serious. You have a problem and you don't know where the problem is. So go back to basics. What are the differences? Obviously there is a difference or you would not be having a problem. Otherwise, you're asking us to guess for you an answer for your problem from information we ...

What are the actual differences between the two servers? Start with that and then you should find your problem.

That would be my approach. If mail from my domain comes into my efa box, I'd just drop it, or set it to a very high spam level.

All our mail is handled internally, so there is no reason why mail from our domain would ever come in from an external source.

I have no idea what is causing your problem. I'd need to log into your system and see what's going on in order to work out why these domains are whitelisted.

EFA uses postfix. Can't you use the same file in /etc/postfix/transport?

how many? 10s? 100s? 1000s?

how often will they be changed?

yes.

look here: it looks like you are whitelisting the spammers, thus the spam is being marked as clean.

You installation of Spamassassin does not appear to be configured to show the detailed spam reports with your messages. For example, in my messages, I will see the following headers: X-efaDomain-MailScanner-EFA-SpamScore: sssss X-efaDomain-MailScanner-EFA-SpamCheck: spam, SpamAssassin (not cached, s...

I got it, and yes, I think you are correct.

I should be able to pull that perl module and disable the extra repo (phew!) and it should behave correctly.

It does and that is the version I have installed. Something must be broken in my dependencies database, because I can see the same thing: [root@efa spamassassin]# yum deplist perl-File-MimeInfo Loaded plugins: fastestmirror, security Finding dependencies: Loading mirror speeds from cached hostfile *...

testing with your configuration.

how did you install your copy of the perl::net::sendbase module?

identical packages, versions and repositories.

However, the only perl packages I have installed are
- perl-File-MimeInfo
- perl-File-DesktopEntry

but not
- perl-file-BaseDir

ovizil, What else did you do to get this working? At the moment, the only results I am getting are like so: Spam Report: Score Matching Rule Description -1.90 BAYES_00 Bayes spam probability is 0 to 1% 0.25 GMD_PDF_HORIZ Contains pdf 100-240 (high) x 450-800 (wide) 0.00 HTML_MESSAGE HTML included in...

Sorry ovizil, I've not got an answer. I suspect the perl File-BaseDir package was installed when I installed File-MimeInfo, but I don't remember. I was able to remove File-BaseDir, and my File-MimeInfo is gone. The File-MimeInfo package is not important for EFA unless you are using the ole2macro.pm ...

I see. I'm using Centos as my base, and Net::SenderBase is not one of the packages available. And since it uses an older version of Perl, attempting to install the module via CPAN is usually a disaster that often trashes my perl installation. I can find the package at the RPMForge repository. I'm go...

Did you try running the EFA-Configure program? Most of the common EFA settings can be found there. I prefer to edit /etc/MailScanner/MailScanner.conf directly, but I think the option you are looking for can be found under 9) Spam Settings? Ah, when in doubt, use google to search this site. You can f...

That's funny. It didn't for me.

Can you reinstall only perl-File-MimeInfoi? or does it require per-File-BaseDir?

Did you install any additional perl modules?

Try removing perl-File-BaseDir by itself and see if only that can be removed.

As far as I know, File-MimeInfo doesn't actually need it.

I've nothing to do with the development, but I can tell you that /etc/MailScanner/phishing.bad.sites.conf comes from the MailScanner webserver.

The script run is /usr/sbin/update_bad_phishing_sites and it is set to run every hour in /etc/cron.hourly/update_bad_phishing_sites

So, I finally got around to testing this. I removed the perl-File-Basedir module with the following command: [root@efa spamassassin]# yum remove perl-File-BaseDir Loaded plugins: fastestmirror, security Setting up Remove Process Resolving Dependencies --> Running transaction check ---> Package perl-...