SPAMD on 1.2-RC1 does not start and blocks ALL mail

Exa

Hi,

I've got a few problems with the spamd package.

1. It installs properly but does not want to start although I click on the right button to start it.
2. If I want to start it I have to reboot. When it's activated it blocks all incoming mail :-o
3. In the spamd sources menu the first line is ALWAYS blank. I can't erase it.

Does someone else have these issues with 1.2RC-1 ?.

Thanks for any answers.
Regards,
/Exa

Guest

SPAMD hasn't really been worked on in a long time, and frankly, I don't know if it works much at all anymore. I'd recommend waiting for the new dspam package (currently in development).

sullrich

SpamD was just removed from the package area.

rcarr

I'm sorry to see spamd removed from the pkg area. Last week I committed several patches to fix a variety of bugs (http://forum.pfsense.org/index.php/topic,5660.0.html) in the pkg. I also had to patch
/etc/inc/filter.inc – so you would need to upgrade to a recent version of pfsense as well.

I also enhanced the pkg so that the first time it sees that you have a blank white list, it pre-populates your whitelist with CIDRs for google, gmail, yahoo, ebay and a few other large sites that don't play well with greylisting, in order to minimize the frustration to first-time spamd users ("Howcome gmail isn't getting through?!").

I have Postfix running on a DMZ box, being front-ended by spamd running on my pfsense firewall. So far my patched version of spamd is working great.

Since deploying my patched spamd, Postfix has gone from rejecting several hundred messages per week (mostly via RBLs) to 3 per week.

Before/after spamd stats below:

=================================================

Postfix stats BEFORE spamd:

Spam 556
Blocked by RBLs: 377
Attempted Mail Relaying: 4
Improper SMTP Pipelining: 0
Invalid recipient: 0
Spam Envelope: 162
Spam Headers: 6
Spam Content: 5
Spam caught by dspam: 2
Malware 0
Viruses and Worms: 0
Attachment Filtering: 0
Misc Malware: 0
Nuisance Mail 0
Backscatter: 0
Phishing and Hoaxes: 0
Misc Nuisance Mail: 0
Misc Rejects, Discards or Blocks 0
Warnings 0
Illegal Address Syntax: 0
No MX host: 0
No IP Address: 0
Address Not Listed: 0

Total blocked messages: 556

=================================================

Postfix stats AFTER spamd:

Spam 3
Blocked by RBLs: 1
Attempted Mail Relaying: 0
Improper SMTP Pipelining: 0
Invalid recipient: 0
Spam Envelope: 1
Spam Headers: 1
Spam Content: 0
Spam caught by dspam: 0
Malware 0
Viruses and Worms: 0
Attachment Filtering: 0
Misc Malware: 0
Nuisance Mail 0
Backscatter: 0
Phishing and Hoaxes: 0
Misc Nuisance Mail: 0
Misc Rejects, Discards or Blocks 0
Warnings 1
Illegal Address Syntax: 0
No MX host: 0
No IP Address: 0
Address Not Listed: 1

Total blocked messages: 3

sullrich

It will be back once someone commits fixes to unbreak it. The bug reports where coming in to fast to warrant leaving it in until it is fixed.

rcarr

SPAMD hasn't really been worked on in a long time, and frankly, I don't know if it works much at all anymore. I'd recommend waiting for the new dspam package (currently in development).
<<

Do you mean this dspam?
http://dspam.nuclearelephant.com/

As you can see from the Postfix stats I just posted, I also run dspam (on my Postfix box). I've been running dspam for 3+ years. Over time, dspam has been catching fewer and fewer msgs for me (because spam techniques have been changing – particularly in the use of image spam, PDF spam, spam with large corpuses of random [but semantically sensical] text, etc). The next time I upgrade my MTA, I'm probably going to leave out dspam.

dspam is not really comparable to spamd. Apples and oranges. dspam is a lot heavier and potentially a lot more complex (in the set-up phase). I'm not sure a firewall is an appropriate place for dspam (though there are reasonable contra-arguments to be made).

I'm getting a lot of benefit out of spamd's greylisting, tarpitting, spam-trapping. It's successfully detecting spammers that are not on RBLs. And hundreds of spammers are being tarpitted per week – sometimes for as long as 10 minutes. I have some Postfix regexes that are very successful at detecting image spam, but those regexes are no longer getting triggered, thanks to spamd.

========

Can we leave spamd in the pkg area (with the patches I committed), but with a note cautioning users that the pkg may not work, isn't well-maintained, has caveats, etc? I would be more likely to fix any other bugs in spamd if the pkg were still available.

rcarr

It will be back once someone commits fixes to unbreak it. The bug reports where coming in to fast to warrant leaving it in until it is fixed.
<<

Really? Ok, let's talk off line about the problems.

studioelement

I use spamd on pfsense 1.0.1 and love it. Works great! Would really like to see this package continue.

rcarr

Incidentally, here are the CIDRs which I use in spamd's "SpamD Whitelist". (My patches also pre-populate the spamd whitelist with these the first time spamd notices the whitelist is empty. The whitelist is pre-populated only once and only if it is empty.)

72.14.192.0/18 Google Mail
64.233.160.0/19 Google
66.102.0.0/20 Google
66.249.64.0/19 Google
72.14.224.0/18 Google
216.239.32.0/19 Google
216.155.192.0/20 Yahoo
68.142.192.0/18 Yahoo
209.191.64.0/18 Yahoo
209.73.160.0/19 Yahoo
66.135.192.0/19 eBay
127.0.0.0/8 Localhost

If anyone else has any useful CIDRs for whitelist, please post them.