bypass spam check for domain

[Miguel]

Hi to all, i got a questiong regarding the spam_lovars_maps static maps,
i undestand that if i want to bypass all spam check for a particular
recipient/domains, i just need to list them in @spam_lovers_maps,
however, i found this tutorial

http://www200.pair.com/mecham/spam/bypassing.html#9

where it says that you have to do it with

@bypass_spam_checks_maps

and additional to add them to @spam_lovars_maps

i just want to do the right thing.
What is the "official", recommended way to do this?

regards,


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
AMaViS-user mailing list
AMaViS-***@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/

[Gary V]

Post by Miguel
Hi to all, i got a questiong regarding the spam_lovars_maps static maps,
i undestand that if i want to bypass all spam check for a particular
however, i found this tutorial
http://www200.pair.com/mecham/spam/bypassing.html#9
where it says that you have to do it with
@bypass_spam_checks_maps
i just want to do the right thing.
What is the "official", recommended way to do this?
regards,

With @spam_lovers_maps, the message is still processed by spamassassin
and a score is assigned, but the message is passed regardless of the
score. With @bypass_spam_checks_maps, the message is usually not
processed by spamassassin, so this saves processing power. However,
when the message is addressed to multiple recipients, and the
recipients disagree whether scanning should occur or not, the message
will be scanned. There is the possibility in this case that the
recipient(s) in the @bypass_spam_checks_maps will not get a copy of
the message. Possibly the best way to set this up so you save as much
processing as possible, but still ensure that spam is passed, is to
include the recipients in both maps.

One other thing to consider however. For any messages that are not
scanned by spamassassin, those messages will not included in the
messages that are learned by Bayes (assuming autolearn is active). So,
you decide.

Another thing to consider. Depending on your default kill_level and
your quarantine setup, spam that is passed to recipients in
@spam_lovers_maps may also have a copy of the message sent to
quarantine. Assuming one is using default static lookups, consider
also creating a @spam_kill_level_maps where the spam lovers are given
a high kill_level (which prevents quarantine), e.g.:

@spam_kill_level_maps = (
{ '***@example.org' => 9999,
'.example.com' => 9999 }, # those in @spam_lovers_maps
\$sa_kill_level_deflt, # catchall default - everyone not in @spam_lovers_maps
);
--
Gary V

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
AMaViS-user mailing list
AMaViS-***@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/

[Miguel]

Post by Gary V

Post by Miguel
Hi to all, i got a questiong regarding the spam_lovars_maps static maps,
i undestand that if i want to bypass all spam check for a particular
however, i found this tutorial
http://www200.pair.com/mecham/spam/bypassing.html#9
where it says that you have to do it with
@bypass_spam_checks_maps
i just want to do the right thing.
What is the "official", recommended way to do this?
regards,

and a score is assigned, but the message is passed regardless of the
processed by spamassassin, so this saves processing power. However,
when the message is addressed to multiple recipients, and the
recipients disagree whether scanning should occur or not, the message
will be scanned.
There is the possibility in this case that the
the message. Possibly the best way to set this up so you save as much
processing as possible, but still ensure that spam is passed, is to
include the recipients in both maps.
One other thing to consider however. For any messages that are not
scanned by spamassassin, those messages will not included in the
messages that are learned by Bayes (assuming autolearn is active). So,
you decide.
Another thing to consider. Depending on your default kill_level and
your quarantine setup, spam that is passed to recipients in
@spam_lovers_maps may also have a copy of the message sent to
quarantine. Assuming one is using default static lookups, consider
@spam_kill_level_maps = (
);

Ok, i do not quarantine any messages ($QUARANTINEDIR = undef), so i
guess the @spam_kill_lelvel_maps is not necesary.
All is clearer now,
Thanks Gary .


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
AMaViS-user mailing list
AMaViS-***@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/

[Gary V]

Post by Gary V
and a score is assigned, but the message is passed regardless of the
processed by spamassassin, so this saves processing power. However,
when the message is addressed to multiple recipients, and the
recipients disagree whether scanning should occur or not, the message
will be scanned.

