On Fri, 2 Feb 2007, Jakob Hirsch wrote:
> Quoting Matthew Hodgson:
>
>> When routing an address in a router, is there a way to store a flag in a
>> variable/header such that when the message is finally delivered by a
>> transport to one of the other recipients, the transport's behaviour can
>
> Hm, I think address_data is separate to each recipient.
> Maybe you can save the value of $address_data after verifying into an
> acl_m variable (not very neat, I know).
Phew - that's what I was just trying to do; thanks for the validation.
ACL based verification only seems to happen currently when the MTA
receives a message through SMTP - is there a way to ensure it happens
during local submission too? I'd obviously need the same behaviour
regardless of the protocol by which the message arrived.
>> depend on that flag? I'm trying to get the presence of an alias-resolved
>> recipient to affect the behaviour of delivery to other recipients of a
>> message.
>
> Example?
An incoming mail needs to be passed through a transport_filter if it has a
particular recipient - but that filter needs to be able to know all the
other alias-resolved recipients for that message (so that if it spawns
additional mails, it doesn't spam people cc'd or bcc'd on the original).
The only way I can see of doing this is to make the filtered pipe
transport accept /all/ recipients so that they are available in a single
batch as $pipe_addresses. But then I need to know whether I need to run
the filter at all - hence needing to somehow flag the presence
of the main recipient elsewhere, as $pipe_addresses can't be used in
normal expansions.
