Re: [exim] Cutthrough routing
|This message is part of the following thread:|
|the complete thread tree sorted by date|
|Dave Lugo at|
|Jeremy Harris at|
1) Headers were being sent onward with only a newline as a line-separator. A destination Exim system didn't care, but VPOP3 did.
2) If cutthrough-routing was requested for an item which turned out to have local delivery then immediate delivery was not done; the item was queued until the next queue-run.
3) Cutthrough was not working for (single) addresses resulting from a routing redirect.
To take advantage of a recipient-verify connection, the use-sender option must be used. Also, unless no_cache is used a successful verification (up to the RCPT TO phase) using the connection will be cached. A subsequent connection for a later message will then be avoided; the connection used for cutthrough being made after the rcpt ACL. This is operational but incurs the cost of routing the (second) message twice, which is suboptimal. Admittedly this is no worse than the traditional case, routing once for the verify and once for the delivery.
|This message was posted to the following mailing lists:|
Mailing List Info | Nearby Messages
|[exim] Defer in warn ACL results in tempfail despite docs||Re: [exim] Unrouteable address but email address is valid|
|Tahini and Hummus Development Archives administrated by Hummus Admins||Lurker (version 2.3)|