STMP problem on v2.1 install regardless of adapter

[anttikivi]

Hi!

I’m installing a Plausible CE v2.1 on a new server. However, I don’t seem to get the mailer working regardless of the SMTP adapter I use. Without the new adapter shipped with v2.1 (without MAILER_ADAPTER in plausible-conf.env), test sending email from Plausible with the following commands:

iex(plausible@fbe9c3dd799c)1> Application.get_env(:plausible, Plausible.Mailer)
[
  adapter: Bamboo.SMTPAdapter,
  server: "email-smtp.eu-north-1.amazonaws.com",
  hostname: "example.com",
  port: "587",
  username: "username",
  password: "password",
  tls: :if_available,
  allowed_tls_versions: [:tlsv1, :"tlsv1.1", :"tlsv1.2"],
  ssl: "false",
  retries: "2",
  no_mx_lookups: true
]
iex> email = Bamboo.Email.new_email(from: "[email protected]", to: "[email protected]", subject: "test", text_body: "test")
%Bamboo.Email{
  from: "[email protected]",
  to: "[email protected]",
  cc: nil,
  bcc: nil,
  subject: "test",
  html_body: nil,
  text_body: "test",
  headers: %{},
  attachments: [],
  assigns: %{},
  private: %{},
  blocked: false
}
iex> Plausible.Mailer.deliver_now(email)

I get the following error when running the code above (with real domains and email addresses of course):

** (CaseClauseError) no case clause matching: <<0>>
    (gen_smtp 1.2.0) /app/deps/gen_smtp/src/gen_smtp_client.erl:841: :gen_smtp_client.read_possible_multiline_reply/1
    (gen_smtp 1.2.0) /app/deps/gen_smtp/src/gen_smtp_client.erl:631: :gen_smtp_client.do_AUTH_each/5
    (gen_smtp 1.2.0) /app/deps/gen_smtp/src/gen_smtp_client.erl:556: :gen_smtp_client.try_AUTH/3
    (gen_smtp 1.2.0) /app/deps/gen_smtp/src/gen_smtp_client.erl:384: :gen_smtp_client.open_smtp_session/2
    (gen_smtp 1.2.0) /app/deps/gen_smtp/src/gen_smtp_client.erl:316: :gen_smtp_client.try_smtp_sessions/3
    (gen_smtp 1.2.0) /app/deps/gen_smtp/src/gen_smtp_client.erl:289: :gen_smtp_client.send_it/2
    (bamboo_smtp 4.2.2) lib/bamboo/adapters/smtp_adapter.ex:87: Bamboo.SMTPAdapter.deliver/2
    iex:3: (file)

The same configuration (with AWS SES on port 587 and SSL disabled) worked fine on Plausible v2.0.

When I’m using the new SMTP adapter (just added MAILER_ADAPTER=Bamboo.Mua in plausible-conf.env), testing the email with same code:

iex(plausible@4950fbaad252)1> Application.get_env(:plausible, Plausible.Mailer)
[
  adapter: Bamboo.Mua,
  auth: [
    username: "username",
    password: "password"
  ],
  relay: "email-smtp.eu-north-1.amazonaws.com",
  port: 587
]
iex(plausible@4950fbaad252)2> email = Bamboo.Email.new_email(from: "[email protected]", to: "[email protected]", subject: "test", text_body: "test")
%Bamboo.Email{
  from: "[email protected]",
  to: "[email protected]",
  cc: nil,
  bcc: nil,
  subject: "test",
  html_body: nil,
  text_body: "test",
  headers: %{},
  attachments: [],
  assigns: %{},
  private: %{},
  blocked: false
}
iex(plausible@4950fbaad252)3> Plausible.Mailer.deliver_now(email)

I get the following error:

{:error,
 %Mua.TransportError{
   reason: {:tls_alert,
    {:unexpected_message,
     ~c"TLS client: In state hello_retry_middlebox_assert at ssl_gen_statem.erl:803 generated CLIENT ALERT: Fatal - Unexpected Message\n {unexpected_msg,\n     {internal,\n         {server_hello,\n             {3,3},\n             <<156,201,202,55,75,224,151,152,26,37,50,113,...>>,\n             <<191,136,249,229,37,77,160,34,70,157,19,...>>,\n             <<19,2>>,\n             0,\n             \#{server_hello_selected_version =>\n                   {server_hello_selected_version,{3,4}},\n               key_share =>\n                   {key_share_server_hello,\n                       {key_share_entry,secp256r1,<<4,51,...>>}},\n               pre_shared_key => undefined}}}}"}}
 }}

I used Caddy as reverse proxy but confirmed that these errors are also present when using Nginx with the Plausible-provided configuration with only the automatic Certbot modifications.

[ruslandoga]

👋 @anttikivi

This discussion might be helpful: #4084 (comment)

tl;dr you can try disabling middlebox_comp_mode and it should work with Mua:

1. Create an extra config file:

_{my_config.exs}

import Config

config :plausible, Plausible.Mailer,
  # in v2.1.1 and after this option is called :ssl, see my comment below (https://github.com/plausible/analytics/discussions/4149#discussioncomment-9725329)
  transport_opts: [middlebox_comp_mode: false]

2. Mount it into plausible container

_{docker-compose.yml}

plausible:
  image: ghcr.io/plausible/community-edition:v2.1.0
+ volumes:
+   - ./my_config.exs:/app/my_config.exs

3. Make Plausible read it on startup

_{plausible-conf.env}

+ EXTRA_CONFIG_PATH=/app/my_config.exs

[wheeleran]

Amazon SES will only accept 587, as far as i understand. this is rather frustrating.

[ruslandoga]

Starting in v2.1.1 middlebox_comp_mode and other :ssl options work with STARTTLS as well.

[ruslandoga]

_{my_config.exs}

import Config

config :plausible, Plausible.Mailer,
  ssl: [middlebox_comp_mode: false]

_{plausible-conf.env}

MAILER_ADAPTER=Bamboo.Mua
SMTP_HOST_PORT=587

[ruslandoga]

There is no dummy .exs file.

#4149 (comment) describes how to create an extra config file.

[wheeleran]

@ruslandoga this is going to be difficult on my Synology NAS; there are all sort of issues currently with its docker Terminal, and finding a workaround is beyond my technical knowledge. it's such a pity, because email used to just WORK, and for whatever reason - for a few months now - fixing it is beyond me and i suppose others. is this the way it's going to be moving forward? or is it something that maybe a future update could possibly fix?