On 9/28/2012 3:12 PM, Jack Bates wrote:
Code needs to be written to handle the special case of us not having
any proxy callbacks as they are all bad.
Timo, please check and approve. This was diff'd on 2.1.10 on my test
server (2.1.9 and 2.1.10 at least had this callback issue).
*** lmtp-proxy.c-orig 2012-09-28 20:17:36.138916678 +0000
--- lmtp-proxy.c 2012-09-28 20:18:12.241940780 +0000
***************
*** 300,303 ****
--- 300,304 ----
lmtp_client_send(conn->client, conn->data_input);
lmtp_client_send_more(conn->client);
}
+ lmtp_proxy_try_finish(proxy);
}
ie, call lmtp_proxy_try_finish once. If all is bad, this will wrap us
up. If we have valid proxies, it'll probably not finish and we'll return
to waiting on callbacks. I'm not sure of any blocking restrictions. I
just know it works.
mail from:<joe>
250 2.1.0 OK
rcpt to:<JOE>
250 2.1.5 OK
data
354 OK
test
.
451 4.4.0 Remote server not answering (connect)
mail from:<joe>
250 2.1.0 OK
rcpt to:<joe>
250 2.1.5 OK
rcpt to:<test>
250 2.1.5 OK
data
354 OK
test
.
451 4.4.0 Remote server not answering (connect)
250 2.0.0 <test> CYKfHcsHZlBcCAAALhEySA Saved
mail from:<joe>
250 2.1.0 OK
rcpt to:<test>
250 2.1.5 OK
data
354 OK
test
.
250 2.0.0 <test> EYKfHcsHZlBcCAAALhEySA Saved
Jack
