Ian,
> > Yes, by-recipients setting is available:
> > @bypass_header_checks_maps = ( list of lookup tables as usual );
>
> So the lookup table is simply regex matched?
If you use a regexp-type of a lookup table, then yes.
All types of availabe lookups are explainded in README.lookups .
> I.E. I
>> If I wanted to whitlist a particular domain, is
>> there a check_maps I could use to do that instead?
>
> Yes, by-recipients setting is available:
>
> @bypass_header_checks_maps = ( list of lookup tables as usual );
So the lookup table is simply regex matched? I.E. I could even do
something
Ian,
> > Do not be misled by the fact that default setting is also
> > to quarantine a mail with a bad header (i.e. a copy goes
> > to a guarantine, but mail is passed to recipients nevertheless).
> > To avoid quarantining mail with bad headers, it must be turned off
> > explicitly, as shown above
> The default setting is $final_bad_header_destiny=D_PASS .
> If you see mail being blocked by header checks, it must be
> because you have explicitly overridden the default in
> your amavisd.conf.
Ah, I must have then. Okay, I'm beginning to see the flow of things now.
Very IPTABLES like.
> D
Ian,
> > @bypass_header_checks_maps = ( 1 );
>
> Thanks again... I see now in the comments that the same method can be used
> to disable spam and virii checks.
>
> >> I get way too many false positives from this!
> >
> > False positives in what sense? That a test said a header is bad
> > but is re
Ian,
> Currently, we've got a special user "archiver" that gets all emails are
> BCC'ed to. I've been trying to figure out how to get amavisd to simply
> send all emails through to this user without exception, even if it
> contains spam, bad headers, virii, etc...
> So far I've got these rules:
>
> Please post your full amavisd.conf file with the comments pulled out.
Steven,
Thanks for looking into this. I've replaced our real domain with
"mydomain" but the text is otherwise identical.
-
This SF.net email is spons
Please post your full amavisd.conf file with the comments pulled out.
Ian wrote:
>> You don't need the => 1 in your entry. That syntax is for creating
>> policy banks, where you assign values to a perl array. Normal rules
>> just take the values as a list.
>>
>> @bypass_virus_checks_maps = ( "[
> You don't need the => 1 in your entry. That syntax is for creating
> policy banks, where you assign values to a perl array. Normal rules
> just take the values as a list.
>
> @bypass_virus_checks_maps = ( "[EMAIL PROTECTED]");
>
> That syntax for all of your entries should work.
>
> Ian wrote:
You don't need the => 1 in your entry. That syntax is for creating
policy banks, where you assign values to a perl array. Normal rules
just take the values as a list.
@bypass_virus_checks_maps = ( "[EMAIL PROTECTED]");
That syntax for all of your entries should work.
Ian wrote:
> I'm having
I'm having a hell of a time tuning our quarantine and thought I'd finally
actually ask the peeps here to give me the nugget of information that I'm
currently lacking. (Even if it's just the nouns I need to use to search
this mailing list history for the answer)
Currently, we've got a special user
11 matches
Mail list logo
