Improving spam filtering

[exyst]

When I tried to add SPF support I received the following.

[root@mailserver ~]# yum install perl-Mail-SPF-Query
Loading "rhnplugin" plugin
Loading "installonlyn" plugin
Setting up Install Process
Setting up repositories
rhel-i386-server-5 100% |=========================| 1.2 kB 00:00
rhel-i386-server-vt-5 100% |=========================| 1.2 kB 00:00
rhel-i386-server-suppleme 100% |=========================| 1.2 kB 00:00
Reading repository metadata in from local files
primary.xml.gz 100% |=========================| 836 kB 00:00
################################################## 2485/2485
Parsing package install arguments
No Match for argument: perl-Mail-SPF-Query
Nothing to do


Did I do something wrong? I'm running RHEL. Any ideas are appreciated.

I'm a programmer trying to be a sys admin, so please excuse my ignorance if I'm making some obvious mistake.


Darryl

[inigoml]

Originally Posted by exyst

When I tried to add SPF support I received the following.

[root@mailserver ~]# yum install perl-Mail-SPF-Query
rhel-i386-server-5 100% |=========================| 1.2 kB 00:00
rhel-i386-server-vt-5 100% |=========================| 1.2 kB 00:00
rhel-i386-server-suppleme 100% |=========================| 1.2 kB 00:00
Did I do something wrong? I'm running RHEL. Any ideas are appreciated.

I'm a programmer trying to be a sys admin, so please excuse my ignorance if I'm making some obvious mistake.
Darryl

Hi Darryl.
As you can see, you are only using RHEL yum repositories. You have to add an extra repository where Perl-SPF resides. RPMForge repository is what you need.

So, exec this command (for 32 bit version):

rpm -Uhv http://apt.sw.be/packages/rpmforge-r...l5.rf.i386.rpm

or, if you have RHEL 64bit, this one:

rpm -Uhv http://apt.sw.be/packages/rpmforge-r....rf.x86_64.rpm

And try again with yum. ;-)

[exyst]

Thank you so much! That worked perfectly. I assume adding the RPM repository to YUM is a one time event per server.

cheers,

Darryl

[Klug]

Originally Posted by exyst

I assume adding the RPM repository to YUM is a one time event per server.

Exactly 8)

[padraig]

Originally Posted by jholder

That's what i did. I subscribed to a SPAM list, and just spent a month training it, rather than having the users train it.

I get about 150 spam e-mails a day, and only about 1 or 2 end up in my inbox.

Hi John,
can you let us know what the spam list is & is it free?
thanks,
Padraig.

[phoenix]

The SpamAssassin Public Corpus on this page should be a good start, a google will find plenty more. Mind you, I'd be wary of passing any of these tests/training email through a live system.

[jdell]

I implemented an SPF record for our domain and was testing this out, but kept getting SPF_SOFTFAIL's using perl-Mail-SPF-Query.

Googling around, I found this thread (The users October 2007 Archive by thread) that suggests that perl-Mail-SPF-Query is abandon-ware, and that you should be using instead perl-Mail-SPF.

After switching to perl-Mail-SPF, everything started working for me, so I've updated the wiki page: Improving Anti-spam system - Zimbra :: Wiki

[Pascal]

Hello,

sorry for resurrecting this thread.

Can someone tell me if the changes mentioned in the anti-spam wiki article are all lost when upgrading to ZCS 6.0, or if they are left untouched?

And another question.
I successfully installed postgrey, but it is of little use for us because we are on dialup and therefor have to use a smarthost. Naturally, all our e-mail is relayed to and from the smarthost, so it gets auto-whitelisted in no time and there is no further greylisting done.
Is there a way to deactivate the AWL in postgrey, does this even make sense? I hope to get our smarthost provider to activate greylisting on his end, which I understand would make more sense. But for the time being, it would be nice to get it somehow going on our end.

Thanks!