Raising the score...
Hello, I have an old email address that a few contacts still use to reach me. I've tried to get everyone up to date on the new address but no luck. That's not really the issue though... The reason I changed addresses was that the spam that was coming in was all addressed to the old address. I see that SA has a concept of 'blacklist_to' but that will probably be overkill...right? If I set up whitelists for the people who I know...and who still use my old adress...and blacklist all other mail that is addressed to this address...will that work? Is there a better way...besides begging these contacts to finally update their address books? :) TIA, Kevin
Raising the score...
Hello, I have an old email address that a few contacts still use to reach me. I've tried to get everyone up to date on the new address but no luck. That's not really the issue though... The reason I changed addresses was that the spam that was coming in was all addressed to the old address. I see that SA has a concept of 'blacklist_to' but that will probably be overkill...right? If I set up whitelists for the people who I know...and who still use my old adress...and blacklist all other mail that is addressed to this address...will that work? Is there a better way...besides begging these contacts to finally update their address books? :) TIA, Kevin
Re: Curious output from spamassassin --local --debug
Cameron, The spamassassin program is waiting for input. If you are checking rules add '--lint' to your command line. Alternately you might want to direct some input into it. I found this out once when I missed typing '--lint' while I was testing my installation. HTH, Kevin Cameron Bales wrote: Hi I'm curious about what the output from spamassassin --local --debug looks like on somebody else's system. I'm getting what seems to me odd behaviour. The command is hanging on my machine (althouth SpamAssassin is working fine) example: [Machine:~] user% spamassassin --local --debug debug: SpamAssassin version 3.0.1 debug: Score set 0 chosen. debug: running in taint mode? yes debug: Running in taint mode, removing unsafe env vars, and resetting PATH debug: PATH included '/bin', keeping. debug: PATH included '/sbin', keeping. debug: PATH included '/usr/bin', keeping. debug: PATH included '/usr/sbin', keeping. debug: Final PATH set to: /bin:/sbin:/usr/bin:/usr/sbin ^C [Machine:~] user% As you can see I don't get a prompt back unless I abort the command. An example of more normal output and a hit about what might be wrong would be great. Cameron .:.
RE: Installation issues
Developement work like developing new rules? Anyway...we're up and running without spamassassin-tools. I need to get on CPAN and pull a couple modules that it claims to need before I can install it. Thank you so much for your help. Now I am off to learn about storing user specific rules...and hopefully being able to store those in an LDAP database. I heard that this was supposed to be a feature available in 3.0.0. This site is all LDAP driven so being able to store rules there will be very nice. Later, Kevin >> -Original Message- >> From: Kevin Morwood [mailto:[EMAIL PROTECTED] >> Sent: Thursday, October 21, 2004 4:32 PM >> To: users@spamassassin.apache.org >> Subject: RE: Installation issues >> >> >> Ok...that was easy. Never built from an RPM source before. Not bad. >> >> I figured out that I needed to then find the generated RPM >> files...and install those. >> >> Woohoo! SA 3.0.0 ...here I come >> >> Thanks again, >> Kevin > > Kevin > > The binaries should be somewhere like: > > /usr/src/redhat/RPMS/i386 > > Unless you use the --target directive of rpmbuild to build for another > architecture e.g. athlon. In which case they will be in: > > /usr/src/redhat/RPMS/athlon > > You get the idea. > > Anyway, you should end up with 2 rpms: > > 226223 Oct 4 23:23 spamassassin-3.0.0-1.athlon.rpm > 95460 Oct 4 23:23 spamassassin-tools-3.0.0-1.athlon.rpm > > You only need install spamassassin-tools-3.0.0-1..rpm if you intend to > do development stuff. > > HTH > > Alan > >
RE: Installation issues
Ok...that was easy. Never built from an RPM source before. Not bad. I figured out that I needed to then find the generated RPM files...and install those. Woohoo! SA 3.0.0 ...here I come Thanks again, Kevin >> -Original Message- >> From: Kevin Morwood [mailto:[EMAIL PROTECTED] >> Sent: Thursday, October 21, 2004 2:18 PM >> To: users@spamassassin.apache.org >> Subject: Installation issues >> >> Now, I am not able to find RPMs for 3.0.0 for RH9. So, I >> figured it shouldn't be >> too hard to just build it. Oh, how wrong can one be! >> > Kevin > > Don't give up. It is very easy. > > You can build the .src.rpm from the tar.gz on the SA website. > > Use: rpmbuild -tb Mail-Spamassassin-3.0.0.tar.gz > > Which may mean you need to rename the name of the download file to the > above. > > Alan >
Installation issues
Hello, I am sure this issue has come up before. I have seen mention of it but no resolution. I am trying to build/install SA 3.0.0. I have been using SA since 2.1 or something really old. The most recent I have installed (running currently) is 2.63. I have been installing these via RPMs. Now, I am not able to find RPMs for 3.0.0 for RH9. So, I figured it shouldn't be too hard to just build it. Oh, how wrong can one be! Not being a Perl/CPAN expert I am lost. When I run perl Makefile.PL...the resulting makefile is garbage. I write software for a living and it is easy to see that this makefile won't build anything. But as I said I write software for a living and I don't have real time to debug/fix this. Since I'm sure that someone has seen this before I would like just a nudge in the right direction. I have tried on both my production server and on a clean RH9. I thought maybe I had messed up the Perl environment so I built a new one from scratch. The end result was exactly the same. I will test whatever steps on the clean machine and then apply the same steps to the production server. In the worst case I'll end up with a new machine for handling all of our email (not a bad thing). Thanks in advance and sorry for the long post... Kevin
