Mark,
> >> originating recip. is local
> >> 0 0 can't happen (open relay)
> >> 0 1 inbound
> >> 1 0 outbound
> >> 1 1 internal-to-internal
> >>
> >> # a global setting, can be overridden by a policy bank,
> >> # so in this case will apply only to inbound mail
> >> #
> >> @bypass_virus_checks_maps = ();
> >>
> >> # mail originating from our users, override global settings
> >> #
> >> $policy_bank{'ORIGINATING'} = {
> >> originating => 1,
> >> bypass_virus_checks_maps => [
> >> { '.mydomain1.org' => 0, # internal-to-internal
> >> '.mydomain2.org' => 0,
> >> '.' => 1, # skip the check for everybody else (outbound)
> >> } ],
> >> };
> >
> > Btw, the shown example is just an illustration on how to deal
> > with the 3(4) possibilities when needed.
> >
> > Assuming mailer is not an open relay, and for the task at hand
> > (needing a setting for outbound mail), a single global setting
> > of @bypass_virus_checks_maps suffices, because if recipient
> > is non-local we know mail could only be originating from our
> > users.
> >
> > @bypass_virus_checks_maps = (
> > { '.mydomain1.org' => 0, # inbound or internal-to-internal
> > '.mydomain2.org' => 0,
> > '.' => 1, # skip the check for everybody else (outbound)
> > } );
> >
>
> I have understood quite well your explanation. I have a problem using
a
> such approach. Infact, I have a long list of "mydomain" too. I
maintain
> domains through a database. But unfortunatly I can't figure out how to
> build a such associative array.
>
> PS: Amavisd-new natively tags as LOCAL some log's entries. If an entry
> is
> tagged as LOCAL it mean that the associated message is either inbound
> or
> internal-to-internal. Right? But how behaves Amavisd-new when face
with
> a
> message which has either local and non-local recipients?
>
Anyway, since I have set Amavisd-new to avoid virus scan for outbound
messages, I get a lot of:
Jan 22 11:20:27 av9 postfix/smtp[29723]: 2C9B815B8D9:
to=<[email protected] >, relay=127.0.0.1[127.0.0.1]:10026, delay=13,
delays=2.4/9.8/1/0, dsn=4.4.2, status=deferred (conversation with
127.0.0.1[127.0.0.1] timed out while receiving the initial server
greeting)
As well
Jan 22 11:20:11 av9 postfix/smtp[29723]: B5D8D15B8BF:
to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=8.1,
delays=2.9/4.3/1/0, dsn=4.4.2, status=deferred (conversation with
127.0.0.1[127.0.0.1] timed out while receiving the initial server
greeting)
I can't figure out why.. Maybe postfix answer so when amavisd-new has no
child to manage a new request? And so this is due to the high incoming
traffic? Or there is some tune to be done in my master.cf?
smtp-amavis unix - - n - 14 smtp
-o smtp_data_done_timeout=1200
-o smtp_send_xforward_command=yes
-o disable_dns_lookups=yes
-o max_use=14
-o smtp_connect_timeout=1
-o smtp_helo_timeout=1
The big problem is that the messages remains starngely queued a long
time before to be forwarded toward Amavisd-new... :-(
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
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/
