1. What this page explains
How Eggy Mail should be installed, configured and handed over as a branded webmail product.
2. Who this is for
Website owners, hosting providers, MSPs, IT agencies and support staff responsible for deploying Eggy Mail.
3. Before you start
Confirm PHP/MySQL requirements, upload the correct package, check database access, confirm writable folders and prepare the customer account/download flow.
4. Step-by-step instructions
Upload the product package, open the installer, complete server and database checks, create the owner/admin account, configure webmail product settings, confirm secure downloads and test one real login/support workflow.
5. Common mistakes
Uploading files into the wrong webroot, skipping writable folder checks, using incorrect database credentials, mixing Regular and Extended packages, or giving customers direct ZIP links instead of secure downloads.
6. Troubleshooting
For missing config files use EGGY-CONFIG-008. For database failure use EGGY-DB-002. For missing downloads use EGGY-DL-005.
7. Related articles
Server requirements, secure downloads, licence/package differences and troubleshooting error codes.
8. When to contact support
After checking permissions, database credentials, package path and the exact error message. Include product, licence type, PHP version and screenshot.