10 pmgconfig - Proxmox Mail Gateway Configuration Management Toolkit
16 include::pmgconfig.1-synopsis.adoc[]
23 Configuration Management
24 ========================
28 {pmg} is usually configured using the web-based Graphical User
29 Interface (GUI), but it is also possible to directly edit the
30 configuration files, use the REST API over 'https'
31 or the command line tool `pmgsh`.
33 The command line tool `pmgconfig` is used to simplify some common
34 configuration tasks, i.e. to generate cerificates and to rewrite
35 service configuration files.
37 NOTE: We use a Postgres database to store mail filter rules and
38 statistic data. See chapter xref:chapter_pmgdb[Database Management]
42 Configuration files overview
43 ----------------------------
45 `/etc/network/interfaces`::
47 Network setup. We never modify this files directly. Instead, we write
48 changes to `/etc/network/interfaces.new`. When you reboot, we rename
49 the file to `/etc/network/interfaces`, so any changes gets activated
54 DNS search domain and nameserver setup.
58 The system's host name.
62 Static table lookup for hostnames.
66 Stores common administration options, i.e. the spam and mail proxy setup.
68 `/etc/pmg/cluster.conf`::
74 The list of relay domains.
76 `/etc/pmg/fetchmailrc`::
78 Fetchmail configuration (POP3 and IMAP setup).
80 `/etc/pmg/ldap.conf`::
84 `/etc/pmg/mynetworks`::
86 List of local (trusted) networks.
88 `/etc/pmg/subscription`::
90 Stores your subscription key and status.
92 `/etc/pmg/tls_policy`::
94 TLS policy for outbound connections.
96 `/etc/pmg/transports`::
98 Message delivery transport setup.
100 `/etc/pmg/user.conf`::
102 GUI user configuration.
104 `/etc/mail/spamassassin/custom.cf`::
106 Custom {spamassassin} setup.
109 Keys and Certificates
110 ---------------------
112 `/etc/pmg/pmg-api.pem`::
114 Key and certificate (combined) used be the HTTPs server (API).
116 `/etc/pmg/pmg-authkey.key`::
118 Privat key use to generate authentication tickets.
120 `/etc/pmg/pmg-authkey.pub`::
122 Public key use to verify authentication tickets.
124 `/etc/pmg/pmg-csrf.key`::
126 Internally used to generate CSRF tokens.
128 `/etc/pmg/pmg-tls.pem`::
130 Key and certificate (combined) to encrypt mail traffic (TLS).
133 Service Configuration Templates
134 -------------------------------
136 {pmg} uses various services to implement mail filtering, for example
137 the {postfix} Mail Transport Agent (MTA), the {clamav} antivirus
138 engine and the Apache {spamassassin} project. Those services use
139 separate configuration files, so we need to rewrite those files when
140 configuration is changed.
142 We use a template based approach to generate those files. The {tts} is
143 a well known, fast and flexible template processing system. You can
144 find the default templates in `/var/lib/pmg/templates/`. Please do not
145 modify them directly, because your modification would get lost on the
146 next update. Instead, copy the template you wish to change to
147 `/etc/pmg/templates/`, then apply your changes there.
149 Templates can access any configuration setting, and you can use the
150 `pmgconfig dump` command to get a list of all variable names:
155 dns.domain = yourdomain.tld
157 ipconfig.int_ip = 192.168.2.127
158 pmg.admin.advfilter = 1
162 The same tool is used to force regeneration of all template based
163 configuration files. You need to run that after modifying a template,
164 or when you directly edit configuration files
167 # pmgconfig sync --restart 1
170 The above command also restarts services if the underlying configuration
171 files are changed. Please note that this is automatically done when
172 you change the configuration using the GUI or API.
174 NOTE: Modified templates from `/etc/pmg/templates/` are automatically
175 synced from the master node to all cluster members.
178 [[pmgconfig_systemconfig]]
186 image::images/screenshot/pmg-gui-network-config.png[]
189 Normally the network and time is already configured when you visit the
190 GUI. The installer asks for those settings and sets up the correct
193 The default setup uses a single Ethernet adapter and static IP
194 assignment. The configuration is stored at '/etc/network/interfaces',
195 and the actual network setup is done the standard Debian way using
198 .Example network setup '/etc/network/interfaces'
200 source /etc/network/interfaces.d/*
203 iface lo inet loopback
206 iface ens18 inet static
207 address 192.168.2.127
208 netmask 255.255.240.0
214 Many tests to detect SPAM mails use DNS queries, so it is important to
215 have a fast and reliable DNS server. We also query some public
216 available DNS Blacklists. Most of them apply rate limits for clients,
217 so they simply will not work if you use a public DNS server (because
218 they are usually blocked). We recommend to use your own DNS server,
219 which need to be configured in 'recursive' mode.
226 image::images/screenshot/pmg-gui-system-options.png[]
230 Those settings are saved to subsection 'admin' in `/etc/pmg/pmg.conf`,
231 using the following configuration keys:
233 include::pmg.admin-conf-opts.adoc[]
236 Mail Proxy Configuration
237 ------------------------
239 [[pmgconfig_mailproxy_relaying]]
244 image::images/screenshot/pmg-gui-mailproxy-relaying.png[]
247 Those settings are saved to subsection 'mail' in `/etc/pmg/pmg.conf`,
248 using the following configuration keys:
250 include::pmg.mail-relaying-conf-opts.adoc[]
252 [[pmgconfig_mailproxy_relay_domains]]
257 image::images/screenshot/pmg-gui-mailproxy-relaydomains.png[]
260 List of relayed mail domains, i.e. what destination domains this
261 system will relay mail to. The system will reject incoming mails to
265 [[pmgconfig_mailproxy_ports]]
270 image::images/screenshot/pmg-gui-mailproxy-ports.png[]
273 Those settings are saved to subsection 'mail' in `/etc/pmg/pmg.conf`,
274 using the following configuration keys:
276 include::pmg.mail-ports-conf-opts.adoc[]
279 [[pmgconfig_mailproxy_options]]
284 image::images/screenshot/pmg-gui-mailproxy-options.png[]
287 Those settings are saved to subsection 'mail' in `/etc/pmg/pmg.conf`,
288 using the following configuration keys:
290 include::pmg.mail-options-conf-opts.adoc[]
293 [[pmgconfig_mailproxy_transports]]
298 image::images/screenshot/pmg-gui-mailproxy-transports.png[]
301 You can use {pmg} to send e-mails to different internal
302 e-mail servers. For example you can send e-mails addressed to
303 domain.com to your first e-mail server, and e-mails addressed to
304 subdomain.domain.com to a second one.
306 You can add the IP addresses, hostname and SMTP ports and mail domains (or
307 just single email addresses) of your additional e-mail servers.
310 [[pmgconfig_mailproxy_networks]]
315 image::images/screenshot/pmg-gui-mailproxy-networks.png[]
318 You can add additional internal (trusted) IP networks or hosts.
319 All hosts in this list are allowed to relay.
321 NOTE: Hosts in the same subnet with Proxmox can relay by default and
322 it’s not needed to add them in this list.
325 [[pmgconfig_mailproxy_tls]]
330 image::images/screenshot/pmg-gui-mailproxy-tls.png[]
333 Transport Layer Security (TLS) provides certificate-based
334 authentication and encrypted sessions. An encrypted session protects
335 the information that is transmitted with SMTP mail. When you activate
336 TLS, {pmg} automatically generates a new self signed
337 certificate for you (`/etc/pmg/pmg-tls.pem`).
339 {pmg} uses opportunistic TLS encryption by default. The SMTP transaction is
340 encrypted if the 'STARTTLS' ESMTP feature is supported by the remote
341 server. Otherwise, messages are sent in the clear.
342 You can set a different TLS policy per desitination domain, should you for
343 example need to prevent e-mail delivery without encryption, or to work around
344 a broken 'STARTTLS' ESMTP implementation. See {postfix_tls_readme} for details
345 on the supported policies.
349 To get additional information about SMTP TLS activity you can enable
350 TLS logging. That way information about TLS sessions and used
351 certificate’s is logged via syslog.
353 Add TLS received header::
355 Set this option to include information about the protocol and cipher
356 used as well as the client and issuer CommonName into the "Received:"
359 Those settings are saved to subsection 'mail' in `/etc/pmg/pmg.conf`,
360 using the following configuration keys:
362 include::pmg.mail-tls-conf-opts.adoc[]
369 image::images/screenshot/pmg-gui-mailproxy-whitelist.png[]
372 All SMTP checks are disabled for those entries (e. g. Greylisting,
375 NOTE: If you use a backup MX server (e.g. your ISP offers this service
376 for you) you should always add those servers here.
379 [[pmgconfig_spamdetector]]
380 Spam Detector Configuration
381 ---------------------------
387 image::images/screenshot/pmg-gui-spam-options.png[]
390 {pmg} uses a wide variety of local and network tests to identify spam
391 signatures. This makes it harder for spammers to identify one aspect
392 which they can craft their messages to work around the spam filter.
394 Every single e-mail will be analyzed and gets a spam score
395 assigned. The system attempts to optimize the efficiency of the rules
396 that are run in terms of minimizing the number of false positives and
399 include::pmg.spam-conf-opts.adoc[]
402 [[pmgconfig_spamdetector_quarantine]]
407 image::images/screenshot/pmg-gui-spamquar-options.png[]
410 Proxmox analyses all incoming e-mail messages and decides for each
411 e-mail if its ham or spam (or virus). Good e-mails are delivered to
412 the inbox and spam messages can be moved into the spam quarantine.
414 The system can be configured to send daily reports to inform users
415 about the personal spam messages received the last day. That report is
416 only sent if there are new messages in the quarantine.
418 Some options are only available in the config file `/etc/pmg/pmg.conf`,
419 and not in the webinterface.
421 include::pmg.spamquar-conf-opts.adoc[]
425 Virus Detector Configuration
426 ----------------------------
428 [[pmgconfig_clamav_options]]
433 image::images/screenshot/pmg-gui-virus-options.png[]
436 All mails are automatically passed to the included virus detector
437 ({clamav}). The default setting are considered safe, so it is usually
438 not required to change them.
440 {clamav} related settings are saved to subsection 'clamav' in `/etc/pmg/pmg.conf`,
441 using the following configuration keys:
443 include::pmg.clamav-conf-opts.adoc[]
446 image::images/screenshot/pmg-gui-clamav-database.png[]
449 Please note that the virus signature database it automatically
450 updated. But you can see the database status on the GUI, and you can
451 trigger manual updates there.
454 [[pmgconfig_clamav_quarantine]]
459 image::images/screenshot/pmg-gui-virusquar-options.png[]
462 Indentified virus mails are automatically moved to the virus
463 quarantine. The administartor can view those mails using the GUI, or
464 deliver them in case of false positives. {pmg} does not notify
465 individual users about received virus mails.
467 Virus quarantine related settings are saved to subsection 'virusquar'
468 in `/etc/pmg/pmg.conf`, using the following configuration keys:
470 include::pmg.virusquar-conf-opts.adoc[]
473 Custom SpamAssassin configuration
474 ---------------------------------
476 This is only for advanced users. To add or change the Proxmox
477 {spamassassin} configuration please login to the console via SSH. Go
478 to directory `/etc/mail/spamassassin/`. In this directory there are several
479 files (`init.pre`, `local.cf`, ...) – do not change them.
481 To add your special configuration, you have to create a new file and
482 name it `custom.cf` (in this directory), then add your
483 configuration there. Be aware to use the {spamassassin}
484 syntax, and test with
487 # spamassassin -D --lint
490 If you run a cluster, the `custom.cf` file is synchronized from the
491 master node to all cluster members.
494 [[pmgconfig_custom_check]]
495 Custom Check Interface
496 ----------------------
498 For use cases which are not handled by the {pmg} Virus Detector and
499 {spamassassin} configuration, advanced users can create a custom check
500 executable which, if enabled will be called before the Virus Detector and before
501 passing an e-mail through the Rule System. The custom check API is kept as
502 simple as possible, while still providing a great deal of control over the
503 treatment of an e-mail. Its input is passed via two CLI arguments:
505 * the 'api-version' (currently `v1`) - for potential future change of the
508 * the 'queue-file-name' - a filename, which contains the complete e-mail as
511 The expected output need to be printed on STDOUT and consists of two lines:
513 * the 'api-version' (currently 'v1') - see above
515 * one of the following 3 results:
516 ** 'OK' - e-mail is ok
517 ** 'VIRUS: <virusdescription>' - e-mail is treated as if it contained a virus
518 (the virusdescription is logged and added to the e-mail's headers)
519 ** 'SCORE: <number>' - <number> is added (negative numbers are also possible)
520 to the e-mail's spamscore
522 The check is run with a 5 minute timeout - if it is exceeded the check
523 executable is killed and the e-mail is treated as OK.
525 All output written to STDERR by the check is written with priority 'err' to the
528 A simple sample script following the API (and yielding a random result) for
534 echo "called with $*" 1>&2
536 if [ "$#" -ne 2 ]; then
537 echo "usage: $0 APIVERSION QUEUEFILENAME" 1>&2
544 if [ "$apiver" != "v1" ]; then
545 echo "wrong APIVERSION: $apiver" 1>&2
553 choice=$(shuf -i 0-3 -n1)
563 echo VIRUS: Random Virus
566 for i in $(seq 1 7); do
567 echo "custom checking mail: $queue_file - minute $i" 1>&2
576 The custom check needs to be enabled in the admin section of `/etc/pmg/pmg.conf`
583 The location of the custom check executable can also be set there with the key
584 `custom_check_path` and defaults to `/usr/local/bin/pmg-custom-check`.
590 User management in {pmg} consists of three types of users/accounts:
593 [[pmgconfig_localuser]]
597 image::images/screenshot/pmg-gui-local-user-config.png[]
599 Local users are used to manage and audit {pmg}. Those users can login on the
600 management web interface.
602 There are three roles:
606 Is allowed to manage settings of {pmg}, except some tasks like
607 network configuration and upgrading.
611 Is allowed to manage quarantines, blacklists and whitelists, but not other
612 settings. Has no right to view any other data.
616 With this role, the user is only allowed to view data and configuration, but
619 In addition there is always the 'root' user, which is used to perform special
620 system administrator tasks, such as updgrading a host or changing the
621 network configuration.
623 NOTE: Only pam users are able to login via the webconsole and ssh, which the
624 users created with the web interface are not. Those users are created for
625 {pmg} administration only.
627 Local user related settings are saved in `/etc/pmg/user.conf`.
629 For details of the fields see xref:pmg_user_configuration_file[user.conf]
632 LDAP/Active Directory
633 ~~~~~~~~~~~~~~~~~~~~~
635 image::images/screenshot/pmg-gui-ldap-user-config.png[]
637 You can specify multiple LDAP/Active Directory profiles, so that you can
638 create rules matching those users and groups.
640 Creating a profile requires (at least) the following:
643 * protocol (LDAP or LDAPS; LDAPS is recommended)
644 * at least one server
645 * a user and password (if your server does not support anonymous binds)
647 All other fields should work with the defaults for most setups, but can be
648 used to customize the queries.
650 The settings are saved to `/etc/pmg/ldap.conf`. Details for the options
651 can be found here: xref:pmg_ldap_configuration_file[ldap.conf]
656 It is highly recommended that the user which you use for connecting to the
657 LDAP server only has the permission to query the server. For LDAP servers
658 (for example OpenLDAP or FreeIPA), the username has to be of a format like
659 'uid=username,cn=users,cn=accounts,dc=domain' , where the specific fields are
660 depending on your setup. For Active Directory servers, the format should be
661 like 'username@domain' or 'domain\username'.
666 {pmg} synchronizes the relevant user and group info periodically, so that
667 that information is available in a fast manner, even when the LDAP/AD server
668 is temporarily not accessible.
670 After a successfull sync, the groups and users should be visible on the web
671 interface. After that, you can create rules targeting LDAP users and groups.
674 [[pmgconfig_fetchmail]]
678 image::images/screenshot/pmg-gui-fetchmail-config.png[]
680 Fetchmail is utility for polling and forwarding e-mails. You can define
681 e-mail accounts, which will then be fetched and forwarded to the e-mail
684 You have to add an entry for each account/target combination you want to
685 fetch and forward. Those will then be regularly polled and forwarded,
686 according to your configuration.
688 The API and web interface offer following configuration options:
690 include::fetchmail.conf.5-opts.adoc[]
694 include::pmg-copyright.adoc[]