AW: NOQUEUE using check_recipient_access and FILTER action

Hi,

> > I'm using the check_recipient_access FILTER action to multiplex
> > incoming mails to different mail filters, depending on the=20
> recipient.
>=20
> What happens if a message has two recipients who, according to your
> rules, should get different filtering treatment?

Hmm, good point. So switching to two different transport_maps would
be better? (One pointing to the filters, one after the filters, pointing
to the destination mail hosts).

I'm assuming that you're implying that postfix won't duplicate the
message for the FILTER action, but will duplicate for the
transport_maps.

> > Postfix logs these incoming mails as=20
> > NOQUEUE: filter: RCPT from {senderhost}[192.168.1.1]:=20
> > <bla@test.de>: Recipient address triggers FILTER=20
> > sweep:[127.0.0.1]:10050; from=3D<sr@XXXXX> to=3D<bla@test.de>=20
> > proto=3DSMTP helo=3D<bla>
> >=20
[snip]
>=20
> NOQUEUE just means that Postfix has not yet assigned a queue=20
> id for this
> message. A queue id is assigned when the first recipient is accepted.

Ah, ok. Thanks for clearing that up for me.

Regs,
Sven