- wrote: > Hi,
> I've been reading and searching everywhere, but because of the hard > search option "without spamassassin" it is almost impossible > to find useful answers. I found some on the web, but none were > complete or clear. So, I'm asking again, and hope for an answer > that actually works and makes sense to me: > - What to comment out in amavisd.conf in order to entirely disable > anything related to spamassassin ? (oh how I hate typing the word, even) I don't use CentOS so I can't precisely answer most of your questions but this one is your main concern. To disable SA: @bypass_spam_checks_maps = (1); # uncomment to DISABLE anti-spam code Before: Jan 15 18:21:12 sfa amavis[2389]: Module Mail::SpamAssassin 3.001004 <...> Jan 15 18:21:12 sfa amavis[2389]: ANTI-SPAM code loaded Jan 15 18:21:12 sfa amavis[2389]: ANTI-SPAM-SA code loaded After: < no mention of Module Mail::SpamAssassin > <...> Jan 15 21:29:49 sfa amavis[2891]: ANTI-SPAM code NOT loaded Jan 15 21:29:49 sfa amavis[2891]: ANTI-SPAM-SA code NOT loaded > - Can anyone using CentOS, not using SA, please show me their: > /etc/amavisd.conf > /etc/freshclam.conf > /etc/clamd.conf > /etc/postfix/main.cf > /etc/postfix/master.cf > in their entire lengths, some that are actually in (production) use. Is your server going to relay mail to other servers or is it going to store mail locally? If local, how many mailboxes are you talking about? No point in showing config files that in no way serve your purpose. If you are looking to use settings from another system 'as is' with only a couple changes then you would have to find a system that installed the programs in the same manner you did, is also a CentOS system and also is going to deliver mail in the same manner (relay, local, virtual etc). http://www.postfix.org/ADDRESS_CLASS_README.html > - Why is the install of amavisd-new only possible WITH spamassassin? Amavisd-new does not require spamassassin. If your package maintainer lists it as such then that is a personal choice of the maintainer. Debian will not install spamassassin as a dependency for example. > Both seem to have been made dependent now, while I have no intention > of ever again using SA, so I don't like having to install it either. > Can I remove all SA parts from my server and don't break anything? I don't see why not. You may have to be careful about how you remove it so as not to remove packages required by other packages. If this were a FC5 system for example: 'rpm -e --nodeps spamassassin' might do the trick. > Anyone tried that with/in CentOS 4.*? > - Anyone ever really found out how to configure user-rights for > postfix, amavis, clamd, clamav, freshclam and all those together > and really understanding the why behind all of them ? Well, it works fine if postfix uses postfix, amavisd-new uses amavis (or vscan), clamd uses clamav (for example). In other words each program has a unique user assigned to it. > They have "user = postfix/clamav/amavis" options in their config files, > I could not find 1 how-to explaining why which of the config-files > should use what user for what option. It's the most confusing config > mess I've ever encountered using linux, not to mention the naming mess. I don't see a mess. I see each program running as a specific user. This seems pretty ordinary to me. This is geared toward preventing unauthorized users from manipulating files the program uses. However, when you have a need for two programs to share data (like clamd and amavisd-new) then you have to make this possible somehow. In this case the easy way is to add the clamav user to the amavisd-new user's group. http://www200.pair.com/mecham/spam/clamav-amavisd-new.html > No offense, but I just need/want to use a decent virusscanner with postfix, Then amavisd-new may be overkill in your case. Check out: http://memberwebs.com/nielsen/software/clamsmtp/ > and I end up having: > clamd, clamav, freshclam, amavis, amavisd, amavisd-new and postfix, > plus I have to find out what is being logged where and how. Total chaos. > To top it all off I can also check headers, bodies, attachments > of mail within postfix! Why would anyone then use amavis for that? Amavisd-new is much more flexible - it's able to provide different settings for different recipients and provide a wider range of actions when undesirable mail is found - such as quarantining and notifying administrators and other recipients. If you don't need that then maybe you don't need amavisd-new. Postfix is not designed as a content filter. > Sorry to post these questions all at once, but most of them are too closely > related to make different messages for them. I'm pretty sure many want > to know the same answers. Google needs them, desperately! > And yes, I'm working on a "how to" that actually shows the answers, > but I first need to have them, right? I can't recall a HOWTO for CentOS but there are a number for Fedora. > If you start with negative comments on what I ask, or begin with admin > moderator "you should read the manual first" crap, forget about me > reading it, you know I'm right about asking all this, it's NOT in the > manual. Also, high time for a wake-up call: Spamassassin is not that > popular among the administrators I know and work with. > Thanks in advance, for constructive answers. > Carl Gary V ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
