(Re)Enable SMTP

[Timusan]

Is your feature request related to a problem? Please describe

The configuration docs mention SMTP email support. Configuring these variables has no effect. Sending email outputs the following in the Monoscope logs:

Background job failed {
  "data": "HttpExceptionRequest Request {\n  host                 = \"api.postmarkapp.com\"\n  port                 = 443\n  secure               = True\n  requestHeaders       = [(\"X-Postmark-Server-Token\",\"\"),(\"Accept\",\"application/json\"),(\"Content-Type\",\"application/json\"),(\"User-Agent\",\"haskell wreq-0.5.4.3\")]\n  path                 = \"/email/withTemplate\"\n  queryString          = \"\"\n  method               = \"POST\"\n  proxy                = Nothing\n  rawBody              = False\n  redirectCount        = 10\n  responseTimeout      = ResponseTimeoutDefault\n  requestVersion       = HTTP/1.1\n  proxySecureMode      = ProxySecureWithConnect\n}\n (StatusCodeException (Response {responseStatus = Status {statusCode = 422, statusMessage = \"Unprocessable Entity\"}, responseVersion = HTTP/1.1, responseHeaders = [(\"Date\",\"Fri, 13 Feb 2026 06:40:08 GMT\"),(\"Content-Type\",\"application/json; charset=utf-8\"),(\"Transfer-Encoding\",\"chunked\"),(\"Connection\",\"keep-alive\"),(\"X-RateLimit-Remaining-Second\",\"4999\"),(\"X-RateLimit-Limit-Second\",\"5000\"),(\"RateLimit-Limit\",\"5000\"),(\"RateLimit-Remaining\",\"4999\"),(\"RateLimit-Reset\",\"1\"),(\"Content-Encoding\",\"gzip\"),(\"Vary\",\"Accept-Encoding\"),(\"X-Postmark-Account\",\"107535\"),(\"X-Postmark-Server\",\"1797631\"),(\"vary\",\"Origin\"),(\"Strict-Transport-Security\",\"max-age=16000000;\")], responseBody = (), responseCookieJar = CJ {expose = []}, responseClose' = ResponseClose, responseOriginalRequest = Request {\n  host                 = \"api.postmarkapp.com\"\n  port                 = 443\n  secure               = True\n  requestHeaders       = [(\"X-Postmark-Server-Token\",\"\"),(\"Accept\",\"application/json\"),(\"Content-Type\",\"application/json\"),(\"User-Agent\",\"haskell wreq-0.5.4.3\")]\n  path                 = \"/email/withTemplate\"\n  queryString          = \"\"\n  method               = \"POST\"\n  proxy                = Nothing\n  rawBody              = False\n  redirectCount        = 10\n  responseTimeout      = ResponseTimeoutDefault\n  requestVersion       = HTTP/1.1\n  proxySecureMode      = ProxySecureWithConnect\n}\n, responseEarlyHints = []}) \"{\\\"ErrorCode\\\":1101,\\\"Message\\\":\\\"The Template's 'Alias' associated with this request is not valid or was not found.\\\"}\")",
  "span_id": "adaf13a06b26338a",
  "trace_id": "dfb704b01ef0e998890ac3383bf979db"
}

Describe the solution you'd like

I briefly discussed this with @tonyalaribe on Discord. SMTP was removed some time ago and only Postmark was kept as this is the most user-friendly, straightforward email setup. Although very much true, adding back generic SMTP would mitigate possible Postmark vendor lock-in and allow more tech-savvy users to enable any desired email relay.

Describe alternatives you've considered

No response

Are you able to assist to bring the feature to reality?

no

Additional context

No response

[tonyalaribe]

Hi @Timusan,

Thanks for creating the MR here. I'll keep you updated. We will bring back SMTP support soon.

[tonyalaribe]

Hi @Timusan,
I just added back SMTP support. Can you give it a try and check if its sufficient?
You would need to set the following environment variables:

SMTP_PORT=587
SMTP_TLS=False
SMTP_HOST=x
SMTP_USERNAME=x
SMTP_PASSWORD=x

You can trigger test notifications from the "Settings > Integrations" page.

[tonyalaribe]

Ofcourse you would need to update your instance to the release: https://github.com/monoscope-tech/monoscope/releases/tag/v0.2.0

[Timusan]

@tonyalaribe This seems to work perfectly 👍 Thanks for the fast response 🙏

There was one small hiccup, configuring on STARTTLS (port 587) fails with the below error:

2026-02-16 06:24:00 ATTENTION [AT]-background-job:"PROD": Email send failed {
  "error": "HandshakeFailed (Error_Packet \"partial packet: expecting 8269 bytes, got: 21\")",
  "span_id": "4c86f22682a8f19f",
  "subject": "[2026-02-16 06:25:00 ATTENTION [AT]-background-job:"PROD": Email send failed {
  "error": "HandshakeFailed (Error_Packet \"partial packet: expecting 8269 bytes, got: 21\")",
  "span_id": "48985f46fd999a9c",
monoscope: Uncaught exception ghc-internal:GHC.Internal.IO.Exception.IOException:
<stdout>: commitAndReleaseBuffer: invalid argument (cannot encode character '\183')
HasCallStack backtrace:
  ioException, called at libraries/ghc-internal/src/GHC/Internal/IO/Encoding/Failure.hs:218:24 in ghc-internal:GHC.Internal.IO.Encoding.Failure

It looks like it only expects implicit TLS (it expects the connection to be encrypted from the very first byte). When it switched to port 465 it runs smoothly. So no big issue, but their might be some hardcoded assumption towards standard TLS?

[tonyalaribe]

Thanks for pointing it out. I will look into that issue.

…

On Mon, Feb 16, 2026, 7:34 AM Tim van der Linden ***@***.***> wrote: *Timusan* left a comment (monoscope-tech/monoscope#314) <#314 (comment)> @tonyalaribe <https://github.com/tonyalaribe> This seems to work perfectly 👍 Thanks for the fast response 🙏 There was one small hiccup, configuring on STARTTLS (port 587) fails with the below error: 2026-02-16 06:24:00 ATTENTION [AT]-background-job:"PROD": Email send failed { "error": "HandshakeFailed (Error_Packet \"partial packet: expecting 8269 bytes, got: 21\")", "span_id": "4c86f22682a8f19f", "subject": "[2026-02-16 06:25:00 ATTENTION [AT]-background-job:"PROD": Email send failed { "error": "HandshakeFailed (Error_Packet \"partial packet: expecting 8269 bytes, got: 21\")", "span_id": "48985f46fd999a9c", monoscope: Uncaught exception ghc-internal:GHC.Internal.IO.Exception.IOException: <stdout>: commitAndReleaseBuffer: invalid argument (cannot encode character '\183') HasCallStack backtrace: ioException, called at libraries/ghc-internal/src/GHC/Internal/IO/Encoding/Failure.hs:218:24 in ghc-internal:GHC.Internal.IO.Encoding.Failure It looks like it only expects implicit TLS (it expects the connection to be encrypted from the very first byte). When it switched to port 465 it runs smoothly. So no big issue, but their might be some hardcoded assumption towards standard TLS? — Reply to this email directly, view it on GitHub <#314 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSCVAWVNWZTLJLLZW6RDQL4MFQGRAVCNFSM6AAAAACVAA5FMWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSMBWG4YDIMBVGU> . You are receiving this because you were mentioned.Message ID: ***@***.***>