[exim-dev] overriding return_path in autoreply

Pàgina inicial
Delete this message
Reply to this message
Autor: Arkadiusz Miśkiewicz
Data:  
A: exim-dev
Assumpte: [exim-dev] overriding return_path in autoreply
Hello.

I'm playing with https://bugs.exim.org/show_bug.cgi?id=2890

Trying to make return_path working in autoreply driver (why or loops
issue - see above report)


begin routers

areply:
driver = accept
no_expn
transport = areply_transport
unseen
no_verify
retry_use_local_part = true


begin transports

areply_transport:
    driver = autoreply
    return_path = "aaaa-testowe@???"
    once_repeat = 5s
    once = /tmp/arekm.test
    from = arekm@???
    to = arekm@???
    subject = Test
    text = "testing testing"



Unfortunately in src/transports/autoreply.c around "Make a subprocess to
send the message" return_path variable (not used there in code but
available) contains sender of original message (user@???).


I'm trying to find part of code which prevents return_path option from
being applied. Any ideas which one is that?


The goal was to do simple thing:
-if ((pid = child_open_exim(&fd, US"autoreply")) < 0)
+if ((pid = child_open_exim2_function(&fd, return_path ?
expand_string(return_path) : US"<>", bounce_sender_authentication,
US"autoreply")) < 0)

and have return_path working for autoreply.

What works (tested) for me is creating new local option like
return_path_autoreply = XYZ
but using existing option meant for that would be nicer.


--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )