61 lines2.25 KB

Mail server, DNS and client connectivity

MILOUD NECILI

Fraîche Flow · IT Systems Integration

Project objective

Build a separate internal mail service using containers, DNS names, TLS and test mailboxes.

My implementation

Set up Docker Engine and Compose for the mail server on ff-mail-01.
Prepared and started Docker Mailserver with an environment file and persistent mail directories.
Set up certificates, DNS/MX references and mailboxes in the lab.
Worked on Thunderbird/client access through SSH forwarding; overall completion was confirmed by the project lead.

Technical context

Host / service name	`ff-mail-01 / mail.fraicheflow.test`
Container	`mailserver`
Image during the project	`ghcr.io/docker-mailserver/docker-mailserver:latest`
Test accounts during the project	`admin` and `student`; no passwords included

Result

The earlier conversation contains the setup of Compose and mailserver.env and work on containers and accounts. A complete SMTP transaction with a Message-ID is not presented as original evidence in this collection.

Verification and operational evidence

docker compose config -q
docker ps --filter name=mailserver
docker logs --tail 40 mailserver
dig @192.168.10.11 fraicheflow.test MX

Mail server on ff-mail-01 with healthy status and published mail ports

DNS resolution for mail.fraicheflow.test and associated MX record

Practical troubleshooting

Compose initially reported a missing mailserver.env. Configuration continued after the environment file was provided. The client name, certificate name and tunnel destination had to be considered separately.

Security and technical context

An internal mail test does not prove public deliverability. SPF, DKIM, DMARC, PTR, relay protection and alert delivery require separate checks. Roundcube is not claimed to be installed.

Transferable skills

LXC/Docker context, mail protocols, DNS MX, TLS and client connectivity.

Project status

Completed according to confirmation from the project lead.

18_Mailserver.mdx