STMP problem on v2.1 install regardless of adapter #4149

anttikivi · 2024-05-27T19:38:32Z

anttikivi
May 27, 2024

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 · 2024-05-28T06:54:37Z

ruslandoga
May 28, 2024
Collaborator

👋 @anttikivi

This discussion might be helpful: #4084 (comment)

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

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]

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

Make Plausible read it on startup

_{plausible-conf.env}

+ EXTRA_CONFIG_PATH=/app/my_config.exs

16 replies

ruslandoga Jun 22, 2024
Collaborator

The Erlang version used starting in v2 changed TLS defaults to more secure ones and at the same time became more strict. It's unlikely we would be downgrading to an older Erlang version or making defaults less secure by default for everyone. Mounting a custom config is an easy solution that allows self-hosters to change any configuration just for themselves, I don't see right now how it can be made better.

And we are not wrestling with an abandoned adapter :)

wheeleran Jun 22, 2024

I was referring to your previous comment in this threat about Bamboo not being maintained...

ruslandoga Jun 22, 2024
Collaborator

You might be confusing Bamboo (email framework), Bamboo.SMTPAdapter (old adapter), and Bamboo.Mua (new adapter). This thread is about the new adapter. Bamboo is also unmaintained but it is less of an issue since it's not affected by the recent changes in Erlang's TLS.

wheeleran Jun 22, 2024

Oh, I was think Mua, my mistake

wreidlinger Jun 24, 2024

👋 @wreidlinger

Seems like a typo issue my-config.exs vs my_config.exs

👋 @ruslandoga you are absolutely right, it was just a stupid typo, guess it was late and my eyes where super tiered!
After correcting the typo the error went ways and I got another error.

plausible_plausible  | 2024-06-21T19:23:31.033539969Z 19:23:31.033 [error] Failed to send e-mail

But than I switched to the port 587 (STARTTLS) and everything was running again.
So now my email config in plausible-conf.env looks like this:

# MAIL
MAILER_NAME=Plausible Analytics
[email protected]
MAILER_ADAPTER=Bamboo.Mua
SMTP_HOST_ADDR=mail.domain.something
SMTP_HOST_PORT=587
[email protected]
SMTP_USER_PWD=***
SMTP_RETRIES=2
EXTRA_CONFIG_PATH=/app/my_config.exs

my_config.exs

import Config

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

You where talking about, that the Erlang version is pretty strict/picky about the TLS/SSL config.
We are using a mailcow email server and I thought the TLS/SSL config is quite correct/good. At least this is what some checking tools told me.

Source: https://www.checktls.com/TestReceiver

Source: https://ssl-tools.net/mailservers

@ruslandoga maybe you have more experience which TLS/SSL config the Bamboo.Mua / Plausible.Mailer likes or which config should be avoided. Maybe it is worth noticing in the docs section about Bamboo.Mua.
For testing the email delivery of the plausible container I was using the proposed syntax from @anttikivi (thanks a lot!).
Maybe it worth asking about a feature request. Would be pretty cool to have a email delivery test function in the plausible web interface... would be nice for admins without to much CLI experience.

Anyways I was testing the email delivery with the following syntax:

# connect to the plausible container
sudo docker exec -it <name of the container> bin/plausible remote

# review the current plausible.mailer settings
Application.get_env(:plausible, Plausible.Mailer)

# create a test email
email = Bamboo.Email.new_email(from: "[email protected]", to: "[email protected]", subject: "test", text_body: "test")

# sends out the test email
Plausible.Mailer.deliver_now(email)

@ruslandoga thanks so much for maintaining this great project!!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

STMP problem on v2.1 install regardless of adapter #4149

{{title}}

Replies: 1 comment 16 replies

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

STMP problem on v2.1 install regardless of adapter #4149

anttikivi May 27, 2024

Replies: 1 comment · 16 replies

ruslandoga May 28, 2024 Collaborator

ruslandoga Jun 22, 2024 Collaborator

wheeleran Jun 22, 2024

ruslandoga Jun 22, 2024 Collaborator

wheeleran Jun 22, 2024

wreidlinger Jun 24, 2024

anttikivi
May 27, 2024

Replies: 1 comment 16 replies

ruslandoga
May 28, 2024
Collaborator

ruslandoga Jun 22, 2024
Collaborator

ruslandoga Jun 22, 2024
Collaborator