Re: [exim] Pass custom variable on to next router

John Robinson wrote:
> On 30/10/2006 18:23, W B Hacker wrote:
>> Online4You wrote:
> [...]
>>> How can I pass on information between routers so the next router can
>>> check for something set in the previous router?
> [...]
>> acl_m4 = acl_m4 uid:$user@$domain prefs=<something> :
> [...etc...]
>
> Bill, I don't think you can set ACL variables from within routers, but I
> may be wrong. There may well be ways of avoiding needing to, too.
>
> Cheers,
>
> John.
>

I haven't been able to *set* them, no. No need to.

Given that all that can be known about a user's preferences is just as available
in acl_smtp_rcpt as it is at delivery time (or can be easily made so), I've not
needed to set them at all - just read them.

IOW - get the prefs, hang onto them until you have a message to scan, scan same,
THEN compare score(s) to prefs instead of the other way 'round.

It has allowed us to reject cleanly OR fakereject in DATA w/o need of calling up
the delivery mechanism as often. Later, the same acl_m() control segregation
into IMAP folders, w/o needing to have added, or then add, plus later remove,
headers-that-existed-only-for-control.

The SA part, of course, predicated on all comers being happy that the 'Xerox
Master' that will become their own copy of any given message can be scanned with
the same tests for all, then differentiated only on the results of those tests.

i.e. - tougher if one bloke wants SPAM-BAYES, and 3 others think it tells
porky-pies!

Even so, by munging the call names, (spamd0, spamd1?, spamd2)? on different IP
and/or sockets, (TBD) ....one could probably scan a message more than once,
using different instances of SA, each tailored to different test suites.

Will have to try that....

Hoping to get some time this week and see how Dspam integrates.

Bill