ISPConfig 3 issueshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues2021-03-16T10:19:21Zhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6110Improve dns records list2021-03-16T10:19:21ZHelmoImprove dns records listThe type, aux and ttl columns take too much space in the DNS records listing.
The patch below is more of a quick fix until a more comprehensive solution like #5490 gets done.
It reduces the width of these columns ... Which should pro...The type, aux and ttl columns take too much space in the DNS records listing.
The patch below is more of a quick fix until a more comprehensive solution like #5490 gets done.
It reduces the width of these columns ... Which should probably be done via CSS, that's why this is not a MR. Someone else is probably better at finding the proper selector and place for it.
```patch
diff --git a/interface/web/dns/templates/dns_a_list.htm b/interface/web/dns/templates/dns_a_list.htm
index 4d0f3b2b2..a7b94fc96 100755
--- a/interface/web/dns/templates/dns_a_list.htm
+++ b/interface/web/dns/templates/dns_a_list.htm
@@ -58,11 +58,11 @@
<thead class="dark form-group-sm">
<tr>
<th class="tiny-col" data-column="active"><tmpl_var name="active_txt"></th>
- <th data-column="type"><tmpl_var name="type_txt"></th>
+ <th data-column="type" style="width: 12%;"><tmpl_var name="type_txt"></th>
<th data-column="name"><tmpl_var name="name_txt"></th>
<th data-column="data"><tmpl_var name="data_txt"></th>
- <th data-column="aux"><tmpl_var name="aux_txt"></th>
- <th data-column="ttl"><tmpl_var name="ttl_txt"></th>
+ <th data-column="aux" style="width: 8%;"><tmpl_var name="aux_txt"></th>
+ <th data-column="ttl" style="width: 8%;"><tmpl_var name="ttl_txt"></th>
<th class="small-col text-right">{tmpl_var name='search_limit'}</th>
</tr>
<tr>
```https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6101Discussion: Simplify the UI for end users2022-06-18T14:34:09ZThomDiscussion: Simplify the UI for end usersI just went through the UI to see which things could be confusing for novice clients, and which could be a reason for ISPs not to use ISPConfig. Some things could be hidden for all clients, some only when a specific setting is set in the...I just went through the UI to see which things could be confusing for novice clients, and which could be a reason for ISPs not to use ISPConfig. Some things could be hidden for all clients, some only when a specific setting is set in the main config or client limits.
## Sites
* Website vs subdomain -> some clients will add a subdomain "different.example.com" for a completely different site than the main web, maybe we could rephrase this, or add some explanation to the tab what adding a subdomain does?
* Read-only database user -> Maybe we can add a global option to enable/disable this, or put it within client limits?
* Order of Databases and database users -> Maybe we should put database users first, as this is the first thing you have to create, or allow the creation of a DB user when creating the DB itself?
## Email
* I think it would be good to switch the order of email mailbox and domain, or at least set mailbox as default tab, as this tab is the most used.
* It would be good to add global settings and/or client limits for the following buttons on the mailbox form:
* Copy during delivery
* Spampolicy (inherited from domain by default) (we might hide this on the domain form aswell and let the admin set a default policy)
* Enable receiving
* Disable sending
* Disable (local) delivering
* Enable greylisting
* Disable IMAP
* Disable POP3
## DNS
* #5490
* Almost all the zone settings could be hidden:
* NS
* Email
* Refresh
* Retry
* Expire
* Minimum (negative cache ttl)
* TTL
* Allow zone transfers to these IPs (comma separated list) (as client limit)
* Also Notify (as client limit)
* Serial
This issue is to discuss this - it's not necessarily a feature request.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6095change of jailkit default/site section addition/override and location2021-03-11T10:08:01Zleechange of jailkit default/site section addition/override and locationit's not particularly clear when looking at the jailkit settings on a website options page if any settings configured there are in addition to the default server jailkit settings, or completely override them, so only sections in the site...it's not particularly clear when looking at the jailkit settings on a website options page if any settings configured there are in addition to the default server jailkit settings, or completely override them, so only sections in the site settings get applied.
it's current location also means that admin intervention is required whenever a client wants a particular application added to their site's jailkit, either to add the section to their sites jailkit settings (or to remove it at a later date), or to add the application to the servers jailkit settings so everyone gets the additional application whether they want it or not.
it may be a better option to move the site's jailkit settings to the ssh account creation/settings page, and have additional sections made available for selection by the client user, just like apache or php directives are.
discussion on howtoforge forum: https://www.howtoforge.com/community/threads/quick-question-about-website-jailkit-options.86557/https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6093Monitor MX records2022-12-27T22:35:12ZHelmoMonitor MX recordsWhen a domain moves to an external mail provider it's important to de-activate or remove the mail domain from ispconfig.
When forgotten this can lead to mails not being delivered.
I've written a perl script to check this in the past and...When a domain moves to an external mail provider it's important to de-activate or remove the mail domain from ispconfig.
When forgotten this can lead to mails not being delivered.
I've written a perl script to check this in the past and now ported that to ispconfig.
It resolves the server name and checks that the MX record for a mail_domain matches one of those IP's. Extra IP's can be added via `$mail_config['additional_smtp_ips']`
On one of my systems I use an extra IP for incomming smtp, so there I had to override the server hostname. There I've put in a `$mail_config['hostname'] = '...'; line in onRunJob() for now. I don't think we have a field for that and it's probably not worth creating it for just me. But I'm open to suggestions.
TODO
- [x] String updates?
- [x] Maybe some layout?
- [x] UI for $mail_config['additional_smtp_ips'] and `$mail_config['additional_smtp_hostnames']`?
- [x] Maybe remove the $app->log warning lines as it might a bit redundant
- [x] translation files
Anyway, feedback welcome.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6092Add Nagios check for ISPconfig2022-05-24T12:28:13ZHelmoAdd Nagios check for ISPconfigThe monitor page in ISPconfig has a nice overview of the system status, but I would like to be alerted when something changes.
In my setup I have Icinga for that, which is Nagios compatible.
I created a Nagios compatible script to expor...The monitor page in ISPconfig has a nice overview of the system status, but I would like to be alerted when something changes.
In my setup I have Icinga for that, which is Nagios compatible.
I created a Nagios compatible script to export data from the monitor page.
It outputs a single line like: `WARNING: (ok: 12, info: system_update, warning: sys_log)`
Usage:
In an NRPE compatible config file:
`command[check_ispconfig]=/usr/bin/sudo /usr/local/ispconfig/server/check_ispconfig.php`
/etc/sudoers.d/ispconfig:
```
Cmnd_Alias CHECK_ISPCONFIG = /usr/local/ispconfig/server/check_ispconfig.php
nagios ALL = NOPASSWD : CHECK_ISPCONFIG
```https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6082rspamd white/blacklist using multimap module2022-07-27T01:05:03ZJesse Norellrspamd white/blacklist using multimap moduleNeed to rework the rspamd implementation of white/blacklists to use the multimap module rather than setting want_spam=yes - see notes/comments in https://git.ispconfig.org/ispconfig/ispconfig3/-/merge_requests/1411Need to rework the rspamd implementation of white/blacklists to use the multimap module rather than setting want_spam=yes - see notes/comments in https://git.ispconfig.org/ispconfig/ispconfig3/-/merge_requests/1411Jesse NorellJesse Norellhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6074Postfix 3.4: TLS SNI Mapping2021-04-27T15:09:13ZColin OgilviePostfix 3.4: TLS SNI Mapping## short description
Postfix 3.4 supports a new feature which enables TLS SNI Mapping to enable each domain to have it's own SSL certificate.
## correct behaviour
It would be good if ISPConfig could support this by default.
## environm...## short description
Postfix 3.4 supports a new feature which enables TLS SNI Mapping to enable each domain to have it's own SSL certificate.
## correct behaviour
It would be good if ISPConfig could support this by default.
## environment
Server OS: Ubuntu
Server OS version: 20.04
ISPConfig version: 3.2.2
## proposed fix
* Allow various options to enable the use of certificates in the domain and include that in the generation of the certificate through LetsEncrypt. This could either be 'mail.domain' or even just domain by default.
* Maintain, or write, the ability to set the `tls_server_sni_maps` variable in Postfix (from SQL if possible)https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6073Aliases created by the "Website auto alias" setting are not added to the Lets...2021-03-03T16:43:53ZJudah - MWAliases created by the "Website auto alias" setting are not added to the Lets Encrypt certificate request## Short description
If a value is defined in System > Server Config > Web > Website Auto Alias, it is automatically added as an alias to the site vhost. However it is not added to the LE certificate request.
## Correct behaviour
The a...## Short description
If a value is defined in System > Server Config > Web > Website Auto Alias, it is automatically added as an alias to the site vhost. However it is not added to the LE certificate request.
## Correct behaviour
The auto alias should be part of the certificate request.
(I know some people use auto alias for internal aliases, that would still be fine as the LE check would catch the non-routable alias and discard it.)
## An example
We have `mail.[website_domain]` configured as our auto alias:
![image](/uploads/75f4a0d35fdedf07204a38da6d8c1d28/image.png)
This correctly appears in all _new_ nginx vhosts like so:
```
server_name example.com www.example.com mail.example.com;
```
However it does not get added to the certificate request. Viewing the request in `acme.log` shows it is not included and viewing the certificate afterwards shows this:
```bash
$ openssl x509 -in /var/www/example.com/ssl/example.com-le.crt -text -noout | grep DNS
DNS: example.com, DNS: www.example.com
```
## Environment
Server OS: CentOS 8
ISPConfig version: 3.2.2
Webserver: NGINX
## Proposed fix
Looks like the certificate generation logic is in [server/plugins-available/nginx_plugin.inc.php:1385](https://git.ispconfig.org/ispconfig/ispconfig3/-/blob/develop/server/plugins-available/nginx_plugin.inc.php#L1385)
```php
//* Generate Let's Encrypt SSL certificat
if($data['new']['ssl'] == 'y' && $data['new']['ssl_letsencrypt'] == 'y' && $conf['mirror_server_id'] == 0 && ( // ssl and let's encrypt is active and no mirror server
($data['old']['ssl'] == 'n' || $data['old']['ssl_letsencrypt'] == 'n') // we have new let's encrypt configuration
|| ($data['old']['domain'] != $data['new']['domain']) // we have domain update
|| ($data['old']['subdomain'] != $data['new']['subdomain']) // we have new or update on "auto" subdomain
|| $this->update_letsencrypt == true
)) {
$success = $app->letsencrypt->request_certificates($data, 'nginx');
if($success) {
/* we don't need to store it.
/* Update the DB of the (local) Server */
$app->db->query("UPDATE web_domain SET ssl_request = '', ssl_cert = '', ssl_key = '' WHERE domain = ?", $data['new']['domain']);
$app->db->query("UPDATE web_domain SET ssl_action = '' WHERE domain = ?", $data['new']['domain']);
/* Update also the master-DB of the Server-Farm */
$app->dbmaster->query("UPDATE web_domain SET ssl_request = '', ssl_cert = '', ssl_key = '' WHERE domain = ?", $data['new']['domain']);
$app->dbmaster->query("UPDATE web_domain SET ssl_action = '' WHERE domain = ?", $data['new']['domain']);
} else {
$data['new']['ssl_letsencrypt'] = 'n';
if($data['old']['ssl'] == 'n') $data['new']['ssl'] = 'n';
/* Update the DB of the (local) Server */
$app->db->query("UPDATE web_domain SET `ssl` = ?, `ssl_letsencrypt` = ? WHERE `domain` = ? AND `server_id` = ?", $data['new']['ssl'], 'n', $data['new']['domain'], $conf['server_id']);
/* Update also the master-DB of the Server-Farm */
$app->dbmaster->query("UPDATE web_domain SET `ssl` = ?, `ssl_letsencrypt` = ? WHERE `domain` = ?", $data['new']['ssl'], 'n', $data['new']['domain']);
}
}
```
The problem appears to be it simply takes the information straight out of `$data` but the part that deals with the auto alias hasn't been called yet as [it's all the way down on line 1651](https://git.ispconfig.org/ispconfig/ispconfig3/-/blob/develop/server/plugins-available/nginx_plugin.inc.php#L1651):
```php
// get autoalias
$auto_alias = $web_config['website_autoalias'];
if($auto_alias != '') {
// get the client username
$client = $app->db->queryOneRecord("SELECT `username` FROM `client` WHERE `client_id` = ?", $client_id);
$aa_search = array('[client_id]', '[website_id]', '[client_username]', '[website_domain]');
$aa_replace = array($client_id, $data['new']['domain_id'], $client['username'], $data['new']['domain']);
$auto_alias = str_replace($aa_search, $aa_replace, $auto_alias);
unset($client);
unset($aa_search);
unset($aa_replace);
$server_alias[] .= $auto_alias.' ';
}
```
There's not an obvious way to add it to that file, as it just passes the `$data` array off to the letsencrypt library. However we could add it in the LE lib, [maybe after line 365?](https://git.ispconfig.org/ispconfig/ispconfig3/-/blob/develop/server/lib/classes/letsencrypt.inc.php#L365) We'd basically just have to add the above "get auto alias" stuff in there. The only problem with that I can see is if the Apache plugin works differently and is already adding the auto alias, in which case we don't want to duplicate it.
Can anyone confirm if the Apache plugin does that? If not would this method be acceptable?
Thankshttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6067Add option to disable backup on mirror systems2021-02-22T08:39:24ZTill BrehmAdd option to disable backup on mirror systemsAdd option to disable backup on mirror systems to avoid that web, mail and database backups get written multiple times.Add option to disable backup on mirror systems to avoid that web, mail and database backups get written multiple times.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6066Enable TLSv1.3 for the panel and apps vhost (nginx)2021-03-07T13:21:47ZThomEnable TLSv1.3 for the panel and apps vhost (nginx)Enable TLSv1.3 if supportedEnable TLSv1.3 if supportedhttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6063problem with mail_user_add api call when missing mohedir and maildir attributes2021-03-04T19:23:17ZJiri Slezkaproblem with mail_user_add api call when missing mohedir and maildir attributes## short description
I am trying add mail user through mail_user_add api call but it behaves strange when I omit some attributes (homedir, maildir).
Mail user dir is created on disk in right place (/var/vmail/example.cz/test) but homedi...## short description
I am trying add mail user through mail_user_add api call but it behaves strange when I omit some attributes (homedir, maildir).
Mail user dir is created on disk in right place (/var/vmail/example.cz/test) but homedir and maildir in db is empty. Also when quota is specified other than 0 (for example 1024MB), every mail is rejected with "Quota exceeded (mailbox for user is full)". .quotausage file is created in right place and it contains
```
priv/quota/messages
6494
priv/quota/storage
1073743931
```
## correct behaviour
homedir and maildir should be generated on ISPConfig side (if missing)
## environment
Server OS: CentOS
Server OS version: CentOS7
ISPConfig version: (3.2.2)
## log entries
maillog
```
Feb 18 09:06:02 server dovecot: lda(test@example.cz): Error: User test@example.cz doesn't have home dir set, disabling duplicate database
Feb 18 09:06:02 server dovecot: lda(test@example.cz): msgid=<20210218080602.616B0249A54@smtp.example.cz>: save failed to INBOX: Quota exceeded (mailbox for user is full)
Feb 18 09:06:02 server dovecot: lda(test@example.cz): msgid=<20210218080602.616B0249A54@smtp.example.cz>: rejected: Quota exceeded (mailbox for user is full)
```https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6059Added directive to `custom_php_ini` to add fpm pool directives2021-02-14T08:31:34ZKreso PendicAdded directive to `custom_php_ini` to add fpm pool directivesHi, I needed to add directives for php fpm 'OPTIONS' tab -> inside existing php.ini settings textarea:
process.priority
pm.status_path
etc..
and that are fpm pool directives but the issue is that plugin `nginx_plugin.inc.ph...Hi, I needed to add directives for php fpm 'OPTIONS' tab -> inside existing php.ini settings textarea:
process.priority
pm.status_path
etc..
and that are fpm pool directives but the issue is that plugin `nginx_plugin.inc.php` file wrappes it in `php_admin_value[]` so I ended up with solution to prefix line with 'POOL' keyword and escaped ithttps://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6055Disable client (/admin) protection by default2021-02-11T19:28:58ZThomDisable client (/admin) protection by defaultAny opinions wether this should be enabled by default or not?Any opinions wether this should be enabled by default or not?https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6043jailkit: xauth error at login2021-02-13T20:40:00ZJesse Norelljailkit: xauth error at loginWhen logging in to a chroot shell user, xauth prints a message showing the non-chroot path (and possibly would not find the correct .Xauthority file?). Mostly harmless, but perhaps an env var (HOME?) could be set earlier before xauth ru...When logging in to a chroot shell user, xauth prints a message showing the non-chroot path (and possibly would not find the correct .Xauthority file?). Mostly harmless, but perhaps an env var (HOME?) could be set earlier before xauth runs, and at least get the correct chrooted path?
```
$ ssh client_user1f@ispc.hoster.tld
kentec_asdf@ispc.hoster.tld's password:
Linux srv-cp 4.19.0-12-amd64 #1 SMP Debian 4.19.152-1 (2020-10-18) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
/usr/bin/xauth: file /var/www/clients/client1/web2/./home/client_user1/.Xauthority does not exist
```https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6034Configure SSL CA Cert in Dovecot2023-05-03T12:43:56ZTill BrehmConfigure SSL CA Cert in DovecotCurrently, the SSL ca (bundle) SSL cert is not configured in dovecot.conf file. This may lead to connection issues with some older clients. We should add the line:
ssl_ca = </usr/local/ispconfig/interface/ssl/ispserver.bundle
in doveco...Currently, the SSL ca (bundle) SSL cert is not configured in dovecot.conf file. This may lead to connection issues with some older clients. We should add the line:
ssl_ca = </usr/local/ispconfig/interface/ssl/ispserver.bundle
in dovecot.conf, when the file /usr/local/ispconfig/interface/ssl/ispserver.bundle exists on the server.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6026resync should setup dkim record2021-01-22T07:06:56ZJesse Norellresync should setup dkim recordRelated to #6025, it would be nice if the Resync tool could correct missing DKIM records. The propogation of DKIM record from mail_domain to dns_rr is currently a feature of the user interface, and neither resyncing dns nor resyncing ma...Related to #6025, it would be nice if the Resync tool could correct missing DKIM records. The propogation of DKIM record from mail_domain to dns_rr is currently a feature of the user interface, and neither resyncing dns nor resyncing mail domains will ensure that the DKIM record is setup in dns, you must edit each email domain in the ui (a pain with admin protection, where you must switch to the client, then edit, then switch back....).https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6013SSL ISPConfig Installer / Updater Code May Be Repetitive2021-02-18T15:12:16ZHj Ahmad Rasyid Hj IsmailSSL ISPConfig Installer / Updater Code May Be RepetitiveI have been revisiting ISPConfig installer_base.lib.php as well as install.php and update.php files and I think the code with regards to SSL may be repetitive and most of them, if not all, may be avoided if the SSL request for the server...I have been revisiting ISPConfig installer_base.lib.php as well as install.php and update.php files and I think the code with regards to SSL may be repetitive and most of them, if not all, may be avoided if the SSL request for the server and its services can be made before configure_postfix (include creation of smtpd.cert and smtpd.key) and configure_dovecot (include creation of dhparam file dh.pem).
Reading on dovecot, I think it is not necessary to use ssl-parameters.dat and convert it as dhparam file (dh.pem) even if it is meant for v2.2 as using it was only a mere suggestion to ease creating creating the same but using openssl to issue it should also work as well and pure-ftpd is using one that can be symlinked.
Since symlinks can be made to all of them whether by using self-signed or LE SSL certs or others, if it is possible to rearrange the priority in those files especially install.php and update.php, we may avoid such a repetition and may be make the install / update process a little bit faster?
A thought to be discussed further before any decision could be made.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6006Add config file changes to UI2021-01-09T14:37:56ZTony GAdd config file changes to UIThis is another feature enhancement suggestion that might be easier than others. I'm hoping it can just be added to the pile of such suggestions for consideration.
The feature for adding Apache Directives can be used as a model for /etc...This is another feature enhancement suggestion that might be easier than others. I'm hoping it can just be added to the pile of such suggestions for consideration.
The feature for adding Apache Directives can be used as a model for /etc/postfix/main.cf and /etc/dovecot/dovecot.conf. In System Config>Mail provide a textarea for Additional Postfix Settings, and another for Additional Dovecot Settings. On Save the resulting config files will have a distinctive #! comment to separate these sections from existing settings. Example:
```
#! Set by ISPConfig Template: ...
smtp_helo_timeout = 15s
smtp_mail_timeout = 15s
smtp_tls_CApath=/etc/ssl/certs
smtp_tls_exclude_ciphers = RC4, aNULL
smtp_tls_protocols = !SSLv2,!SSLv3
smtp_tls_security_level = may
#! ISPConfig Overrides
smtp_mail_timeout = 30s
smtpd_tls_loglevel = 1
smtp_tls_security_level = dane
```
On Save, scan for `^#! ISPConfig Overrides$`, remove anything below it, and insert the new content.
For consistency that pattern can be used for Postfix and Dovecot, but for Dovecot it can be made more elegant: In the tpl config, add the single line `!include conf.d/93-ispconfig.conf` and then create that file. Just replace that file with the UI textarea. At some point if Postfix supports an `include` directive then the same mechanism can be used.
Rather than using postconf for update, for this mechanism just reload Postfix whenever the related textarea changes. An admin using multi-line settings and comments is more free to write the config as they please, for better or worse.
ISPConfig itself could use this same mechanism, where defaults set by install/update are in the config file under comment `#! Set by ISPConfig Template`, updates made through the UI or API are echoed under that with comment `#! Set in ISPConfig` and then under that the manual overrides can follow. This would allow the admin to easily see only fields that are defined with ISPConfig, rather than using postconf or doveconf statements which return all possible settings.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6005New feature to create a new tpl and tpl-custom folder?2021-01-20T18:16:14ZHj Ahmad Rasyid Hj IsmailNew feature to create a new tpl and tpl-custom folder?https://www.howtoforge.com/community/threads/new-feature-to-create-a-new-tpl-and-tpl-custom-folder.86053/
This is a mere suggestion which I think could be useful to all users.
What do you all think if ISPConfig 3.2 /tpl/ folder in inst...https://www.howtoforge.com/community/threads/new-feature-to-create-a-new-tpl-and-tpl-custom-folder.86053/
This is a mere suggestion which I think could be useful to all users.
What do you all think if ISPConfig 3.2 /tpl/ folder in installation package is also copied to the ISPConfig directory?
What I had early in my mind is /usr/local/ispconfig/server/conf/tpl/ or /usr/local/ispconfig/server/conf-tpl/. I don't know which one is preferred but I think it is best to copy latest tpl folder to ISPConfig folder for users' customization needs, if any.
I think this is quite easy to implement via ISPConfig installer so if there is any need to customize any of its files, one can copy and move it to /conf-custom/install/ folder, almost like the /conf/ folder itself.
Or may be introduce /usr/local/ispconfig/server/tpl/ and /usr/local/ispconfig/server/tpl-custom/ ?
Your comments, suggestions and feedback are most welcomed.https://git.ispconfig.org/ispconfig/ispconfig3/-/issues/6003tpl debian_postfix.conf.master includes hard-coded /etc/postfix2021-01-08T14:31:18ZTony Gtpl debian_postfix.conf.master includes hard-coded /etc/postfixThe {config_dir} placeholder is used in the debian_postfix.conf.master file, replaced with /etc/postfix in main.cf. There are a couple instances of the literal text `/etc/postfix` in the settings. I have no idea if this would affect any ...The {config_dir} placeholder is used in the debian_postfix.conf.master file, replaced with /etc/postfix in main.cf. There are a couple instances of the literal text `/etc/postfix` in the settings. I have no idea if this would affect any sites. But the file was made configurable for a reason, so I'm noting that this would be an error for a site that relies on a non-default config_dir.
If approved, this can be assigned to me.Tony GTony G