Peter wrote: > Hi, I'm having difficulty navigating the vast amount of configuration > options.
Yes, some day it may come in a friendlier form. > For instance, in a supplied conf file (amavisd.conf-default) > there is the following line: > @local_domains_maps = > (\%local_domains,[EMAIL PROTECTED],\$local_domains_re); > What does this mean? I can't find any explanations to the 2nd and 3rd > variables. This is the default value for @local_domains_maps (as are all the other items listed in amavisd.conf-default). If the value of @local_domains_maps is not changed from this default, it will use what is assigned to the three listed legacy variables. This particular setting is an example of backwards compatibility in amavisd-new. For example, in older versions of amavisd-new, one would often set: @local_domains_acl = ( ".$mydomain" ); or maybe: read_hash(\%local_domains, '/var/amavis/local_domains'); (or maybe both). This trick allows you to continue to do so, so when a user upgrades from 20030616-p10 to 2.4.2, they can get amavisd-new running without changing their amavisd.conf. >From the amavisd.conf supplied with the old 20030616-p10 version: @local_domains_acl = ( ".$mydomain" ); # $mydomain and its subdomains # @local_domains_acl = qw(); # default is empty, no recipient treated as local # @local_domains_acl = qw( .example.com ); # @local_domains_acl = qw( .example.com !host.sub.example.net .sub.example.net ); # @local_domains_acl = ( ".$mydomain", '.example.com', 'sub.example.net' ); # or alternatively(A), using a Perl hash lookup table, which may be assigned # directly, or read from a file, one domain per line; comments and empty lines # are ignored, a dot before a domain name implies its subdomains: # #read_hash(\%local_domains, '/var/amavis/local_domains'); #or alternatively(B), using a list of regular expressions: # $local_domains_re = new_RE( qr'[EMAIL PROTECTED]'i ); # # see README.lookups for syntax and semantics http://www.ijs.si/software/amavisd/README.lookups.txt > In general, I have found the documentation not to be lacking in > technical terms but it might be good to have several *basic* > configuration examples followed by more complex ones. > Peter The basic settings are in the supplied amavisd.conf. You can often start amavisd-new up by setting only $mydomain (and possibly $myhostname) and changing a few paths if you deviated from the installation instructions. The amavisd.conf-sample file has more detailed examples of many common settings. The amavisd.conf-default is used only as a reference to determine what the default values are for all the settings (and what possible settings there are). Unlike amavisd.conf and amavisd.conf-sample, amavisd.conf-default is not the type of file that (could|should) be used to configure amavisd-new. You may also find this of some use: http://www200.pair.com/mecham/spam/amavisd-settings.html Gary V Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ 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/
