platform/services/mail/pod-mail

Mail Service

Overview

The Mail Service is responsible for sending emails using SMTP or SES transfer. It supports sending emails with multiple recipients, along with optional CC, BCC, and HTML content.

Configuration

Environment variables should be set to configure the Mail Service:

• PORT: The port on which the mail service listens for incoming HTTP requests.
• API_KEY: An API key that clients must pass. The parameter is optional, should be provided when external access to the service is allowed.

Settings for SMTP or SES email service should be specified, simultaneous use of both protocols is not supported

SMTP settings:

• SMTP_HOST: Hostname of the SMTP server used for sending emails.
• SMTP_PORT: Port number of the SMTP server.
• SMTP_USERNAME: Username for authenticating with the SMTP server. Refer to your SMTP server documentation for the appropriate format.
• SMTP_PASSWORD: Password for authenticating with the SMTP server. Refer to your SMTP server documentation for the appropriate format.

SES settings:

• SES_ACCESS_KEY: AWS SES access key for authentication.
• SES_SECRET_KEY: AWS SES secret key for authentication.
• SES_REGION: AWS SES region where your SES service is hosted.

Running the Service

Add .env file to the root of the project with the following content to add integration with fake SMTP server:

PORT=8097
SMTP_HOST="mail.smtpbucket.com"
SMTP_PORT=8025 

To use the real SMTP server it is required to register an account in some email service provider and specify settings and credentials for it.

Start the service locally using:

rushx run-local

The service will run and listen for incoming requests on the configured port.

API Endpoints

POST /send

Send an email message.

Request Body

• to: Required. String or array of strings containing recipient email addresses.
• text: Required. String containing the plain text message body.
• subject: Required. String containing the email subject.
• html: Optional. String containing HTML message body.
• from: Optional. Sender's email address.
• headers: Optional. An object or array of additional header fields.
• apiKey: Required if the service started with API_KEY.
• attachments: Optional. Array of objects, each object can have the following fields:
  • filename: Filename to be reported as the name of the attached file. Use of unicode is allowed.
  • contentType: Optional. Content type for the attachment, if not set will be derived from the filename property.
  • content: String, Buffer, or a Stream contents for the attachment.
  • href: Optional. An URL to the file (data URIs are allowed as well).
  • contentDisposition: Optional. Content disposition type for the attachment, defaults to ‘attachment’.
  • cid: Optional. Content id for using inline images in HTML message source.
  • encoding: Optional. If set and content is a string, then encodes the content to a Buffer using the specified encoding. Example values: ‘base64’, ‘hex’, ‘binary’ etc. Useful if you want to use binary attachments in a JSON formatted email object.
  • raw: An optional special value that overrides the entire contents of the current MIME node, including MIME headers. Useful if you want to prepare node contents yourself.

Request body example:

{
  "subject": "Test SMTP",
  "text": "My text",
  "from": "test1@example.com",
  "to": "test2@example.com",
  "attachments": [
    {
      "filename": "test.txt",
      "content": "Hello world",
      "contentType": "text/plain"
    }	
  ]
}

Response

• 200 OK on success.
• 400 Bad Request if required fields are missing.