Spam Assassin

[xcensus]

Desperately need Spam Assassin feature added.

[DirectAdmin Support]

Hello,

It's already available, you just have to turn it on:

cd /usr/local/directadmin/scripts
./spam.sh

then edit /etc/exim.conf
and uncomment the spamassasin transport and director (remove the # character from the start of the lines)

John

[roman]

Can particular domain users turn on and off spam assassin?

I wouldn't want to turn it on for all domains. It's petter to let the domain user decide on that.

[DirectAdmin Support]

Hello,

Not at the momment.

John

[jhobbs]

Cpanel (End-User panel) allows installation of SpamAssassin on a per-domain basis.

I hope DirectAdmin can add this feature soon.

[ProWebUK]

CPanel allows everything including search engine submitters.....:rolleyes: you can make up your own rulesets for spamassassin aswell as mailscanner, would take a bit of time and possibly a small cost....... automatic intergration with directadmin would simply be echo 1 line into the file using the domain variable. then to remove just wipe the line.

[DirectAdmin Support]

Hello,

Spamassin control is one of the many things on the todo list. :)

John

[jhobbs]

How can I add SpamAssassin to a domain, using DirectAdmin's Reseller and/or End-User panels?

I believe the installation requires access to directories that are denied to End Users?

[DirectAdmin Support]

Hello,

Right now it's just on or off for the whole server, hence it's on the todo list.

John

[jlasman]

We offer our clients both SpamAssassin and spam-blocking via several RBLs (realtime block lists).

By default for new clients we turn SpamAssassin on (since it just marks) and we turn RBLs off.

The choices we offer are:

1) SpamAssassin on, RBLs off
2) SpamAssassin on, RBLs on
3) SpamAssassin off, RBLs on
4) SpamAssassin off, RBLs off

If server load were our only concern we'd force our clients to use RBLs to catch up to 99% of the spam, and SpamAssassin to catch 60% or so of the rest.

Not only are RBLs more effective, they take a major load off the server, blocking the spam before it's accepted for delivery, at RCPT time, and the few false positives get directed to a friendly page explaining the problem.

SpamAssassin puts a major load on the server, as it has to scan each incoming email through lots of rules.

And even with multiple and very effective rulesets, we still don't catch over 60% of the spam with SpamAssassin.

However many of our clients want to get all their mail, even suspected spam, so we do offer only SpamAssassin as an option.

If you're running at least Exim version 4.24 I'll be happy to give you our RBL blocking ACL and you can set up the files it requires yourself, or we can offer the entire setup on your system as a service.

For those who don't want to even see spam, we're offering SpamBlocked.net; a complete offsite solution.

For more information on what we're doing and how we're doing it see:

http://www.spamblocked.net/

Jeff

[josetann]

Originally posted by DirectAdmin Support
Hello,

Right now it's just on or off for the whole server, hence it's on the todo list.

John

Any ETA on this? I get literally hundreds of spam messages every day, and would love to enable it for my personal account. However, I'm one of those admins that don't want to force the same settings on everyone and needs spamassassin to be configurable on a per-domain or per-user basis.

[wdv]

I think it's a pretty important issue.

Though it's not that hard to add for DirectAdmin. Basicly it's just adding the domain to a file, to enable/disable it (exim just looks up whether or not the domain is in the file).

[DirectAdmin Support]

Hello,

I would most likely not be overly difficult, but we're currently working on larger things at the moment. If someone is upto figuring it out, be my guest :) (mainly, the specifics in the exim.conf and the spamassasin setup)

John

[jlasman]

I've figured it out :) .

I'll be posting a new exim.conf file which works for us for both SpamAssassin and using RBLs to actually block at the server, to the howto section later today.

And instructions for whitelisting domains/users from SpamAssassin.

And instructions for blacklisting senders in SpamAssassin.

Jeff

[wdv]

Originally posted by jlasman
I've figured it out :) .

I'll be posting a new exim.conf file which works for us for both SpamAssassin and using RBLs to actually block at the server, to the howto section later today.

And instructions for whitelisting domains/users from SpamAssassin.

And instructions for blacklisting senders in SpamAssassin.

Jeff

Looking forward to that

[DirectAdmin Support]

Thanks a lot Jeff :) Many people will greatly appreciate your efforts! Once it's setup, I can add the required interface to DA.

John

[jlasman]

I'm delayed in setting it up...

Here's why:

My original box is running spamd

Our new box isn't.

I just installed spamassassin and it installed without errors, from your shell script.

But when I tried to start spamd manually, using

/usr/bin/spamd -d -a -c -m 5

(which is what's in the startup script I've got in my /etc/rc.d/init.d directory in my original box), it fails with:

