SpamD Package Needs Testers

flachance

I concur with those issues. I am seeing the same on one of my client's firewall. I just didn't have time to put it down in words. I personally find the third one most annoying.

Add to this the parsing error that Knobee & blueivy reported earlier. I too am seeing that in some entries.

Francois

I'm still trying to chase down why this happened and what the details are, but as soon as I removed a blacklist from the spamd configuration, my shaper rules blew up:

Apr 28 16:54:07 spamlogd[81627]: exiting
Apr 28 16:54:07 spamlogd[81627]: exiting
Apr 28 16:54:09 spamd[77903]: listening for incoming connections.
Apr 28 16:54:09 spamd[77903]: listening for incoming connections.
Apr 28 16:54:12 check_reload_status: reloading filter
Apr 28 16:54:16 php: : New alert found: There were error(s) loading the rules: /tmp/rules.debug:41: syntax error /tmp/rules.debug:46: queue qlanRoot has no parent /tmp/rules.debug:46: errors in queue definition /tmp/rules.debug:48: queue qlandef has no parent /tmp/rules.debug:48: errors in queue definition /tmp/rules.debug:50: queue qlanacks has no parent /tmp/rules.debug:50: errors in queue definition /tmp/rules.debug:52: queue qPenaltyDown has no parent /tmp/rules.debug:52: errors in queue definition /tmp/rules.de
Apr 28 16:54:16 php: : There were error(s) loading the rules: /tmp/rules.debug:41: syntax error /tmp/rules.debug:46: queue qlanRoot has no parent /tmp/rules.debug:46: errors in queue definition /tmp/rules.debug:48: queue qlandef has no parent /tmp/rules.debug:48: errors in queue definition /tmp/rules.debug:50: queue qlanacks has no parent /tmp/rules.debug:50: errors in queue definition /tmp/rules.debug:52: queue qPenaltyDown has no parent /tmp/rules.debug:52: errors in queue definition /tmp/rules.debug:54: queue qP2
Apr 28 16:55:35 spamlogd[77901]: exiting
Apr 28 16:55:35 spamlogd[77901]: exiting
Apr 28 16:55:38 spamd[78329]: listening for incoming connections.
Apr 28 16:55:38 spamd[78329]: listening for incoming connections.
Apr 28 16:55:41 check_reload_status: reloading filter
Apr 28 16:55:46 php: : New alert found: There were error(s) loading the rules: /tmp/rules.debug:41: syntax error /tmp/rules.debug:46: queue qlanRoot has no parent /tmp/rules.debug:46: errors in queue definition /tmp/rules.debug:48: queue qlandef has no parent /tmp/rules.debug:48: errors in queue definition /tmp/rules.debug:50: queue qlanacks has no parent /tmp/rules.debug:50: errors in queue definition /tmp/rules.debug:52: queue qPenaltyDown has no parent /tmp/rules.debug:52: errors in queue definition /tmp/rules.de
Apr 28 16:55:46 php: : There were error(s) loading the rules: /tmp/rules.debug:41: syntax error /tmp/rules.debug:46: queue qlanRoot has no parent /tmp/rules.debug:46: errors in queue definition /tmp/rules.debug:48: queue qlandef has no parent /tmp/rules.debug:48: errors in queue definition /tmp/rules.debug:50: queue qlanacks has no parent /tmp/rules.debug:50: errors in queue definition /tmp/rules.debug:52: queue qPenaltyDown has no parent /tmp/rules.debug:52: errors in queue definition /tmp/rules.debug:54: queue qP2
Apr 28 16:56:06 check_reload_status: reloading filter
Apr 28 16:56:16 php: : New alert found: There were error(s) loading the rules: /tmp/rules.debug:41: syntax error /tmp/rules.debug:46: queue qlanRoot has no parent /tmp/rules.debug:46: errors in queue definition /tmp/rules.debug:48: queue qlandef has no parent /tmp/rules.debug:48: errors in queue definition /tmp/rules.debug:50: queue qlanacks has no parent /tmp/rules.debug:50: errors in queue definition /tmp/rules.debug:52: queue qPenaltyDown has no parent /tmp/rules.debug:52: errors in queue definition /tmp/rules.de
Apr 28 16:56:16 php: : There were error(s) loading the rules: /tmp/rules.debug:41: syntax error /tmp/rules.debug:46: queue qlanRoot has no parent /tmp/rules.debug:46: errors in queue definition /tmp/rules.debug:48: queue qlandef has no parent /tmp/rules.debug:48: errors in queue definition /tmp/rules.debug:50: queue qlanacks has no parent /tmp/rules.debug:50: errors in queue definition /tmp/rules.debug:52: queue qPenaltyDown has no parent /tmp/rules.debug:52: errors in queue definition /tmp/rules.debug:54: queue qP2

