On 24/11/2019 11:07, Magnus Holmgren via Exim-dev wrote: > Similar but different issue: I just now noticed that smtp_printf(), which is > part of the local_scan API, was changed two years ago with the addition of a > second, BOOL argument related to pipelining. I'm not sure how to know when to > pass true or false. The documentation hasn't been updated.
Arghh. I'll add a note in docs, but I think we may be too late to properly (however that's decided) fix it for the upcoming release. Heiko is the release master. (The BOOL is for indicating that further data will be passed imminently, so the data from this call can be buffered to save syscalls/packets. False to write/flush immediately.) > Maintaining a stable API is *hard*. As I'm finding :( Obviously very few people use the API, or care to raise bugs... or test (preferably early) RCs. Thanks for doing the latter. -- Cheers, Jeremy -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##
