[exim] using $recipients in transports - exim 4.34

Etusivu
Poista viesti
Vastaa
Lähettäjä: Andy Rabagliati
Päiväys:  
Vastaanottaja: Exim Users Mailing List
Aihe: [exim] using $recipients in transports - exim 4.34
Folks,

For interaction with a legacy UUCP system, I want a transport
like this :-

##################################
wcsn:
driver = pipe
command = "uux - $host!rmail $recipients"
return_fail_output
user = nobody

##################################

The desired result is a UUCP request like this :-

cat <mail_message> | uux - upstreamprovider!rmail user1@??? user2@??? user3@???

In the docs, the description of $recipients says :-

------- exim 4.34 spec -----------
$recipients: This variable contains a list of envelope recipients for a
message. A comma and a space separate the addresses in the replacement text.
However, the variable is not generally available, to prevent exposure of Bcc
recipients in unprivileged users' filter files. You can use $recipients only

(1) In a system filter file.

  (2)  In the DATA or non-SMTP ACL, that is, in the final ACL for accepting a
       message.
------- end exim spec -----------


So - I thought I might do something like this :-

------- exim.conf - important bits only ---------
acl_smtp_data = check_message

begin acl

check_message:
accept set acl_m0 = $recipients

begin routers

rmail:
driver = manualroute
domains = ! +local_domains
route_list = * uucp
transport = wcsn

begin transports

wcsn:
driver = pipe
command = "uux - $host!rmail $acl_m0"
return_fail_output
user = nobody

------- end exim.conf ---------

But I find acl_m0 unset at this stage - I see only "uucp!rmail"

Back to the docs ..

------- exim spec -----------

$acl_m0 - $acl_m9: Values can be placed in these variables by the "set"
  modifier in an ACL. They retain their values while a message is being
  received, but are reset afterwards. They are also reset by MAIL, RSET, EHLO,
  HELO, and after starting a TLS session. When a message is received, the      
  values of these variables are saved with the message, and can be accessed by
  filters, routers, and transports during subsequent delivery.               


------- end exim spec -----------

What am I doing wrong ?

Cheers, Andy!