No manual editing, no additional work, just add recipient and SES credentials, in Amazon SES authorize the recipients and upload the exported site to own server. I think all that's needed is to find some well maintained php-send library and finally let BSS create and link the submit button to a PHP file. A self-hosted option that doesn't use Martin's infrastructure. So allowing to use to my SES account and dropping a contact-us-send.php module can be good for many small projects I manage.

Like for gmaps I can code a better one, but for a small website, the BSS provided module is enough. On AWS SES I could authorize my own recipients and define how long the form will work for my customers, even receive and act on spam reports. I prefer to have things under my control. BSS is a prototyping/IDE software, not an email provider. Or have to write here a support message and hope that Martin is not on holidays and fixes the issue soon. I don't like the idea to share the same mail-from with some unknown guy creating spammy sites and risking my customer forms get blacklisted and blocked by $someprovider. Amazon SES is really cheap and that would give me complete control over all email sending process, payments, and using my own account, never to be banned or blocked or suspended if Martin has a problem or gets banned. That latter option for me would be the best. **) additional packages with 100 recipients with 10yrs license sold apart.Īdd to that an option to drop locally a few PHP files for self-hosted form processing that can connect to own (SMTP or to) Amazon SES like ) lifetime license -> 10/20 recipients never expiring (legally I prefer 10 years license) ) 1-year license -> 3/5 recipients expiring after 1 year ) free student version -> 1 fixed recipient with the school address used to register the free license, to be renewed yearly, like - I hope- the license.

) pirates -> 0 recipients, that feature should check a legit install I'd say that number should be differentiated:

Bootstrap studio license