[root@bes init.d]# /usr/bin/spamd -d -a -c -m 5
Can't locate HTML/Parser.pm in @INC (@INC contains: ../lib /usr/lib/perl5/site_perl/5.6.1/i386-linux /usr/lib/perl5/site_perl/5.6.1 /usr/lib/perl5/5.6.1/i386-linux /usr/lib/perl5/5.6.1 /usr/lib/perl5/site_perl/5.6.0 /usr/lib/perl5/site_perl /usr/lib/perl5/vendor_perl/5.6.1/i386-linux /usr/lib/perl5/vendor_perl/5.6.1 /usr/lib/perl5/vendor_perl .) at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/HTML.pm line 7.
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/HTML.pm line 7.
Compilation failed in require at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/PerMsgStatus.pm line 44.
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/PerMsgStatus.pm line 44.
Compilation failed in require at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin.pm line 62.
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin.pm line 62.
Compilation failed in require at /usr/bin/spamd line 32.
BEGIN failed--compilation aborted at /usr/bin/spamd line 32.

Perhaps I've done something wrong in my setup of the new box. Nevertheless, until I know why some boxes are different, I can't go ahead with this.

Any ideas, John?

Jeff

[ProWebUK]

Check you have the perl-HTML-Parser module installed

Chris

[jlasman]

I'd love to :) .

What should I look for?

Thanks.

Jeff

[ProWebUK]

Easiest way is to use a tool called perldiver to get a complete list of modules...

http://www.scriptsolutions.com/support/files/4-115-perldiver.zip

Chris

[Ryan]

Originally posted by DirectAdmin Support
Hello,

Spamassin control is one of the many things on the todo list. :)

John

Is there any update on an ETA for this? This seems like a pretty important and popular feature.

Thanks,

[DirectAdmin Support]

Hello,

We may be including spam controls into the next release, or the one after that. I'm not sure if it will be for spamassin, or just RealTime Blackhole Lists (RBLs). We might include both (RBL and SA), but I'm not sure about that yet.

John

[jlasman]

Okay, John...

I hear you, and I'll be delivering within a day or two.

At most.

:)

Jeff

[retroweb]

Per-user MailScanner enabling/disabling was mentioned earlier... how can I do this manually, so that certain users won't have their emails checked for viruses or spam?

Thanks :)

[SlashChick]

Per-domain SpamAssassin controls are the #1 feature request for us at this point. I hope this will be a DA feature soon.

[jlasman]

We may eventually build it into our products, either free or commercial.

You could certainly build it into exim.conf easily enough.

But then you'll need a skin to support it.

So it should probably come from DA.

Jeff

[blacknight]

Originally posted by DirectAdmin Support
I'm not sure if it will be for spamassin, or just RealTime Blackhole Lists (RBLs).

At what point are you considering RBLs?
What level of control are you talking about?

We're trying to move all mail scanning away from our shared servers and onto our custom gateway, thence the questions.

[jlasman]

RBLs are already available from my SpamBlocker exim.conf file available on this forum (earch for the thread).

I'm hoping DA will add skin-based support for it in the near future.

Anyone can add functionality for per user or per domain implementation; all the necessary info is in the new Exim Book (the one from the UK) and on the exim.org website.

Jeff

[DirectAdmin Support]

Hello,

The skin based spamassasin settings are going to be included when we release the exim bandwidth/email counting bit. No eta, but it's currently being worked on, among other things.

John

[digilexic]

It says it installed, but it isnt filtering anything. My exim.conf looks like it had already had the filter uncommented, but spam is still invading my syste. Can anyone help me?

[blacknight]

Just poking around and noticed that the Spam Assassin version in spam.sh is dangerously old.

Is there any particular reason?

2.55 does not recognise some newer MUAs, including Outlook 2003 and still makes explicit references to a number of dead RBLs

[prophecy]

I'd love to see a UI for spam assassin on a per domain basis too. That would rulezor.

[DirectAdmin Support]

Hello,

The new exim.conf and exim.pl are still in beta, but we should have the SpamAssassin UI shortly after they're out of beta.

I'll start updating spamassassin to 2.63 in the spamd.sh (i'll get it to auto download so you'll just have to run spamd.sh to update)

John

[Herbster]

ETA? :(

[resolveit]

It would be great if it were possible to install the latest versioin of SpamAssassin from the Admin Control Panel.

Also ability to enable/disable SpamAssassin feature for a reseller, user and domain.

Keep up the good work :)

Kind Regards,
Onno Vrijburg

[nuance9]

Any update on whether SpamAssassin and RBL's will be included any time soon in the DA GUI?

Thanks!

[rldev]

Next Release, around Sept 22.

[jlasman]

Look here (http://www.directadmin.com/versions.php?version=1.225000) to see what will be included.

Note that there will be a Spamassassin user interface.

However no user interface for SpamBlocker is included.

Jeff

[flyer727]

> I wouldn't want to turn it on for all domains. It's petter to let the domain user decide on that.

Exactly. If my hosted forced that junk on me, I'd be switching hosts ASAP.