In my experience this applies to Mavericks (10.9) and Yosemite (10.10) the same way that Apple says to do it for Mountain Lion.
https://support.apple.com/en-ca/HT5032
- In Server.app, go to Users and select a user.
- Click the gear icon (or Control-click the user name) and choose "Edit Mail Options..."
- From the "Mail should be:" pop-up menu, select "forwarded".
- Enter the forwarding email address in the "to email address:" field.
Additionally or alternatively, there is also a configuration file at /etc/aliases, /etc/postfix/aliases, and/or /Library/Server/Mail/Config/postfix/aliases which can be edited (using sudo) and in the area "# Put your local aliases here." you could put the line:
user: myname@gmail.com
If you want a copy to stay in the local mailbox of user you could use:
user: user,myname@gmail.com
If you want copies to go to additional accounts, they are separated by commas.
some-name: user1,user2,user3
This can be used for email addresses that do not have accounts on the machine such as webmaster or postmaster.
After saving the file, one needs to run the command:
sudo newaliases
I have done this for Mavericks Server for local email addresses, recently tested it for Yosemite Server and found that it works for external address too.
Note that individual aliases can also be added for particular users in Server.app.
Also of possible use are the notes kept by "magnusviri" about managing postfix on OS X Server (3.1.2) on Mavericks 10.9.4 - there is disussion about the different locations of configuration files between /etc, /etc/postfix, and/or /Library/Server/Mail/Config/postfix/ Only one of these three locations will be being used by your setup, so editing the "wrong" files will have no effect on the system's behaviour.
http://www.magnusviri.com/OS_X_Server/os-x-server-postfix.html
After some work I got it working. I went through all the steps in the video minus access group. I guess my problem was related with capturing the new basestation, after going over the setup of the second Basestation and rebooting everything works now! I corrected also some certification related problems. I used the excellent Admin Tool Radius to set alt up correctly, an incorrect setting might have been the cause of my troubles!
1) I would like to know what kind of RADIUS support does Server App provide?
It appears to provide full support.
2) Since adding a second Airport basestation does not work, I guess I will have to configure a RADIUS server outside of Server App, probably following this video: https://vimeo.com/53774350?
Still excellent tutorial, slightly outdated in macOS Sierra.
3) What happens to the Server App's Airport Basestation configuration I had active for the first Basestation? Can I still configure Services and mapping from Server App?
It works in our case
4) Should I just keep the Basestation activated in Server App, but deactivate the authentication requirement over WiFi and configure a separate RADIUS server?
It works in our case. No need to set up the Radiusserver again. My incomplete Radius Server was probably a certification related problem.
5) How about certificates: Server App already has a global certificate, can i use this instead of building a new one?
Radius will use the certificate used in the Server App. I used the excellent Admin Tool Radius to set it up.
6) Will the access group (which is mentioned in the video) be visible in Server App?
If you choose "show system accounts" under Server>View then it should show up. But there is no need to set an access group, since RADIUS will use Opendirectory.
So everything is working now. As I said I just went over the single steps again, the problem I had was probably related to the Certificate or a mistake in the Client setup.
Now I just have to figure out how to get the RADIUS logs into Console, since they do not appear there in macOS Sierra!
Best Answer
The OS X Cache server is for caching only Apple products. For having web caching you can try something like Squidman