Server status
~~~~~~~~~~~~~
-image::images/screenshot/pmg-gui-server-status.png[]
+[thumbnail="pmg-gui-server-status.png", big=1]
This page shows server statistics about CPU, memory, disk and network
usage. You can select the displayed time span on the upper right.
Services
~~~~~~~~
-image::images/screenshot/pmg-gui-service-status.png[]
+[thumbnail="pmg-gui-service-status.png", big=1]
This panel lists all major services used for mail processing and
cluster synchronization. If necessary, you can start, stop or restart
Updates
~~~~~~~
-image::images/screenshot/pmg-gui-updates.png[]
+[thumbnail="pmg-gui-updates.png", big=1]
We release software updates on a regular basis, and it is recommended
to always run the latest available version. This page shows the
Syslog and Tasks
~~~~~~~~~~~~~~~~
-image::images/screenshot/pmg-gui-syslog.png[]
+[thumbnail="pmg-gui-syslog.png", big=1]
The syslog page gives you a quick real-time log view. Please use the
xref:pmg_tracking_center[Tracking Center] to search the logs.
Spam
~~~~
-image::images/screenshot/pmg-gui-spam-quarantine.png[]
+[thumbnail="pmg-gui-spam-quarantine.png", big=1]
This panel lets you inspect the mail quarantine. Emails can be safely
previewed and if desired, delivered to the original user.
Tracking Center
---------------
-image::images/screenshot/pmg-gui-tracking-center.png[]
+[thumbnail="pmg-gui-tracking-center.png", big=1]
Email processing is a complex task and involves several service
daemons. Each daemon logs information to the syslog service. The
powerful way to define filter rules by user, domains, time frame,
content type and resulting action.
-image::images/screenshot/pmg-gui-mail-filter-rules.png[]
+[thumbnail="pmg-gui-mail-filter-rules.png", big=1]
Every rule has 5 categories ('FROM', 'TO', 'WHEN', 'WHAT' and
'ACTION'), and each category may contain several objects to match
'Action' - objects
------------------
-image::images/screenshot/pmg-gui-mail-filter-actions.png[]
+[thumbnail="pmg-gui-mail-filter-actions.png", big=1]
Please note that some actions stops further rule precessing. We call
such actions 'final'.
'Who' - objects
---------------
-image::images/screenshot/pmg-gui-mail-filter-who-objects.png[]
+[thumbnail="pmg-gui-mail-filter-who-objects.png", big=1]
This type of objects can be used for the 'TO' and/or 'FROM' category,
and macth the sender or receiver of the e-mail. A single object can
'What' - objects
----------------
-image::images/screenshot/pmg-gui-mail-filter-what-objects.png[]
+[thumbnail="pmg-gui-mail-filter-what-objects.png", big=1]
'What' - objects are used to classify the mail content. A single
object can combine multiple items, and the following item types are
'When' - objects
----------------
-image::images/screenshot/pmg-gui-mail-filter-when-objects.png[]
+[thumbnail="pmg-gui-mail-filter-when-objects.png", big=1]
'When' - objects are use to activate rules at specific daytimes. You
can compose them of one or more time-frame items.
~~~~~~~~~~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-network-config.png[]
+[thumbnail="pmg-gui-network-config.png", big=1]
endif::manvolnum[]
Normally the network and time is already configured when you visit the
~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-system-options.png[]
+[thumbnail="pmg-gui-system-options.png", big=1]
endif::manvolnum[]
~~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-mailproxy-relaying.png[]
+[thumbnail="pmg-gui-mailproxy-relaying.png", big=1]
endif::manvolnum[]
Those settings are saved to subsection 'mail' in `/etc/pmg/pmg.conf`,
~~~~~~~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-mailproxy-relaydomains.png[]
+[thumbnail="pmg-gui-mailproxy-relaydomains.png", big=1]
endif::manvolnum[]
List of relayed mail domains, i.e. what destination domains this
~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-mailproxy-ports.png[]
+[thumbnail="pmg-gui-mailproxy-ports.png", big=1]
endif::manvolnum[]
Those settings are saved to subsection 'mail' in `/etc/pmg/pmg.conf`,
~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-mailproxy-options.png[]
+[thumbnail="pmg-gui-mailproxy-options.png", big=1]
endif::manvolnum[]
Those settings are saved to subsection 'mail' in `/etc/pmg/pmg.conf`,
~~~~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-mailproxy-transports.png[]
+[thumbnail="pmg-gui-mailproxy-transports.png", big=1]
endif::manvolnum[]
You can use {pmg} to send e-mails to different internal
~~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-mailproxy-networks.png[]
+[thumbnail="pmg-gui-mailproxy-networks.png", big=1]
endif::manvolnum[]
You can add additional internal (trusted) IP networks or hosts.
~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-mailproxy-tls.png[]
+[thumbnail="pmg-gui-mailproxy-tls.png", big=1]
endif::manvolnum[]
Transport Layer Security (TLS) provides certificate-based
~~~~~~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-mailproxy-dkim.png[]
+[thumbnail="pmg-gui-mailproxy-dkim.png", big=1]
endif::manvolnum[]
DomainKeys Identified Mail (DKIM) Signatures (see {dkim_rfc}) is a method to
~~~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-mailproxy-whitelist.png[]
+[thumbnail="pmg-gui-mailproxy-whitelist.png", big=1]
endif::manvolnum[]
All SMTP checks are disabled for those entries (e. g. Greylisting,
~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-spam-options.png[]
+[thumbnail="pmg-gui-spam-options.png", big=1]
endif::manvolnum[]
{pmg} uses a wide variety of local and network tests to identify spam
~~~~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-spamquar-options.png[]
+[thumbnail="pmg-gui-spamquar-options.png", big=1]
endif::manvolnum[]
Proxmox analyses all incoming e-mail messages and decides for each
~~~~~~~~~~~~~~~~~~~~~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-spam-custom-scores.png[]
+[thumbnail="pmg-gui-spam-custom-scores.png", big=1]
endif::manvolnum[]
While the default scoring of {spamassassin}'s ruleset provides very good
~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-virus-options.png[]
+[thumbnail="pmg-gui-virus-options.png", big=1]
endif::manvolnum[]
All mails are automatically passed to the included virus detector
include::pmg.clamav-conf-opts.adoc[]
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-clamav-database.png[]
+[thumbnail="pmg-gui-clamav-database.png", big=1]
endif::manvolnum[]
Please note that the virus signature database it automatically
~~~~~~~~~~
ifndef::manvolnum[]
-image::images/screenshot/pmg-gui-virusquar-options.png[]
+[thumbnail="pmg-gui-virusquar-options.png", big=1]
endif::manvolnum[]
Indentified virus mails are automatically moved to the virus
Local Users
~~~~~~~~~~~
-image::images/screenshot/pmg-gui-local-user-config.png[]
+[thumbnail="pmg-gui-local-user-config.png", big=1]
Local users are used to manage and audit {pmg}. Those users can login on the
management web interface.
LDAP/Active Directory
~~~~~~~~~~~~~~~~~~~~~
-image::images/screenshot/pmg-gui-ldap-user-config.png[]
+[thumbnail="pmg-gui-ldap-user-config.png", big=1]
You can specify multiple LDAP/Active Directory profiles, so that you can
create rules matching those users and groups.
Fetchmail
~~~~~~~~~
-image::images/screenshot/pmg-gui-fetchmail-config.png[]
+[thumbnail="pmg-gui-fetchmail-config.png", big=1]
Fetchmail is utility for polling and forwarding e-mails. You can define
e-mail accounts, which will then be fetched and forwarded to the e-mail