SpamD Package Needs Testers
-
For kicks, add another ip to the alias. Does the problem go away?
Afraid not:
===
php: : There were error(s) loading the rules: no IP address found for SBS /tmp/rules.debug:44: could not parse host specification pfctl: Syntax error in config file: pf rules not loaded - The line in question reads [44]: rdr pass on re1 proto tcp from <spamd-white>to port smtp -> {SBS} port smtpSBS = "{ 192.168.10.10 192.168.10.101 }"
===</spamd-white>
-
-
Actually I am not too sure the {} business is correct. Try changing your alias to $aliasname. $SBS
-
Actually I am not too sure the {} business is correct. Try changing your alias to $aliasname. $SBS
That fixed it :-)
Need to change the instructions on the settings page and it's all done!
Thanks for that!
-
New changes on their way. Reinstall in about 5 minutes.
-
Make that another 5, found a small other problem and bounced the version.
-
I have turned on greylisting of connections and tested it from a few clients using Telnet to port 25 on cmd.exe (from Windows).
From each client it looks like they connection is being treated as blacklisted (blacklisted connections stutter for the entire conversation rtather than the first 109 that greylisted connections do).
I have also followed the rules and connected (through telnet again to port 25) and then waited for the default 25 minutes before connecting again. I understand that in this case the connecting IP should be whitelisted but it's not, it continues to be chatted to like it's a blacklisted connection (stutter the whole way through the conversation).
The settings tab has been left at it's default settings with the exception of the NextMTA and greylisting.
Any suggestions?
-
Yeah, /var/db/spamd is not being created. I am researching it. Gotta run for the evening but will look into it tomorrow. If someone beats me to the solution, please post it!
-
The /var/db/spamd problem has been resolved. After 5 minutes from this posting reinstall the package and please test.
-
i today test long time spamd and we long time not received any mail, any mail conn no accepted..
after spamd removed. (sorry log cleared, test prev. 4-5hours)i think smtp connection no expired added after graylist or tracking..
-
The /var/db/spamd problem has been resolved. After 5 minutes from this posting reinstall the package and please test.
Seems to be working so far - will have to wait the obligatory 25 minutes to see if the greys move to the white. However non-blacklisted server are now only being stuttered for 10 second and they are appearing in the SpamD Database tab as grey.
Will update you. Fingers crossed.
-
i today test long time spamd and we long time not received any mail, any mail conn no accepted..
after spamd removed. (sorry log cleared, test prev. 4-5hours)i think smtp connection no expired added after graylist or tracking..
Prior to the release of just an hour or so ago it didn't work. Reinstall the package and greylist tracking should be working.
-
Then you are not running the latest version as i just commited fixes an hour ago. You have not been loved long time. Reinstall and long time test again.
-
The /var/db/spamd problem has been resolved. After 5 minutes from this posting reinstall the package and please test.
Seems to be working so far - will have to wait the obligatory 25 minutes to see if the greys move to the white. However non-blacklisted server are now only being stuttered for 10 second and they are appearing in the SpamD Database tab as grey.
Will update you. Fingers crossed.
Good deal. Thank you for your clear and detailed reports.
-
i today test long time spamd and we long time not received any mail, any mail conn no accepted..
after spamd removed. (sorry log cleared, test prev. 4-5hours)i think smtp connection no expired added after graylist or tracking..
long time = 5hour and i use 1.2-RELEASE built on Sun Feb 24 17:04:58 EST 2008, sorry, fair enough.
-
I think you are not reading us correctly. The fix was commited ONE hour ago. So your 5 hour test did NOT include the fix.
-
The /var/db/spamd problem has been resolved. After 5 minutes from this posting reinstall the package and please test.
Seems to be working so far - will have to wait the obligatory 25 minutes to see if the greys move to the white. However non-blacklisted server are now only being stuttered for 10 second and they are appearing in the SpamD Database tab as grey.
Will update you. Fingers crossed.
Good deal. Thank you for your clear and detailed reports.
Greys are moving to Whites and Black's are being blocked … excellent work. Fantastic!
The SpamD Database tab is a bit messy and the headers don't correspond with the columns (for example the Attempts column has entries such as 1208560605 in it and what I assume is the real Attempts column has no header and values such as 0 and 1 in it). This doesn't affect the package itself but I thought I would point it out as nothing else is broken :-)
Again, good work.
-
No problem-o. I need to get my mail account setup shortly and forwarding to do some more tests. I am definitely not done fixing / improving the package.
Thanks for testing!
-
I've been composing this message for several hours while fighting fires around here. Please forgive me if you've fixed some of these things since I started.
Bugs found so far:
Once I added a few traplist entries I noticed that on the SpamD Database tab, the icons for blacklist and spamtrap are not displaying.
spamd.conf:
the symlink needs to be in /usr/local/etc/spamd/ rather than /usr/local/etc.The SpamD External Sources tab adds entries similar to :
test:
:black:
:msg="you are rejected":
:method=http:
:http:
:file=www.openbsd.org/spamd/traplist.gz:The documentation does not show the :http: entry. My edits last night were geared toward removing the ":http:" lines.
Wierd, today I'm not getting the warning message when I start "/usr/local/libexec/spamd -d -v" manually even with those lines.
The all entry seems to be not generating correctly. This is what is generated:
all:
:whitelist:blacklist:nixspam:uatraps:test:This is what should be generated, assuming you want "blacklist" to override "whitelist" entries:
all:
:nixspam:whitelist:uatraps:whitelist:test:whitelist:blacklistIf you want "whitelist" to override the "blacklist" entries:
all:
:nixspam:whitelist:uatraps:whitelist:test:whitelist:blacklist:whitelistI would prefer to rename "whitelist" to something like "local-overrides" or "local-whitelist", and "blacklist" to "local-blacklist", just to avoid confusion when discussing having whitelist "whitelist" override entries in blacklist "blacklist". Probably not terribly important in the grand scheme of things.
-
I've been composing this message for several hours while fighting fires around here. Please forgive me if you've fixed some of these things since I started.
Bugs found so far:
Once I added a few traplist entries I noticed that on the SpamD Database tab, the icons for blacklist and spamtrap are not displaying.
spamd.conf:
the symlink needs to be in /usr/local/etc/spamd/ rather than /usr/local/etc.The SpamD External Sources tab adds entries similar to :
test:
:black:
:msg="you are rejected":
:method=http:
:http:
:file=www.openbsd.org/spamd/traplist.gz:The documentation does not show the :http: entry. My edits last night were geared toward removing the ":http:" lines.
Wierd, today I'm not getting the warning message when I start "/usr/local/libexec/spamd -d -v" manually even with those lines.
The all entry seems to be not generating correctly. This is what is generated:
all:
:whitelist:blacklist:nixspam:uatraps:test:This is what should be generated, assuming you want "blacklist" to override "whitelist" entries:
all:
:nixspam:whitelist:uatraps:whitelist:test:whitelist:blacklistIf you want "whitelist" to override the "blacklist" entries:
all:
:nixspam:whitelist:uatraps:whitelist:test:whitelist:blacklist:whitelistI would prefer to rename "whitelist" to something like "local-overrides" or "local-whitelist", and "blacklist" to "local-blacklist", just to avoid confusion when discussing having whitelist "whitelist" override entries in blacklist "blacklist". Probably not terribly important in the grand scheme of things.
As far as I know every one of these are fixed. Please reinstall and test again and report back further issues.