|Jan-Lukas Else f79df1a8c3||4 days ago|
|.drone.yml||6 months ago|
|.gitignore||7 months ago|
|Dockerfile||4 days ago|
|LICENSE||7 months ago|
|README.md||7 months ago|
|config.go||4 days ago|
|config_test.go||4 days ago|
|form.html||7 months ago|
|forms.go||6 months ago|
|forms_test.go||6 months ago|
|go.mod||4 days ago|
|go.sum||4 days ago|
|mail.go||4 days ago|
|mail_test.go||6 months ago|
|mailygo.go||6 months ago|
|spamcheck.go||4 days ago|
|spamcheck_test.go||4 days ago|
MailyGo is a small tool written in Go that allows to send HTML forms, for example from static websites without a dynamic backend, via email. It can be used for contact forms on pages created with Hugo (example).
MailyGo is lean and resource-saving. It can be installed with just one executable file.
MailyGo can be compiled with the following command:
go get -u codeberg.org/jlelse/mailygo
It can then be executed directly.
To run the server, you must set a few environment variables from the list below.
||required||-||The SMTP user|
||required||-||The SMTP password|
||required||-||The SMTP host|
||optional||587||The SMTP port|
||required||-||The sender mail address|
||required||-||All allowed recipients (separated by
||The port on which the server should listen|
||Honeypot form fields (separated by
||optional||-||Google API Key for the Google Safe Browsing API|
||List of spam words|
You can find a sample form in the
form.html file. Only fields whose name do not start with an underscore (
_) will be sent by email. Fields with an underscore serve as control fields for special purposes:
||optional||-||Recipient, it must be in
||optional||-||Email address which should be configured as replyTo, (most probably not hidden)|
||optional||-||URL to redirect to, hidden|
||optional||-||Name of the form, hidden|
||optional||-||(Default) “Honeypot” field, not hidden, advised (see notice below)|
If a Google Safe Browsing API key is set, submitted URLs will also get checked for threats.
MailyGo is licensed under the MIT license, so you can do basically everything with it, but nevertheless, please contribute your improvements to make MailyGo better for everyone. See the LICENSE file.