The point here is that even client_name can be expanded, so you could
(for example) use the sender address michael@??? as a key to look
into a text file that contained the "translated names". The file would
be formatted like an alias file:
michael@???: jakscht_de_003
...
And your transport would contain:
client_name = ${lookup{${sender_address}} lsearch {/etc/authnames}}
This would translate the sender address into the proper client name.
Same technique could be used for client_secret. If you wanted to get
fancier, you could store them both in the same file and do more
complicated lookups, but it's easier to start off simply.
Michael Jakscht wrote:
> Hi again!
>
> Tamas TEVESZ wrote at Wednesday, 28. August 2002 09:55
>
>
>>cram:
>> driver = cram_md5
>> public_name = CRAM-MD5
>> client_name = ${sender_address}
>> client_secret = <some appropriately crafted lookup>
>
>
> Really a good point, but I can't do this, because my mailbox name
> (michael@???), especially the "michael" does not equal with
> "jakscht_de_003" which is needed in the client_name.
> So is there any possibility to have a condition on a transport
> or on an authenticator??
> I know how I can use conditions on directors or routers, that's ok,
> this would be the first step to solve my problem, but are there any
> conditions available (or something equal to differ something) in the
> transports or authenticators???
>
> Michael
>
>
>
> --
>
> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim details at http://www.exim.org/ ##
>
