> >> OOPS, I blundered. You cannot bypass spam checks and still
> get spam
> >> tags. You should ONLY use spam_lover if you want mail spam tagged.
>
> > I tried to sent a spam to an address of the spam lover domain:
>
> > /usr/local/src/amavisd-new-2.4.4/test-messages # sendmail -i
> > [EMAIL
Rocco wrote:
>> OOPS, I blundered. You cannot bypass spam checks and still
>> get spam tags. You should ONLY use spam_lover if you want
>> mail spam tagged.
> I tried to sent a spam to an address of the spam lover domain:
> /usr/local/src/amavisd-new-2.4.4/test-messages # sendmail -i
> [EMAIL
Gary wrote:
> Rocco wrote:
>>> If the domain is considered local and the message scores over
>>> spam_tag2_level it should get this tag. Each user in
>>> @example.com could still have a policy where where their
>>> spam_tag2_level is set.
> OOPS, I blundered. You cannot bypass spam checks and
Rocco wrote:
>> If the domain is considered local and the message scores over
>> spam_tag2_level it should get this tag. Each user in
>> @example.com could still have a policy where where their
>> spam_tag2_level is set.
>>
>> > rocsca
>>
>> Gary V
> Still thanks,
OOPS, I blundered. You can
> If the domain is considered local and the message scores over
> spam_tag2_level it should get this tag. Each user in
> @example.com could still have a policy where where their
> spam_tag2_level is set.
>
> > rocsca
>
> Gary V
Still thanks,
rocsca
-
Rocco wrote:
>> If you were not using SQL (or every user in the @example.com
>> domain had spam_lover = NULL and bypass_spam_checks = NULL) ,
>> you could set:
> Sorry for the confusion..
>> @bypass_spam_checks_maps = ( [qw( .example.com )] );
>> @spam_lovers_maps = ( [qw( .example.com )] );
Gary wrote:
> Rocco wrote:
>>> One possibility (depending on your setup). Create a policy
>>> where every configuration setting is NULL with the exception
>>> of spam_lover and bypass_spam_checks (you need to set both
>>> when bypassing). Something like this:
>> My setup is Amavisd-new+Postfix
> If you were not using SQL (or every user in the @example.com
> domain had spam_lover = NULL and bypass_spam_checks = NULL) ,
> you could set:
Sorry for the confusion..
> @bypass_spam_checks_maps = ( [qw( .example.com )] );
> @spam_lovers_maps = ( [qw( .example.com )] );
Codld I get spam fo
Rocco wrote:
>> One possibility (depending on your setup). Create a policy
>> where every configuration setting is NULL with the exception
>> of spam_lover and bypass_spam_checks (you need to set both
>> when bypassing). Something like this:
> My setup is Amavisd-new+Postfix+MySQL
>> INSERT I
> One possibility (depending on your setup). Create a policy
> where every configuration setting is NULL with the exception
> of spam_lover and bypass_spam_checks (you need to set both
> when bypassing). Something like this:
My setup is Amavisd-new+Postfix+MySQL
> INSERT INTO policy (id, polic
Rocco wrote:
> Hello,
> I would like to not block the spam for some domain.
> I saw a parameter $bypass_spam_checks_maps it seems the right suitable
> for my case, but I would like to know how to use it storing domain name
> in a file or SQL database and other better methods (if there any) for
Hello,
I would like to not block the spam for some domain.
I saw a parameter $bypass_spam_checks_maps it seems the right suitable
for my case, but I would like to know how to use it storing domain name
in a file or SQL database and other better methods (if there any) for
my purpouse.
thanks,
r
12 matches
Mail list logo
