On Fri, 8 Feb 2019 at 17:17, Robert Moskowitz <[email protected]> wrote:
...
I would think I want to use MILTER.
On 08.02.19 17:34, Dominic Raferd wrote:
I too am interested in running amavis as milter (Patrick has written
some instructions in German), but the standard and more common setup,
and the one which you are emulating at present, is as content filter
instead, and I think you should focus on getting that working first.
I use milter when receiving mail from outside (mail servers).
When I configured milter on users connections, users were complaining that
sending mail takes too long.
Thus, clients on submission,smtps ports (and when possible, port 25 clients
on internal interface) use content_filter.
As I understand it the disadvantages of this content filter
post-queue(?) approach are
- that mails are queued twice in the MTA [postfix] (once when it sends
them out to amavis, and again when they return), with two different
queue-ids, which is untidy and can make log tracking harder, and
- that the response from amavis cannot be passed back to the client
because the client has been told all is ok (250) when the email is
passed over to amavis and before amavis has processed it - but usually
you may not want to tell the client if you are quaranting or
discarding the mail it has sent.
The main advantage over calling amavis as a milter is that it doesn't
really matter how long amavis takes to process the mail, whereas with
a milter you have the client still connected and waiting for a
response. You can use something like
$child_timeout = 20;
so that amavis forces any child processes (esp. clamav) to give up
after a given period - this isn't required with the content_filter
approach.
coprrect.
--
Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Depression is merely anger without enthusiasm.
