Configuration

Logging into admin interface

Once you have a blank install of WebMail Pro set up, you can navigate to admin interface by appending /adminpanel/ to the installation URL and supplying superadmin as username, and an empty password.

(Note that previous version 8 of the product didn't have a separate login page for administrator, it was the same main page of the product interface used.)

Right after entering admin interface, you're strongly advised to set up a password. If you wish, you can change admin login as well.

In the future, if you forget admin username or password, check data/settings/config.json file, you'll find AdminLogin there in clear text. To reset admin password, set empty value for AdminPassword, then log in with empty password and set a new one.

License key

Most of the product functionality will be locked until you supply a license key. WebMail Pro license key starts with AU90.

When you log in as superadmin, you should see System tab with Licensing section. License key field is where you need to type the key.

If you have supplied a trial license key, and then you purchase a product license, you won't have to download or reinstall anything, just replace trial license key with a permanent one.

Database settings

Another critical part of setting up the product is configuring database settings. It's assumed that you already have a database created, fill in the connection details, press Save, then you can Create Tables.

IMPORTANT: When setting up a new installation of WebMail Pro, be sure to click "Update configuration" button on Database Settings screen. Doing so will ensure all the modules have their configuration files initialized under data/settings/modules directory.

Setting up mail servers

To access your accounts, you would need to set at least one mail server. Under Mail Servers tab, click Add New Server button. You'll need to supply IMAP and SMTP server connection details, as well as the complete list of domains that belong to this server.

Note that you will not need to add users manually - instead, users simply log in from main page by specifying their email and password. And based on domain part of their email address, a certain mail server is used, out of those you have added in this step.

Configuring Notes support (optional)

If you wish to make use of Notes feature, enable it as described at Enabling Notes support documentation page. Note that the module forces creating Notes folder in every email account users log into, unless the folder exists there already.

Configuring Filters (optional)

If you'd like to enable Filters tab in account settings, you need to configure ManageSieve integration. The same applies to setting up Forwarding and Autoresponder.

Enabling Paranoid Encryption

Check Enabling Paranoid Encryption documentation page.

Displaying detailed error messages in user interface

When error of some kind occurs and error message is shown in WebMail Pro interface, by default it also includes detailed error information such as copy of server's response.

You might wish to have error details suppressed in web interface, that's done by setting DisplayServerErrorInformation to false in data/settings/config.json file.

Please note that regardless of this setting, detailed error information can always be found in can be found in debug logs.

Troubleshooting

If you encounter any issues with users logging in, receiving or sending mails etc., you need to enable debug logging. Typically, you would need Verbosity paramete set to Debug as it offers the most complete logging, including full communication with email server.

Troubleshooting MySQL server performance

If you encounter performance issues with the database, and InnoDB storage engine is used, you can either switch to MyISAM or reconfigure your database server as suggested in this blog post.

CSRF protection

In v8.3.5, CSRF protection was substantially revised and may require web server reconfiguration. We're now shipping .htaccess file to ensure authentication headers are sent through, but if you're getting Error 500, that may mean you have mod_rewrite disabled. And if you receive "Cookies need to be updated. To continue, please click here or reload this page." message, make sure .htaccess file is actually read by the web server. Read more on this at CSRF protection documentation page.