From: Dominik Csapak <d.csapak@proxmox.com>
To: Stoiko Ivanov <s.ivanov@proxmox.com>, pmg-devel@lists.proxmox.com
Subject: Re: [pmg-devel] [PATCH pmg-api 1/7] config: add admin-mail-from key
Date: Tue, 25 Feb 2025 11:29:45 +0100 [thread overview]
Message-ID: <74515557-408e-4b39-ba33-adfe47424c8f@proxmox.com> (raw)
In-Reply-To: <20250224232451.399803-2-s.ivanov@proxmox.com>
high level:
wouldn't it make sense to squash this patch with the ones where it's actually used?
IMHO it only makes sense to split such things when the changes are rather
large, but that's not the case here.
On 2/25/25 00:24, Stoiko Ivanov wrote:
> To be used as From header address for mails generated by the PMG
> stack. Currently this is hardcoded to postmaster in a few places.
>
> While PMG generates mails as the mail-system and postmaster is a
> good choice for such mails, users sometimes wish to customize the
> e-mail shown e.g. in the backup-notification and the daily admin
> report.
>
> The set value will be used in the header only, following the similar
> setting 'mailfrom' in the 'spamquar' setting.
> I decided against reusing the existing setting, as it's specifically
> tied to a category.
>
> PMG will as keep sending most mails with an empty envelope-from or
> with 'postmaster'.
>
> This is a first step towards DKIM signing those mails.
>
> Users will have to opt-in to it and use a email with domain-part to
> get DKIM signing.
>
> I decided against changing the current behavior of using 'postmaster'
> without domain, as this makes postfix complete the address with
> '@$myorigin.$mydomain'[0], and I've seen quite a few installations
> which set those settings in their main.cf.in templates.
>
> [0] https://www.postfix.org/postconf.5.html#internal_mail_filter_classes
>
> Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
> ---
> src/PMG/Config.pm | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/src/PMG/Config.pm b/src/PMG/Config.pm
> index 3170241..c583cc6 100644
> --- a/src/PMG/Config.pm
> +++ b/src/PMG/Config.pm
> @@ -140,6 +140,11 @@ EODESC
> enum => [qw(header envelope)],
> default => 'envelope',
> },
> + 'admin-mail-from' => {
> + description => "Text for 'From' header in admin mails and bounces.",
> + type => 'string',
should we try to restrict this a bit?
> + default => 'postmaster',> + },
> };
> }
>
> @@ -159,6 +164,7 @@ sub options {
> dkim_sign_all_mail => { optional => 1 },
> dkim_selector => { optional => 1 },
> 'dkim-use-domain' => { optional => 1 },
> + 'admin-mail-from' => { optional => 1 },
> };
> }
>
_______________________________________________
pmg-devel mailing list
pmg-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pmg-devel
next prev parent reply other threads:[~2025-02-25 10:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 23:24 [pmg-devel] [PATCH pmg-api 0/6] DKIM sign mails generated by PMG itself Stoiko Ivanov
2025-02-24 23:24 ` [pmg-devel] [PATCH pmg-api 1/7] config: add admin-mail-from key Stoiko Ivanov
2025-02-25 10:29 ` Dominik Csapak [this message]
2025-02-24 23:24 ` [pmg-devel] [PATCH pmg-api 2/7] reports: use admin-mail-from as from header Stoiko Ivanov
2025-02-25 10:32 ` Dominik Csapak
2025-02-25 12:55 ` Stoiko Ivanov
2025-02-24 23:24 ` [pmg-devel] [PATCH pmg-api 3/7] smtp-engine: use admin-mail-from as from header for bounces Stoiko Ivanov
2025-02-25 9:53 ` Maximiliano Sandoval
2025-02-25 10:29 ` Stoiko Ivanov
2025-02-25 10:29 ` Dominik Csapak
2025-02-24 23:24 ` [pmg-devel] [PATCH pmg-api 4/7] ruledb: use admin-mail-from where sensible Stoiko Ivanov
2025-02-24 23:24 ` [pmg-devel] [PATCH pmg-api 5/7] dkim: signer: degrade missing domain in from header to info Stoiko Ivanov
2025-02-24 23:24 ` [pmg-devel] [PATCH pmg-api 6/7] reinject_local_mail: sign mails with DKIM based on header Stoiko Ivanov
2025-02-25 10:32 ` Maximiliano Sandoval
2025-02-25 10:47 ` Dominik Csapak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=74515557-408e-4b39-ba33-adfe47424c8f@proxmox.com \
--to=d.csapak@proxmox.com \
--cc=pmg-devel@lists.proxmox.com \
--cc=s.ivanov@proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.