Re: [AMaViS-user] newbie questions

This is a discussion on Re: [AMaViS-user] newbie questions within the Amavis User forums, part of the Anti-Spam and Anti-Virus Related Forums category; John, (apart from what Gary V already answered) > Does it just add the normal spam assassin headers? Most of ...


Go Back   Usenet Forums > Anti-Spam and Anti-Virus Related Forums > Amavis User

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 08-07-2005
Mark Martinec
 
Posts: n/a
Default Re: [AMaViS-user] newbie questions

John,


(apart from what Gary V already answered)

> Does it just add the normal spam assassin headers?


Most of it's lookalikes, yes. Remember that spam header fields are only
added for inbound mail, i.e. for recipients matching @local_domains_maps.

> 3) where do I define various pieces of the spam assassin environment?
> (like the location of the rules files, etc.) Mine are in a non-standard
> place.


The SA is initialized with the following call:

sub init() {
do_log(1, "SpamControl: initializing Mail::SpamAssassin");
my($saved_umask) = umask;
$spamassassin_obj = Mail::SpamAssassin->new({
debug => $sa_debug,
save_pattern_hits => $sa_debug,
dont_copy_prefs => 1,
local_tests_only => $sa_local_tests_only,
home_dir_for_helpers => $helpers_home,
stop_at_threshold => 0,
# DEF_RULES_DIR => '/usr/local/share/spamassassin',
# LOCAL_RULES_DIR => '/etc/mail/spamassassin',
#see man Mail::SpamAssassin for other options
});

in package Amavis::SpamControl, file amavisd.

If SA will not find its files in you environment, you will
need to either provide soft links, or modify the call,
e.g. by providing additional arguments, like the two
commented-out example lines. There is currently no
configurable parameter in amavisd.conf for that purpose.

> 4) it would be nice to see something that even remotely resembled a man
> page, especially for amavis.conf


I know. So far you will have to do with amavisd.conf*,
README.* files (especially the README.lookups),
and the amavisd-new-docs.html.

> 5) it would also be nice to see things like those virus definitions
> moved to a library type file, with the conf file being somewhat more
> human readable. Mailscanner's conf-file format seems pretty ideal to
> me.


Multiple config files are supported (place multiple -c options
in the 'amavisd start' line), or use the example at the end of
amavisd.conf-sample to 'include' all sub-config files from a
provided directory. The virus scanner definitions and other
settings may be placed into separate files if desired.

Mark


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
AMaViS-user mailing list
AMaViS-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/...fo/amavis-user
AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3
AMaViS-HowTos:http://www.amavis.org/howto/
Reply With Quote
Reply


Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT +1. The time now is 11:22 PM.


Powered by vBulletin® Version 3.6.8
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0