Default docker-compose.yml exposes far too many ports? #262

New Issue

MrUnknownDE · 2026-04-05T16:17:12+02:00

MrUnknownDE commented

2026-04-05 16:17:12 +02:00

Originally created by @MaximumFish on 8/28/2025

Firstly, THANK YOU SO MUCH for making a mail archive solution that actually works and is relatively simple to setup. I've lost track of the times I've tried and failed to setup Mailpiler in the past.

As for the issue report, it seems very odd (and somewhat of a security risk?) that so many ports would be exposed externally in the docker-compose file when the whole stack is running in its own network. I've commented out everything except for the frontend port on my own install and it's all working fine.

Can these be checked and trimmed down to only what's necessary?

Thanks again for an amazing project!

*Originally created by @MaximumFish on 8/28/2025* Firstly, THANK YOU SO MUCH for making a mail archive solution that actually works and is relatively simple to setup. I've lost track of the times I've tried and failed to setup Mailpiler in the past. As for the issue report, it seems very odd (and somewhat of a security risk?) that so many ports would be exposed externally in the docker-compose file when the whole stack is running in its own network. I've commented out everything except for the frontend port on my own install and it's all working fine. Can these be checked and trimmed down to only what's necessary? Thanks again for an amazing project!

MrUnknownDE closed this issue

2026-04-05 16:17:12 +02:00

MrUnknownDE added the improvement improvement labels 2026-04-05 16:17:12 +02:00

Sign in to join this conversation.

No Label improvement improvement

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/OpenArchiver#262