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.
100 `/etc/mail/spamassassin/custom.cf`::
102 Custom {spamassassin} setup.
105 Keys and Certificates
106 ---------------------
108 `/etc/pmg/pmg-api.pem`::
110 Key and certificate (combined) used be the HTTPs server (API).
112 `/etc/pmg/pmg-authkey.key`::
114 Privat key use to generate authentication tickets.
116 `/etc/pmg/pmg-authkey.pub`::
118 Public key use to verify authentication tickets.
120 `/etc/pmg/pmg-csrf.key`::
122 Internally used to generate CSRF tokens.
124 `/etc/pmg/pmg-tls.pem`::
126 Key and certificate (combined) to encrypt mail traffic (TLS).
129 Service Configuration Templates
130 -------------------------------
132 {pmg} uses various services to implement mail filtering, for example
133 the {postfix} Mail Transport Agent (MTA), the {clamav} antivirus
134 engine and the Apache {spamassassin} project. Those services use
135 separate configuration files, so we need to rewrite those files when
136 configuration is changed.
138 We use a template based approach to generate those files. The {tts} is
139 a well known, fast and flexible template processing system. You can
140 find the default templates in `/var/lib/pmg/templates/`. Please do not
141 modify them directly, because your modification would get lost on the
142 next update. Instead, copy them to `/etc/pmg/templates/`, then apply
145 Templates can access any configuration setting, and you can use the
146 `pmgconfig dump` command to get a list of all variable names:
151 dns.domain = yourdomain.tld
153 ipconfig.int_ip = 192.168.2.127
154 pmg.admin.advfilter = 1
158 The same tool is used to force regeneration of all template based
159 configuration files. You need to run that after modifying a template,
160 or when you directly edit configuration files
163 # pmgconfig sync --restart 1
166 Above commands also restarts services if underlying configuration
167 files are changed. Please note that this is automatically done when
168 you change the configuration using the GUI or API.
170 NOTE: Modified templates from `/etc/pmg/templates/` are automatically
171 synced from the master node to all cluster members.
181 image::images/screenshot/pmg-gui-network-config.png[]
184 Normally the network and time is already configured when you visit the
185 GUI. The installer asks for those setting and sets up the correct
188 The default setup uses a single Ethernet adapter and static IP
189 assignment. The configuration is stored at '/etc/network/interfaces',
190 and the actual network setup is done the standard Debian way using
193 .Example network setup '/etc/network/interfaces'
195 source /etc/network/interfaces.d/*
198 iface lo inet loopback
201 iface ens18 inet static
202 address 192.168.2.127
203 netmask 255.255.240.0
209 Many tests to detect SPAM mails use DNS queries, so it is important to
210 have a fast and reliable DNS server. We also query some public
211 available DNS Blacklists. Most of them apply rate limits for clients,
212 so they simply will not work if you use a public DNS server (because
213 they are usually blocked). We recommend to use your own DNS server,
214 which need to be configured in 'recursive' mode.
221 image::images/screenshot/pmg-gui-system-options.png[]
225 Those settings are saved to subsection 'admin' in `/etc/pmg/pmg.conf`,
226 using the following configuration keys:
228 include::pmg.admin-conf-opts.adoc[]
231 Mail Proxy Configuration
232 ------------------------
238 image::images/screenshot/pmg-gui-mailproxy-relaying.png[]
241 Those settings are saved to subsection 'mail' in `/etc/pmg/pmg.conf`,
242 using the following configuration keys:
244 include::pmg.mail-relaying-conf-opts.adoc[]
251 image::images/screenshot/pmg-gui-mailproxy-relaydomains.png[]
261 image::images/screenshot/pmg-gui-mailproxy-ports.png[]
264 Those settings are saved to subsection 'mail' in `/etc/pmg/pmg.conf`,
265 using the following configuration keys:
267 include::pmg.mail-ports-conf-opts.adoc[]
275 image::images/screenshot/pmg-gui-mailproxy-options.png[]
285 image::images/screenshot/pmg-gui-mailproxy-transports.png[]
295 image::images/screenshot/pmg-gui-mailproxy-networks.png[]
305 image::images/screenshot/pmg-gui-mailproxy-tls.png[]
314 image::images/screenshot/pmg-gui-mailproxy-whitelist.png[]
320 Spam Detector Configuration
321 ---------------------------
326 Virus Detector Configuration
327 ----------------------------
339 include::pmg-copyright.adoc[]