A mail app, to manage mail server from docker

[miguelgargallo]

This would solve startups email, with Mail apps, there is none

[Jaffa-Cakes]

It would be great if we could get something fully featured like Mailcow or docker-mailserver :)

[MelchiorKokernoot]

I have docker mailserver running, was pretty alright to setup just following the basic instructions. Only thing i am having some trouble with is TLS configuration. I just created a package repo where I have the .env and docker compose files configured.

[rodrgds]

I feel like https://github.com/Mailu/Mailu might be the easiest since it's Docker based? Just an idea - would be cool to have a template for it.

[miguelgargallo]

lemme see

[gitekDev]

+1 for Mailcow

[ItzAmirreza]

Looking forward to this! It's a serious feature that needs to be implemented.

[yes-oo]

i agree !

[ooomytech]

Stalwart Mail Server - As an alternative, it can also be used.
Overall, it can already be used right now.

[ItzAmirreza]

Stalwart Mail Server - As an alternative, it can also be used.

Overall, it can already be used right now.

By any chance can you share the setup config for coolify? I have tried mailu but I seem to have problems with SSL certification and traefik.

[cntrvsy]

I second this, im currently going through the same issue with SSL certificate with traefik making the site not accessible via https (stalwarts/mail server). Also if you can link any resources on using it outside of the document that will be helpful.

[MelchiorKokernoot]

You can easily fix this by adding a whoami container to your docker-compose file:

whoami:
    image: 'docker.io/traefik/whoami:latest'

[ooomytech]

Create a Docker Compose-based application. I provided an example of how I use it. For HTTPS to work and to proxy traffic, you need to specify the domain along with the port. After that, you can enter the panel address in the browser without explicitly specifying the port.

Additionally, after creating your application, you need to check the logs where you’ll see the login and password for the administrator. I manually generated the TLS certificates for the server itself, but there is an option to generate them automatically, though I encountered some issues with that. Overall, the server works fine, and it sends and receives mail.

Config for Stalwart Mail Server

Docker Compose:

services:
  stalwart-mail:
    image: 'stalwartlabs/mail-server:latest'
    container_name: stalwart-mail
    ports:            
      - '25:25'
      - '587:587'
      - '465:465'
      - '143:143'
      - '993:993'
      - '4190:4190'
      - '110:110'
      - '995:995'
    volumes:
      - '<STALWART_DIR>:/opt/stalwart-mail'
    tty: true
    stdin_open: true
    restart: always

[CareProID]

can you assist, i have successfuly deployed but i am not gettin credentials, trying to run docker logs stalwart-mail and its giving me

You should see on Application logs when the container is run for the first time.

[antonind72]

how do you generate the ssl/tls certificate? and where do you manage your dns? can you show the steps to generate the certifica? please

[c7e715d1b04b17683718fb1e8944cc28]

I am also curious about how to set ssl/tls.
I have set it up, but I don't know how to set up ssl/tls

[invays]

Hi! Idk why, but after status - Started, I have no logs info... Only message that I need to restart the page. Mb i did something wrong ?

[phykas]

<STALWART_DIR> needs to be created and referenced from host machine in order to get username and password in logs.
example that works:
volumes:
- '/var/lib/stalwart-mail:/opt/stalwart-mail'

[yborisovp]

+1

[cntrvsy]

@ooomytech, sorry to bother you but i cannot for the life of me figure out what's wrong with my deployment, I have been able to get the mail server running on my vps and i can send emails but for some reason i cannot receive emails ( using mail-tester.com i receive a score of 8/10 missing out on 2 point as i have more than one DKIM signature in your message.), did some digging and my connection to the SMTP server is successful, but the issue is with the certificate verification returning the error code: 18 (self-signed certificate) which im assuming isn't trusted by default (i didn't think this would be a problem as i thought coolify does the SSL Certificate for me), I'm pretty new to mail servers and VPS and all the information is general overwhelming. Im doing all of this in the hopes of fixing another error as i would my pocketbase instance running on the same vps to be able to use my custom emails but i get the error "Failed to send the test email. Raw error: tls: failed to verify certificate: x509: certificate is valid for localhost, not mail.company.com". any guidance will be appreciated.

[ooomytech]

use the command: certbot certonly --manual --preferred-challenges dns -d yourdomain.com -d *.yourdomain.com.

[ooomytech]

To create certificates using Certbot with DNS verification, use the command: certbot certonly --manual --preferred-challenges dns -d yourdomain.com -d *.yourdomain.com. Verify the process by adding DNS records. Then upload the obtained certificates (fullchain.pem and privkey.pem) in the web interface in the TLS section (Stalwart)

Make sure that the ports for sending mail are open. On Hetzner, ports may be blocked for new accounts, so you need to send a request to support to unblock them.

[cntrvsy]

@antonind72 i for the life of me cannot find the SSL section on the web interface for stalwart

[ooomytech]

@antonind72 i for the life of me cannot find the SSL section on the web interface for stalwart

[cntrvsy]

thanks for everything, everything working now as expected

[PAYDAYTEAM]

Hey! Thanks for the help, you are a god, I was able to setup everything and is working as expected but it keeps going to spam folder, is there any config on DKIM or SPF to at least try to lower the percentage of mails flagged as spam?

[PAYDAYTEAM]

Already solved it! I was able to stop the spam flag writing all the DNS records in the DNS zone of my domain including TXT, TLSA and CNAME (for easyconfig on devices). Then I made a small change in
the SPF TXT to refer directly to the MX record. Example of my modified value: TXT | yourdomain.com | "v=spf1 mx a -all"

PS: Still happening in certain cases like personal gmail accounts but working for other corporate emails.

[mredodos]

+1 for mailcow

[cntrvsy]

honestly looking back i should have tried mailcow first instead of being cutting edge and but you live and you learn i guess.

[dr-diffie]

+1 for Stalwart. Was mentioned here as well #4118

[dr-diffie]

@ysfaran

[rohankm]

need this

[ApoloApps]

need this!!!

[xer0xde]

+1 for Mailcow