Peter wrote:
> Permit me to specify my situation...
> I have SQL lookups going but I decided I want to remove them. I have
> about a dozen domains being checked. I have the following pertinent
> lines:
> -----------------------
> $mydomain = 'myhostdomain.com';
> read_hash(\%local_domains, '/etc/postfix/relay_domains');
> @lookup_sql_dsn = (
> ['DBI:mysql:database=spamassassin;host=127.0.0.1;port=3306', 'amavisd',
> 'password'] );
> @storage_sql_dsn = @lookup_sql_dsn;
> -----------------------
> QUESTIONS:
> 1. What is the best way of specifying my domains? Is it like this:
> @local_domains_maps = ( read_hash("$MYHOME/local_domains") );
There is no reason to change the way you have it listed now. The way
you are doing it is very convenient.
> 2. In order to cease to use SQL lookups for my domains do I simply
> remove the last 2 lines? An earlier tip on this list suggested I at
> least keep SQL lookups for AWL & Bayes (no idea yet on how to implement
> these two mechanisms).
Yes, comment out those *_sql_dsn settings. The Bayes SQL stuff has nothing
to do with amavisd-new per se, it's a SpamAssassin thing and is configured
in local.cf. Here are a bunch of links:
http://www200.pair.com/mecham/spam/debian-spamassassin-sql.html
http://www200.pair.com/mecham/spam/fc4-spamassassin-sql.html
http://wiki.apache.org/spamassassin/BetterDocumentation/SqlReadmeBayes?highlight=%28mysql%29
http://people.apache.org/~parker/presentations/
http://www.paulstimesink.com/index.php?op=ViewArticle&articleId=163&blogId=2
http://www.paulstimesink.com/index.php?op=ViewArticle&articleId=167&blogId=2
http://dev.mysql.com/doc/mysql/en/index.html
http://infocenter.guardiandigital.com/archive/amavis/2004/Dec/0319.html
http://spamassassin.apache.org/full/3.0.x/dist/sql/README.bayes
http://spamassassin.apache.org/full/3.0.x/dist/sql/README
http://www.sng.ecs.soton.ac.uk/mailscanner/serve/cache/390.html
https://secure.renaissoft.com/maia/wiki/SpamAssassin3SQLBayes
> 3. How do I bypass all checks for specific recipients?
There are a number of ways, it depends on how many you are talking
about. If you are talking about just a few, you can simply list them
in amavisd.conf:
@bypass_virus_checks_maps = ( [qw( [EMAIL PROTECTED] [EMAIL PROTECTED] )] );
@virus_lovers_maps = ( [qw( [EMAIL PROTECTED] [EMAIL PROTECTED] )] );
@bypass_spam_checks_maps = ( [qw( [EMAIL PROTECTED] [EMAIL PROTECTED] )] );
@spam_lovers_maps = ( [qw( [EMAIL PROTECTED] [EMAIL PROTECTED] )] );
@bypass_banned_checks_maps = ( [qw( [EMAIL PROTECTED] [EMAIL PROTECTED] )] );
@banned_files_lovers_maps = ( [qw( [EMAIL PROTECTED] [EMAIL PROTECTED] )] );
@bypass_header_checks_maps = ( [qw( [EMAIL PROTECTED] [EMAIL PROTECTED] )] );
@bad_header_lovers_maps = ( [qw( [EMAIL PROTECTED] [EMAIL PROTECTED] )] );
When you use @bypass for someone, also set a corresponding @lovers
for them to insure delivery.
Since in this example every setting is identical (this is not always
the case - you might want to mix and match), you could abbreviate it
like this: First, populate one variable:
@bad_header_lovers_maps = ( [qw( [EMAIL PROTECTED] [EMAIL PROTECTED] )] );
Then assign the same data to the rest:
@bypass_virus_checks_maps = @virus_lovers_maps = @bypass_spam_checks_maps =
@spam_lovers_maps = @bypass_banned_checks_maps = @banned_files_lovers_maps =
@bypass_header_checks_maps = @bad_header_lovers_maps
(boy, that's going to wrap)
> 4. I based my current setup on a ready-made tutorial. Now I see that I
> am missing a boatload of options listed in the provided amavisd.conf
> file. Are the following settings really recommended by default? I am
> using 2.3.3 and none of them are in my file:
> a) @decoders
> b) @score_sender_maps
> c) $banned_filename_re
> d) @keep_decoded_original_maps
> e) @viruses_that_fake_sender_maps
> For (a) I have lines that look related:
> $file = 'file';
> $arc = ['nomarch', 'arc'];
> $gzip = 'gzip';
> $bzip2 = 'bzip2';
> $cpio = 'cpio';
> $uncompress = ['uncompress', 'gzip -d', 'zcat'];
> $lha = 'lha';
> $unarj = 'unarj';
> $unrar = 'unrar';
> $zoo = 'zoo';
a) They are related, and you can continue to use what you have instead
of the @decoders section. Use one or the other, but not both. Since you
are using a newer version of amavisd-new, you can use the newer form and
probably should (it is more complete that what you have here - and a
cleaner way to do it with newer versions on amavisd-new).
Note: $file = 'file'; is not part of the @decoders section. It is a
default however, so you could remove it.
b) If you want to do any soft white/black listing, you would need to
copy the entire section over. It's at your discretion.
c) Unless you are using $banned_namepath_re, without $banned_filename_re,
you have no list of files/file types you ban. Most people retain and
configure this section in order to ban certain file types. Most people
will not use $banned_namepath_re. Just don't have both configured.
d) @keep_decoded_original_maps adds some safety so go ahead and bring
it over.
e) @viruses_that_fake_sender_maps will prevent sending of DSNs to
virus senders (because the configuration example assumes all
viruses use a spoofed sender address). Use at your discretion, but I
personally recommend it.
> Thanks for your help.
> Peter
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/
