mirror of
https://github.com/mainflux/mainflux.git
synced 2025-05-02 22:17:10 +08:00

* Use gomail package for sending emails Signed-off-by: Ivan Milosevic <iva@blokovi.com> * remove print err Signed-off-by: Ivan Milosevic <iva@blokovi.com> * Add vendor Signed-off-by: Ivan Milosevic <iva@blokovi.com> * Rename email structure remove logger Signed-off-by: Ivan Milosevic <iva@blokovi.com> * typo in var name Signed-off-by: Ivan Milosevic <iva@blokovi.com> * rename var Signed-off-by: Ivan Milosevic <iva@blokovi.com> * remove MF_EMAIL_SECRET Signed-off-by: Ivan Milosevic <iva@blokovi.com>
22 lines
1.4 KiB
Markdown
22 lines
1.4 KiB
Markdown
# Mainflux Email Agent
|
|
|
|
Mainflux Email Agent is used for sending emails. It wraps basic SMTP features and
|
|
provides a simple API that Mainflux services can use to send email notifications.
|
|
|
|
## Configuration
|
|
|
|
Mainflux Email Agent is configured using the following configuration parameters:
|
|
|
|
| Parameter | Description |
|
|
| ----------------------------------- | ----------------------------------------------------------------------- |
|
|
| MF_EMAIL_HOST | Mail server host |
|
|
| MF_EMAIL_PORT | Mail server port |
|
|
| MF_EMAIL_USERNAME | Mail server username |
|
|
| MF_EMAIL_PASSWORD | Mail server password |
|
|
| MF_EMAIL_FROM_ADDRESS | Email "from" address |
|
|
| MF_EMAIL_FROM_NAME | Email "from" name |
|
|
| MF_EMAIL_TEMPLATE | Email template for sending notification emails |
|
|
|
|
There are two authentication methods supported: Basic Auth and CRAM-MD5.
|
|
If `MF_EMAIL_USERNAME` is empty, no authentication will be used.
|