App Suggestion: Poste.io

Hey there!

I was trying to get poste.io working, and saw 2 red-flags in their Web UI.

{
  "captainVersion": "1",
  "dockerCompose": {
    "version": "3.7",
    "services": {
      "$$cap_appname": {
        "image": "analogic/poste.io",
        "ports": [
          "25:25",
          "110:110",
          "143:143",
          "465:465",
          "587:587",
          "993:993",
          "995:995",
          "4190:4190"
        ],
        "volumes": [
          "/etc/localtime:/etc/localtime:ro",
          "$$cap_appname-data:/data",
          "/captain/generated/static/domains/$$cap_host/.well-known:/opt/www/.well-known."
        ],
        "restart": "always",
        "environment": {
          "HTTPS": "OFF",
          "LETSENCRYPT_EMAIL": "$$cap_email",
          "LETSENCRYPT_HOST": "$$cap_host",
          "VIRTUAL_HOST": "$$cap_host"
        }
      }
    }
  },
  "instructions": {
    "start": "SMTP + IMAP + POP3 + Antispam + Antivirus\nWeb administration + Web email\n...on your server in ~5 minutes\n\nRecommended: Use\"mail\" as the App Name.",
    "end": "Poste is deployed and available as $$cap_appname. \n\n IMPORTANT: It will take up to 2 minutes for Poste to be ready. Before that, you might see 502 error page.\n"
  },
  "variables": [
    {
      "id": "$$cap_email",
      "label": "Email Address",
      "description": "The email address used for Lets Encrpt certificates."
    },
    {
      "id": "$$cap_host",
      "label": "Hostname",
      "description": "The full hostname for this captain app. (usually mail.mydomain.com)"
    }
  ]
}

Could you please guide me on how I can solve these 2 issues?

It seems like poste.io requires the --hostname argument to work, and caprover ignores that in docker-compose.

Not sure what the Let’s encrypt warning is about.

[valoricDe]

If your app is called myapp at path /#/apps/details/myapp `

[valoricDe]

When my mail client connects to poste.io it says the poste certificate does not match the hostname. So I created multiple volumes following @githubsaturn 's suggestions:

/captain/data/letencrypt/etc/live/mail.domain.de/chain.pem -> /data/ssl/ca.crt
/captain/data/letencrypt/etc/live/mail.domain.de/cert.pem -> /data/ssl/server.crt
/captain/data/letencrypt/etc/live/mail.domain.de/privkey.pem -> /data/ssl/server.key

I don’t know what will happen when caprover refreshes the certificate but the poste server is not restarted. Would be theoretically a way that caprover restarts the service on certificate renewal?