Peter, > I am planning to implement a policy for my internals users > where I will set: > > $spam_admin_maps => Our ServiceDesk > $spam_kill_level_maps => [7.0] > $final_spam_destiny = 'D_BOUNCE'
Ok (just watch the syntax). > Tried this in a test setup and it works perfectly. > The reason I want to do this is that in between a user machine > gets hacked or they answer on a phishing attempt. > Then someone from outside may use this to spread SPAM. > > But what if this insider try to send BIG amounts of SPAM. > and the systems catch theese attempts, bouncing back and at the > same time advertising Our service desk - this might break Our system. > > Any way to put a threashold to this? For quick burst of spam the Postfix rate limiting is a big help, something like: # resource limits - see anvil(8) anvil_rate_time_unit = 60 smtpd_client_connection_count_limit = 8 smtpd_client_connection_rate_limit = 40 smtpd_client_message_rate_limit = 40 smtpd_client_event_limit_exceptions = 127.0.0.0/8, [::1] (just make sure to exclude your other mailers and amavisd) For slow but persistent internal sources of spam the $spam_admin_maps is a good solution, hoping that admins are around and read their mail. Mark ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ 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/
