[pfSense Support] Spamd
Spamd Database shows only white listed host, also unable to blacklist ips. any I Ideas? Thanks guys Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] spamd
hello, On pfsense board I cannnot find out whether spamd is working on pfsense 1.2.3 or not. Most messages on this topic suggest that it is not working. I would like to install it, but is it worth the trouble trying? Maybe special hacks are needed to make it work? Please help me to get rid of all this messages suggesting that I might need viagra. Peter - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] spamd package
Hello! How can I see if external providers for blacklists are working? Going to the shell my spamd.conf looks like: all:\ :whitelist:blacklist:SpewsL1:ChinaCIDR:KoreaCIDR: whitelist:\ :method=file:\ :white:\ :file=/var/db/whitelist.txt: blacklist:\ :black:\ :msg="Sorry, you spammed us before.":\ :method=file:\ :file=/var/db/blacklist.txt: SpewsL1:\ :black:\ :msg="":\ :method=http:\ :http:\ :file=www.openbsd.org/spamd/spews_list_level1.txt.gz: ChinaCIDR:\ :black:\ :msg="":\ :method=http:\ :http:\ :file=www.openbsd.org/spamd/chinacidr.txt.gz: KoreaCIDR:\ :black:\ :msg="":\ :method=http:\ :http:\ :file=www.openbsd.org/spamd/koreacidr.txt.gz: Thanks in advance, Josep Pujadas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] spamd issue?
I'm trying to set the NextMTA as an external IP for a good reason, but here's what I've found. Any ideas would be appreciated. Here's what I have figured out so far. external IP -> pfsense (spamd) -> next MTA (internal IP) This works fine external IP -> pfsense (spamd) -> next MTA (public IP) this will not work. Thanks, Sean
[pfSense Support] spamd package
Hi, I just tried to install spamd today, but it seems to block all my messages. I've waited 25 minutes, and still no mail arrives. I also tried to add some blacklist servers from the openbsd/spamd page, but it seems not to really work. It just kept three entries in the greylist, and nothing else passed into that list, nor anything went through the mailserver I entered as next MTA. When I telnetted into the SMTP port on my WAN side (from another location obviously), the SMTP HELO string came very slowly (but changing the value to '0' for the delay didn't make it faster). Where can I find good info on how to configure it basic... from that point I could maybe tweak a little, but a basic guideline would be great to start with. Kind regards, Michel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] spamd
Peter Roosenboom wrote: > hello, > > On pfsense board I cannnot find out whether spamd is working on pfsense 1.2.3 > or not. > Most messages on this topic suggest that it is not working. > I would like to install it, but is it worth the trouble trying? Maybe special > hacks are needed to make it work? > > Please help me to get rid of all this messages suggesting that I might need > viagra. > > Peter > > - > To unsubscribe, e-mail: support-unsubscr...@pfsense.com > For additional commands, e-mail: support-h...@pfsense.com > > Commercial support available - https://portal.pfsense.org > > spamd is a program to scan email looking for spam. what part of pfsense handles email messages? pfsense is a firewall. It deals in packets of data, not email messages. You need to use spamd with your email client or MTA, not pfsense. Lyle Giese LCR Computer Services, Inc. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] spamd
Lyle Giese wrote: Peter Roosenboom wrote: hello, On pfsense board I cannnot find out whether spamd is working on pfsense 1.2.3 or not. Most messages on this topic suggest that it is not working. I would like to install it, but is it worth the trouble trying? Maybe special hacks are needed to make it work? Please help me to get rid of all this messages suggesting that I might need viagra. Peter - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org spamd is a program to scan email looking for spam. what part of pfsense handles email messages? pfsense is a firewall. It deals in packets of data, not email messages. You need to use spamd with your email client or MTA, not pfsense. Lyle Giese LCR Computer Services, Inc. pfSense does have spamd and it behaves in completely different way than spamd you use with your mta. From package description: "Tarpits like spamd are fake SMTP servers, which accept connections but don't deliver mail. Instead, they keep the connections open and reply very slowly. If the peer is patient enough to actually complete the SMTP dialogue (which will take ten minutes or more), the tarpit returns a 'temporary error' code (4xx), which indicates that the mail could not be delivered successfully and that the sender should keep the mail in their queue and retry again later." Very effective if you are not afraid to loose any legitimate e-mail without being able to restore it from spam. Evgeny. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] spamd
On Fri, Oct 23, 2009 at 8:06 AM, Evgeny Yurchenko wrote: > Lyle Giese wrote: >> >> Peter Roosenboom wrote: >> >>> >>> hello, >>> >>> On pfsense board I cannnot find out whether spamd is working on pfsense >>> 1.2.3 or not. >>> Most messages on this topic suggest that it is not working. >>> I would like to install it, but is it worth the trouble trying? Maybe >>> special hacks are needed to make it work? >>> >>> Please help me to get rid of all this messages suggesting that I might >>> need viagra. >>> >>> Peter >>> >>> - >>> To unsubscribe, e-mail: support-unsubscr...@pfsense.com >>> For additional commands, e-mail: support-h...@pfsense.com >>> >>> Commercial support available - https://portal.pfsense.org >>> >>> >> >> spamd is a program to scan email looking for spam. what part of pfsense >> handles email messages? pfsense is a firewall. It deals in packets of >> data, not email messages. You need to use spamd with your email client >> or MTA, not pfsense. >> >> Lyle Giese >> LCR Computer Services, Inc. >> > > pfSense does have spamd and it behaves in completely different way than > spamd you use with your mta. > From package description: "Tarpits like spamd are fake SMTP servers, which > accept connections but don't deliver mail. Instead, they keep the > connections open and reply very slowly. If the peer is patient enough to > actually complete the SMTP dialogue (which will take ten minutes or more), > the tarpit returns a 'temporary error' code (4xx), which indicates that the > mail could not be delivered successfully and that the sender should keep the > mail in their queue and retry again later." > Very effective if you are not afraid to loose any legitimate e-mail without > being able to restore it from spam. To be very clear, the spamd package for pfSense performs grey and blacklisting as well as tarpitting. If the sending MTA comes back _after_ whatever the greylist time is, it'll be passed through to your MTA, if it comes back while it's still greylisted, it will be tarpitted. Read http://www.benzedrine.cx/relaydb.html for a good description on how this all works. FWIW, on my inbox it was about 90% effective (although I no longer have the graphs to show it) - however I personally stopped using it as I was tired of the delay in mails from sources that have never sent mail to me (standard issue with the greylist technique). --Bill - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] spamd
It seems that my question was not clear. I know what spamd is, I know that it is a package, connected tot pfSense 1.2.3. About half a year ago I even installed on my pfSense. But it did not function correctly. So I Uninstalled it. My question is does it function now? Or do I have to use special hacks to install it on the actual pfsense 1.2.3? Peter - Oorspronkelijk bericht - Van: "Evgeny Yurchenko" Aan: support@pfsense.com Verzonden: Vrijdag 23 oktober 2009 15:06:38 GMT +01:00 Amsterdam / Berlijn / Bern / Rome / Stockholm / Wenen Onderwerp: Re: [pfSense Support] spamd Lyle Giese wrote: > Peter Roosenboom wrote: > >> hello, >> >> On pfsense board I cannnot find out whether spamd is working on pfsense >> 1.2.3 or not. >> Most messages on this topic suggest that it is not working. >> I would like to install it, but is it worth the trouble trying? Maybe >> special hacks are needed to make it work? >> >> Please help me to get rid of all this messages suggesting that I might need >> viagra. >> >> Peter >> >> - >> To unsubscribe, e-mail: support-unsubscr...@pfsense.com >> For additional commands, e-mail: support-h...@pfsense.com >> >> Commercial support available - https://portal.pfsense.org >> >> >> > spamd is a program to scan email looking for spam. what part of pfsense > handles email messages? pfsense is a firewall. It deals in packets of > data, not email messages. You need to use spamd with your email client > or MTA, not pfsense. > > Lyle Giese > LCR Computer Services, Inc. > pfSense does have spamd and it behaves in completely different way than spamd you use with your mta. From package description: "Tarpits like spamd are fake SMTP servers, which accept connections but don't deliver mail. Instead, they keep the connections open and reply very slowly. If the peer is patient enough to actually complete the SMTP dialogue (which will take ten minutes or more), the tarpit returns a 'temporary error' code (4xx), which indicates that the mail could not be delivered successfully and that the sender should keep the mail in their queue and retry again later." Very effective if you are not afraid to loose any legitimate e-mail without being able to restore it from spam. Evgeny. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
[pfSense Support] Spamd and RRD
I have noticed that the log never changes in size from the default creation of 9.8k. It appears that my SPAMD service is not logging. If I delete the log it is never recreated unless I re-install the package. When I go to view the rrd graphs for Spamd I receive the message "There is no database available to generate spamd from." I'm wondering if anyone else has encountered this problem and what they did to fix it. Thanks in advance. Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] spamd package
On Thu, 1 Feb 2007 23:26:38 +0100, Josep Pujadas i Jubany wrote > - Is somebody working with the spamd package ??? With pfsense 1.0.1 it seems that the external providers and whitelist are not working. GUI don't have also a place to put blacklists (?). I had to make the following script: #!/bin/sh # # Josep Pujadas i Jubany (02-feb-2007) # Updating /var/db/blacklist.txt and /var/db/whitelist.txt for pfSense 1.0.1 # mkdir tmp cd tmp # /usr/bin/fetch http://www.openbsd.org/spamd/spews_list_level1.txt.gz /usr/bin/gunzip spews_list_level1.txt.gz cat spews_list_level1.txt > blacklist.txt cat ../lf.txt >> blacklist.txt # /usr/bin/fetch http://www.openbsd.org/spamd/chinacidr.txt.gz /usr/bin/gunzip chinacidr.txt.gz cat chinacidr.txt >> blacklist.txt cat ../lf.txt >> blacklist.txt # /usr/bin/fetch http://www.openbsd.org/spamd/koreacidr.txt.gz /usr/bin/gunzip koreacidr.txt.gz cat chinacidr.txt >> blacklist.txt cat ../lf.txt >> blacklist.txt # /usr/bin/fetch http://www.bellera.cat/josep/pfsense/spamd/whitelist.txt # mv blacklist.txt /var/db/. mv whitelist.txt /var/db/. /usr/local/sbin/spamd-setup # cd .. rm -R tmp (lf.txt is just a file with a blank line ...) Now the GUI says: Database totals: 70 total items in the whitelist. 15357 total items in the blacklist. 120 total items in the SpamDB. But I'm not sure that my spmad is good working. I think it does'nt not use blacklist.txt and whitelist.txt. For example, messages from gmail.com (a pool of mailservers) continue to be greylisted ... Please help! Josep Pujadas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] spamd installation failure
Here is the log file I'm getting when trying to install spamd. I have a fresh install of pfsense 1.0.1. The file apkg_spamd-3.7_3.tbz is created in the /tmp directory but is a zero byte file. # cat pkg_mgr_spamd.log Beginning package installation. Downloading package configuration file... Adding text to file /etc/syslog.conf spamd-3.7_3 Array ( [0] => tar: Error opening archive: Empty input file: Inappropriate file type or format [1] => pkg_add: tar extract of /tmp/apkg_spamd-3.7_3.tbz failed! [2] => pkg_add: unable to extract table of contents file from '/tmp/apkg_spa md-3.7_3.tbz' - not a package? [3] => pkg_add: 1 package addition(s) failed ) Package WAS NOT installed properly. Sean C. Peters President / Founder Tech Squared, Inc. 401 Albemarle Ave SE Roanoke, VA 24013 540.767.TECH (8324)
Re: [pfSense Support] spamd issue?
Public IP ---> NAT ---> Public IP not work, need proxy Con fecha 27/7/2007, "Sean Peters" <[EMAIL PROTECTED]> escribió: >I'm trying to set the NextMTA as an external IP for a good reason, but here's >what I've found. Any ideas would be appreciated. > > >Here's what I have figured out so far. > >external IP -> pfsense (spamd) -> next MTA (internal IP) > >This works fine > >external IP -> pfsense (spamd) -> next MTA (public IP) > >this will not work. > >Thanks, > >Sean WebMail Fuerza Aerea de Chile - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] spamd package
I have been successfully using the spamd package for about 2 weeks at one of my client sites, and it is working wonderfully. It has reduced the amount of spam that the site's email server was receiving from about 15000 per day to about 50 to 75 per day. I configured the package as follows: On the external spam data sources page, I have the following 2 items configured: provider: spamhaus type: blacklist provider method: url url: zen.spamhaus.org provider: uceprotect network type: blacklist provider method: file file: http://wget-mirrors.uceprotect.net/rbldnsd-all/dnsbl-1.uceprotect.net.gz On the white list tab, I have the client's local email server's IP address listed. I left the default configuration on the spamd settings tab. I am having excellent luck with this package running on a pair of firewalls using CARP. I manually replicated my settings on both boxes, and it successfully works during failover (although the settings and spam database don't replicate -- but that's a given with most of the add-on packages). I believe that you may be experiencing problems because you don't have your local email server white listed. Vaughn Reid III Michel Servaes wrote: Hi, I just tried to install spamd today, but it seems to block all my messages. I've waited 25 minutes, and still no mail arrives. I also tried to add some blacklist servers from the openbsd/spamd page, but it seems not to really work. It just kept three entries in the greylist, and nothing else passed into that list, nor anything went through the mailserver I entered as next MTA. When I telnetted into the SMTP port on my WAN side (from another location obviously), the SMTP HELO string came very slowly (but changing the value to '0' for the delay didn't make it faster). Where can I find good info on how to configure it basic... from that point I could maybe tweak a little, but a basic guideline would be great to start with. Kind regards, Michel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] spamd package
Vaughn, You should re-visit the spamhaus terms of service for their Zen service. It is not free for commercial use as you are apparently doing. Otherwise, thank you for the feedback on the package. -Gary Vaughn L. Reid III wrote: I have been successfully using the spamd package for about 2 weeks at one of my client sites, and it is working wonderfully. It has reduced the amount of spam that the site's email server was receiving from about 15000 per day to about 50 to 75 per day. I configured the package as follows: On the external spam data sources page, I have the following 2 items configured: provider: spamhaus type: blacklist provider method: url url: zen.spamhaus.org provider: uceprotect network type: blacklist provider method: file file: http://wget-mirrors.uceprotect.net/rbldnsd-all/dnsbl-1.uceprotect.net.gz On the white list tab, I have the client's local email server's IP address listed. I left the default configuration on the spamd settings tab. I am having excellent luck with this package running on a pair of firewalls using CARP. I manually replicated my settings on both boxes, and it successfully works during failover (although the settings and spam database don't replicate -- but that's a given with most of the add-on packages). I believe that you may be experiencing problems because you don't have your local email server white listed. Vaughn Reid III Michel Servaes wrote: Hi, I just tried to install spamd today, but it seems to block all my messages. I've waited 25 minutes, and still no mail arrives. I also tried to add some blacklist servers from the openbsd/spamd page, but it seems not to really work. It just kept three entries in the greylist, and nothing else passed into that list, nor anything went through the mailserver I entered as next MTA. When I telnetted into the SMTP port on my WAN side (from another location obviously), the SMTP HELO string came very slowly (but changing the value to '0' for the delay didn't make it faster). Where can I find good info on how to configure it basic... from that point I could maybe tweak a little, but a basic guideline would be great to start with. Kind regards, Michel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] spamd package
Gary, Thanks for the suggestion. My client is a not-for-profit library. They own the hardware. I provide consulting services/labor. So, I believe that their usage is appropriate. I do not sale pre-configured appliances. Gary Buckmaster wrote: Vaughn, You should re-visit the spamhaus terms of service for their Zen service. It is not free for commercial use as you are apparently doing. Otherwise, thank you for the feedback on the package. -Gary Vaughn L. Reid III wrote: I have been successfully using the spamd package for about 2 weeks at one of my client sites, and it is working wonderfully. It has reduced the amount of spam that the site's email server was receiving from about 15000 per day to about 50 to 75 per day. I configured the package as follows: On the external spam data sources page, I have the following 2 items configured: provider: spamhaus type: blacklist provider method: url url: zen.spamhaus.org provider: uceprotect network type: blacklist provider method: file file: http://wget-mirrors.uceprotect.net/rbldnsd-all/dnsbl-1.uceprotect.net.gz On the white list tab, I have the client's local email server's IP address listed. I left the default configuration on the spamd settings tab. I am having excellent luck with this package running on a pair of firewalls using CARP. I manually replicated my settings on both boxes, and it successfully works during failover (although the settings and spam database don't replicate -- but that's a given with most of the add-on packages). I believe that you may be experiencing problems because you don't have your local email server white listed. Vaughn Reid III Michel Servaes wrote: Hi, I just tried to install spamd today, but it seems to block all my messages. I've waited 25 minutes, and still no mail arrives. I also tried to add some blacklist servers from the openbsd/spamd page, but it seems not to really work. It just kept three entries in the greylist, and nothing else passed into that list, nor anything went through the mailserver I entered as next MTA. When I telnetted into the SMTP port on my WAN side (from another location obviously), the SMTP HELO string came very slowly (but changing the value to '0' for the delay didn't make it faster). Where can I find good info on how to configure it basic... from that point I could maybe tweak a little, but a basic guideline would be great to start with. Kind regards, Michel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] spamd package
So you don't config anything in the SpamD settings at all ? The nextMTA shouldn't be your mailserver ?? I tried with and without, but still no mail gets delivered... If I send a mail (from a spamless address), should the mail be visible in the SpamD database ?? And how much time will it take to be delivered in the true mailbox? 25 minutes, or is this a complete other thing here (the greylist I mean) I used to use MDaemon's SPAM (which was quite easy, since it almost works without a hassle), so this is quite a new approach for me... Vaughn L. Reid III schreef: I have been successfully using the spamd package for about 2 weeks at one of my client sites, and it is working wonderfully. It has reduced the amount of spam that the site's email server was receiving from about 15000 per day to about 50 to 75 per day. I configured the package as follows: On the external spam data sources page, I have the following 2 items configured: provider: spamhaus type: blacklist provider method: url url: zen.spamhaus.org provider: uceprotect network type: blacklist provider method: file file: http://wget-mirrors.uceprotect.net/rbldnsd-all/dnsbl-1.uceprotect.net.gz On the white list tab, I have the client's local email server's IP address listed. I left the default configuration on the spamd settings tab. I am having excellent luck with this package running on a pair of firewalls using CARP. I manually replicated my settings on both boxes, and it successfully works during failover (although the settings and spam database don't replicate -- but that's a given with most of the add-on packages). I believe that you may be experiencing problems because you don't have your local email server white listed. Vaughn Reid III Michel Servaes wrote: Hi, I just tried to install spamd today, but it seems to block all my messages. I've waited 25 minutes, and still no mail arrives. I also tried to add some blacklist servers from the openbsd/spamd page, but it seems not to really work. It just kept three entries in the greylist, and nothing else passed into that list, nor anything went through the mailserver I entered as next MTA. When I telnetted into the SMTP port on my WAN side (from another location obviously), the SMTP HELO string came very slowly (but changing the value to '0' for the delay didn't make it faster). Where can I find good info on how to configure it basic... from that point I could maybe tweak a little, but a basic guideline would be great to start with. Kind regards, Michel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] spamd package
On 5/1/08, Michel Servaes <[EMAIL PROTECTED]> wrote: > So you don't config anything in the SpamD settings at all ? > The nextMTA shouldn't be your mailserver ?? I tried with and without, but > still no mail gets delivered... Yep. > If I send a mail (from a spamless address), should the mail be visible in > the SpamD database ?? > And how much time will it take to be delivered in the true mailbox? 25 > minutes, or is this a complete other thing here (the greylist I mean) About 30 minutes to white list. > I used to use MDaemon's SPAM (which was quite easy, since it almost works > without a hassle), so this is quite a new approach for me... Verify in /tmp/rules.debug that you have a rdr for port 25 going to the next mta. In fact, post the block of rules around the SpamD rdr. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] spamd package
It still won't react... I waited more than 30 minutes, but it still doesn't come through... I see in the System log a lot of spamd(1080), disconnect after xxx seconds... This is the snip in my rules.debug : spam table table persist table persist table persist table persist file "/var/db/whitelist.txt" rdr pass on fxp0 proto tcp from to port smtp -> 127.0.0.1 port spamd rdr pass on fxp0 proto tcp from to port smtp -> 127.0.0.1 port spamd rdr pass on fxp0 proto tcp from ! to port smtp -> 127.0.0.1 port spamd rdr pass on fxp0 proto tcp from to port smtp -> 192.168.10.200 port smtp 192.168.10.200 is our local mailserver. Scott Ullrich schreef: On 5/1/08, Michel Servaes <[EMAIL PROTECTED]> wrote: So you don't config anything in the SpamD settings at all ? The nextMTA shouldn't be your mailserver ?? I tried with and without, but still no mail gets delivered... Yep. If I send a mail (from a spamless address), should the mail be visible in the SpamD database ?? And how much time will it take to be delivered in the true mailbox? 25 minutes, or is this a complete other thing here (the greylist I mean) About 30 minutes to white list. I used to use MDaemon's SPAM (which was quite easy, since it almost works without a hassle), so this is quite a new approach for me... Verify in /tmp/rules.debug that you have a rdr for port 25 going to the next mta. In fact, post the block of rules around the SpamD rdr. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] spamd package
What I just come to think of... should I disable the rule of pfsense itself ? I have used pfSense for almost 2 months now, and have opened port 25 in the very beginning... might it be that this open port is still there, and that spamd also has an open port ? I think I have the sitation below, when installing spamd ? WAN --> port25 --> LAN 192.168.10.200 WAN --> port25 --> LOCALHOST --> LAN 192.168.10.200 However, when telnetting into port 25 (with or without spamd) I get the answer of my mailserver (very slow with spamd installed, but I guess that would be that option to disappoint a spammer :) ) Michel Servaes schreef: It still won't react... I waited more than 30 minutes, but it still doesn't come through... I see in the System log a lot of spamd(1080), disconnect after xxx seconds... This is the snip in my rules.debug : spam table table persist table persist table persist table persist file "/var/db/whitelist.txt" rdr pass on fxp0 proto tcp from to port smtp -> 127.0.0.1 port spamd rdr pass on fxp0 proto tcp from to port smtp -> 127.0.0.1 port spamd rdr pass on fxp0 proto tcp from ! to port smtp -> 127.0.0.1 port spamd rdr pass on fxp0 proto tcp from to port smtp -> 192.168.10.200 port smtp 192.168.10.200 is our local mailserver. Scott Ullrich schreef: On 5/1/08, Michel Servaes <[EMAIL PROTECTED]> wrote: So you don't config anything in the SpamD settings at all ? The nextMTA shouldn't be your mailserver ?? I tried with and without, but still no mail gets delivered... Yep. If I send a mail (from a spamless address), should the mail be visible in the SpamD database ?? And how much time will it take to be delivered in the true mailbox? 25 minutes, or is this a complete other thing here (the greylist I mean) About 30 minutes to white list. I used to use MDaemon's SPAM (which was quite easy, since it almost works without a hassle), so this is quite a new approach for me... Verify in /tmp/rules.debug that you have a rdr for port 25 going to the next mta. In fact, post the block of rules around the SpamD rdr. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] SpamD not working
Sawadeekap
After a failed upgrade from 1.2.2 to 1.2.3, I made a fresh install from
pfSense Full, installed SpamD Package, but it didn't forward any Mails
to the internal Exchange Server.
I used the default settings from the package, added my internal exchange
server (172.22.1.x), and some blacklist RBLs. Didn't create NAT or Rules
for Port 25 on WAN ("easy" setup, public WAN IP, and a 172.22.0.0/16 on
the LAN).
And no, our IP is not blacklisted or so.
Is something known about that problem?
Thanks,
Fabian
-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] spamd installation failure
installed pfsense 1.2beta1 On 6/7/07, Sean Peters <[EMAIL PROTECTED]> wrote: Here is the log file I'm getting when trying to install spamd. I have a fresh install of pfsense 1.0.1. The file apkg_spamd-3.7_3.tbz is created in the /tmp directory but is a zero byte file. # cat pkg_mgr_spamd.log installBeginning package installation. Downloading package configuration file... Adding text to file /etc/syslog.conf spamd-3.7_3 Array ( [0] => tar: Error opening archive: Empty input file: Inappropriate file type or format [1] => pkg_add: tar extract of /tmp/apkg_spamd-3.7_3.tbz failed! [2] => pkg_add: unable to extract table of contents file from '/tmp/apkg_spa md-3.7_3.tbz' - not a package? [3] => pkg_add: 1 package addition(s) failed ) Package WAS NOT installed properly. Sean C. Peters President / Founder Tech Squared, Inc. 401 Albemarle Ave SE Roanoke, VA 24013 540.767.TECH (8324)
[pfSense Support] SpamD Package Needs Testers
For those of you not on the support forums, a bounty project to resurrect the SpamD package for pfSense 1.2-Release has started and Scott has kindly taken up the project. For the most part, it seems to be working, but it would be helpful for many more eyes to be looking at it. I know there have been a lot of people wanting this kind of functionality, so here's your chance to make it a great package. Keep in mind that this is a bounty project, however, so please do not be disrespectful to the developer or to the people who have paid for this development by flooding with feature requests. If you have a feature request, please contribute to the bounty in the forum and make your request there. -Gary - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] SpamD not working
Em 14-12-2009 21:20, Fabian Abplanalp escreveu:
Sawadeekap
After a failed upgrade from 1.2.2 to 1.2.3, I made a fresh install
from pfSense Full, installed SpamD Package, but it didn't forward any
Mails to the internal Exchange Server.
I used the default settings from the package, added my internal
exchange server (172.22.1.x), and some blacklist RBLs. Didn't create
NAT or Rules for Port 25 on WAN ("easy" setup, public WAN IP, and a
172.22.0.0/16 on the LAN).
And no, our IP is not blacklisted or so.
Is something known about that problem?
Thanks,
Fabian
-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
I'm using pfsense 1.2.3-Release and today i installed spamd to test.
In the first moment spamd are blocking every mail that come to port 25
to my network don't forwarding nothing to my mail server (postfix) too.
But, looking in pfsense forum i followed some threads about a bug in
spamd where we need change some permission to avoid a pfctl error report
in log.
That link show u what i'm talking about.
http://forum.pfsense.org/index.php?topic=18405.0
Then made the command:
"/pw user mod _spamd -u 0/"
And rebooting, the problema appear to be solved.
Now my mails are forwarded to mail server.
Remember, i've installed today, and don't know if everything is really fine.
att
Re: [pfSense Support] SpamD not working
Em 14-12-2009 21:55, zhushazang escreveu:
Em 14-12-2009 21:20, Fabian Abplanalp escreveu:
Sawadeekap
After a failed upgrade from 1.2.2 to 1.2.3, I made a fresh install
from pfSense Full, installed SpamD Package, but it didn't forward any
Mails to the internal Exchange Server.
I used the default settings from the package, added my internal
exchange server (172.22.1.x), and some blacklist RBLs. Didn't create
NAT or Rules for Port 25 on WAN ("easy" setup, public WAN IP, and a
172.22.0.0/16 on the LAN).
And no, our IP is not blacklisted or so.
Is something known about that problem?
Thanks,
Fabian
-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
I'm using pfsense 1.2.3-Release and today i installed spamd to test.
In the first moment spamd are blocking every mail that come to port 25
to my network don't forwarding nothing to my mail server (postfix) too.
But, looking in pfsense forum i followed some threads about a bug in
spamd where we need change some permission to avoid a pfctl error
report in log.
That link show u what i'm talking about.
http://forum.pfsense.org/index.php?topic=18405.0
Then made the command:
"/pw user mod _spamd -u 0/"
And rebooting, the problema appear to be solved.
Now my mails are forwarded to mail server.
Remember, i've installed today, and don't know if everything is really
fine.
att
Sorry guy, i need advise u about a this change in permission.
I really don't know if a process like that with root permitions are secure.
Then, think better before make this change in your system.
att
Re: [pfSense Support] SpamD not working
On 12/15/09 1:03 AM, zhushazang wrote: Em 14-12-2009 21:55, zhushazang escreveu: Sorry guy, i need advise u about a this change in permission. I really don't know if a process like that with root permitions are secure. Then, think better before make this change in your system. att Yes, sounds really ugly... Currently I use a portforward without spamd... I hope it will get fixed... Thanks, Fabian
[pfSense Support] spamd pfsense 2.0 beta 4
Has anyone using and **really working** with spamd inside pfsense 2.0 BETA 4. Cos i don't get any log, block or result using spamd. My version: Current version: 2.0-BETA4 Built On: Wed Aug 25 23:36:00 EDT 2010 Thanks for attention... signature.asc Description: OpenPGP digital signature
[pfSense Support] SpamD in front of multiple MTAs
I'm giving SpamD and have it all basically configured, although I'm stuck at the NextMTA setting. This setting appears to assume only a single MTA behind pfSense. Is this correct? Is there a way to specify multiple transport mappings for multiple MTAs or would this require me installing postfix behind the scenes and setting up the transport mappings from there? Another, semi-related question. How would the spamD package handle a situation where an MTA or multiple MTAs are sitting behind a bridged DMZ interface? Does the package set up an interception rule for inbound tcp-25 traffic? -Gary - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] spamd pfsense 2.0 beta 4
On Tue, Aug 31, 2010 at 3:18 PM, Zhu Sha Zang wrote: > Has anyone using and *really working* with spamd inside pfsense 2.0 BETA 4. Not that I'm aware of. Probably doesn't work. I'm not sure it works on any version. May not be hard to fix if you poke at the underlying bits. - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] SpamD in front of multiple MTAs
On 4/27/06, Gary Buckmaster <[EMAIL PROTECTED]> wrote: > I'm giving SpamD and have it all basically configured, although I'm > stuck at the NextMTA setting. This setting appears to assume only a > single MTA behind pfSense. Is this correct? Is there a way to specify > multiple transport mappings for multiple MTAs or would this require me > installing postfix behind the scenes and setting up the transport > mappings from there? Good question. I'd say right now its hot-wired to one host *BUT* we can make a change to support aliases, then you can add as many MTA's until your heart is content. > Another, semi-related question. How would the spamD package handle a > situation where an MTA or multiple MTAs are sitting behind a bridged DMZ > interface? Does the package set up an interception rule for inbound > tcp-25 traffic? Yep, at the moment it hijacks anything incoming to the firewall with destination port 25. Let me think about how this can be improved, but I have a feeling we may be able to do the same trick with aliases. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [pfSense Support] SpamD in front of multiple MTAs
Scott, Both of those additions would be truly awesome and I'm willing to offer up some testing resources for when you have free time to mess with these additions. Thanks very much! -Gary Scott Ullrich wrote: On 4/27/06, Gary Buckmaster <[EMAIL PROTECTED]> wrote: I'm giving SpamD and have it all basically configured, although I'm stuck at the NextMTA setting. This setting appears to assume only a single MTA behind pfSense. Is this correct? Is there a way to specify multiple transport mappings for multiple MTAs or would this require me installing postfix behind the scenes and setting up the transport mappings from there? Good question. I'd say right now its hot-wired to one host *BUT* we can make a change to support aliases, then you can add as many MTA's until your heart is content. Another, semi-related question. How would the spamD package handle a situation where an MTA or multiple MTAs are sitting behind a bridged DMZ interface? Does the package set up an interception rule for inbound tcp-25 traffic? Yep, at the moment it hijacks anything incoming to the firewall with destination port 25. Let me think about how this can be improved, but I have a feeling we may be able to do the same trick with aliases. Scott - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[pfSense Support] SpamD Broken Behavior Fixed, see attached patch.
filter.inc.patch: necessary for the correct operation of spamd
Table exists but was never populated or used. Fixed.
Table exists but was never populated. Fixed.
Broken rule logic for whitelist entries, either (rdr) or (no rdr). Fixed.
Comments:
I guess no one noticed that the static whitelisting didn't work, since
the same entries would eventually be dynamically whitelisted anyway.
You can observe the broken behavior clearly by whitelisting a test IP
that is known to not be dynamically whitelisted already, then telneting
to any IP behind pfsense on port 25 from the test IP.
Having been whitelisted, you should not be rdr(ed) to spamd. But you are.
The problem was in using as the same table for both static
and dynamic entries. spamlogd removes the entries immediately after
they're loaded.
Blacklisting (via /var/db/blacklist.txt) did not work.
813,822d812
< if(file_exists("/var/db/whitelist.txt"))
< $natrules .= "table persist file
\"/var/db/whitelist.txt\"\n";
< else
< $natrules .= "table persist\n";
< if(file_exists("/var/db/blacklist.txt"))
< $natrules .= "table persist file
\"/var/db/blacklist.txt\"\n";
< else
< $natrules .= "table persist\n";
< $natrules .= "table persist\n";
< $natrules .= "table persist\n";
823a814,821
> $natrules .= "table persist\n";
> $natrules .= "table persist\n";
> $natrules .= "table persist\n";
> if(file_exists("/var/db/whitelist.txt"))
> $natrules .= "table persist file
> \"/var/db/whitelist.txt\"\n";
> $natrules .= "rdr pass on {$wanif} proto tcp from
> to port smtp -> 127.0.0.1 port spamd\n";
> $natrules .= "rdr pass on {$wanif} proto tcp from to
> port smtp -> 127.0.0.1 port spamd\n";
> $natrules .= "rdr pass on {$wanif} proto tcp from
> ! to port smtp -> 127.0.0.1 port spamd\n";
825,832c823,827
<
foreach($config['installedpackages']['spamdsettings']['config'] as $ss)
< $nextmta = $ss['nextmta'];
< if($nextmta <> "")
< $natrules .= "rdr pass on {$wanif} proto tcp from {
} to port smtp -> {$nextmta} port smtp\n";
< else
< $natrules .= "no rdr on {$wanif} proto tcp from
to any port = smtp\n";
< $natrules .= "rdr pass on {$wanif} proto tcp from {
} to port smtp -> 127.0.0.1 port spamd\n";
< $natrules .= "rdr pass on {$wanif} proto tcp from {
! } to port smtp -> 127.0.0.1 port spamd\n";
---
>
> foreach($config['installedpackages']['spamdsettings']['config'] as $ss)
> $nextmta = $ss['nextmta'];
> if($nextmta <> "") {
> $natrules .= "rdr pass on {$wanif} proto tcp from
> to port smtp -> {$nextmta} port smtp\n";
> }
-
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] SpamD Broken Behavior Fixed, see attached patch.
On Thu, Jun 18, 2009 at 10:25 AM, Tim A. wrote: > > filter.inc.patch: necessary for the correct operation of spamd > > Table exists but was never populated or used. Fixed. > Table exists but was never populated. Fixed. > Broken rule logic for whitelist entries, either (rdr) or (no rdr). Fixed. > > > Comments: > I guess no one noticed that the static whitelisting didn't work, since the > same entries would eventually be dynamically whitelisted anyway. > You can observe the broken behavior clearly by whitelisting a test IP that is > known to not be dynamically whitelisted already, then telneting to any IP > behind pfsense on port 25 from the test IP. > Having been whitelisted, you should not be rdr(ed) to spamd. But you are. > The problem was in using as the same table for both static and > dynamic entries. spamlogd removes the entries immediately after they're > loaded. > Blacklisting (via /var/db/blacklist.txt) did not work. > Hey this is great, thank you! Can you please do a diff -rub and then email the patch as an attachment to coret...@pfsense.org and I will get it promptly committed. Thanks for working on this! Scott - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] SpamD Broken Behavior Fixed, see attached patch.
Scott Ullrich wrote: Can you please do a diff -rub you want a recursive diff of the whole system? - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] SpamD Broken Behavior Fixed, see attached patch.
On Thu, Jun 18, 2009 at 9:24 PM, Tim A. wrote: > Scott Ullrich wrote: >> >> Can you please do a diff -rub > > you want a recursive diff of the whole system? No, sorry I was not more clear. Just a diff -rub of filter.inc Scott - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] SpamD Broken Behavior Fixed, see attached patch.
Scott Ullrich wrote: want a recursive diff of the whole system? No, sorry I was not more clear. Just a diff -rub of filter.inc No, no, I'm unfamiliar with the process. I'm sure you were perfectly clear. Ok, but I'll have to clean up first. A diff -rub in my current setup is messy. I guess I'm working a bit bass ackwards here. I copied the modified file from my production box (1.2.2) to my new 1.2.2 dev VM and diffed it there, removing the additional (dev) entries by hand, leaving only the pertinent. Anyway, I have a standard 1.2.2 vm installing and can do it there when its done.
Re: [pfSense Support] SpamD Broken Behavior Fixed, see attached patch.
Scott Ullrich wrote:
Hey this is great, thank you!
Can you please do a diff -rub and then email the patch as an
attachment to coret...@pfsense.org and I will get it promptly
committed.
Done.
I've also attached a patch for spamd_db.php that makes the GUI more
accurate and informative in the db accounting.
I'd also like to modify the package to add options for enabling
spamd-setup -b and spamlogd -I options which I use and should be
selectable I think.
There should also be a blacklist tab for editing the blacklist.txt file,
just as there is with the whitelist.txt\
~Tim
--- filter.inc_1.2.2-REL2009-06-18 22:09:05.0 -0400
+++ filter.inc_1.2.2-REL-spamd-fix 2009-06-18 21:35:09.0 -0400
@@ -810,21 +810,26 @@
/* is SPAMD insalled? */
if (is_package_installed("spamd") == 1) {
$natrules .= "\n# spam table \n";
-
+ if(file_exists("/var/db/whitelist.txt"))
+ $natrules .= "table persist file
\"/var/db/whitelist.txt\"\n";
+ else
$natrules .= "table persist\n";
+ if(file_exists("/var/db/blacklist.txt"))
+ $natrules .= "table persist file
\"/var/db/blacklist.txt\"\n";
+ else
$natrules .= "table persist\n";
$natrules .= "table persist\n";
- if(file_exists("/var/db/whitelist.txt"))
- $natrules .= "table persist file
\"/var/db/whitelist.txt\"\n";
- $natrules .= "rdr pass on {$wanif} proto tcp from
to port smtp -> 127.0.0.1 port spamd\n";
- $natrules .= "rdr pass on {$wanif} proto tcp from to
port smtp -> 127.0.0.1 port spamd\n";
- $natrules .= "rdr pass on {$wanif} proto tcp from
! to port smtp -> 127.0.0.1 port spamd\n";
+ $natrules .= "table persist\n";
+
if($config['installedpackages']['spamdsettings']['config'])
foreach($config['installedpackages']['spamdsettings']['config'] as $ss)
$nextmta = $ss['nextmta'];
- if($nextmta <> "") {
- $natrules .= "rdr pass on {$wanif} proto tcp from
to port smtp -> {$nextmta} port smtp\n";
- }
+ if($nextmta <> "")
+$natrules .= "rdr pass on {$wanif} proto tcp from {
} to port smtp -> {$nextmta} port smtp\n";
+ else
+ $natrules .= "no rdr on {$wanif} proto tcp from
to any port = smtp\n";
+ $natrules .= "rdr pass on {$wanif} proto tcp from {
} to port smtp -> 127.0.0.1 port spamd\n";
+ $natrules .= "rdr pass on {$wanif} proto tcp from {
! } to port smtp -> 127.0.0.1 port spamd\n";
}
/* load balancer anchor */
--- spamd_db.php_1.2.2-REL 2009-06-18 01:56:34.0 -0400
+++ spamd_db.php_1.2.2-REL-spamd-fix2009-06-18 11:15:14.0 -0400
@@ -176,17 +176,18 @@
include("head.inc");
if(file_exists("/var/db/whitelist.txt"))
- $whitelist_items = `cat /var/db/whitelist.txt | wc -l`;
+ $static_whitelist_items = `pfctl -T show -t whitelist | wc -l`;
else
$whitelist_items = 0;
if(file_exists("/var/db/blacklist.txt"))
- $blacklist_items = `cat /var/db/blacklist.txt | wc -l`;
+ $static_blacklist_items = `pfctl -T show -t blacklist | wc -l`;
else
$blacklist_items = 0;
// Get an overall count of the database
$spamdb_items = `/usr/local/sbin/spamdb | wc -l`;
+$accounted_items = $spamdb_items + $static_whitelist_items +
$static_blacklist_items;
// Get blacklist and whitelist count from database
$spamdb_white = `/usr/local/sbin/spamdb | grep WHITE | wc -l`;
@@ -194,8 +195,8 @@
$spamdb_grey = `/usr/local/sbin/spamdb | grep GREY | wc -l`;
// Now count the user contributed whitelist and blacklist count
-$whitelist_items = $whitelist_items + $spamdb_white;
-$blacklist_items = $blacklist_items + $spamdb_black;
+$whitelist_items = $static_whitelist_items + $spamdb_white;
+$blacklist_items = $static_blacklist_items + $spamdb_black;
?>
@@ -447,10 +448,11 @@
Database totals:
";
- echo "{$blacklist_items} total items in the
blacklist.";
+ echo "{$whitelist_items} total items in the whitelist:
{$spamdb_white} dynamic, {$static_whitelist_items} static
(/var/db/whitelist.txt).";
+ echo "{$blacklist_items} total items in the blacklist:
{$spamdb_black} dynamic, {$static_blacklist_items} static
(/var/db/blacklist.txt).";
echo "{$spamdb_grey} total items in the greylist.";
echo "{$spamdb_items} total items in the SpamDB.";
+ echo "{$accounted_items} total accounted items.";
?>
-
To
Re: [pfSense Support] SpamD Broken Behavior Fixed, see attached patch.
On Thu, Jun 18, 2009 at 9:53 PM, Tim A. wrote: > No, no, I'm unfamiliar with the process. I'm sure you were perfectly clear. > Ok, but I'll have to clean up first. > A diff -rub in my current setup is messy. I guess I'm working a bit bass > ackwards here. > I copied the modified file from my production box (1.2.2) to my new 1.2.2 > dev VM and diffed it there, removing the additional (dev) entries by hand, > leaving only the pertinent. > > Anyway, I have a standard 1.2.2 vm installing and can do it there when its > done. All you need to do is use the -rub option with diff the next time. When you try to apply your patch it will not work. For example: diff -rub filter.inc.new filter.inc.old (I may have the arguments reversed but it should be obvious). Thanks, Scott - To unsubscribe, e-mail: support-unsubscr...@pfsense.com For additional commands, e-mail: support-h...@pfsense.com Commercial support available - https://portal.pfsense.org
Re: [pfSense Support] SpamD Broken Behavior Fixed, see attached patch.
Scott Ullrich wrote: All you need to do is use the -rub option with diff the next time. When you try to apply your patch it will not work. I thought there might be a problem. When I tested the patch it complained but worked out anyway. So I figured it was ok. Will -rub em from now on.
Re: [pfSense Support] SpamD Broken Behavior Fixed, see attached patch.
Tim A. wrote:
Scott Ullrich wrote:
Hey this is great, thank you!
Can you please do a diff -rub and then email the patch as an
attachment to coret...@pfsense.org and I will get it promptly
committed.
Done.
I've also attached a patch for spamd_db.php that makes the GUI more
accurate and informative in the db accounting.
I'd also like to modify the package to add options for enabling
spamd-setup -b and spamlogd -I options which I use and should be
selectable I think.
There should also be a blacklist tab for editing the blacklist.txt
file, just as there is with the whitelist.txt\
~Tim
I am disappointed to see SpamD was removed from the packages rather than
fixed.
Now I need it.
How do I get it?
I can fix it after its installed, but I'm not sure how to make the
package to get it installed
--- filter.inc_1.2.2-REL2009-06-18 22:09:05.0 -0400
+++ filter.inc_1.2.2-REL-spamd-fix 2009-06-18 21:35:09.0 -0400
@@ -810,21 +810,26 @@
/* is SPAMD insalled? */
if (is_package_installed("spamd") == 1) {
$natrules .= "\n# spam table \n";
-
+ if(file_exists("/var/db/whitelist.txt"))
+ $natrules .= "table persist file
\"/var/db/whitelist.txt\"\n";
+ else
$natrules .= "table persist\n";
+ if(file_exists("/var/db/blacklist.txt"))
+ $natrules .= "table persist file
\"/var/db/blacklist.txt\"\n";
+ else
$natrules .= "table persist\n";
$natrules .= "table persist\n";
- if(file_exists("/var/db/whitelist.txt"))
- $natrules .= "table persist file
\"/var/db/whitelist.txt\"\n";
- $natrules .= "rdr pass on {$wanif} proto tcp from
to port smtp -> 127.0.0.1 port spamd\n";
- $natrules .= "rdr pass on {$wanif} proto tcp from to
port smtp -> 127.0.0.1 port spamd\n";
- $natrules .= "rdr pass on {$wanif} proto tcp from
! to port smtp -> 127.0.0.1 port spamd\n";
+ $natrules .= "table persist\n";
+
if($config['installedpackages']['spamdsettings']['config'])
foreach($config['installedpackages']['spamdsettings']['config'] as $ss)
$nextmta = $ss['nextmta'];
- if($nextmta <> "") {
- $natrules .= "rdr pass on {$wanif} proto tcp from
to port smtp -> {$nextmta} port smtp\n";
- }
+ if($nextmta <> "")
+$natrules .= "rdr pass on {$wanif} proto tcp from {
} to port smtp -> {$nextmta} port smtp\n";
+ else
+ $natrules .= "no rdr on {$wanif} proto tcp from
to any port = smtp\n";
+ $natrules .= "rdr pass on {$wanif} proto tcp from {
} to port smtp -> 127.0.0.1 port spamd\n";
+ $natrules .= "rdr pass on {$wanif} proto tcp from {
! } to port smtp -> 127.0.0.1 port spamd\n";
}
/* load balancer anchor */
--- spamd_db.php_1.2.2-REL 2009-06-18 01:56:34.0 -0400
+++ spamd_db.php_1.2.2-REL-spamd-fix2009-06-18 11:15:14.0 -0400
@@ -176,17 +176,18 @@
include("head.inc");
if(file_exists("/var/db/whitelist.txt"))
- $whitelist_items = `cat /var/db/whitelist.txt | wc -l`;
+ $static_whitelist_items = `pfctl -T show -t whitelist | wc -l`;
else
$whitelist_items = 0;
if(file_exists("/var/db/blacklist.txt"))
- $blacklist_items = `cat /var/db/blacklist.txt | wc -l`;
+ $static_blacklist_items = `pfctl -T show -t blacklist | wc -l`;
else
$blacklist_items = 0;
// Get an overall count of the database
$spamdb_items = `/usr/local/sbin/spamdb | wc -l`;
+$accounted_items = $spamdb_items + $static_whitelist_items +
$static_blacklist_items;
// Get blacklist and whitelist count from database
$spamdb_white = `/usr/local/sbin/spamdb | grep WHITE | wc -l`;
@@ -194,8 +195,8 @@
$spamdb_grey = `/usr/local/sbin/spamdb | grep GREY | wc -l`;
// Now count the user contributed whitelist and blacklist count
-$whitelist_items = $whitelist_items + $spamdb_white;
-$blacklist_items = $blacklist_items + $spamdb_black;
+$whitelist_items = $static_whitelist_items + $spamdb_white;
+$blacklist_items = $static_blacklist_items + $spamdb_black;
?>
@@ -447,10 +448,11 @@
Database totals:
";
- echo "{$blacklist_items} total items in the
blacklist.";
+ echo "{$whitelist_items} total items in the whitelist:
{$spamdb_white} dynamic, {$static_whitelist_items} static
(/var/db/whitelist.txt).";
+ echo "{$blacklist_items} total items in the blacklist:
{$spamdb_black} dynamic, {$static_blacklist_items} static
(/var/db/blacklist.txt).";
echo "{$spamdb_grey} total items in the greylist.";
