On Thu, 17 May 2001, Odhiambo Washington wrote:
> wash:~$ exim -d9 -bt root
> Exim version 3.22 debug level 9 uid=1000 gid=0
> probably Berkeley DB version 1.8x (native mode)
> Actual local interface address is 62.8.64.108 (xl0)
> Actual local interface address is 212.49.74.108 (xl0)
> Actual local interface address is 127.0.0.1 (lo0)
> root@???
> deliver to root in domain alligator.wananchi.com
> director = amavis_director, transport = amavis
> wash:~$
>
> Under normal circumstance, that is in the absence of the Amavis director,
> the scenario would be like this:
>
> alligator# exim -bt root
> admin@???
> <-- root@???
> deliver to admin in domain alligator.wananchi.com
> director = localuser, transport = local_delivery
>
> So there seems to be an issue with the amavis director which I am not able
> to see???
Well, it is going to deliver the message to amavis using the "amavis"
transport. Is this what you want or not? After all, you have set up your
first director as
amavis_director:
condition = "${if eq {$received_protocol}{scanned-ok} {0}{1}}"
driver = smartuser
transport = amavis
so it will always do that unless the received protocol is "scanned-ok".
When amavis sends the message back, it should set the protocol value to
"scanned-ok". You can test what will happen then with
exim -oMr scanned-ok -bt root
--
Philip Hazel University of Cambridge Computing Service,
ph10@??? Cambridge, England. Phone: +44 1223 334714.
