This repository has been archived by the owner on Nov 26, 2024. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
Thanks for GroupServer! I ran into some issues during install and modified the docs accordingly.
It was unclear how Postfix forwards mail to GroupServer's automagic handler. I added a bit to the Postfix conf docs to clarify that you need to add your domains for it to work, eg
@groups.example.com groupserver-automagic@localhost
Nginx server configuration must contain
listen [::]:80;
in addition tolisten 80;
to support IPv6. Without this, the server blocks will be ignored and nginx will select the first server block it finds. This confused me for about an hour because nginx was selecting a different site other than GroupServer until I added this.I made the nginx upstream block consistent with the section about selecting a custom hostname, using
gstest:8080
instead oflocalhost:8080
and reminding users they should change it to whatever they set earlier.I simplified the nginx ZMI configuration by putting it into a location block rather than a sever block. I'm not sure if the docs are outdated here, but a subdomain isn't needed; ZMI lives at
/manage
. This also confused me quite a bit and resulted in this strange error.I expanded on the DNS configuration section, rewording it to be easier to understand and providing examples.
I tested this on nginx on my own install and it is working great. I did not update the Apache section with these changes because I don't have an Apache install to test with. The updated nginx instructions shouldn't conflict with the Apache section, although I am concerned the Apache configuration will have the same issues I ran into with the nginx one and may need to be updated accordingly.
Let me know if you disagree or if I need to change anything. This is my first experience setting up a mailing list server and configuring Postfix manually. I hope my changes here will help others.
Thanks!