No analytics about listmonk HOT 4 CLOSED

Are you using Amazon SES? For bounces & complaints with SES see https://listmonk.app/docs/bounces/#amazon-simple-email-service-ses.

For tracking opens & clicks see https://listmonk.app/docs/concepts/#tracking-pixel. Though those docs sections could use some improvements to describe how to enable/disable them.

You could check the Tutorials section https://listmonk.app/docs/installation/#tutorials or search other issues since I think it's been discussed.

from listmonk.

Ah regarding tracking, I see now, from an email noob it's not clear that you have to set up the routes yourself 😅

Also how to retrieve the original URL from the TrackLink URL?

EDIT: Oops, it was because the root URL was different. I kinda did prefer my custom implementation though...I'll look into the appearance settings, see if that will suffice.

Thanks for the help!

from listmonk.

I do have one more query, my emails have started to go to spam upon setting the correct root URL and I suspect it's due to the non-ssl ec2 link. I've added a subdomain record and have a certificate ready, so now just need listmonk to be available on port 443.

Is it just a case of updating the port in the config and restarting the app with docker?

version: "3.7"

x-app-defaults: &app-defaults
  restart: unless-stopped
  image: listmonk/listmonk:latest
  ports:
    - "9000:9000"
  networks:
    - listmonk
  environment:
    - TZ=Etc/UTC

from listmonk.

Hi @liampmccabe. listmonk config needn't change.

You've to run a TLS (SSL) proxy like Caddy or Nginx that'll listen on port 443 externally on your subdomain and proxy requests to listmonk internally to 9000. You also have to make sure that port 9000 is not exposed to the internet.

If you pick Caddy, the config file will look something like this. You don't have to generate or handle certificates manually as it'll automatically use LetsEncrypt to generate SSL certs for your subdomain.

https://subdomain.yoursite.com {
    # Proxy incoming requests to listmonk running in Docker.
    reverse_proxy localhost:9000

    encode gzip
    tls {
        # This will automatically handle certs and listen on 443.
        on_demand
    }
}

from listmonk.