Cory, > I just read up on policy banks but all they talk about is the > originating source.
That is the most common application, but mapping a port number to a policy name is a general mechanism. It is up to a setup and MTA configuration to attribute meaning to different content filtering ports. > The email may have originated from your internal > network but doesn't necessarily mean its going to be sent outside the > network. I see no variable or method of distinguishing an email thats > destined for the outside world vs. one that is delivered locally. If recipient matches @local_domains_maps it goes to an inside recipient (inbound or all-internal), otherwise mail is outbound. Note that policy banks are per-message, and @local_domains_maps is per-recipient. A message may have more than one recipient, which means that inbound/outbound/internal distinction is not an attribute of a message as a whole, but is applicable to recipients. You need to combine a policy bank with @*_maps to distinguish all three possibilities, if that is needed. > The way mine is configured is as follows: > > email comes in to server:25 (postfix) > sends it to localhost:10024 > (amavis) > sends it to localhost:10025 (postfix) > > All mail travels the same path. Its easy to alter a locally delivered > email because you specify it in postfix's master.cf but there is nothing > you can do for an email that isn't delivered locally from what I see. > Am I missing something? See some examples in: http://www.ijs.si/software/amavisd/amavisd-new-docs.html#pbanks-ex and further down at #dkim. Search RELEASE_NOTES (2.5.2) for: - provided interface code to allow mangling/defanging/sanitation to be performed by an external utility, either by ... [...] - a special case of mangling is adding a disclaimer, by invoking an external program 'altermime' (if available and enabled). This differs from mangling inbound mail in two details: and note example there. Mark ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ AMaViS-user mailing list AMaViS-user@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/
