SpamD Package Needs Testers
-
The service does restart after changes:
mwexec("/usr/local/etc/rc.d/spamd.sh stop");
mwexec("/usr/local/etc/rc.d/spamd.sh start");Still need to convert the crontab code over to the new format. Will do so shortly.
-
Using an alias in the NextMTA field doesn't appear to work (I have surrounded in quotes as per the instructions). If you tell me the command to view the logs I will tell you the exact error that spamd says (it has vanished from the web view of the log).
Putting in the IP works fine.
Look in /tmp/rules.debug
-
The service does restart after changes:
mwexec("/usr/local/etc/rc.d/spamd.sh stop");
mwexec("/usr/local/etc/rc.d/spamd.sh start");Still need to convert the crontab code over to the new format. Will do so shortly.
To get the NextMTA to change first of all from what I had {SBSr} to what I needed {SBS} (I made a typo) resulted in the same error in the logs still mentioning {SBSr}. I restarted the service and the error was being reported with the correct alias.
When I changed from {SBS} to the actual IP address the error was still shown in the logs with {SBS}. The way I fixed both of these was to manually restart the service.
-
other log …
Apr 17 19:13:39 spamlogd[38948]: Can not open db /var/db/spamd: No such file or directory -
To get the NextMTA to change first of all from what I had {SBSr} to what I needed {SBS} (I made a typo) resulted in the same error in the logs still mentioning {SBSr}. I restarted the service and the error was being reported with the correct alias.
When I changed from {SBS} to the actual IP address the error was still shown in the logs with {SBS}. The way I fixed both of these was to manually restart the service.
Aha. Fix coming up shortly…
-
ops error in package 4.3.3
when hiting save button
Warning: Cannot modify header information - headers already sent by (output started at /usr/local/pkg/spamd.inc:1) in /usr/local/www/pkg_edit.php on line 35 -
ops error in package 4.3.3
when hiting save button
Warning: Cannot modify header information - headers already sent by (output started at /usr/local/pkg/spamd.inc:1) in /usr/local/www/pkg_edit.php on line 35Just fixed, thanks.
-
Lets keep this thread to bug reports only. Only folks who are contributing to the bounty will have a voice for feature additions for obvious reasons and I would like to keep that in the other bounty thread. Thanks.
-
Change NextMTA back to {SBS} and got the error:
===
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 is an alias. Changing to the IP address works fine (and the service doesn't appear to need restarted this time).</spamd-white>
-
Cahnge NextMTA back to {SBS} and got the error:
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 smtp
SBS is an alias.
Changing to the IP address works fine (and the service doesn't appear to need restarted this time).</spamd-white>
Show me the header of /tmp/rules.debug where the aliases are set. you should see something mentioning SBS near the top.
-
-
For kicks, add another ip to the alias. Does the problem go away?
-
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!