From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>, Stefan Sterz <s.sterz@proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pbs-devel] [PATCH proxmox-backup] email_notifications: make html template more valid
Date: Wed, 30 Nov 2022 17:09:23 +0100 [thread overview]
Message-ID: <378ec591-f9e8-6263-2aae-bfdcc3c1797d@proxmox.com> (raw)
In-Reply-To: <a94d0dcf-e1bc-a621-6a42-8b29f1552ee2@proxmox.com>
Am 30/11/2022 um 16:19 schrieb Stefan Sterz:
> ill add it if we go with the "keep the full html structure" option
> instead of the "<pre>-only" one 😄
If we change this I'd prefer a "full" HTML structure. Not much of a point in
over-optimization here, and _if_ some client renders this badly, and the user
checks the source of the mail and sees missing tags or the like, the technicality
of it being valid w3c; we highly probably still will be the one blamed first.
Anyhow, if there's no known (and not totally obscure) MUA that has issues with the
current form I'd avoid touching it.
prev parent reply other threads:[~2022-11-30 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 16:40 Stefan Sterz
2022-11-30 14:26 ` Dominik Csapak
2022-11-30 15:02 ` Stefan Sterz
2022-11-30 15:14 ` Dominik Csapak
2022-11-30 15:19 ` Stefan Sterz
2022-11-30 16:09 ` Thomas Lamprecht [this message]
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=378ec591-f9e8-6263-2aae-bfdcc3c1797d@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=d.csapak@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
--cc=s.sterz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox