Hi Wietse, Thanks - I'll stop trying to attempt to do it this way then. The SMTP approach does have the advantage of realtime feedback on the 'rcpt to:' being accepted and I can spread the load across multiple threads / connections.
Next question: Is there a way to get a 'delivered' notification (ie. once the e-mail has left Postfix and is now at the destination mail server - or at least, the next mail server in the chain). (or any status change for that matter) thanks Kent. > On 2/06/2017, at 11:50 AM, Wietse Venema <wie...@porcupine.org> wrote: > > Kent: >> Hi All, >> >> I have a MongoDB with a set of e-mails that I want to send. I want to be >> able to track their delivery / bounce / delayed status - plus link any >> replies back to the original e-mail. >> >> I have already written a c++ service to handle incoming e-mails (by piping >> the incoming e-mails to my app) - which is still under development, but >> meeting that side of my needs. >> >> >> Now I'm onto the actual sending side. I've written a separate C++ service >> to run on the mail server to process the table of e-mails in the MongoDB >> (From, To, Subject, Body, etc). >> >> My original plan was to dump each e-mail to a file on disk, move to the >> /var/spool/postfix/maildrop/ folder, set the permissions correctly and >> leave Postfix to process the queue. > > You MUST use Postfix interfaces: submit over SMTP, or use the Postfix > sendmail command. WRITING TO THE QUEUE IS NOT SUPPORTED. > > Wietse
