From Gary V:
> Creating and sending spam notifications is of limited use. In my
> opinion the reports are just as annoying as spam itself, but on
> occasion provide useful information for debugging.
Right. An exception to the above is when spam admin notifications
are only enabled for messages coming from inside. Regardless of
possibly faked sender address, an inside telltale IP address could
alert a postmaster of an infected/spam-zombie internal host.
To achieve that goal a MYNETS policy bank needs to be used.
For example:
$policy_bank{'MYNETS'} = { # mail originating from @mynetworks
virus_admin_maps => ["[EMAIL PROTECTED]"], # alert of infected local hosts
spam_admin_maps => ["[EMAIL PROTECTED]"], # alert of internal spam
spam_kill_level_maps => [7.0], # slightly more permissive spam kill level
};
A client's IP address is only available when using Postfix (through
its XFORWARD extension to the SMTP protocol)
(or I believe also through Petr Rehor's AM.PDP sendmail milter,
see README.milter for a link; but not through the old amavis-milter
that comes with amavisd-new, nor in dual-sendmail setup).
From Peter Huetmannsberger:
> > Off topic I would also be interested in using different logfiles for the
> > two domains, but I guess that i snot possible with just one instance of
> > sendmail running? Or is it.
Dynamically switching syslog 'facility' is currently not possible,
but is on a wish list. Don't hold your breath.
Mark
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
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/
