Karsten,
> Nov 18 13:36:22 mail01 amavis[15852]: (15852-11) Passed SPAMMY,
> [80.67.18.000] [89.101.56.41] <[EMAIL PROTECTED]> ->
> <[EMAIL PROTECTED]>, Message-ID: <[EMAIL PROTECTED]>, mail_id:
> r6afH9rLp+KS, Hits: 8.349, size: 1760, queued_as: 4021F950009, 1589 ms
>
> Its obviously found spammy.
> But for this one customer neither the spam score header or the "### SPAM
> ###" as configured is added to the mail.
Make sure the recipient's domain is listed in @local_domains_maps.
'Subject' is only allowed to be modified for inbound and
internal-to-internal mail.
> My first problem is I can't really test this now because I drop Spam of
> score 10 or higher. Of course I will change this sometime for a minute
> and try out.
> But is there a better method to test a mail with spam score around 8?
My preferred way of testing new and unusual settings is to run a
test instance of amavisd on a separate port, then use mini_sendmail
to feed a test mail to that particular port.
When a regular amavisd is running too, a test instance must use
its own PID and lock file, its own port number, a temporary (work)
directory and a db directory (is used). The rest can be shared
(like SQL server, SpamAssassin helper directory, quarantine, ...).
This can be achieved by using a separate config file and specifying
it on a command line with a -c option, or, my preferred way,
by using a neat trick -- a command line option: -i instance-name,
then by the end of your usual amavisd.conf file override some
of the previously defined settings when $instance_name variable
happens to match your chosen name. There is no special magic
to the -i option and the $instance_name, all it does is
assign the value of option -i to the $instance_name variable,
which you can use as you please, typically in a .conf file.
For example, amavisd.conf:
[all your usual stuff here, but just before the end of a file:]
if ($instance_name eq 'test') {
$max_servers = 1;
$log_level = 5;
# $sa_debug = 1;
$TEMPBASE = "$MYHOME/tmp-am2";
$ENV{TMPDIR} = $TEMPBASE;
$pid_file = "$helpers_home/amavisd2.pid";
$lock_file = "$helpers_home/amavisd2.lock";
$db_home = "$MYHOME/var/db/amavis2";
$enable_db = 0;
$unix_socketname = undef;
$inet_socket_port = [8888];
# ... and any other setting you choose to override
}
Then run it from a command line:
# amavisd -i test debug
and submit a test mail to port 8888 from another console window:
mini_sendmail [EMAIL PROTECTED] -s127.0.0.1 -p8888 [EMAIL PROTECTED] <0.msg
> The real problem is I have no clue why it seems to work for all other
> smtp relay domains but not this one?
My first guess is that recipient is not considered local.
If that is not the case, some logging would be helpful.
Mark
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
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/
