include::pmg-intro.adoc[]
-include::pmg-quick-start.adoc[]
-
include::pmg-planning-deployment.adoc[]
-include::pmgconfig.adoc[]
-
-// Return to normal title levels.
-:leveloffset: 0
+include::pmg-installation.adoc[]
-TODO
-----
-// FIXME
+include::pmgconfig.adoc[]
-[[nmap]]
-nmap
+include::pmg-mail-filter.adoc[]
-[[create_bootable_usb]]
-create_bootable_usb
+include::pmgbackup.adoc[]
-[[mail_server_config]]
-mail_server_config
+include::pmgcm.adoc[]
-[[fitering_outgoing_mail]]
-fitering_outgoing_mail
+// Return to normal title levels.
+:leveloffset: 0
Important Service Daemons
include::pmgsh.adoc[]
+include::pmgversion.adoc[]
+
+include::pmgsubscription.adoc[]
+
include::pmgperf.adoc[]
include::pmgqm.adoc[]
include::pmgreport.adoc[]
+include::pmgupgrade.adoc[]
+
:leveloffset: 0
+[[nmap]]
+`nmap` - Port Scans
+-------------------
+
+`nmap` is designed to allow system administrators to scan large
+networks to determine which hosts are up and what services they are
+offering. You can use nmap to test your firewall setting, for example
+to see if the required ports are open.
+
+.Test Razor port (tcp port 2703):
+----
+# nmap -P0 -sS -p 2703 c301.cloudmark.com
+
+Starting Nmap 5.00 ( http://nmap.org ) at 2012-07-31 11:10 CEST
+Interesting ports on c301.cloudmark.com (208.83.137.114):
+PORT STATE SERVICE
+2703/tcp open unknown
+
+Nmap done: 1 IP address (1 host up) scanned in 0.17 seconds
+----
+
+See the manual page (`man nmap`) for more information about nmap.
+
+
+:leveloffset: 1
+
+include::pmg-bibliography.adoc[]
+
+:leveloffset: 0
+
+[appendix]
+SSL certificate
+---------------
+
+Access to the administration web interface is always done via
+`https`. The default certificate is never valid for your browser and
+you get always warnings.
+
+If you want to get rid of these warnings, you have to generate a valid
+certificate for your server.
+
+Login to your Proxmox via ssh or use the console:
+
+----
+openssl req -newkey rsa:2048 -nodes -keyout key.pem -out req.pem
+----
+
+Follow the instructions on the screen, see this example:
+
+----
+Country Name (2 letter code) [AU]: AT
+State or Province Name (full name) [Some-State]:Vienna
+Locality Name (eg, city) []:Vienna
+Organization Name (eg, company) [Internet Widgits Pty Ltd]: Proxmox GmbH
+Organizational Unit Name (eg, section) []:Proxmox Mail Gateway
+Common Name (eg, YOUR name) []: yourproxmox.yourdomain.com
+Email Address []:support@yourdomain.com
+
+Please enter the following 'extra' attributes to be sent with your certificate request
+A challenge password []: not necessary
+An optional company name []: not necessary
+----
+
+After you finished this certificate request you have to send the file
+`req.pem` to your Certification Authority (CA). The CA will issue the
+certificate (BASE64 encoded) based on your request – save this file as
+`cert.pem` to your Proxmox.
+
+To activate the new certificate, do the following on your Proxmox:
+
+----
+cat key.pem cert.pem >/etc/pmg/pmg-api.pem
+----
+
+The restart the API servers
+
+----
+systemctl restart pmgproxy
+----
+
+Test your new certificate by using your browser.
+
+NOTE: To transfer files from and to your Proxmox, you can use secure
+copy: If you desktop is Linux, you can use the `scp` command line
+tool. If your desktop PC is windows, please use a scp client like
+WinSCP (see http://winscp.net/).
+
+
[appendix]
Command Line Interface
----------------------
+*pmgbackup* - Proxmox Mail Gateway Backup and Restore Utility
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+include::pmgbackup.1-synopsis.adoc[]
+
+
+*pmgcm* - Proxmox Mail Gateway Cluster Management Toolkit
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+include::pmgcm.1-synopsis.adoc[]
+
+
*pmgsh* - API Shell
~~~~~~~~~~~~~~~~~~~
include::cluster.conf.adoc[]
+include::user.conf.adoc[]
+
+include::ldap.conf.adoc[]
+
:leveloffset: 0
:leveloffset: 1
projects / pmg-docs.git / blobdiff