Clifton Royston a écrit :
Ah, I see.
If you replace transports with a Postfix access map that does:
example.com FILTER smtp:localhost:10026
example.net FILTER smtp:localhost:10025
or similar, then you can still route domains (or even specific users)
to a specific amavisd port/instance, or even route them "around"
amavisd and into the outbound Postfix instance, but you do not get the
problems associated with using the transport mechanism to do it.
This is the strategy our Scora system uses.
unfortunately, only one FILTER action is taken, so in the case of multi
recipient mail, things may go wrong.
with tranpsort, such email will be split, and copies are sent to
multiple amavisd. Thus achieving the OP's goal (with more overhead
though, since clam and SA are run multiple times).
I still prefer to let all mail go to one amavisd and only make the
disposition (quarantine, pass, ...) configurable per recipient. but this
is just a personal preference.
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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/
