I'm trying to use spamassassin on 9.2, but it seems to be ignoring both /etc/mail/spamassassin/local.cf and ~/.spamassassin/user_prefs. Does anyone know how I can change the behavior of spamd so that it respects both of those files? Thanks, dk
On Thu, 23 Dec 2004 12:57:15 -0500, you wrote:
I'm trying to use spamassassin on 9.2, but it seems to be ignoring both /etc/mail/spamassassin/local.cf and ~/.spamassassin/user_prefs. Does anyone know how I can change the behavior of spamd so that it respects both of those files?
Thanks, dk
How did you install SA, and which version of SA are you trying to use? Current is 3.01, and the last time I let YOU near my SA installation, it busted what had been working very nicely for a year. YMMV. Mike- -- If you can keep your head while those around you are losing theirs... You may have a great career as a network administrator ahead! -- Please note - Due to the intense volume of spam, we have installed site-wide spam filters at catherders.com. If email from you bounces, try non-HTML, non-encoded, non-attachments,
On Thu, 2004-12-23 at 13:13 -0500, Michael W Cocke wrote:
How did you install SA, and which version of SA are you trying to use? Current is 3.01, and the last time I let YOU near my SA installation, it busted what had been working very nicely for a year. YMMV.
Mike-
I'm just using what came with SuSE 9.2, installed via YaST, at this point. (And any patches, if any, because I blindly apply whatever SuSE is handing out.) dk
David Krider wrote:
On Thu, 2004-12-23 at 13:13 -0500, Michael W Cocke wrote:
How did you install SA, and which version of SA are you trying to use? Current is 3.01, and the last time I let YOU near my SA installation, it busted what had been working very nicely for a year. YMMV.
Mike-
I'm just using what came with SuSE 9.2, installed via YaST, at this point. (And any patches, if any, because I blindly apply whatever SuSE is handing out.)
In that case you should check if sa is called by amavisd-new. Did you also install amavisd-new? If so, what output does the command "amavisd debug" generate? It should have a line like: Dec 23 23:20:05 hostname amavisd[9537]: ANTI-VIRUS code loaded Dec 23 23:20:05 hostname amavisd[9537]: ANTI-SPAM code loaded Sandy
On Thu, 2004-12-23 at 23:24 +0100, Sandy Drobic wrote:
In that case you should check if sa is called by amavisd-new. Did you also install amavisd-new? If so, what output does the command "amavisd debug" generate? It should have a line like:
Dec 23 23:20:05 hostname amavisd[9537]: ANTI-VIRUS code loaded Dec 23 23:20:05 hostname amavisd[9537]: ANTI-SPAM code loaded
Sandy
I hadn't had it installed, but everything I was reading was talking abou it, so I tried it out. Then it wouldn't process any mail because I didn't have an actual virus scanner installed. I thought amavis *was* a virus scanner. I was confused, and didn't want to continue to complicate the issue, so I uninstalled it again. dk
On Thursday 23 December 2004 5:24 pm, Sandy Drobic wrote:
In that case you should check if sa is called by amavisd-new. Did you also install amavisd-new? If so, what output does the command "amavisd debug" generate? It should have a line like:
Dec 23 23:20:05 hostname amavisd[9537]: ANTI-VIRUS code loaded Dec 23 23:20:05 hostname amavisd[9537]: ANTI-SPAM code loaded> rpm -qa|grep amav rpm -qa|grep amavis shows: amavisd-new-20030616p9-0
PaulsPC:/home/pbc # amavisd debug ERROR: MISSING REQUIRED BASIC MODULES: IO::Wrap IO::Stringy Unix::Syslog Mail::Field Mail::Address Mail::Header Mail::Internet MIME::Head MIME::Body MIME::Entity MIME::Parser Net::Server Net::Server::PreForkSimple MIME::Decoder::Base64 MIME::Decoder::Gzip64 BEGIN failed--compilation aborted at /usr/sbin/amavisd line 128. so, what does that mean?? -- Paul Cartwright Registered Linux user # 367800 X-Request-PGP: http://home.comcast.net/~p.cartwright/wsb/key.asc
Paul Cartwright wrote:
PaulsPC:/home/pbc # amavisd debug ERROR: MISSING REQUIRED BASIC MODULES: IO::Wrap IO::Stringy Unix::Syslog Mail::Field Mail::Address Mail::Header Mail::Internet MIME::Head MIME::Body MIME::Entity MIME::Parser Net::Server Net::Server::PreForkSimple MIME::Decoder::Base64 MIME::Decoder::Gzip64 BEGIN failed--compilation aborted at /usr/sbin/amavisd line 128.
so, what does that mean??
Dependency hell, I suppose. amavisd-new is a basically a perl script and it complains that several perl modules it requires are missing. Try to resolve the dependencies of amavisd-new in yast. Sandy
BEGIN failed--compilation aborted at /usr/sbin/amavisd line 128.
so, what does that mean??
Dependency hell, I suppose. amavisd-new is a basically a perl script and it complains that several perl modules it requires are missing. Try to resolve the dependencies of amavisd-new in yast. I just today finished a session with SUSE tech support, where I finally got YOU working. Yes, I know I have dependency H&LL ! I tried to run apt-get dist-upgrade and got all KINDS of errors!!! it said it would remove 50 packages including all kinds of KDE
On Thursday 23 December 2004 6:51 pm, Sandy Drobic wrote: packages..... so apt isn't going to work any time soon. I originally upgraded from 9.1 to 9.2 and I think there are still some 9.1 packages lingering... I just did a "check dependencies" on amavisd and it said all was FINE. on another note, I just noticed a button in YAST, UML ? install a UML system? was this always there and I just didn't notice it? -- Paul Cartwright Registered Linux user # 367800 X-Request-PGP: http://home.comcast.net/~p.cartwright/wsb/key.asc
Paul Cartwright wrote:
On Thursday 23 December 2004 6:51 pm, Sandy Drobic wrote:
BEGIN failed--compilation aborted at /usr/sbin/amavisd line 128.
so, what does that mean??
Dependency hell, I suppose. amavisd-new is a basically a perl script and it complains that several perl modules it requires are missing. Try to resolve the dependencies of amavisd-new in yast.
I just today finished a session with SUSE tech support, where I finally got YOU working. Yes, I know I have dependency H&LL ! I tried to run apt-get dist-upgrade and got all KINDS of errors!!! it said it would remove 50 packages including all kinds of KDE packages..... so apt isn't going to work any time soon.
Check the installation source in yast: Software -> Change Source of Installation (Check for version 9.2 and remove any previous sources) "rpm --rebuilddb" on the command line. That should rebuild the rpm database. Fire up yast and check again for missing and clashing packages. Also you can check the packages "amavisd-new" in yast. The button [Information] -> [Package Relations] will give you a list of the required packages. The list is quite long. I suggest you rebuild the rpm database, check if you can now detect missing dependencies in the system and then reinstall amavisd-new. There are a LOT of dependencies!!
I originally upgraded from 9.1 to 9.2 and I think there are still some 9.1 packages lingering... I just did a "check dependencies" on amavisd and it said all was FINE. on another note, I just noticed a button in YAST, UML ? install a UML system? was this always there and I just didn't notice it?
Haven't seen such a button but I am still using Suse 9.1 only as a server installation via ssh. Good luck! I would hate to reinstall my system from scratch. Are there any more buggy services on your system, critical installations you need to access continuously? Sandy
On Thursday 23 December 2004 8:11 pm, Sandy Drobic wrote:
Check the installation source in yast: Software -> Change Source of Installation (Check for version 9.2 and remove any previous sources) I did have packman_9.1 and old 9.1 repositories in there, but they were below the 9.2 CDs and ftp.suse
"rpm --rebuilddb" on the command line. That should rebuild the rpm database.
done.
Fire up yast and check again for missing and clashing packages.
YIPES! man, are there a BUNCH of problems. ok, I can resolve a bunch of problems of gnome issues ( I don't run gnome ). libecal.so.6 not available, required by gnome-panel...etc but kdegraphics3-scan 3.3.2-3 requires libexif.so.10 GIMP requires libexif.so.10 libhd.so.8 is required by hotplugctl,kdebase3-SuSE,susehelp_en and sssusehelp, and it wants to remove those packages!
Also you can check the packages "amavisd-new" in yast. The button [Information] -> [Package Relations] will give you a list of the required packages. The list is quite long. I suggest you rebuild the rpm database, check if you can now detect missing dependencies in the system and then reinstall amavisd-new. There are a LOT of dependencies!!
-- Paul Cartwright Registered Linux user # 367800 X-Request-PGP: http://home.comcast.net/~p.cartwright/wsb/key.asc
David Install amavisd, clamav Update via yast. Set in yast to use amavisd with postfix. Now all of your configurations are run from /etc/amavisd.conf. That is you will not use your spam settings under the spammassasin config file (not totally true, but it helps to know this.). This should help..... Personal Note: So when you going to update your site :> Neal http://www.justsuse.com
I'm just using what came with SuSE 9.2, installed via YaST, at this point. (And any patches, if any, because I blindly apply whatever SuSE is handing out.)
dk
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
On Thu, 2004-12-23 at 19:51 -0800, suse-list wrote:
David Install amavisd, clamav Update via yast.
Set in yast to use amavisd with postfix.
Now all of your configurations are run from /etc/amavisd.conf. That is you will not use your spam settings under the spammassasin config file (not totally true, but it helps to know this.). This should help.....
<SNIP>
I read through some of Neal's stuff, specifically this: http://www.justsuse.com/guides.php?which=23 The bottom line is that I'm going to write up what's going on here. Mail comes to port 25. Postfix picks it up. Postfix's config passes the email to amavisd running on port 10024. (Look at /etc/postfix/master.cf.) Then amavisd passes the email back to postfix on port 10025. (Look at /etc/amavisd.conf.) (Amavisd is configured OotB with the support for using clamd NOT enabled. Also clamd is setup for network use, not local, which I think would be backwards of the normal use case. Why SuSE would ship the config like this, I have NO idea, but you'll have to change these things.) Here's the tricky part. If you want spam scanning, you can take two paths. According to the article above, calling spamassassin from amavis makes spamassassin look for configs in different places, and might (I can't really be sure) not look at users' ~/.spamassassin/user_prefs.) I decided to skip allowing amavis to pass off to spamassassin. I commented out the spam checks in its config file. Instead, I put my old /etc/procmailrc file back into place: :0 hbfw | /usr/bin/spamc Which hands off to spamd. Luckily, it would seem that spamassassin is smart enough not to scan the email twice. If I leave spam detection enabled in amavis, and leave my feed to spamc in my procmailrc file, it would seem that only the amavis check is performed. So, at least there's that, right? This seems to be the most general way of using the tools as shipped. YMMV. I have to take SUSE to task on this one. There ought to be some writeup in the manual on how their email config is supposed to work. This whole setup took me almost a whole day to probe from the backside to see how it worked. Admittedly, I had never used virus scanning in email before, so this was a new chapter. But it remains that just writing up a few paragraphs like I did above would really have saved me a lot of time, and I'm sure I'm not alone here. Regards, dk
David Krider wrote:
I'm trying to use spamassassin on 9.2, but it seems to be ignoring both /etc/mail/spamassassin/local.cf and ~/.spamassassin/user_prefs. Does anyone know how I can change the behavior of spamd so that it respects both of those files?
Thanks, dk
You mean, it is actually checking mail, but it doesnt pay attention to config files, or it doesnt check at all? (you can check mail headers for X-Spam tag) Regards LeoR
On Thu, 2004-12-23 at 17:24 -0300, LeoRivas wrote:
You mean, it is actually checking mail, but it doesnt pay attention to config files, or it doesnt check at all? (you can check mail headers for X-Spam tag) Regards LeoR
Yeah, it checks, and I can see the header. For instance: X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=6.0 tests= I like my "required" down around 4.5, but setting "required_score 4.5" in either /etc/mail/spamassassin/local.cf or ~/.spamassassin/user_prefs never changes that line. dk
David Krider wrote:
On Thu, 2004-12-23 at 17:24 -0300, LeoRivas wrote:
You mean, it is actually checking mail, but it doesnt pay attention to config files, or it doesnt check at all? (you can check mail headers for X-Spam tag) Regards LeoR
Yeah, it checks, and I can see the header. For instance:
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=6.0 tests=
I like my "required" down around 4.5, but setting "required_score 4.5" in either /etc/mail/spamassassin/local.cf or ~/.spamassassin/user_prefs never changes that line.
dk
Is spamd running? i mean 'rcspamd status' or 'rcspamd start'?
On Friday 24 December 2004 7:02 am, LeoRivas wrote:
rcspamd status
Hi, Of course you can do it any way you want, but in SUSE 9.2 running KMail there is Spammassasin and anti vir integration. Use YAST > Install & Remove to install SA and Cclam AV, then under KMail > Tools > AV Wizard and SPAM Wizard and follow the wizard. Works like a charm. PeterB -- -- Proud SUSE user since 5.2 Loving SUSE 9.2 My BLOG == http://vancampen.org/blog --
participants (7)
-
David Krider -
LeoRivas -
Michael W Cocke -
Paul Cartwright -
Peter B Van Campen -
Sandy Drobic -
suse-list