|
|
|
@ -41,15 +41,25 @@ DOCUMENTS/ folder.
|
|
|
|
|
1. Unarchive new Postfix Admin
|
|
|
|
|
------------------------------
|
|
|
|
|
|
|
|
|
|
Make sure that you are in your WWW directory and then unarchive the
|
|
|
|
|
Postfix Admin archive (whatever the filename is):
|
|
|
|
|
(if you installed PostfixAdmin as RPM or DEB package, you can obviously skip this step.)
|
|
|
|
|
|
|
|
|
|
$ tar -zxvf postfixadmin-$version.tgz
|
|
|
|
|
Assuming we are installing Postfixadmin into /srv/postfixadmin, then something like this should work :
|
|
|
|
|
|
|
|
|
|
(if you installed PostfixAdmin as RPM or DEB package, you can obviously skip this step.)
|
|
|
|
|
$ mkdir -p /srv/postfixadmin
|
|
|
|
|
$ cd /srv/postfixadmin
|
|
|
|
|
$ wget -O https://github.com/postfixadmin/postfixadmin/archive/postfixadmin-3.1.tar.gz postfixadmin-3.1.tar.gz
|
|
|
|
|
$ tar -zxvf postfixadmin-version.tgz
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2. Setup Web Server
|
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
|
|
Assuming /var/www/html is where your webserver reads from :
|
|
|
|
|
|
|
|
|
|
$ ln -s /srv/postfixadmin/public /var/www/html/postfixadmin
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2. Setup a Database
|
|
|
|
|
3. Setup a Database
|
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
|
|
With your chosen/preferred database server (i.e. MySQL or PostgreSQL),
|
|
|
|
@ -73,10 +83,10 @@ For PostgreSQL:
|
|
|
|
|
CREATE DATABASE postfix OWNER postfix ENCODING 'unicode';
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3. Configure PostfixAdmin so it can find the database
|
|
|
|
|
4. Configure PostfixAdmin so it can find the database
|
|
|
|
|
-----------------------------------------------------
|
|
|
|
|
|
|
|
|
|
Create a config.local.php file for your local configuration:
|
|
|
|
|
Create /srv/postfixadmin/config.local.php file for your local configuration:
|
|
|
|
|
|
|
|
|
|
<?php
|
|
|
|
|
$CONF['database_type'] = 'mysqli';
|
|
|
|
@ -108,10 +118,12 @@ directory (smarty cache). You can therefore leave the files owned by root (or
|
|
|
|
|
another user); as long as the web server user (e.g. www-data) can read them, it
|
|
|
|
|
will be fine.
|
|
|
|
|
For templates_c/, allow write access (only) for the web server user (e. g. www-data).
|
|
|
|
|
The easiest way to do this is chown -R www-data templates_c
|
|
|
|
|
The easiest way to do this is
|
|
|
|
|
|
|
|
|
|
$ chown -R www-data /srv/postfixadmin/templates_c
|
|
|
|
|
|
|
|
|
|
4. Check settings, and create Admin user
|
|
|
|
|
|
|
|
|
|
5. Check settings, and create Admin user
|
|
|
|
|
----------------------------------------
|
|
|
|
|
|
|
|
|
|
Hit http://yourserver.tld/postfixadmin/setup.php in a web browser.
|
|
|
|
@ -128,13 +140,13 @@ out - with appropriate instructions on what to do with it).
|
|
|
|
|
|
|
|
|
|
create the admin user using the form displayed.
|
|
|
|
|
|
|
|
|
|
5. Use PostfixAdmin
|
|
|
|
|
6. Use PostfixAdmin
|
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
|
|
This is all that is needed. Fire up your browser and go to the site that you
|
|
|
|
|
specified to host Postfix Admin.
|
|
|
|
|
|
|
|
|
|
6. Integration with Postfix, Dovecot etc.
|
|
|
|
|
7. Integration with Postfix, Dovecot etc.
|
|
|
|
|
-----------------------------------------
|
|
|
|
|
|
|
|
|
|
Now that PostfixAdmin is working, you need to do some configuration in Postfix,
|
|
|
|
@ -159,10 +171,12 @@ You'll need to enable the xmlrpc link (see config.inc.php)
|
|
|
|
|
8. More information
|
|
|
|
|
-------------------
|
|
|
|
|
|
|
|
|
|
PostfixAdmin is hosted on SourceForge. For the forum posts and source updates, see:
|
|
|
|
|
https://sourceforge.net/projects/postfixadmin
|
|
|
|
|
|
|
|
|
|
The code and issue tracker is on GitHub:
|
|
|
|
|
https://github.com/postfixadmin/postfixadmin
|
|
|
|
|
|
|
|
|
|
There is also #postfixadmin on irc.freenode.net.
|
|
|
|
|
IRC - a community of people may be able to help in #postfixadmin on irc.freenode.net.
|
|
|
|
|
See http://webchat.freenode.net/
|
|
|
|
|
|
|
|
|
|
Legacy forum posts are on SourceForce at
|
|
|
|
|
https://sourceforge.net/projects/postfixadmin
|
|
|
|
|
|
|
|
|
|