Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please add configuration instructions for domain #1

Open
jet10000 opened this issue Feb 2, 2021 · 8 comments
Open

Please add configuration instructions for domain #1

jet10000 opened this issue Feb 2, 2021 · 8 comments

Comments

@jet10000
Copy link

jet10000 commented Feb 2, 2021

Please add configuration instructions such as A record, mx record and SPF record of the domain name.

Example for a standalone mail server.

Please add instructions on how to disable some servers, such as webmail or IMAP services for scratch.

There are two purposes, one is quickly configure and build a mail server, and the other is to develop secondary applications based on some services, Meet custom requirements.

Add a docker-compose mail server quick setup file, which can be downloaded and installed directly from hub.docker.com. Simple, convenient and clean.

The project astzweig/wildduck I have been using before is very fast and convenient.

https://hub.docker.com/r/astzweig/wildduck

Thanks, great project

@louis-lau
Copy link
Member

Hi,

Please add configuration instructions such as A record, mx record and SPF record of the domain name.

That could be handy I suppose. I'll look into it.

Please add instructions on how to disable some servers

Just remove them from the docker-compose file. This is the same as with all docker-compose files, you should be able to just Google it.

Add a docker-compose mail server quick setup file,

Have you tried it? Because that's exactly what this project is. So I'm not sure what you mean.

Simple, convenient and clean.

I agree. Which is why I chose to use docker-compose and docker hub already.

great project

Thanks!

@yarosdev
Copy link

It is really not clear how to setup mail server, for instance I am not familiar with traefik.
wildduck listens to 9993 and 9995 so there are no mentions of those anywhere also docker-compose.yml.
How to deal with ports? What ports are running on the wildduck?

Please add configuration instructions such as A record, mx record and SPF record of the domain name.

it is a good request!

@yarosdev
Copy link

This docker-compose.yml is good for bare OS server only. But for real cases you should make reverse engineering of this example to be able to do something.

@louis-lau
Copy link
Member

I am not familiar with traefik

You don't really have to be, but to get familiar with Traefik I would point you to the Traefik docs ;)
It's a reverse proxy.

wildduck listens to 9993 and 9995

It does not.

How to deal with ports

How do you mean?

What ports are running on the wildduck?

143 and 110. You can look inside the wildduck config and change them if you want. Traefik exposes port 993 and 995, handles TLS, and forwards to wildduck.

@louis-lau
Copy link
Member

This docker-compose.yml is good for bare OS server only. But for real cases you should make reverse engineering of this example to be able to do something.

The example docker-compose is for anyone that has either port 80/443 available, or is already using Traefik as their reverse proxy. It's an example of a setup of wildduck in docker. I believe you should always be able to edit a docker-compose to conform to your own setup.

This is an issue about DNS config instructions, you're getting off topic. :)

@yarosdev
Copy link

yarosdev commented Mar 10, 2021

This is a cool project. But it has poor docs. everything is clear for you but for others not. what do I need to receive emails? I have just started wildduck and exposed 110 and 143 ports. I am able to work with imap
image
what does it mean port 993 ? I have checked netstat -tulpn | grep LISTEN and there is no listener on 993... only 110&143

@louis-lau
Copy link
Member

louis-lau commented Mar 10, 2021

Well, right now you're looking at the wildduck configuration. So this isn't really a wildduck-dockerized issue.

That's the port that gets put into apple mobileconfig files if you generate those with wildduck. So it should be where your imap server is reachable externally. In the case of wildduck-dockerized that would normally be through traefik. So port 993.

I agree in this case it's not clear what those config options do. But that isn't an issue for this repository ;).

@louis-lau
Copy link
Member

what do I need to receive emails? I have just started wildduck and exposed 110 and 143 ports

Email transmission doesn't happen over pop3 or imap. I happens over smtp on port 25. In this case haraka is used for inbound email. You may want to read more about how email sending and recieving works before you continue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants