|Contact:||Michael JasonSmith <firstname.lastname@example.org>|
|Copyright:||This document is licensed under a Creative Commons Attribution-Share Alike 4.0 International License by OnlineGroups.net.|
For new installations of GroupServer the most important change is the updated buildout recipes, that should make the process of installing GroupServer more robust. For existing systems DMARC support has been added, as well as improvements to how incoming SMTP is handled. Finally there have been many other minor code improvements.
GroupServer itself is installed using four recipes that are used by Buildout. All four recipes have been improved. There is now a base recipe class that is shared by the recipes, and unit-tests have been added to ensure the recipes work as expected. Specific improvements include the following.
With the Slivovica release of GroupServer messages are more likely to be received by people whose email is provided by hosts that implement strict DMARC. With strict DMARC messages are checked to ensure that message was actually sent from the host listed in the From address. All mailing-lists (including GNU Mailman, Google Groups, and Yahoo! Groups) modify the message before sending it out, and this would cause the DMARC check to fail.
Like most other mailing lists, GroupServer now rewrites the From address if the group member uses an email provider that implements strict DMARC. The new address includes the name of the sender, and the ID of his or her profile (see Feature 4108). This ensures that the person who sent the message can still be identified, and email message will still get through.
With the Slivovica release of GroupServer email messages are correctly sent to GroupServer when it is running on a non-standard port. Messages are received by Postfix, which then uses the smtp2gs programme to add the message to GroupServer. Previously manual intervention was needed if GroupServer was listening to a non-standard port.
Now all components of GroupServer correctly handle the port that is set in the configuration file when GroupServer is first set-up. This includes the recipe that creates the alias file for Postfix, the smtp2gs script that uploads the email message, and the gs.form library that smtp2gs uses to connect to GroupServer.
Four components have undergone minor updates for Slivovica.
In addition the following general changes have been made to GroupServer.
To get Slivovica go to the Downloads page for GroupServer and follow the GroupServer Installation documentation. Those who already have a functioning installation can update an existing GroupServer system.
To update a system running the Ouzo release of GroupServer (14.03) to Slivovica (14.06) carry out the following steps.
Download the Slivovica tar-ball from the GroupServer download page.
Uncompress the tar-ball:
$ tar cfz groupserver-14.06.tar.gz
Change to the directory that contains your existing GroupServer installation.
Copy the new version-configuration files to your existing GroupServer installation:
$ cp ../groupserver-14.06/[vz]*cfg .
In your existing GroupServer installation run:
$ ./bin/buildout -n
Restart your GroupServer instance.