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/transports`::
94 Message delivery transport setup.
96 `/etc/pmg/user.conf`::
98 GUI user configuration.
101 Keys and Certificates
102 ---------------------
104 `/etc/pmg/pmg-api.pem`::
106 Key and certificate (combined) used be the HTTPs server (API).
108 `/etc/pmg/pmg-authkey.key`::
110 Privat key use to generate authentication tickets.
112 `/etc/pmg/pmg-authkey.pub`::
114 Public key use to verify authentication tickets.
116 `/etc/pmg/pmg-csrf.key`::
118 Internally used to generate CSRF tokens.
120 `/etc/pmg/pmg-tls.pem`::
122 Key and certificate (combined) to encrypt mail traffic (TLS).
125 Service Configuration Templates
126 -------------------------------
128 {pmg} uses various services to implement mail filtering, for example
129 the {postfix} Mail Transport Agent (MTA), the {clamav} antivirus
130 engine and the Apache {spamassassin} project. Those services use
131 separate configuration files, so we need to rewrite those files when
132 configuration is changed.
134 We use a template based approach to generate those files. The {tts} is
135 a well known, fast and flexible template processing system. You can
136 find the default templates in `/var/lib/pmg/templates/`. Please do not
137 modify them directly, because your modification would get lost on the
138 next update. Instead, copy them to `/etc/pmg/templates/`, then apply
141 Templates can access any configuration setting, and you can use the
142 `pmgconfig dump` command to get a list of all variable names:
147 dns.domain = yourdomain.tld
149 ipconfig.int_ip = 192.168.2.127
150 pmg.admin.advfilter = 1
154 The same tool is used to force regeneration of all template based
155 configuration files. You need to run that after modifying a template,
156 or when you directly edit configuration files
159 # pmgconfig sync --restart 1
162 Above commands also restarts services if underlying configuration
163 files are changed. Please note that this is automatically done when
164 you change the configuration using the GUI or API.
166 NOTE: Modified templates from `/etc/pmg/templates/` are automatically
167 synced from the master node to all cluster members.
177 image::images/screenshot/pmg-gui-network-config.png[]
180 Normally the network and time is already configured when you visit the
181 GUI. The installer asks for those setting and sets up the correct
184 The default setup uses a single Ethernet adapter and static IP
185 assignment. The configuration is stored at '/etc/network/interfaces',
186 and the actual network setup is done the standard Debian way using
189 .Example network setup '/etc/network/interfaces'
191 source /etc/network/interfaces.d/*
194 iface lo inet loopback
197 iface ens18 inet static
198 address 192.168.2.127
199 netmask 255.255.240.0
205 Many tests to detect SPAM mails use DNS queries, so it is important to
206 have a fast and reliable DNS server. We also query some public
207 available DNS Blacklists. Most of them apply rate limits for clients,
208 so they simply will not work if you use a public DNS server (because
209 they are usually blocked). We recommend to use your own DNS server,
210 which need to be configured in 'recursive' mode.
217 image::images/screenshot/pmg-gui-system-options.png[]
220 include::pmg.admin-conf-opts.adoc[]
227 image::images/screenshot/pmg-gui-backup.png[]
235 include::pmg-copyright.adoc[]