awdeorio
commented
4 years ago Another way to do this would be to render all templates first, storing base64 encoded messages in ~/.mailmerge.d/messages. Then log each sent message to ~/.mailmerge.d/sent.log, be sure to append to log and buffer to file system. When mailmerge starts up, check ~/.mailmerge.d/ for an incomplete log. Offer the user an option to resume with mailmerge --resume.
It might also be nice to store a detailed debug log in ~/.mailmerge.d/debug.log.
Testing
- Simple resume
- Resume after SMTP timeout exception
- Resume after multiple timeout exceptions
- Resume after unhandled exception
- Template file modified between first and second send attempt
- Database file modified between first and second send attempt
- Server config file modified between first and second send attempt
- Clean up
~/mailmerge.d/ - Verify user instructions to stdout
It would be nice to have a
mailmerge --resumeoption to resume sending emails in the event of a failure.Along with this, it would makes sense to report the database row number of a sent message. It should correspond to row number when viewing the database CSV file in a spreadsheet program.