Installing WordPress on a local server environment is fairly straight forward. On a Mac the local Apache server may report Error 404 Object not found! errors as it attempts to serve WordPress posts and pages.
These errors can often be attributed to the use of pretty permalinks in WordPress. Stopping them from occurring can be achieved by a simple amendment to the Apache server’s configuration file.
For a while I was using the excellent swiftmailer which performed perfectly on both my local and remote servers for a while, but subsequently ceased working on my remote server.
A great alternative is the PEAR Mail package. Both MAMP and XAMPP come with the PEAR framework pre-configured, so installing the Mail package is straightforward.
An important feature of MAMP is an option to have the Apache and MySQL servers started as the application opens. Include MAMP as a Login Item and the MAMP servers are up-and-running after login.
XAMPP has no such option. Including XAMPP as a Login Item merely opens the XAMPP Control.app and the servers have to be started manually.
The answer is to a use a daemon.