Anyone seen anything like this?

Yep, its definitely related to spamd, I had to kill the install of spamd and now the shaper rules are not broken anymore.

sullrich

I don't see any way that it could be linked to SpamD. I'll have to speak with eri

sullrich

submicron, please send a broken rules.debug to my email (gmail). Thanks

I'm still trying to reliably re-create it, if I can, I'll send you the rules.

sullrich

Just fixed all the button operations, delete, spamtrap, etc. Please test!!

I just re-installed the package and the jiggly buttons that do nothing still seem to be there.

sullrich

They are still there, but they do work now… Or at least the delete function button worked for me?

Apparently they work, but only if you reload the page manually. My personal feeling is that pressing the buttons should cause the page to reload itself, otherwise you'll have lots of people frustratedly thinking that the buttons don't work.

Also, on that same page, the database totals apparently don't work. I have several items listed as "Whitelisted" but the totals show 0 items whitelisted.

sullrich

@submicron:

Apparently they work, but only if you reload the page manually. My personal feeling is that pressing the buttons should cause the page to reload itself, otherwise you'll have lots of people frustratedly thinking that the buttons don't work.

Also, on that same page, the database totals apparently don't work. I have several items listed as "Whitelisted" but the totals show 0 items whitelisted.

There is a little blurb about that on the page at the bottom. The idea is being able to rapdily delete, deny or whitelist a number of domains without having to wait on page reloads… So I dunno, I personally like the ajax option but maybe we just need to hide the table row after an operation occurs.

Yeah probably, since we all know that nobody reads the helpful little blurbs.

glanc

Hi! I would like to test spamD, on one of my pfsense installation, but i need some guide on setting it up. I've read the man page on openbsd site just to have a clue, but a quick howto would speed things up.

The idea is to let my pfsense box be a gateway for our internal exchange server, that is being flooded with spam right now :-.

Thanks.

The package is really for testing right now, I wouldn't recommend putting it in production unless you 1) know what you're doing or 2) can tolerate potential lost email.

glanc

Ok. You would not implement it at this point! :-[ Anyway i can help to accellerate the testing process? I was testing it with vmware.

hammeraus001

Installed at 8:15am Thursday 8/5/2008.

So far, no bugs or issues - working perfectly. Spam hitting the server has dropped dramatically.

From start of April to time of installation - 10864
Since installation to 10:00am 15/5/2008 - 193

98.15% drop (and growing) in Spam hitting the mail server.

Will be testing pfSense including SpamD under VMWare in the next week.

Hammeraus,

For those people who are wanting to test this package, would you mind telling people how you have yours configured? There are a lot of people who want to test this, but many of them don't know where to begin.

technopop

Been using PF/Spamd for a couple years on another system with tweaking here and there…

With the pfsense package, I set the numbers low and it seems to block out the majority of spam while keeping late deliveries to a minimum.

Is anyone currently using the spamd package in a CARP cluster? We definitely need more people pounding on this package in that type of environment.

Whitelisting - it should be possible to create a whitelist of a range of IPs instead of having to whitelist a single IP address. For larger sites like gmail it may be desirable to whitelist all their _spf.google.com ranges. Currently, the GUI doesn't seem to support this.