Email Software Resources

Moving installation to another server It is possible to move Aurora Corporate 8 installation to a different server by performing the following steps. Export full structure and content of MySQL database used by Aurora Corporate 8, tools like phpMyAdmin can do that for you. On a new server, create the database for use with Aurora Corporate 8 and import structure and content into it. Copy all the directories and files of Aurora Corporate 8 installation to a new server. Make sure database connection details are supplied correctly, you can adjust those in the admin interface or by editing data/settings/config.json file directly. Make sure the data directory is set recursively writeable by the web server on the new installation.

By default, user session in Aurora Corporate 8 doesn't expire. If you wish to reconfigure the product so that users are logged out after a certain amount of time due to inactivity, that's done by modifying data/settings/modules/SessionTimeoutWebclient.config.json file: { "Disabled": [ true, "bool" ], "TimeoutMinutes": [ 30, "int" ], "IncludeInMobile": [ true, "bool" ] } Set Disabled to false and specify a timeout value in TimeoutMinutes as the amount of minutes.

Aurora Corporate 8 offers OpenPGP support. You can sign and encrypt outgoing emails, as well as verify and decrypt messages you receive. To implement OpenPGP support, we used OpenPGP.js library. It works with current versions of Firefox, Chrome, and Safari; Internet Explorer is not supported. This functionality is enabled in product configuration by default - however, the administrator can disable OpenPGP support https://afterlogic.com/docs/aurora-corporate-8/configuring-webmail/how-to-disable-openpgp-support By default, OpenPGP support is disabled for all the users, and each specific user should enable it for their account if they're willing to use OpenPGP. That's done in OpenPGP screen of user account settings. The first thing to do is to set up your public and private key. If you don't have those yet, you can generate those in the interface directly: press Generate button, select the email address you're willing to use, specify the password for the key pair (''optional'') and select the key length. Generating keys may take a while, once that's done you'll have the keys stored in your Aurora Corporate 8 account. If you already have those keys, you can import those into the application, that is done separately for the public and private key. You can have keys supplied for multiple email addresses linked to the same Aurora Corporate 8 account if necessary. IMPORTANT: Private and public keys are never transmitted to the server where the application runs, handling keys is performed in your browser only. So if you have multiple locations you access your account on, you'll need to add the same keys across all of them. The next step is to send your public keys to parties you're willing to exchange emails securely with. That can be done in multiple ways, for example making them available on your website. Of course, you can send those via the interface, too - in OpenPGP settings screen, click View and then Send button. When someone sends you the key file with .asc extension, you'll be able to import that one - and just like your own keys, they're stored in the browser, not on the server. In message compose mode, you can press the OpenPGP button which opens the dialog for processing outgoing mail. For signing emails, you'll need to have your own private key, and in case of encrypting, public keys of all the recipients are required. When you receive signed or encrypted message, you'll get an option to verify/decrypt that message. For decrypting messages, you only need your private key; for verification purposes, sender's public key is required. Note that using OpenPGP has its limitations - only plaintext messages can be processed, attachments or HTML bodies can not. And once you invoke OpenPGP tool at message compose screen, you'll get a prompt for removing message formatting before proceeding with signing/encrypting.