I'm not sure I understand your question. Here is an axample. A message
is addressed to ***@example.com and ***@example.org (both of which
are domains you are responsible for).

@bypass_spam_checks_maps = ( ["example.com"] );

This message will still be scanned because ***@example.org is not
included in @bypass_spam_checks_maps. ***@example.com is in the map,
but in this case this recipient may not receive a copy of the message
(assuming it is spam). @bypass_spam_checks_maps does not guarantee
delivery of spam. To guarantee delivery of a message that has been
scanned by spamassassin and subsequently marked as spam, you want to
also include the recipient in @spam_lovers_maps.
--
Gary V

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
AMaViS-user mailing list
AMaViS-***@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/

[Mark Martinec]

This post might be inappropriate. Click to display it.

[Gary V]

Post by Mark Martinec

Post by Gary V
Another thing to consider. Depending on your default kill_level and
your quarantine setup, spam that is passed to recipients in
@spam_lovers_maps may also have a copy of the message sent to
quarantine. Assuming one is using default static lookups, consider

Well, yes, high kill level does disable quarantine (because spam level
never reaches a high kill level, so mail is never considered spam and
quarantining does not apply), but it also makes spam_lovers redundant,
as mail is never considered spam, so there is no need to bother with
spam_lovers, mail will be delivered normally.
So setting kill level high to some recipients achieves both: they will
receive mail (same as spam_lovers), and no spam quarantining takes place
(same as disabling quarantine for these users).

But what if you have one recipient in a @bypass_spam_checks_maps and
another that is not? Would you still not need to place the recipient
in the @bypass_spam_checks_maps in the @spam_lovers_maps?
--
Gary V

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
AMaViS-user mailing list
AMaViS-***@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/

[Mark Martinec]

Gary,

Post by Gary V
another that is not? Would you still not need to place the recipient

@bypass_spam_checks_maps is pretty much independent from everything else.
If at least one recipient requires spam checking (has bypass at false),
then spam checking is performed. Or in other words, if all recipients
have bypass at true, spam checking need not be performed (but the result
may still be available, e.g. when cached).

What happens next depends on whether mail is considered spam (above kill level
for this recipient), or not. If it is not spam, it is delivered normally
and not quarantined. If it is spam, it gets quarantined unless quarantining
is disabled, and it is blocked, unless recipient is a spam lover.

As you can see, if mail is not considered spam (e.g. when mail is clean
or recipient has a high kill level, same thing), the @spam_lovers_maps is
irrelevant.

See first couple of items under:
http://www.ijs.si/software/amavisd/amavisd-new-docs.html

Mark

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
AMaViS-user mailing list
AMaViS-***@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/

[Gary V]

Post by Mark Martinec
Gary,

Post by Gary V
another that is not? Would you still not need to place the recipient

@bypass_spam_checks_maps is pretty much independent from everything else.
If at least one recipient requires spam checking (has bypass at false),
then spam checking is performed. Or in other words, if all recipients
have bypass at true, spam checking need not be performed (but the result
may still be available, e.g. when cached).
What happens next depends on whether mail is considered spam (above kill level
for this recipient), or not. If it is not spam, it is delivered normally
and not quarantined. If it is spam, it gets quarantined unless quarantining
is disabled, and it is blocked, unless recipient is a spam lover.
As you can see, if mail is not considered spam (e.g. when mail is clean
irrelevant.
http://www.ijs.si/software/amavisd/amavisd-new-docs.html
Mark

I see. Oops, for some reason I must have casually assumed that because mail
is tagged as spam at tag2_level, this alone might be sufficient to short circuit
delivery of a message to a recipient in @bypass_spam_checks_maps. Now I
imagine this is actually a result of $final_destiny being set to
anything other than
D_PASS. Thus, if kill_level is beyond any possible spam score, the action in
$final_destiny never takes place. All spam is delivered.
--
Gary V

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
AMaViS-user mailing list
AMaViS-***@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/

[Mark Martinec]

This post might be inappropriate. Click to display it.