From: Stoiko Ivanov <s.ivanov@proxmox.com>
To: pmg-devel@lists.proxmox.com
Subject: [pmg-devel] [PATCH pmg-api v2] rulesystem: limit linelength of disclaimer to 998 bytes
Date: Wed, 24 Nov 2021 22:00:48 +0100 [thread overview]
Message-ID: <20211124210048.78905-1-s.ivanov@proxmox.com> (raw)
As described in
http://www.postfix.org/postconf.5.html#smtp_line_length_limit
postfix splits lines which are longer by inserting <cr><lf><space> to
adhere with RFC 5322 (section 2.1.1):
https://datatracker.ietf.org/doc/html/rfc5322#section-2.1.1
(or actually section 4.5.3.1.6. where characters are translated to
octets)
If a longer line is part of the disclaimer pmg-smtp-filter adds it
without this modification, which breaks DKIM signatures (since the
body is modified by postfix after the body hash is computed)
regular-expression matching is used instead of length(), because the
limit is on line-length (and a disclaimer can contain multiple lines)
reported in our community forum:
https://forum.proxmox.com/threads/.97919/
Signed-off-by: Stoiko Ivanov <s.ivanov@proxmox.com>
---
v2->v1:
* incorporated Thomas' feedback - huge thanks!
* replaced the 2/3 occurences of encode('UTF-8',...) by a temporary varialbe
* read up quite a bit on the magic world of encoding)
* verified that the encoded value is indeed the one we want to compare
against
src/PMG/RuleDB/Disclaimer.pm | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/src/PMG/RuleDB/Disclaimer.pm b/src/PMG/RuleDB/Disclaimer.pm
index 1b1accf..d3003b2 100644
--- a/src/PMG/RuleDB/Disclaimer.pm
+++ b/src/PMG/RuleDB/Disclaimer.pm
@@ -84,12 +84,17 @@ sub save {
defined($self->{ogroup}) || die "undefined object attribute: ERROR";
defined($self->{value}) || die "undefined object attribute: ERROR";
+ my $value = encode('UTF-8', $self->{value});
+ if ($value =~ /^.{998,}$/m) {
+ die "too long line in disclaimer - breaks RFC 5322!\n";
+ }
+
if (defined ($self->{id})) {
# update
$ruledb->{dbh}->do(
"UPDATE Object SET Value = ? WHERE ID = ?",
- undef, encode('UTF-8', $self->{value}), $self->{id});
+ undef, $value, $self->{id});
} else {
# insert
@@ -98,7 +103,7 @@ sub save {
"INSERT INTO Object (Objectgroup_ID, ObjectType, Value) " .
"VALUES (?, ?, ?);");
- $sth->execute($self->ogroup, $self->otype, encode('UTF-8', $self->{value}));
+ $sth->execute($self->ogroup, $self->otype, $value);
$self->{id} = PMG::Utils::lastid($ruledb->{dbh}, 'object_id_seq');
}
--
2.30.2
next reply other threads:[~2021-11-24 21:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-24 21:00 Stoiko Ivanov [this message]
2021-11-25 8:28 ` [pmg-devel] applied: " Thomas Lamprecht
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=20211124210048.78905-1-s.ivanov@proxmox.com \
--to=s.ivanov@proxmox.com \
--cc=pmg-devel@lists.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