smtprelay VS inbucket

If you have an always on host within the office and accessible to the copiers, even a RPi, there are tons of solutions on Github (ex. https://github.com/decke/smtprelay). A Windows machine I will typically configure hMailServer with MariaDB. For all-cloud, SMTP2Go is really the only solid choice I have found. Others I tried were either more pricey or required a super long key for authentication that copiers did not like.

Yep. I use https://github.com/decke/smtprelay for this purpose.

I use smtprelay, an alternative to the pain in the butt postfix, 3 lines and you are ready to use it to receive email, anything sent to it is automatically "relayed" to your email provider (127.0.0.1) via STARTTLS.

I know about dma, ssmtp, msmtp, nullmailer and https://github.com/decke/smtprelay/, but these don't seem to support queuing and retries.

This is what I use: https://github.com/decke/smtprelay

Longtime mailhog user here; this looks like a nice improvement for cold start developer environments! Another option in the same space (emphasis container size) is https://github.com/inbucket/inbucket

inbucket is what you need

yeah, it is still helpful. But I was also recommended to play with mailhog or https://github.com/inbucket/inbucket

https://inbucket.org/ is very easy to host, does not require you to setup mailboxes, does not require any sort of database, has a built in webmail interface, and you can also grab via POP3 if you want to use a traditional mail client.

If all you need is a system to receive SMTP mail and read the messages via web GUI then inbucket is probably the easiest solution.

Will have to play around with GitHub pages settings, looks like https://www.inbucket.org/ is the workaround for now

I run https://www.inbucket.org/ at home. I wrote it, so I'm biased, but it works well for me. ;)

This is what you need inbucket