Nice, got down to it. I’ve added consistent streaming API which could be used in Samotop. There was a possibility to send body as a reader, but there were still big memory copies in some Transport implementations. And it wouldn’t suit the model in Samotop where mail service return a sink to write to. Taking the reader in would mean taking the incoming TCP stream and I need that 
Please review, I can adjust. It is bulky, I had to move a few things around to actually maintain the current API and fit the new one. Feature/jo/#33 streaming api by jocutajar · Pull Request #34 · async-email/async-smtp · GitHub
1 Like