On Wed, 15 Jun 2005, Annette Jaekel <[EMAIL PROTECTED]> wrote
Am 14.06.2005 16:57 Uhr schrieb "Sven Riedel" unter <[EMAIL PROTECTED]>:
Hi,
with amavisd-new and centralized SA and dspam:
Is there an easy possibility for an user to decide to
"opt-out" from the
spam-checks of amavisd-new by itself? For dspam there would be a nice
$USERHOME/.nodspam. Is there an option for amavisd similiar
to that one?
There is nothing built in that I know of. But since the config
file is in essence a perl script that is invoked with perls
'do'-function (q.v.) you'll be able to write a small loop
in the config file that will build your spam_lovers_map
for you. (Mark will correct me if I said anything wrong here :) ).
The other approach is to use MySQL lookups to decide on what policy
applies to what user, and write an interface for users to select their
preferred policies.
Meanwhile I also found bypass_spam_checks_map. Is it better to configure
spam_lovers or bypass_spam_checks, if a mail receiver generelly want to
opt-out from the centralized spam-checks? Whats the main difference between
these two maps?
bypass_*_checks bypasses checks. On the face of it this is fine. The
problem is that with multiple recipient emails if at least one recipient
wants checks, then checks are performed. Because of this it is wise to
also set *_lovers to match. That way they'll get the mail even if the
checks are performed and failed.
The only problem I've had is with viruses, where I've been unable (using
MySQL) to work out how to set defang* options on a per user basis. This
has meant that sometimes people who want viruses get them defanged if
the message hash is cached. bypass_*_checks it seems doesn't bypass
checking the cache.
Furthermore I assume difficulties to realize "no-spam-check" for someone, if
a mail to a list or alias this user is on is receiving by amavis. I read
some hints, that for lists of receivers amavis process the mail for every
receiver, ignoring "opt-out" settings, if not all receivers agree not to
check the mail. So what with members of spam_lovers oder bypass_spam_check
if they are on a mail alias list?
I'm not sure what sort of list you mean. If one hosted on your box, then
if the list address is set for filtering, incoming mail is going to be
filtered before it hits the list expander. If this isn't what you want,
add the list address to bypass_* and *_lovers. Personally, I think the
spam policy of a list is down to the list admin, and I'd filter. I don't
want my lists used for distributing spam and viruses thanks.
If you have aliases and rewrites then take care to have amavis at the
appropriate point in the system if you want per user configuration.
Whether amavis checks before or after the alias translation will affect
what addresses you need to place in bypass* and *lovers.
HTH
--
Chris Hastie
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
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/
