]>
Commit | Line | Data |
---|---|---|
e62ceaf0 DM |
1 | [[chapter_pmgconfig]] |
2 | ifdef::manvolnum[] | |
3 | pmgconfig(1) | |
4 | ============ | |
5 | :pmg-toplevel: | |
6 | ||
7 | NAME | |
8 | ---- | |
9 | ||
10 | pmgconfig - Proxmox Mail Gateway Configuration Management Toolkit | |
11 | ||
12 | ||
13 | SYNOPSIS | |
14 | -------- | |
15 | ||
16 | include::pmgconfig.1-synopsis.adoc[] | |
17 | ||
18 | ||
19 | DESCRIPTION | |
20 | ----------- | |
21 | endif::manvolnum[] | |
22 | ifndef::manvolnum[] | |
66e9c719 DM |
23 | Configuration Management |
24 | ======================== | |
e62ceaf0 DM |
25 | :pmg-toplevel: |
26 | endif::manvolnum[] | |
27 | ||
a4f14219 TL |
28 | {pmg} is usually configured using the web-based Graphical User Interface (GUI), |
29 | but it is also possible to directly edit the configuration files, using the | |
db96e742 | 30 | REST API over 'https' or the command-line tool `pmgsh`. |
685576c2 | 31 | |
db96e742 | 32 | The command-line tool `pmgconfig` is used to simplify some common configuration |
a4f14219 TL |
33 | tasks, such as generating certificates and rewriting service configuration |
34 | files. | |
685576c2 | 35 | |
a4f14219 TL |
36 | NOTE: We use a Postgres database to store mail filter rules and statistical |
37 | data. See chapter xref:chapter_pmgdb[Database Management] for more information. | |
66e9c719 DM |
38 | |
39 | ||
40 | Configuration files overview | |
41 | ---------------------------- | |
42 | ||
43 | `/etc/network/interfaces`:: | |
44 | ||
3f18659b | 45 | Network setup. We never modify this file directly. Instead, we write |
eb269701 DW |
46 | changes to `/etc/network/interfaces.new`. When you reboot, {pmg} renames |
47 | the file to `/etc/network/interfaces`, thus applying the changes. | |
66e9c719 | 48 | |
9bfe27f3 DM |
49 | `/etc/resolv.conf`:: |
50 | ||
fa483193 SI |
51 | DNS search domain and nameserver setup. {pmg} uses the search domain setting |
52 | to create the FQDN and domain name used in the postfix configuration. | |
9bfe27f3 DM |
53 | |
54 | `/etc/hostname`:: | |
55 | ||
eb269701 | 56 | The system's hostname. {pmg} uses the hostname to create the FQDN used |
fa483193 | 57 | in the postfix configuration. |
9bfe27f3 DM |
58 | |
59 | `/etc/hosts`:: | |
60 | ||
61 | Static table lookup for hostnames. | |
62 | ||
66e9c719 DM |
63 | `/etc/pmg/pmg.conf`:: |
64 | ||
eb269701 DW |
65 | Stores common administration options, such as the spam and mail proxy |
66 | configuration. | |
66e9c719 DM |
67 | |
68 | `/etc/pmg/cluster.conf`:: | |
69 | ||
70 | The cluster setup. | |
71 | ||
72 | `/etc/pmg/domains`:: | |
73 | ||
74 | The list of relay domains. | |
75 | ||
5053eecc SI |
76 | `/etc/pmg/dkim/domains`:: |
77 | ||
78 | The list of domains for outbound DKIM signing. | |
79 | ||
66e9c719 DM |
80 | `/etc/pmg/fetchmailrc`:: |
81 | ||
82 | Fetchmail configuration (POP3 and IMAP setup). | |
83 | ||
84 | `/etc/pmg/ldap.conf`:: | |
85 | ||
86 | LDAP configuration. | |
87 | ||
88 | `/etc/pmg/mynetworks`:: | |
89 | ||
90 | List of local (trusted) networks. | |
91 | ||
92 | `/etc/pmg/subscription`:: | |
93 | ||
94 | Stores your subscription key and status. | |
95 | ||
37b2b051 SI |
96 | `/etc/pmg/tls_policy`:: |
97 | ||
98 | TLS policy for outbound connections. | |
99 | ||
374bcb5f CH |
100 | `/etc/pmg/tls_inbound_domains`:: |
101 | ||
102 | Sender domains for which TLS is enforced on inbound connections. | |
103 | ||
f43c6983 | 104 | `/etc/pmg/transport`:: |
66e9c719 DM |
105 | |
106 | Message delivery transport setup. | |
107 | ||
108 | `/etc/pmg/user.conf`:: | |
109 | ||
110 | GUI user configuration. | |
111 | ||
797db11d DM |
112 | `/etc/mail/spamassassin/custom.cf`:: |
113 | ||
114 | Custom {spamassassin} setup. | |
115 | ||
8b4756e5 SI |
116 | `/etc/mail/spamassassin/pmg-scores.cf`:: |
117 | ||
118 | Custom {spamassassin} rule scores. | |
66e9c719 DM |
119 | |
120 | Keys and Certificates | |
121 | --------------------- | |
122 | ||
123 | `/etc/pmg/pmg-api.pem`:: | |
124 | ||
eb269701 | 125 | Key and certificate (combined) used by the HTTPS server (API). |
66e9c719 DM |
126 | |
127 | `/etc/pmg/pmg-authkey.key`:: | |
128 | ||
eb269701 | 129 | Private key used to generate authentication tickets. |
66e9c719 DM |
130 | |
131 | `/etc/pmg/pmg-authkey.pub`:: | |
132 | ||
eb269701 | 133 | Public key used to verify authentication tickets. |
66e9c719 DM |
134 | |
135 | `/etc/pmg/pmg-csrf.key`:: | |
136 | ||
137 | Internally used to generate CSRF tokens. | |
138 | ||
139 | `/etc/pmg/pmg-tls.pem`:: | |
140 | ||
141 | Key and certificate (combined) to encrypt mail traffic (TLS). | |
142 | ||
5053eecc SI |
143 | `/etc/pmg/dkim/<selector>.private`:: |
144 | ||
145 | Key for DKIM signing mails with selector '<selector>'. | |
146 | ||
66e9c719 | 147 | |
69a428d9 | 148 | [[pmgconfig_template_engine]] |
66e9c719 DM |
149 | Service Configuration Templates |
150 | ------------------------------- | |
151 | ||
eb269701 | 152 | {pmg} uses various services to implement mail filtering, for example, |
9c85cc80 | 153 | the {postfix} Mail Transport Agent (MTA), the {clamav} antivirus |
eb269701 DW |
154 | engine, and the Apache {spamassassin} project. These services use |
155 | separate configuration files, so we need to rewrite those files when the | |
9c85cc80 DM |
156 | configuration is changed. |
157 | ||
eb269701 | 158 | We use a template-based approach to generate these files. The {tts} is |
9c85cc80 DM |
159 | a well known, fast and flexible template processing system. You can |
160 | find the default templates in `/var/lib/pmg/templates/`. Please do not | |
eb269701 | 161 | modify these directly, otherwise your modifications will be lost on the |
9dd45bd7 SI |
162 | next update. Instead, copy the template you wish to change to |
163 | `/etc/pmg/templates/`, then apply your changes there. | |
9c85cc80 | 164 | |
eb269701 | 165 | Templates can access any configuration settings, and you can use the |
9c85cc80 DM |
166 | `pmgconfig dump` command to get a list of all variable names: |
167 | ||
168 | ---- | |
169 | # pmgconfig dump | |
170 | ... | |
171 | dns.domain = yourdomain.tld | |
172 | dns.hostname = pmg | |
173 | ipconfig.int_ip = 192.168.2.127 | |
174 | pmg.admin.advfilter = 1 | |
175 | ... | |
176 | ---- | |
177 | ||
eb269701 DW |
178 | The same tool is used to force the regeneration of all template-based |
179 | configuration files. You need to run the following after modifying a template, | |
180 | or when you directly edit configuration files: | |
9c85cc80 DM |
181 | |
182 | ---- | |
183 | # pmgconfig sync --restart 1 | |
184 | ---- | |
185 | ||
9dd45bd7 | 186 | The above command also restarts services if the underlying configuration |
9c85cc80 DM |
187 | files are changed. Please note that this is automatically done when |
188 | you change the configuration using the GUI or API. | |
189 | ||
190 | NOTE: Modified templates from `/etc/pmg/templates/` are automatically | |
191 | synced from the master node to all cluster members. | |
66e9c719 | 192 | |
7e7126d6 ML |
193 | [[pmgconfig_whitelist_overview]] |
194 | White- and Blacklists | |
195 | --------------------- | |
196 | ||
eb269701 DW |
197 | {pmg} has multiple white- and blacklists. It differentiates between the |
198 | xref:pmgconfig_mailproxy_options[SMTP Whitelist], the rule-based whitelist | |
7e7126d6 | 199 | and the user whitelist. |
eb269701 | 200 | In addition to the whitelists, there are two separate blacklists: the rule-based |
7e7126d6 ML |
201 | blacklist and the user blacklist. |
202 | ||
203 | SMTP Whitelist | |
204 | ~~~~~~~~~~~~~~ | |
205 | ||
61b59f73 | 206 | The xref:pmgconfig_mailproxy_whitelist[SMTP Whitelist] is responsible for disabling |
eb269701 | 207 | greylisting, as well as SPF and DNSBL checks. These are done during the SMTP |
7e7126d6 ML |
208 | dialogue. |
209 | ||
210 | Rule-based White-/Blacklist | |
211 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
212 | ||
213 | The xref:chapter_mailfilter[rule-based white- and blacklists] are predefined | |
eb269701 DW |
214 | rules. They work by checking the attached 'Who' objects, containing, for |
215 | example, a domain or a mail address for a match. If it matches, the assigned | |
216 | action is used, which by default is 'Accept' for the whitelist rule and 'Block' | |
217 | for the blacklist rule. In the default setup, the blacklist rule has priority | |
218 | over the whitelist rule and spam checks. | |
7e7126d6 ML |
219 | |
220 | User White-/Blacklist | |
221 | ~~~~~~~~~~~~~~~~~~~~~ | |
222 | ||
223 | The user white- and blacklist are user specific. Every user can add mail addresses | |
224 | to their white- and blacklist. When a user adds a mail address to the whitelist, | |
225 | the result of the spam analysis will be discarded for that recipient. This can | |
eb269701 DW |
226 | help in the mail being accepted, but what happens next still depends on the |
227 | other rules. In the default setup, this results in the mail being accepted for | |
7e7126d6 ML |
228 | this recipient. |
229 | ||
eb269701 DW |
230 | For mail addresses on a user's blacklist, the spam score will be increased by |
231 | 100. What happens when a high spam score is encountered still depends on the | |
232 | rule system. In the default setup, it will be recognized as spam and quarantined | |
7e7126d6 | 233 | (spam score of 3 or higher). |
66e9c719 | 234 | |
4a08dffe | 235 | [[pmgconfig_systemconfig]] |
685576c2 DM |
236 | System Configuration |
237 | -------------------- | |
238 | ||
239 | Network and Time | |
240 | ~~~~~~~~~~~~~~~~ | |
241 | ||
242 | ifndef::manvolnum[] | |
38d14519 | 243 | [thumbnail="screenshot/pmg-gui-network-config.png", big=1] |
685576c2 DM |
244 | endif::manvolnum[] |
245 | ||
eb269701 DW |
246 | As network and time are configured in the installer, these generally do not |
247 | need to be configured again in the GUI. | |
45de5bf5 DM |
248 | |
249 | The default setup uses a single Ethernet adapter and static IP | |
250 | assignment. The configuration is stored at '/etc/network/interfaces', | |
eb269701 | 251 | and the actual network setup is done the standard Debian way, using the |
45de5bf5 DM |
252 | package 'ifupdown'. |
253 | ||
254 | .Example network setup '/etc/network/interfaces' | |
255 | ---- | |
256 | source /etc/network/interfaces.d/* | |
257 | ||
258 | auto lo | |
259 | iface lo inet loopback | |
260 | ||
261 | auto ens18 | |
262 | iface ens18 inet static | |
263 | address 192.168.2.127 | |
264 | netmask 255.255.240.0 | |
265 | gateway 192.168.2.1 | |
266 | ---- | |
267 | ||
268 | .DNS recommendations | |
269 | ||
270 | Many tests to detect SPAM mails use DNS queries, so it is important to | |
3f18659b | 271 | have a fast and reliable DNS server. We also query some publicly |
45de5bf5 DM |
272 | available DNS Blacklists. Most of them apply rate limits for clients, |
273 | so they simply will not work if you use a public DNS server (because | |
274 | they are usually blocked). We recommend to use your own DNS server, | |
3f18659b | 275 | which needs to be configured in 'recursive' mode. |
685576c2 DM |
276 | |
277 | ||
278 | Options | |
279 | ~~~~~~~ | |
280 | ||
281 | ifndef::manvolnum[] | |
38d14519 | 282 | [thumbnail="screenshot/pmg-gui-system-options.png", big=1] |
685576c2 DM |
283 | endif::manvolnum[] |
284 | ||
e09057ab | 285 | |
eb269701 | 286 | These settings are saved to the 'admin' subsection in `/etc/pmg/pmg.conf`, |
e09057ab DM |
287 | using the following configuration keys: |
288 | ||
685576c2 DM |
289 | include::pmg.admin-conf-opts.adoc[] |
290 | ||
c331641e | 291 | |
8c889e95 TL |
292 | include::pmg-ssl-certificate.adoc[] |
293 | ||
c331641e DM |
294 | Mail Proxy Configuration |
295 | ------------------------ | |
296 | ||
4a08dffe | 297 | [[pmgconfig_mailproxy_relaying]] |
c331641e DM |
298 | Relaying |
299 | ~~~~~~~~ | |
300 | ||
c331641e | 301 | ifndef::manvolnum[] |
38d14519 | 302 | [thumbnail="screenshot/pmg-gui-mailproxy-relaying.png", big=1] |
c331641e DM |
303 | endif::manvolnum[] |
304 | ||
782f24f4 DC |
305 | These settings are saved to the 'mail' subsection in `/etc/pmg/pmg.conf`. Some of these correspond |
306 | to postfix options in the `main.cf` (see the | |
307 | https://www.postfix.org/postconf.5.html[postconf documentation]). | |
308 | ||
309 | They use the following configuration keys: | |
e09057ab DM |
310 | |
311 | include::pmg.mail-relaying-conf-opts.adoc[] | |
c331641e | 312 | |
4a08dffe | 313 | [[pmgconfig_mailproxy_relay_domains]] |
c331641e DM |
314 | Relay Domains |
315 | ~~~~~~~~~~~~~ | |
316 | ||
c331641e | 317 | ifndef::manvolnum[] |
38d14519 | 318 | [thumbnail="screenshot/pmg-gui-mailproxy-relaydomains.png", big=1] |
c331641e DM |
319 | endif::manvolnum[] |
320 | ||
eb269701 | 321 | A list of relayed mail domains, that is, what destination domains this |
6822b369 DM |
322 | system will relay mail to. The system will reject incoming mails to |
323 | other domains. | |
c331641e | 324 | |
d9c56b22 | 325 | |
4a08dffe | 326 | [[pmgconfig_mailproxy_ports]] |
c331641e DM |
327 | Ports |
328 | ~~~~~ | |
329 | ||
c331641e | 330 | ifndef::manvolnum[] |
38d14519 | 331 | [thumbnail="screenshot/pmg-gui-mailproxy-ports.png", big=1] |
c331641e DM |
332 | endif::manvolnum[] |
333 | ||
782f24f4 DC |
334 | These settings are saved to the 'mail' subsection in `/etc/pmg/pmg.conf`. Many of these correspond |
335 | to postfix options in the `main.cf` (see the | |
336 | https://www.postfix.org/postconf.5.html[postconf documentation]). | |
337 | ||
338 | They use the following configuration keys: | |
d9c56b22 DM |
339 | |
340 | include::pmg.mail-ports-conf-opts.adoc[] | |
341 | ||
c331641e | 342 | |
4a08dffe | 343 | [[pmgconfig_mailproxy_options]] |
c331641e DM |
344 | Options |
345 | ~~~~~~~ | |
346 | ||
c331641e | 347 | ifndef::manvolnum[] |
38d14519 | 348 | [thumbnail="screenshot/pmg-gui-mailproxy-options.png", big=1] |
c331641e DM |
349 | endif::manvolnum[] |
350 | ||
eb269701 | 351 | These settings are saved to the 'mail' subsection in `/etc/pmg/pmg.conf`, |
e3d778e0 DM |
352 | using the following configuration keys: |
353 | ||
354 | include::pmg.mail-options-conf-opts.adoc[] | |
c331641e DM |
355 | |
356 | ||
89028579 SI |
357 | [[pmgconfig_mailproxy_before_after_queue]] |
358 | Before and After Queue scanning | |
359 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
360 | ||
eb269701 | 361 | Email scanning can happen at two different stages of mail-processing: |
89028579 | 362 | |
eb269701 | 363 | * Before-queue filtering: During the SMTP session, after the complete message |
1824eab9 | 364 | has been received (after the 'DATA' command). |
89028579 | 365 | |
1824eab9 SI |
366 | * After-queue filtering: After initially accepting the mail and putting it on |
367 | a queue for further processing. | |
89028579 | 368 | |
1824eab9 SI |
369 | Before-queue filtering has the advantage that the system can reject a mail (by |
370 | sending a permanent reject code '554'), and leave the task of notifying the | |
eb269701 | 371 | original sender to the other mail server. This is of particular advantage if |
1824eab9 | 372 | the processed mail is a spam message or contains a virus and has a forged |
eb269701 | 373 | sender address. Sending out a notification in this situation leads to so-called |
89028579 | 374 | 'backscatter' mail, which might cause your server to get listed as spamming on |
3f18659b | 375 | RBLs (Real-time Blackhole List). |
89028579 | 376 | |
1824eab9 | 377 | After-queue filtering has the advantage of providing faster delivery of |
eb269701 DW |
378 | mails for the sending servers, since queuing emails is much faster than |
379 | analyzing them for spam and viruses. | |
380 | ||
381 | If a mail is addressed to multiple recipients (for example, when multiple | |
382 | addresses are subscribed to the same mailing list), the situation is more | |
383 | complicated; your mail server can only reject or accept the mail for all | |
384 | recipients, after having received the complete message, while your rule setup | |
385 | might accept the mail for part of the recipients and reject it for others. This | |
386 | can be due to a complicated rule setup, or if your users use the 'User White- | |
387 | and Blacklist' feature. | |
388 | ||
389 | If the resulting action of the rule system is the same for all recipients, {pmg} | |
390 | responds accordingly, if configured for before-queue filtering (sending '554' | |
89028579 | 391 | for a blocked mail and '250' for an accepted or quarantined mail). If some |
3f18659b | 392 | mailboxes accept the mail and some reject it, the system has to accept the mail. |
89028579 SI |
393 | |
394 | Whether {pmg} notifies the sender that delivery failed for some recipients by | |
395 | sending a non-delivery report, depends on the 'ndr_on_block' setting in | |
eb269701 | 396 | '/etc/pmg/pmg.conf'. If enabled, an NDR is sent. Keeping this disabled prevents |
89028579 | 397 | NDRs being sent to the (possibly forged) sender and thus minimizes the chance |
eb269701 | 398 | of getting your IP listed on an RBL. However in certain environments, it can be |
89028579 SI |
399 | unacceptable not to inform the sender about a rejected mail. |
400 | ||
eb269701 | 401 | The setting has the same effect if after-queue filtering is configured, with |
89028579 SI |
402 | the exception that an NDR is always sent out, even if all recipients block the |
403 | mail, since the mail already got accepted before being analyzed. | |
404 | ||
405 | The details of integrating the mail proxy with {postfix} in both setups are | |
406 | explained in {postfix_beforequeue} and {postfix_afterqueue} respectively. | |
407 | ||
89028579 | 408 | |
d41aa039 SI |
409 | [[pmgconfig_mailproxy_greylisting]] |
410 | Greylisting | |
411 | ~~~~~~~~~~~ | |
412 | ||
413 | Greylisting is a technique for preventing unwanted messages from reaching the | |
414 | resource intensive stages of content analysis (virus detection and spam | |
eb269701 DW |
415 | detection). By initially replying with a temporary failure code ('450') to |
416 | each new email, {pmg} tells the sending server that it should queue the | |
417 | mail and retry delivery at a later point. Since certain kinds of spam get | |
418 | sent out by software which has no provisioning for queuing, these mails are | |
d41aa039 SI |
419 | dropped without reaching {pmg} or your mailbox. |
420 | ||
421 | The downside of greylisting is the delay introduced by the initial deferral of | |
422 | the email, which usually amounts to less than 30 minutes. | |
423 | ||
424 | In order to prevent unnecessary delays in delivery from known sources, emails | |
425 | coming from a source for a recipient, which have passed greylisting in the | |
426 | past are directly passed on: For each email the triple '<sender network, | |
427 | sender email, recipient email>' is stored in a list, along with the time when | |
428 | delivery was attempted. If an email fits an already existing triple, the | |
eb269701 | 429 | timestamp for that triple is updated, and the email is accepted for further |
d41aa039 SI |
430 | processing. |
431 | ||
eb269701 | 432 | As long as a sender and recipient communicate frequently, there is no delay |
d41aa039 | 433 | introduced by enabling greylisting. A triple is removed after a longer period |
eb269701 | 434 | of time, if no mail fitting that triple has been seen. The timeouts in {pmg} |
d41aa039 SI |
435 | are: |
436 | ||
437 | * 2 days for the retry of the first delivery | |
438 | ||
eb269701 | 439 | * 36 days for a known triple |
d41aa039 | 440 | |
eb269701 | 441 | Mails with an empty envelope sender are always delayed. |
d41aa039 SI |
442 | |
443 | Some email service providers send out emails for one domain from multiple | |
eb269701 DW |
444 | servers. To prevent delays due to an email coming in from two separate IPs of |
445 | the same provider, the triples store a network ('cidr') instead of a single IP. | |
446 | For certain large providers, the default network size might be too small. You | |
d41aa039 SI |
447 | can configure the netmask applied to an IP for the greylist lookup in |
448 | '/etc/pmg/pmg.conf' or in the GUI with the settings 'greylistmask' for IPv4 | |
449 | and 'greylistmask6' for IPv6 respectively. | |
450 | ||
451 | ||
4a08dffe | 452 | [[pmgconfig_mailproxy_transports]] |
c331641e DM |
453 | Transports |
454 | ~~~~~~~~~~ | |
455 | ||
456 | ifndef::manvolnum[] | |
38d14519 | 457 | [thumbnail="screenshot/pmg-gui-mailproxy-transports.png", big=1] |
c331641e DM |
458 | endif::manvolnum[] |
459 | ||
3599cb04 | 460 | You can use {pmg} to send emails to different internal email servers. For |
eb269701 | 461 | example, you can send emails addressed to domain.com to your first email server |
3599cb04 | 462 | and emails addressed to subdomain.domain.com to a second one. |
b335e06b | 463 | |
31259590 | 464 | You can add the IP addresses, hostname, transport protocol (smtp/lmtp), |
3599cb04 TL |
465 | transport ports and mail domains (or just single email addresses) of your |
466 | additional email servers. When transport protocol is set to `lmtp`, the option | |
eb269701 | 467 | 'Use MX' is useless and will automatically be set to 'No'. |
c331641e DM |
468 | |
469 | ||
4a08dffe | 470 | [[pmgconfig_mailproxy_networks]] |
c331641e DM |
471 | Networks |
472 | ~~~~~~~~ | |
473 | ||
474 | ifndef::manvolnum[] | |
38d14519 | 475 | [thumbnail="screenshot/pmg-gui-mailproxy-networks.png", big=1] |
c331641e DM |
476 | endif::manvolnum[] |
477 | ||
3599cb04 TL |
478 | You can add additional internal (trusted) IP networks or hosts. All hosts in |
479 | this list are allowed to relay. | |
20e879ad | 480 | |
eb269701 DW |
481 | NOTE: Hosts in the same subnet as {pmg} can relay by default and don't need to |
482 | be added to this list. | |
c331641e DM |
483 | |
484 | ||
4a08dffe | 485 | [[pmgconfig_mailproxy_tls]] |
c331641e DM |
486 | TLS |
487 | ~~~ | |
488 | ||
489 | ifndef::manvolnum[] | |
38d14519 | 490 | [thumbnail="screenshot/pmg-gui-mailproxy-tls.png", big=1] |
c331641e DM |
491 | endif::manvolnum[] |
492 | ||
3599cb04 TL |
493 | Transport Layer Security (TLS) provides certificate-based authentication and |
494 | encrypted sessions. An encrypted session protects the information that is | |
495 | transmitted with SMTP mail. When you activate TLS, {pmg} automatically | |
496 | generates a new self signed certificate for you (`/etc/pmg/pmg-tls.pem`). | |
20e879ad | 497 | |
37b2b051 | 498 | {pmg} uses opportunistic TLS encryption by default. The SMTP transaction is |
20e879ad | 499 | encrypted if the 'STARTTLS' ESMTP feature is supported by the remote |
eb269701 | 500 | server. Otherwise, messages are sent unencrypted. |
91d501f6 SI |
501 | |
502 | You can set a different TLS policy per destination. A destination is either a | |
eb269701 | 503 | remote domain or a next-hop destination, as specified in `/etc/pmg/transport`. |
3f18659b | 504 | This can be used if you need to prevent email delivery without |
91d501f6 SI |
505 | encryption, or to work around a broken 'STARTTLS' ESMTP implementation. See |
506 | {postfix_tls_readme} for details on the supported policies. | |
20e879ad | 507 | |
374bcb5f CH |
508 | Additionally, TLS can also be enforced on incoming connections on the external |
509 | port for specific sender domains by creating a TLS inbound domains entry. Mails | |
510 | with matching domains must use a encrypted SMTP session, otherwise they are | |
511 | rejected. All domains on this list have and entry of | |
512 | https://www.postfix.org/postconf.5.html#reject_plaintext_session[`reject_plaintext_session`] | |
513 | in a `check_sender_access` table. | |
514 | ||
20e879ad DM |
515 | Enable TLS logging:: |
516 | ||
eb269701 DW |
517 | To get additional information about SMTP TLS activity, you can enable |
518 | TLS logging. In this case, information about TLS sessions and used | |
3f18659b | 519 | certificates is logged via syslog. |
20e879ad DM |
520 | |
521 | Add TLS received header:: | |
522 | ||
523 | Set this option to include information about the protocol and cipher | |
eb269701 | 524 | used, as well as the client and issuer CommonName into the "Received:" |
20e879ad DM |
525 | message header. |
526 | ||
a649b38f DM |
527 | Those settings are saved to subsection 'mail' in `/etc/pmg/pmg.conf`, |
528 | using the following configuration keys: | |
529 | ||
530 | include::pmg.mail-tls-conf-opts.adoc[] | |
531 | ||
c331641e | 532 | |
20522d96 SI |
533 | [[pmgconfig_mailproxy_dkim]] |
534 | DKIM Signing | |
535 | ~~~~~~~~~~~~ | |
536 | ||
f5fddbff | 537 | ifndef::manvolnum[] |
38d14519 | 538 | [thumbnail="screenshot/pmg-gui-mailproxy-dkim.png", big=1] |
f5fddbff SI |
539 | endif::manvolnum[] |
540 | ||
20522d96 SI |
541 | DomainKeys Identified Mail (DKIM) Signatures (see {dkim_rfc}) is a method to |
542 | cryptographically authenticate a mail as originating from a particular domain. | |
eb269701 | 543 | Before sending the mail, a hash over certain header fields and the body is |
20522d96 SI |
544 | computed, signed with a private key and added in the `DKIM-Signature` header of |
545 | the mail. The 'selector' (a short identifier chosen by you, used to identify | |
546 | which system and private key were used for signing) is also included in the | |
547 | `DKIM-Signature` header. | |
548 | ||
eb269701 | 549 | The verification is done by the receiver. The public key is fetched |
20522d96 SI |
550 | via DNS TXT lookup for `yourselector._domainkey.yourdomain.example` and used |
551 | for verifying the hash. You can publish multiple selectors for your domain, | |
3f18659b | 552 | each used by a system which sends email from your domain, without the need to |
20522d96 SI |
553 | share the private key. |
554 | ||
555 | {pmg} verifies DKIM Signatures for inbound mail in the Spam Filter by default. | |
556 | ||
eb269701 DW |
557 | Additionally, it supports conditionally signing outbound mail, if configured. |
558 | It uses one private key and selector per {pmg} deployment (all nodes in a | |
559 | cluster use the same key). The key has a minimal size of 1024 bits and | |
560 | rsa-sha256 is used as the signing algorithm. | |
20522d96 SI |
561 | |
562 | The headers included in the signature are taken from the list of | |
563 | `Mail::DKIM::Signer`. Additionally `Content-Type` (if present), `From`, `To`, | |
564 | `CC`, `Reply-To` and `Subject` get oversigned. | |
565 | ||
566 | You can either sign all mails received on the internal port using the domain of | |
3f18659b | 567 | the envelope sender address or create a list of domains, for which emails |
20522d96 SI |
568 | should be signed, defaulting to the list of relay domains. |
569 | ||
570 | ||
571 | Enable DKIM Signing:: | |
572 | ||
573 | Controls whether outbound mail should get DKIM signed. | |
574 | ||
575 | Selector:: | |
576 | ||
577 | The selector used for signing the mail. The private key used for signing is | |
3fe91910 | 578 | saved under `/etc/pmg/dkim/yourselector.private`. You can display the DNS TXT |
20522d96 SI |
579 | record which you need to add to all domains signed by {pmg} by clicking on the |
580 | 'View DNS Record' Button. | |
581 | ||
582 | Sign all Outgoing Mail:: | |
583 | ||
584 | Controls whether all outbound mail should get signed or only mails from domains | |
eb269701 DW |
585 | listed in `/etc/pmg/dkim/domains`, if it exists and `/etc/pmg/domains` |
586 | otherwise. | |
20522d96 | 587 | |
90f38c3d MS |
588 | Select Signing Domain:: |
589 | ||
590 | Determines whether to DKIM sign emails using the domain found in the envelope | |
b53b522b SI |
591 | from or the from header of the email. The envelope from is also known as |
592 | reverse-path and RFC5321.MailFrom (see {rfc_5321} section 3.3). | |
593 | The from header is also known as RFC5322.From (see {rfc_5322} section 3.6.2). | |
90f38c3d | 594 | + |
b53b522b | 595 | The envelope from of certain emails, bounces for example, can be empty. In these |
90f38c3d MS |
596 | cases it is desirable to sign them using the domain found in the from header. |
597 | + | |
598 | Additionally, DMARC (see {dmarc_rfc} section 3.1.1) needs the domain found in | |
599 | the from header in certain situations. | |
600 | ||
eb269701 | 601 | These settings are saved to the 'admin' subsection in `/etc/pmg/pmg.conf`, |
20522d96 SI |
602 | using the following configuration keys: |
603 | ||
604 | include::pmg.admin-dkim-conf-opts.adoc[] | |
605 | ||
606 | ||
61b59f73 | 607 | [[pmgconfig_mailproxy_whitelist]] |
c331641e DM |
608 | Whitelist |
609 | ~~~~~~~~~ | |
610 | ||
611 | ifndef::manvolnum[] | |
38d14519 | 612 | [thumbnail="screenshot/pmg-gui-mailproxy-whitelist.png", big=1] |
c331641e DM |
613 | endif::manvolnum[] |
614 | ||
3f18659b | 615 | All SMTP checks are disabled for those entries (e.g. Greylisting, |
74ec1f38 ML |
616 | SPF, DNSBL, ...) |
617 | ||
eb269701 | 618 | DNSBL checks are done by `postscreen`, which works on IP addresses and networks. |
74ec1f38 | 619 | This means it can only make use of the `IP Address` and `IP Network` entries. |
6822b369 | 620 | |
eb269701 | 621 | NOTE: If you use a backup MX server (for example, your ISP offers this service |
6822b369 | 622 | for you) you should always add those servers here. |
c331641e | 623 | |
74ec1f38 ML |
624 | NOTE: To disable DNSBL checks entirely, remove any `DNSBL Sites` entries in |
625 | xref:pmgconfig_mailproxy_options[Mail Proxy Options]. | |
c331641e | 626 | |
4a08dffe | 627 | [[pmgconfig_spamdetector]] |
c331641e DM |
628 | Spam Detector Configuration |
629 | --------------------------- | |
630 | ||
2d672352 DM |
631 | Options |
632 | ~~~~~~~ | |
633 | ||
74bfe8ba | 634 | ifndef::manvolnum[] |
38d14519 | 635 | [thumbnail="screenshot/pmg-gui-spam-options.png", big=1] |
74bfe8ba DM |
636 | endif::manvolnum[] |
637 | ||
3371c521 DM |
638 | {pmg} uses a wide variety of local and network tests to identify spam |
639 | signatures. This makes it harder for spammers to identify one aspect | |
640 | which they can craft their messages to work around the spam filter. | |
641 | ||
eb269701 | 642 | Every single email will be analyzed and have a spam score |
3371c521 DM |
643 | assigned. The system attempts to optimize the efficiency of the rules |
644 | that are run in terms of minimizing the number of false positives and | |
645 | false negatives. | |
646 | ||
647 | include::pmg.spam-conf-opts.adoc[] | |
648 | ||
649 | ||
4a08dffe | 650 | [[pmgconfig_spamdetector_quarantine]] |
2d672352 DM |
651 | Quarantine |
652 | ~~~~~~~~~~ | |
3371c521 | 653 | |
74bfe8ba | 654 | ifndef::manvolnum[] |
38d14519 | 655 | [thumbnail="screenshot/pmg-gui-spamquar-options.png", big=1] |
74bfe8ba DM |
656 | endif::manvolnum[] |
657 | ||
3f18659b OB |
658 | {pmg} analyses all incoming email messages and decides for each |
659 | email if it is ham or spam (or virus). Good emails are delivered to | |
660 | the inbox and spam messages are moved into the spam quarantine. | |
3371c521 DM |
661 | |
662 | The system can be configured to send daily reports to inform users | |
eb269701 | 663 | about personal spam messages received in the last day. The report is |
3371c521 DM |
664 | only sent if there are new messages in the quarantine. |
665 | ||
ee34edb0 | 666 | Some options are only available in the config file `/etc/pmg/pmg.conf`, |
3f18659b | 667 | and not in the web interface. |
ee34edb0 | 668 | |
3371c521 | 669 | include::pmg.spamquar-conf-opts.adoc[] |
c331641e DM |
670 | |
671 | ||
36b169e6 SI |
672 | [[pmgconfig_spamdetector_customscores]] |
673 | Customization of Rulescores | |
674 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
675 | ||
f5fddbff | 676 | ifndef::manvolnum[] |
38d14519 | 677 | [thumbnail="screenshot/pmg-gui-spam-custom-scores.png", big=1] |
f5fddbff SI |
678 | endif::manvolnum[] |
679 | ||
36b169e6 SI |
680 | While the default scoring of {spamassassin}'s ruleset provides very good |
681 | detection rates, sometimes your particular environment can benefit from | |
682 | slightly adjusting the score of a particular rule. Two examples: | |
683 | ||
684 | * Your system receives spam mails which are scored at 4.9 and you have | |
685 | a rule which puts all mails above 5 in the quarantine. The one thing the | |
686 | spam mails have in common is that they all hit 'URIBL_BLACK'. By increasing | |
687 | the score of this rule by 0.2 points the spam mails would all be quarantined | |
688 | instead of being sent to your users | |
689 | ||
690 | * Your system tags many legitimate mails from a partner organization as spam, | |
691 | because the organization has a policy that each mail has to start with | |
692 | 'Dear madam or sir' (generating 1.9 points through the rule | |
eb269701 | 693 | 'DEAR_SOMETHING'). By setting the score of this rule to 0, you can disable |
36b169e6 SI |
694 | it completely. |
695 | ||
3f18659b | 696 | The system logs all the rules which a particular mail hits. Analyzing the logs can |
36b169e6 SI |
697 | lead to finding such a pattern in your environment. |
698 | ||
699 | You can adjust the score of a rule by creating a new 'Custom Rule Score' entry | |
e1f6d6d0 | 700 | in the GUI and entering a {spamassassin} rule as the name. |
36b169e6 | 701 | |
eb269701 | 702 | NOTE: In general, it is strongly recommended not to make large changes to the |
36b169e6 SI |
703 | default scores. |
704 | ||
705 | ||
4a08dffe | 706 | [[pmgconfig_clamav]] |
c331641e DM |
707 | Virus Detector Configuration |
708 | ---------------------------- | |
709 | ||
4a08dffe | 710 | [[pmgconfig_clamav_options]] |
2d672352 DM |
711 | Options |
712 | ~~~~~~~ | |
713 | ||
e7c18c7c | 714 | ifndef::manvolnum[] |
38d14519 | 715 | [thumbnail="screenshot/pmg-gui-virus-options.png", big=1] |
e7c18c7c DM |
716 | endif::manvolnum[] |
717 | ||
0bfbbf88 | 718 | All mails are automatically passed to the included virus detector |
3f18659b | 719 | ({clamav}). The default settings are considered safe, so it is usually |
0bfbbf88 DM |
720 | not required to change them. |
721 | ||
722 | {clamav} related settings are saved to subsection 'clamav' in `/etc/pmg/pmg.conf`, | |
723 | using the following configuration keys: | |
724 | ||
725 | include::pmg.clamav-conf-opts.adoc[] | |
726 | ||
e7c18c7c | 727 | ifndef::manvolnum[] |
38d14519 | 728 | [thumbnail="screenshot/pmg-gui-clamav-database.png", big=1] |
e7c18c7c DM |
729 | endif::manvolnum[] |
730 | ||
3f18659b OB |
731 | Please note that the virus signature database is automatically |
732 | updated. You can see the database status in the GUI, and also | |
eb269701 | 733 | trigger manual updates from there. |
e7c18c7c | 734 | |
0bfbbf88 | 735 | |
4a08dffe | 736 | [[pmgconfig_clamav_quarantine]] |
2d672352 DM |
737 | Quarantine |
738 | ~~~~~~~~~~ | |
0bfbbf88 | 739 | |
e7c18c7c | 740 | ifndef::manvolnum[] |
38d14519 | 741 | [thumbnail="screenshot/pmg-gui-virusquar-options.png", big=1] |
e7c18c7c DM |
742 | endif::manvolnum[] |
743 | ||
eb269701 DW |
744 | Identified virus mails are automatically moved to the virus |
745 | quarantine. The administrator can view these mails from the GUI, and | |
746 | choose to deliver them, in case of false positives. {pmg} does not notify | |
0bfbbf88 DM |
747 | individual users about received virus mails. |
748 | ||
749 | Virus quarantine related settings are saved to subsection 'virusquar' | |
750 | in `/etc/pmg/pmg.conf`, using the following configuration keys: | |
751 | ||
752 | include::pmg.virusquar-conf-opts.adoc[] | |
c331641e DM |
753 | |
754 | ||
7eff8815 DM |
755 | Custom SpamAssassin configuration |
756 | --------------------------------- | |
757 | ||
833e1edc SI |
758 | This is only for advanced users. {spamassassin}'s rules and their associated |
759 | scores get updated regularly and are trained on a huge corpus, which gets | |
eb269701 | 760 | classified by experts. In most cases, adding a rule for matching a particular |
833e1edc SI |
761 | keyword is the wrong approach, leading to many false positives. Usually bad |
762 | detection rates are better addressed by properly setting up DNS than by adding | |
763 | a custom rule - watch out for matches to 'URIBL_BLOCKED' in the logs or | |
764 | spam-headers - see the {spamassassin_dnsbl}. | |
765 | ||
eb269701 DW |
766 | To add or change the Proxmox {spamassassin} configuration, log in to the |
767 | console via SSH and change to the `/etc/mail/spamassassin/` directory. In this | |
d2f49775 | 768 | directory there are several files (`init.pre`, `local.cf`, ...) - do not change |
69a428d9 SI |
769 | them, as `init.pre`, `v310.pre`, `v320.pre`, `local.cf` will be overwritten by |
770 | the xref:pmgconfig_template_engine[template engine], while the others can | |
771 | get updated by any {spamassassin} package upgrade. | |
833e1edc | 772 | |
e1f6d6d0 DW |
773 | To add your custom configuration, you have to create a new file named |
774 | `custom.cf` (in `/etc/mail/spamassassin/`), then add your configuration there. | |
775 | Make sure to use the correct {spamassassin_rule_syntax} and test it with: | |
7eff8815 DM |
776 | |
777 | ---- | |
778 | # spamassassin -D --lint | |
779 | ---- | |
780 | ||
781 | If you run a cluster, the `custom.cf` file is synchronized from the | |
d2f49775 | 782 | master node to all cluster members automatically. |
7eff8815 | 783 | |
eb269701 | 784 | To adjust the score assigned to a particular rule, you |
36b169e6 SI |
785 | can also use the xref:pmgconfig_spamdetector_customscores[Custom Rule Score] |
786 | settings in the GUI. | |
787 | ||
7eff8815 | 788 | |
ed7970d8 SI |
789 | [[pmgconfig_custom_check]] |
790 | Custom Check Interface | |
791 | ---------------------- | |
792 | ||
3f18659b | 793 | For use-cases which are not handled by the {pmg} Virus Detector and |
ed7970d8 SI |
794 | {spamassassin} configuration, advanced users can create a custom check |
795 | executable which, if enabled will be called before the Virus Detector and before | |
3f18659b | 796 | passing an email through the Rule System. The custom check API is kept as |
ed7970d8 | 797 | simple as possible, while still providing a great deal of control over the |
3f18659b | 798 | treatment of an email. Its input is passed via two CLI arguments: |
ed7970d8 SI |
799 | |
800 | * the 'api-version' (currently `v1`) - for potential future change of the | |
801 | invocation | |
802 | ||
3f18659b | 803 | * the 'queue-file-name' - a filename, which contains the complete email as |
ed7970d8 SI |
804 | rfc822/eml file |
805 | ||
eb269701 | 806 | The expected output needs to be printed to STDOUT and consists of two lines: |
ed7970d8 SI |
807 | |
808 | * the 'api-version' (currently 'v1') - see above | |
809 | ||
810 | * one of the following 3 results: | |
eb269701 | 811 | ** 'OK' - email is OK |
3f18659b OB |
812 | ** 'VIRUS: <virusdescription>' - email is treated as if it contained a virus |
813 | (the virus description is logged and added to the email's headers) | |
ed7970d8 | 814 | ** 'SCORE: <number>' - <number> is added (negative numbers are also possible) |
3f18659b | 815 | to the email's spamscore |
ed7970d8 | 816 | |
eb269701 | 817 | The check is run with a 5 minute timeout - if this is exceeded, the check |
3f18659b | 818 | executable is killed and the email is treated as OK. |
ed7970d8 SI |
819 | |
820 | All output written to STDERR by the check is written with priority 'err' to the | |
821 | journal/mail.log. | |
822 | ||
eb269701 DW |
823 | Below is a simple sample script following the API (and yielding a random result) |
824 | for reference: | |
ed7970d8 SI |
825 | |
826 | ---- | |
827 | #!/bin/sh | |
828 | ||
829 | echo "called with $*" 1>&2 | |
830 | ||
831 | if [ "$#" -ne 2 ]; then | |
832 | echo "usage: $0 APIVERSION QUEUEFILENAME" 1>&2 | |
833 | exit 1 | |
834 | fi | |
835 | ||
836 | apiver="$1" | |
837 | shift | |
838 | ||
839 | if [ "$apiver" != "v1" ]; then | |
840 | echo "wrong APIVERSION: $apiver" 1>&2 | |
841 | exit 2 | |
842 | fi | |
843 | ||
844 | queue_file="$1" | |
845 | ||
846 | echo "v1" | |
847 | ||
848 | choice=$(shuf -i 0-3 -n1) | |
849 | ||
850 | case "$choice" in | |
851 | 0) | |
852 | echo OK | |
853 | ;; | |
854 | 1) | |
855 | echo SCORE: 4 | |
856 | ;; | |
857 | 2) | |
858 | echo VIRUS: Random Virus | |
859 | ;; | |
860 | 3) #timeout-test | |
861 | for i in $(seq 1 7); do | |
862 | echo "custom checking mail: $queue_file - minute $i" 1>&2 | |
863 | sleep 60 | |
864 | done | |
865 | ;; | |
866 | esac | |
867 | ||
868 | exit 0 | |
869 | ---- | |
870 | ||
871 | The custom check needs to be enabled in the admin section of `/etc/pmg/pmg.conf` | |
872 | ||
873 | ---- | |
874 | section: admin | |
875 | custom_check 1 | |
876 | ---- | |
877 | ||
878 | The location of the custom check executable can also be set there with the key | |
879 | `custom_check_path` and defaults to `/usr/local/bin/pmg-custom-check`. | |
880 | ||
881 | ||
c331641e DM |
882 | User Management |
883 | --------------- | |
884 | ||
05336835 DC |
885 | User management in {pmg} consists of three types of users/accounts: |
886 | ||
887 | ||
4a08dffe | 888 | [[pmgconfig_localuser]] |
05336835 DC |
889 | Local Users |
890 | ~~~~~~~~~~~ | |
891 | ||
38d14519 | 892 | [thumbnail="screenshot/pmg-gui-local-user-config.png", big=1] |
f02d2b90 | 893 | |
4885bff7 TL |
894 | Local users can manage and audit {pmg}. They can login on the management web |
895 | interface. | |
05336835 | 896 | |
a8ac4ab3 | 897 | There are four roles: |
05336835 | 898 | |
4885bff7 TL |
899 | Administrator:: |
900 | ||
eb269701 | 901 | Is allowed to manage settings of {pmg}, excluding some tasks like network |
4885bff7 TL |
902 | configuration and upgrading. |
903 | ||
904 | Quarantine manager:: | |
05336835 | 905 | |
05336835 DC |
906 | Is allowed to manage quarantines, blacklists and whitelists, but not other |
907 | settings. Has no right to view any other data. | |
908 | ||
4885bff7 TL |
909 | Auditor:: |
910 | ||
05336835 DC |
911 | With this role, the user is only allowed to view data and configuration, but |
912 | not to edit it. | |
913 | ||
a8ac4ab3 TL |
914 | Helpdesk:: |
915 | ||
916 | Combines permissions of the 'Auditor' and the 'Quarantine Manager' role. | |
917 | ||
eb269701 | 918 | In addition, there is always the 'root' user, which is used to perform special |
4885bff7 TL |
919 | system administrator tasks, such as upgrading a host or changing the network |
920 | configuration. | |
05336835 | 921 | |
eb269701 DW |
922 | NOTE: Only PAM users are able to log in via the web interface and ssh, while the |
923 | users created through the web interface are not. Those users are created for | |
924 | {pmg} administration only. | |
05336835 DC |
925 | |
926 | Local user related settings are saved in `/etc/pmg/user.conf`. | |
927 | ||
eb269701 | 928 | For details on the fields, see xref:pmg_user_configuration_file[user.conf] |
05336835 | 929 | |
4a08dffe | 930 | [[pmgconfig_ldap]] |
05336835 DC |
931 | LDAP/Active Directory |
932 | ~~~~~~~~~~~~~~~~~~~~~ | |
933 | ||
38d14519 | 934 | [thumbnail="screenshot/pmg-gui-ldap-user-config.png", big=1] |
f02d2b90 | 935 | |
fc11986a DW |
936 | With {pmg}, users can use LDAP and Active directory as authentication methods to |
937 | access their individual xref:pmgadministration_spam_quarantine[Spam Quarantine]. | |
938 | Additionally, if users have extra email aliases defined in the LDAP directory, | |
939 | they will have a single spam quarantine for all of these. | |
940 | ||
941 | NOTE: Authentication via LDAP must first be enabled using the `Authentication | |
942 | mode` (`authmode`) parameter in the | |
943 | xref:pmgconfig_spamdetector_quarantine[Spam Detector's Quarantine configuration settings]. | |
944 | ||
05336835 | 945 | You can specify multiple LDAP/Active Directory profiles, so that you can |
fc11986a | 946 | create rules matching particular users and groups. |
05336835 DC |
947 | |
948 | Creating a profile requires (at least) the following: | |
949 | ||
fc11986a DW |
950 | * `Profile Name`: The name assigned to the LDAP profile. |
951 | * `Protocol`: LDAP, LDAPS, or LDAP+STARTTLS (LDAP+STARTTLS is recommended). | |
952 | * `Server`: The domain name/IP address of the LDAP server. A fallback can also | |
953 | be configured using the second field. | |
954 | * `User name`: The Bind DN for authentication on the LDAP server. | |
955 | This is required if your server does not support anonymous binds. | |
956 | * `Password`: Password for the Bind DN user. | |
957 | * `Base DN`: The directory which users are searched under. | |
05336835 DC |
958 | |
959 | All other fields should work with the defaults for most setups, but can be | |
960 | used to customize the queries. | |
961 | ||
fc11986a | 962 | The settings are saved to `/etc/pmg/ldap.conf`. Details about the options |
05336835 DC |
963 | can be found here: xref:pmg_ldap_configuration_file[ldap.conf] |
964 | ||
965 | Bind user | |
966 | ^^^^^^^^^ | |
967 | ||
968 | It is highly recommended that the user which you use for connecting to the | |
eb269701 | 969 | LDAP server only has permission to query the server. For LDAP servers |
05336835 | 970 | (for example OpenLDAP or FreeIPA), the username has to be of a format like |
eb269701 DW |
971 | 'uid=username,cn=users,cn=accounts,dc=domain', where the specific fields |
972 | depend on your setup. For Active Directory servers, the format should be | |
fc11986a | 973 | 'username@domain' or 'domain\username'. |
05336835 DC |
974 | |
975 | Sync | |
976 | ^^^^ | |
977 | ||
eb269701 DW |
978 | {pmg} synchronizes the relevant user and group information periodically, so that |
979 | the information is quickly available, even when the LDAP/AD server is | |
980 | temporarily inaccessible. | |
05336835 | 981 | |
3f18659b | 982 | After a successful sync, the groups and users should be visible on the web |
eb269701 | 983 | interface. Following this, you can create rules targeting LDAP users and groups. |
c331641e DM |
984 | |
985 | ||
4a08dffe | 986 | [[pmgconfig_fetchmail]] |
8538d9a2 | 987 | Fetchmail |
05336835 DC |
988 | ~~~~~~~~~ |
989 | ||
38d14519 | 990 | [thumbnail="screenshot/pmg-gui-fetchmail-config.png", big=1] |
f02d2b90 | 991 | |
eb269701 | 992 | Fetchmail is a utility for polling and forwarding emails. You can define |
3f18659b | 993 | email accounts, which will then be fetched and forwarded to the email |
05336835 DC |
994 | address you defined. |
995 | ||
996 | You have to add an entry for each account/target combination you want to | |
eb269701 | 997 | fetch and forward. These will then be regularly polled and forwarded, |
05336835 DC |
998 | according to your configuration. |
999 | ||
eb269701 | 1000 | The API and web interface offer the following configuration options: |
8538d9a2 DM |
1001 | |
1002 | include::fetchmail.conf.5-opts.adoc[] | |
1003 | ||
a4f14219 TL |
1004 | [[user_tfa_auth]] |
1005 | Two-Factor Authentication | |
1006 | ------------------------- | |
1007 | ||
1008 | Users of the admin interface can configure two-factor authentication to | |
1009 | increase protection of their accounts. | |
1010 | ||
1a4f8407 TL |
1011 | NOTE: Joining a cluster with two-factor authentication enabled for the `root` |
1012 | user is not supported. Remove the second factor when joining the cluster. | |
f8dc6aec | 1013 | |
a4f14219 TL |
1014 | Available Second Factors |
1015 | ~~~~~~~~~~~~~~~~~~~~~~~~ | |
1016 | ||
1017 | You can set up multiple second factors, in order to avoid a situation in which | |
1018 | losing your smartphone or security key locks you out of your account | |
1019 | permanently. | |
1020 | ||
c4f5ee14 | 1021 | The following two-factor authentication methods are available: |
a4f14219 TL |
1022 | |
1023 | * User configured TOTP | |
1024 | (https://en.wikipedia.org/wiki/Time-based_One-Time_Password[Time-based One-Time Password]). | |
1025 | A short code derived from a shared secret and the current time, it changes | |
1026 | every 30 seconds. | |
1027 | * WebAuthn (https://en.wikipedia.org/wiki/WebAuthn[Web Authentication]). | |
1028 | A general standard for authentication. It is implemented by various security | |
1029 | devices, like hardware keys or trusted platform modules (TPM) from a computer | |
1030 | or smart phone. | |
1031 | * Single use Recovery Keys. A list of keys which should either be | |
1032 | printed out and locked in a secure place or saved digitally in an electronic | |
1033 | vault. Each key can be used only once. These are perfect for ensuring that | |
1034 | you are not locked out, even if all of your other second factors are lost or | |
1035 | corrupt. | |
1036 | ||
1037 | Configuration of Two-Factor | |
1038 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ | |
1039 | ||
1040 | Users can choose to enable 'TOTP' or 'WebAuthn' as a second factor on login, | |
c4f5ee14 | 1041 | via the 'TFA' button in the user list. |
a4f14219 TL |
1042 | |
1043 | Users can always add and use one time 'Recovery Keys'. | |
1044 | ||
1045 | //[thumbnail="screenshot/gui-datacenter-two-factor.png"]//TODO | |
1046 | ||
1047 | [[user_tfa_setup_totp]] | |
1048 | === TOTP | |
1049 | ||
1050 | //[thumbnail="screenshot/pve-gui-tfa-add-totp.png"]//TODO | |
1051 | ||
1052 | There is no server setup required. Simply install a TOTP app on your | |
1053 | smartphone (for example, https://github.com/andOTP/andOTP#downloads[andOTP]) | |
1054 | and use the Proxmox Backup Server web-interface to add a TOTP factor. | |
1055 | ||
1056 | After opening the 'TOTP' window, the user is presented with a dialog to set up | |
1057 | 'TOTP' authentication. The 'Secret' field contains the key, which can be | |
1058 | randomly generated via the 'Randomize' button. An optional 'Issuer Name' can be | |
1059 | added to provide information to the 'TOTP' app about what the key belongs to. | |
1060 | Most 'TOTP' apps will show the issuer name together with the corresponding | |
1061 | 'OTP' values. The username is also included in the QR code for the 'TOTP' app. | |
1062 | ||
1063 | After generating a key, a QR code will be displayed, which can be used with most | |
1064 | OTP apps such as FreeOTP. The user then needs to verify the current user | |
1065 | password (unless logged in as 'root'), as well as the ability to correctly use | |
1066 | the 'TOTP' key, by typing the current 'OTP' value into the 'Verification Code' | |
1067 | field and pressing the 'Apply' button. | |
1068 | ||
1069 | ||
1070 | [[user_tfa_setup_webauthn]] | |
1071 | === WebAuthn | |
1072 | ||
1073 | For WebAuthn to work, you need to have two things: | |
1074 | ||
1075 | * A trusted HTTPS certificate (for example, by using | |
c4f5ee14 | 1076 | xref:sysadmin_certs_get_trusted_acme_cert[Let's Encrypt]). |
a4f14219 TL |
1077 | While it probably works with an untrusted certificate, some browsers may |
1078 | warn or refuse WebAuthn operations if it is not trusted. | |
1079 | * Setup the WebAuthn configuration (see *User Management -> Two Factor -> | |
1080 | WebAuthn* in the {pmg} web interface). This can be | |
1081 | auto-filled in most setups. | |
1082 | ||
1083 | Once you have fulfilled both of these requirements, you can add a WebAuthn | |
1084 | configuration in the *Two Factor* panel under *Datacenter -> Permissions -> Two | |
1085 | Factor*. | |
1086 | ||
1087 | [[user_tfa_setup_recovery_keys]] | |
1088 | === Recovery Keys | |
1089 | ||
1090 | //[thumbnail="screenshot/pve-gui-tfa-add-recovery-keys.png"]//TODO | |
1091 | ||
1092 | Recovery key codes do not need any preparation; you can simply create a | |
1093 | set of recovery keys in the *Two Factor* panel under *Datacenter -> Permissions | |
1094 | -> Two Factor*. | |
1095 | ||
1096 | NOTE: There can only be one set of single-use recovery keys per user at any | |
1097 | time. | |
1098 | ||
1099 | WebAuthn Configuration | |
1100 | ~~~~~~~~~~~~~~~~~~~~~~ | |
1101 | ||
1102 | //[thumbnail="screenshot/gui-datacenter-webauthn-edit.png"]//TODO | |
1103 | ||
1104 | To allow users to use 'WebAuthn' authentication, it is necessaary to use a valid | |
1105 | domain with a valid SSL certificate, otherwise some browsers may warn or refuse | |
1106 | to authenticate altogether. | |
1107 | ||
1108 | NOTE: Changing the 'WebAuthn' configuration may render all existing 'WebAuthn' | |
1109 | registrations unusable! | |
1110 | ||
1111 | You can configure WebAuthn directly in the 'Two Factor' panel, there's an | |
1112 | auto-fill button that will set the correct values for most setups. | |
8538d9a2 | 1113 | |
e62ceaf0 DM |
1114 | ifdef::manvolnum[] |
1115 | include::pmg-copyright.adoc[] | |
1116 | endif::manvolnum[] |