On 1/16/07, Gary V <[EMAIL PROTECTED]> wrote:
> > - 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

OK, so that doesn't influence amavis' internal spamchecks, and is only
related to SA?

> 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?

14 users in total, all locally.

> 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'

I'm not really looking for 'as is' copying, just working examples to adapt.
That's always the best way, or at least that's what I've learned over the years.
For some reason the defaults in config files are not always that applicable.
Loads of double and triple negatives in descriptions too, it's like
reading law-books;
"# If you don't want to use this, do not disable that, try use this
instead, but only if" ;-)

> 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

Which is the majority, since CentOS has quite good and functional yum support.
That's why I'm asking, all the how-to's and tutorials are for strange
extra difficult
configurations, where the writer either assumes the reader knows all about it,
or thinks administrators spend 4 hours a day on just their e-mail server(s), or
all of them are using the CPU memory monster Spamassassin.

> (relay, local,
> virtual etc). http://www.postfix.org/ADDRESS_CLASS_README.html

If you use virtual or not is more a postfix config issue, not something
I need to worry about. I can read config files and understand them.
The combination: postfix, amavis, clamav seems to be the best one I know,
but as soon as you update versions, change the underlying operating system,
all hell breaks loose in config land..

> > - 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.

That's odd. Who would manage packages like that?
I think it's the rpmforge, the former Dag Wieers repository, in this case.
Go figure, they don't tell you that before you pick and install your server OS,
and Debian was a little too far behind on other packages I wanted, plus
I'm more familiar with the RH family.

> 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.

Unfortunately I found out it did not work fine, clam needed amavis, amavis
needed clam, I needed to at least change group permissions on some folders,
and not knowing why is a pain for me.

> 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

This clears it up a little, thanks.

> Then amavisd-new may be overkill in your case. Check out:
> http://memberwebs.com/nielsen/software/clamsmtp/

Very good tip, but I think I will miss the other amavis options,
as you so correctly write:

> 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.

Thanks for the great hints, I will use them in a wiki,
the How To will appear soon, with my experiences added.


Carl

-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/

Reply via email to