Hi !!
>>- add an expansion condition to run exim filters (i.e
>> run_filter), this will allow the use of exim filter's power
>> features like if-else constructions and the mail or logfile
>> command on acl's and other places
>
> The possibility of recursion makes this not as easy to implement
> correctly as you might think.
i know, is very easy to suggest improvments but make it working
is another thing ... as acl's get more complex if-else constructions
will be a need (as named variables). In the other hand, acl's could
also be better completly implemented via 'filter language'
>>- add an expansion condition to run acl's, so acl's could be
>> called from other interesting places like router conditions.
>
> The problem here is in knowing what data is available at an unknown
> time.
yes, maybe you could implement some special value that could be
tested by a new expansion operator to test if a variable is set
or not (i.e. ${is isset{sender_address} ... )
>>- add a on_success event to transports, this could be just
>> an expansion string (where it's expanded value will just be
>> ignored). This way it will be possible to implement return
>> receipts (by running an exim filter's mail command) or
>> executing a sql insert/update query to keep some real-time
>> statics or accounting info.
>
> Shadow transports sort of do this, though only for local deliveries
> (but that allows the implementation of return receipts).
we need to do that for remote deliveries as some customers need to
know if their messages where really delivered to the remote end.
-
Best regards ...
If rabbits feet are so lucky, what happened to the rabbit?
----------------------------------------------------------------
David Saez Padros http://www.ols.es
On-Line Services 2000 S.L. e-mail david@???
Pintor Vayreda 1 telf +34 902 50 29 75
08184 Palau-Solita i Plegamans movil +34 670 35 27 53
----------------------------------------------------------------
