Hi,
I have postfix-3.5.10 configured as a multi-instance along with
amavisd for spam filtering. Amavis is limited in its ability to create
different filtering policies for individual domains, so I wanted to be
able to have amavisd run on one port for one domain and another port
for another domain.
On Thu, Jan 27, 2022 at 05:14:06PM -0500, Alex wrote:
> I have postfix-3.5.10 configured as a multi-instance along with
> amavisd for spam filtering.
One of the key features of a multi-instance pipeline with separate input
and output instances is that routing of messages into content filters
uses
Viktor Dukhovni:
> On Thu, Jan 27, 2022 at 05:14:06PM -0500, Alex wrote:
>
> > I have postfix-3.5.10 configured as a multi-instance along with
> > amavisd for spam filtering.
>
> One of the key features of a multi-instance pipeline with separate input
> and output instances is that routing of mes
Alex wrote:
Hi,
I have postfix-3.5.10 configured as a multi-instance along with
amavisd for spam filtering. Amavis is limited in its ability to create
different filtering policies for individual domains,
Unless a lot of functionality has been dropped since I last took a dive
in the Amavis docs
On 2022-01-27 23:14, Alex wrote:
btw, off-topic, but is anyone using fuglu in place of amavisd, which
seems kind of dead now?
so lets be offtopic, i do use fuglu in prequeue setup with postfix
more info in maillist or on fuglu https://gitlab.com/fumail/fuglu